frenck/python-wled

Custom Palettes are not supported

Closed this issue · 3 comments

bcpearce commented

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

  1. Set up one or more custom palettes using WLED's web interface or mobile app. These are added as "~ Custom {i} ~" to the bottom of the palette list and have an ID of {255 -i}.
  2. Using CLI or HomeAssistant integration:
  • Using the CLI, run $ wled info. And $ wled palettes. The custom palettes will increase the "Palette count" in info but the custom palettes will not be shown in palettes. Info does not include custom_palette_count from the "cpalcount" item in info either.
  • Using HomeAssistant integration. Set up the integration in HomeAssistant, then change WLED to a custom palette in the WLED web interface or app. HomeAsssistant will generate errors for failing to find the palette and may fail to setup the "select" platform for choosing a palette entirely.
  1. Or, using Home Assistant,

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.

github-actions commented

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

bcpearce commented

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

The issue still exists in the latest version.

github-actions commented

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!