-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Custom Palettes are not supported #1602
Comments
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
The issue still exists in the latest version. |
Problem/Motivation
Custom Palettes are not supported in this library. I discovered this was generating error messages in HomeAssistant if a WLED controller was set to a custom palette.
Expected behavior
The library should be able to discover custom palettes.
Actual behavior
Custom palettes are not detected.
Steps to reproduce
$ wled info
. And$ wled palettes
. The custom palettes will increase the "Palette count" ininfo
but the custom palettes will not be shown inpalettes
. Info does not includecustom_palette_count
from the "cpalcount" item ininfo
either.Proposed changes
Custom Palettes can be merged into the palette data returned by this library. See changes here bcpearce@6879987
This mostly solves the issues in HomeAssistant as well, however HomeAssistant will not update the selector entity after the initial setup.
The text was updated successfully, but these errors were encountered: