-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Color_mode wrongly reported by some light #25193
Comments
I initially understood the issue wrong, could you provide the debug log when it goes to |
You should have some data in my last debug log. It happens right after the pairing. The ieee address of the device is Let me know if you need more... An other log right after pairing on 1.42.0-dev commit: e234f42e1f7c63115664010e2f497c230d850366 |
I have the same issue with other device: #24963 |
Does it only happen right after pairing, or does it also happen after setting the color temp once? If yes, could you provide the log of that? |
After the pairing. When you set a |
I changed color_temp and the device stops to report XY. Thanks chris-1243 |
Found and fixed the issue! Changes will be available in the dev branch in a few hours from now. Note that the dev branch currently contains breaking changes, see #24198 |
I'm able to reproduce this issue with Tuya TS0502B in the form of LUUMR Smart LED GX53 lights. Zigbee2MQTT version: 2.0.0 commit: 060ae99 |
What happened?
Since last dev (1.42.0-dev commit: 1dde41f7eafe2ecfc55fa1d10a7963c211294043), it seems the color_mode is wrongly reported in HA. The color_mode is always "xy". This would be fine for an RGB light but not for a color temperature capable light only like INNR RB 249 T.
What did you expect to happen?
Light which is not RGB capable not to set
color_mode
"xy" but only "color_temp"How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.42.0-dev commit: 1dde41f
Adapter firmware version
20240710
Adapter
Sonoff Dongle-P
Setup
Z2M on Docker
Debug log
log.txt
home-assistant.log
The text was updated successfully, but these errors were encountered: