You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Octoprint running on old laptop on Windows as a service
Printer connected via USB to Windows laptop with it's own swtich always on
Both elements connect to the same power strip with a Tasmota device
I'm already able to turn the printer on and connect to it when turning on the computer using your plugin.
What I want to do:
Being able to shutdown printer when I shutdown computer (either by power off button or Octoprint's web UI).
I've tried with the Disconnect / Autodisconnect options, but entered in a "bootloop" (Windows shutting down on startup) and Tasmota/Printer turning on & off constantly. I've managed to recover from that but I don't want to get into that again. Any pointers?
I should note that as the notebook has it's own battery I don't really care if the Tasmota device is turned off before the computer shuts down.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
I'd have to add shutdown event monitoring like I have in my TPLinkSmartplug plugin in order to get what you're after cleanly. A workaround for now might be using OctoPrint's event manager to send gcode triggers for the plugin to react to.
My setup:
I'm already able to turn the printer on and connect to it when turning on the computer using your plugin.
What I want to do:
Being able to shutdown printer when I shutdown computer (either by power off button or Octoprint's web UI).
I've tried with the Disconnect / Autodisconnect options, but entered in a "bootloop" (Windows shutting down on startup) and Tasmota/Printer turning on & off constantly. I've managed to recover from that but I don't want to get into that again. Any pointers?
I should note that as the notebook has it's own battery I don't really care if the Tasmota device is turned off before the computer shuts down.
Thanks in advance.
The text was updated successfully, but these errors were encountered: