Skip to content
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

Closed
chris-1243 opened this issue Dec 13, 2024 · 8 comments
Closed

Color_mode wrongly reported by some light #25193

chris-1243 opened this issue Dec 13, 2024 · 8 comments
Labels
problem Something isn't working

Comments

@chris-1243
Copy link

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

@chris-1243 chris-1243 added the problem Something isn't working label Dec 13, 2024
@Koenkk
Copy link
Owner

Koenkk commented Dec 15, 2024

I initially understood the issue wrong, could you provide the debug log when it goes to color_mode: xy?

@chris-1243
Copy link
Author

chris-1243 commented Dec 15, 2024

You should have some data in my last debug log. It happens right after the pairing.

The ieee address of the device is 0x9c69370000cbca15, Innr E14 dimmable + color temp

Let me know if you need more...

An other log right after pairing on 1.42.0-dev commit: e234f42e1f7c63115664010e2f497c230d850366

log (1).txt

@alexsotoaguilera
Copy link

alexsotoaguilera commented Dec 16, 2024

I have the same issue with other device: #24963

@Koenkk
Copy link
Owner

Koenkk commented Dec 17, 2024

It happens right after the pairing.

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?

@chris-1243
Copy link
Author

After the pairing. When you set a color_temp value, the error is not present anymore

@alexsotoaguilera
Copy link

I changed color_temp and the device stops to report XY.

Thanks chris-1243

@Koenkk
Copy link
Owner

Koenkk commented Dec 21, 2024

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

@coradia
Copy link

coradia commented Jan 16, 2025

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
Coordinator type: EmberZNet
Coordinator revision: 8.0.2 [GA]
Coordinator IEEE Address: 0x9035eafffeb85676
Frontend version: 0.9.4
zigbee-herdsman-converters version: 21.12.0
zigbee-herdsman version: 3.2.1

home-assistant_mqtt_2025-01-16T02-53-52.941Z.log
z2mqtt.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants