-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Multiple WLED instances and the ability to choose which effects on which instance (or multiple instances for the same effect. #23
Comments
Maybe in the longer term future - this adds an additional dimension to the plugin, from multiple segments to multiple segments on each device. The plugin is already fairly complex to configure to begin with, it will a fair bit of work to add in a way that doesn't make it complex. |
I would be fine with just being able to assign multiple WLED instances, to Octoprint. The different effects for each WLED instance wouldn't be an issue for most, I wouldn't think. |
Agreed that could be an interim solution, to connect to multiple WLED devices, but have the same effects on each. With this plugin there's a lot more care that has to go in, because it is an external device over the network. I will think about it. |
This feature would be cool, but personally I use Home Assistant and Node Red with Octoprint and WLED integrations, so for my secondary (or more) WLED devices I could use automations to set those and use this for the strip at my printer. |
Nice that I am not the only one thinking of this. |
you can youse the SYNC feature of WLED in the App to Sync them up. No need to adjust the plugin |
I have the same request, sending via the plugin to multiple devices. |
Please add the ability to select multiple WLED instances, and for each effect, which instance you want it to display on.
I have numerous WLED lights throughout the house. I'd like to be able to set a print status/progress alert on multiple lights in order to see the status from anywhere.
The text was updated successfully, but these errors were encountered: