None (<class 'custom_components.tuya_local.light.TuyaLocalLight'>) sets invalid supported color modes {<ColorMode.HS: 'hs'>, <ColorMode.BRIGHTNESS: 'brightness'>}

[robinhood-code]

Describe the bug

None (<class 'custom_components.tuya_local.light.TuyaLocalLight'>) sets invalid supported color modes {<ColorMode.HS: 'hs'>, <ColorMode.BRIGHTNESS: 'brightness'>}, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/make-all/tuya-local/issues

To Reproduce

This error message only appears when HA is restarted.

Please check if there are messages from Tuya Local in the Home
Assistant log (Settings / System / Logs), and include those too.

Logger: homeassistant.components.light
Source: components/light/init.py:1165
integration: Light (documentation, issues)
First occurred: 10:48:19 AM (1 occurrences)
Last logged: 10:48:19 AM

None (<class 'custom_components.tuya_local.light.TuyaLocalLight'>) sets invalid supported color modes {<ColorMode.HS: 'hs'>, <ColorMode.BRIGHTNESS: 'brightness'>}, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/make-all/tuya-local/issues

[make-all]

You did not include any details about what device this report is about, but from a quick scan, it seems it must be hdmi_sync_light, as that is the only one that incorrectly uses brightness mode together with other modes.

[robinhood-code]

My apology but that was all the info I could gather as there was no other info in the log that told me which device it was related to, but glad that you found the specific device that caused the issue.

I made your change to my local copy and I confirm the warning message is now gone. Thanks for the quick action on this.