Closed guigro closed 3 years ago
A duplicate of #113 & #13, yeah I have no idea how to fix this one. I still haven't been able to reproduce the issue here to try and fix it. It obviously does not affect all that many people, since I have 3 reports of it in like 8 months & over 780 instances in the last month.
The latest theory we were able to come up with was that there was a resource being inherited by the sub process the plugin uses to run the LED strip & effects etc.
There are two current workarounds, not necessary to restart OctoPrint:
I will look into it again - but I can't guarantee I'll be able to find much. It could be printer/hardware specific, but there is no pattern with the people that have this issue. I spent ages looking through documentation and code, to find nothing of much use...
Alright you got it, the second tip (the request exclusive) make it work perfectly !
Sorry for the duplicate, and thanks for the amazing work !
Description of the bug
I use the TP Link SmartPlug plugin to shut down the printer on idle and put it back on when I upload a file. When it's powered off and I try to power it on, Octoprint can't connect to the printer again, until I restart Octoprint.
I guess it's the same if I have Octoprint running and then power off manually the printer, the power it back on.
For info : Pi running is a 4, and the printer is a Prusa MK3S.
Steps to reproduce
What did you expect to happen
I expect the printer to go back on and Octoprint to be able to reconnect to it :)
Logs and screenshots plugin_ws281x_led_status_debug.log :
octoprint.log :
Version of plugin and OctoPrint
Plugin 0.7.2 Octoprint : 1.5.3
(If applicable) Browser version & browser error console
Not applicable
Additional context
I made the same kind of feedback to the TPLinkSmartPlug plugin creator on his Github