-
-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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
palettes:null = complete failure to initialize #123506
Comments
Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) wled documentation |
That is an odd value to have, but... thanks for reporting! Will take a look |
Yep! It seems mostly a bug in WLED, but that otherwise doesn't completely block usage. |
The problem
This is the same as #96456 and #88429, which has been closed for staleness - what doesn't mean the issue is not relevant.
When WLED can't report palettes because it's running on a simpler device (Aircoookie/WLED#1974), the integration will completely fail to initialize, and keep trying every minute or so.
It should gracefully "downgrade" to an empty palette list and throw a log warning, given the WLED instance is completely usable otherwise. This suggestion was already made on the previous issue, which had great research by @sowbug (tagging him in case he still wants to follow up).
What version of Home Assistant Core has the issue?
core-2024.8.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
WLED
Link to integration documentation on our website
https://www.home-assistant.io/integrations/wled/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
Going to
http://my-wled-instance/json
shows the following:The text was updated successfully, but these errors were encountered: