Colin Keenan

Thank you so much for your reply. I think I will try out your image first and if I run into issues try the dietpi route. Do I have to...

Thank you so much for your help. I ran into one issue with the image so far. It seems, at least with the M2 Zero image, that the OctoPrint service...

Update: I enabled UART 3 and soldered the pins like the ZeroW and it is working well now in the back of the Einsy board. Only issue now is it...

This is in the config.yaml: ``` server: commands: serverRestartCommand: sudo service octoprint restart systemRestartCommand: sudo shutdown -r now systemShutdownCommand: sudo shutdown -h now ``` And for the sudoers.d: ``` root@Prusa-OctoPi-M2Zero:/#...

``` GNU nano 3.2 sudoers # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of #...

``` root@Prusa-OctoPi-M2Zero:~# ls -l /etc/sudoers -r--r----- 1 root root 669 Apr 12 23:11 /etc/sudoers ``` ``` pi@Prusa-OctoPi-M2Zero:~$ ls -l /etc/sudoers.d total 12 -rw-rw-r-- 1 root root 59 Dec 27 10:26...

Okay, so what can I do to fix? Also sorry I just started another print, 24hr this time 🤣. I forgot we still had to troubleshoot this.

On which files? The octoprint-service and octoprint-shutdown?

OK it is working now with one minor modification. Inside OctoPrint the command has to be `sudo systemctl restart octoprint.service` instead of `sudo service octoprint restart` since you gave permissions...

I am having this issue as well. I am trying to autostart an instance of node red. It seems to be acquiring the wake-lock properly, but then says 0 sessions....