Closed samwiseg0 closed 2 years ago
Untested, but going by code analysis I think I have the problem fixed.
You should be able to switch to the 'Development' Release channel and find 0.7.3dev0
, hopefully that works.
Thanks for putting that out so fast but unfortunately that did not solve the problem.
I'll have to give it a proper look and test at some point then. Might take a while, there's a lot on the list
I'll have to give it a proper look and test at some point then. Might take a while, there's a lot on the list
No worries. I have a workaround. Disabling the on/off fade works.
I think this should be fixed with 0.8.0. I can't reproduce it anymore, following adjustments to the way some of this stuff was handled.
Description of the bug
I recently changed the wat my lights were being powered. They are now on their own power supply. Given that, I wanted to have them turn off when the printer is shutdown. I have another plugin issue the off @ command before shutting off the printer. This seems to be successful as the UI shows that the lights are powered off yet they still remain in an on state running the disconnect effect. I suspect this has to do with the fact that the printer goes into a disconnect state before the lights have had a chance to turn off or that effect is overriding the off command.
Edit: I had a thought that the fade effect was getting in the way. It seems this is the case. If I disable the fade effect for on/off the lights work correctly.
Steps to reproduce
@WS_LIGHTSOFF
commandWhat did you expect to happen
I expect when asking the lights to power off that they remain in an off state even if the printer state changes.
Logs and screenshots
octoprint-logs.zip
Version of plugin and OctoPrint
WS281x LED Status (0.7.2) Octoprint 1.6.0
(If applicable) Browser version & browser error console
N/A
Additional context
N/A