Closed trevor229 closed 3 years ago
It should be fixed in the upcoming version, I was aware of this issue. Since the connect comes before the plugin is started up, it can't play the effect. In future versions it should (a) not fail and (b) save the connect event so it can be used when the strip etc. is setup.
Awesome, thank you for the quick response and info.
Hey @trevor229, 0.7.0rc1 is out now for testing - there's a feedback ticket here for any comments on the release. Any feedback is appreciated.
0.7.0 has been released.
What do you need help with? I just set up octoprint 0.18.0 and when booting, the connecting effect plays as it should, however when octoprint auto-connects at bootup, the plugin remains in the connecting effect and does not switch to the idle effect. When I manually disconnect, it changes to the disconnected effect and then changes to the idle effect upon clicking connect manually.
I have tried with and without the PortLister plugin and
Request exclusive serial port access
The only error I see is in
octoprint.log
and it is this sectionLog files
Here are my log files:
plugin_ws281x_led_status_debug.log
octoprint.log
[x] I have read the troubleshooting guide found at https://github.com/cp2004/OctoPrint-WS281x_LED_Status/wiki/Troubleshooting-Guide