search

cp2004 / OctoPrint-WS281x_LED_Status

Add some RGB LEDs to your printer for a quick status update!
https://plugins.octoprint.org/plugins/ws281x_led_status
GNU Affero General Public License v3.0
112 stars 27 forks source link

Resetting success/failure states back to idle #159

Closed kdegraaf closed 3 years ago

kdegraaf commented 3 years ago

Describe your problem

Hello,

First, thank you for your efforts on this plugin. It has worked well for me and added lots of value to my OctoPrint experience. :-)

Perhaps I've missed something, but is there a method of acknowledging a printer success/failure state and transitioning back to the idle state? That is, if I've collected a good print or cleaned up a failed one, I'd like to get rid of the green/red indication.

I'd be okay with doing this from the Web UI, but would really love some way to trigger that via the Physical Button plugin, as I've made a custom push-button controller.

Thanks!

Please confirm the following

Log files

No response

cp2004 commented 3 years ago

Perhaps I've missed something, but is there a method of acknowledging a printer success/failure state and transitioning back to the idle state? That is, if I've collected a good print or cleaned up a failed one, I'd like to get rid of the green/red indication.

Nothing missed there, it doesn't exist. The only thing that does exist is the 'return to idle' timer. Which could be slightly dodgy as I think there's some bugs with priority and the timer getting cancelled there.

cp2004 commented 3 years ago

When I get round to implementing #125 you may be able to do this from custom triggers in WS281x LED Status, and then you can setup physical button to use this.

But, that may be a fairly long way off. I have planned & done some of the work there but I'm not sure if it will make it into the next release or not. You'll notice when it does get updated, because I will be plastering this across the plugin's docs & release notes.

github-actions[bot] commented 3 years ago

This issue has been marked a stale because it has been open for 14 days with no activity. If there is no further activity in the next 7 days this issue will be closed.

github-actions[bot] commented 3 years ago

This issue has been closed as there was no activity for 21 days. If this issue is still relevant, please request a reopen or create a new issue.