Sonoff Zigbee coordinator and Hue lights, color picker not shown

[Amonius (Daniel Dönigus)]

Hmm, I’ve got the same controller setup (Sonoff Zigbee coordinator, Zigbee.Ember-Binding), but different light. The color temperature works fine, but color doesn’t get initialized.

Is this really a solution? Do I have to get another bridge, change the color once and then the light works as desired? What about OpenHAB-restarts? I expect the light to fail again, right?

There is also this thread:

Issue with Sonoff Zigbee Bridge with Tasmota - controlling RGB strip through MQTT

Hi all, Am using OH2.5.10 and playing around with a Tasmota flashed Sonoff Zigbee Bridge. I have binded sensors, lights and switches to OH through MQTT and it works. I then just bought an RGB strip and an RGB lamp - and even if turning it on/off/dimming it works, I would like to set up my “Thing” in OH to be able to control the colors of the light as well However, I simply cannot find usuable examples of this anywhere? - it seems, that the tasmota-zigbee-mqtt bridge expects the color …

I don’t know if the solution could help for our setup (Zigbee-Binding without MQTT).

When I change from XY-Commands to Hue commands, this is the debug log:

2023-02-11 11:01:44.343 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:e8b9c7232b:04cd15fffee032b1
2023-02-11 11:01:44.345 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:e8b9c7232b:04cd15fffee032b1 in 14430 seconds
2023-02-11 11:01:44.348 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 04CD15FFFEE032B1: Channel zigbee:device:e8b9c7232b:04cd15fffee032b1:04CD15FFFEE032B1_1_color updated to 0,0,100
2023-02-11 11:01:44.348 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:e8b9c7232b:04cd15fffee032b1
2023-02-11 11:01:44.350 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 04CD15FFFEE032B1: Updating ZigBee channel state zigbee:device:e8b9c7232b:04cd15fffee032b1:04CD15FFFEE032B1_1_color to 0,0,100
2023-02-11 11:01:44.353 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:e8b9c7232b:04cd15fffee032b1
2023-02-11 11:01:44.355 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:e8b9c7232b:04cd15fffee032b1 in 14430 seconds
2023-02-11 11:01:44.359 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:e8b9c7232b:04cd15fffee032b1
2023-02-11 11:01:44.361 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:e8b9c7232b:04cd15fffee032b1
2023-02-11 11:01:44.362 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:e8b9c7232b:04cd15fffee032b1 in 14430 seconds
2023-02-11 11:01:44.365 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 04CD15FFFEE032B1: Channel zigbee:device:e8b9c7232b:04cd15fffee032b1:04CD15FFFEE032B1_1_color updated to UNDEF
2023-02-11 11:01:44.367 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 04CD15FFFEE032B1: Updating ZigBee channel state zigbee:device:e8b9c7232b:04cd15fffee032b1:04CD15FFFEE032B1_1_color to UNDEF
2023-02-11 11:01:44.369 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker reset for handler with thingUID=zigbee:device:e8b9c7232b:04cd15fffee032b1
2023-02-11 11:01:44.371 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker cancelled task for thingUID=zigbee:device:e8b9c7232b:04cd15fffee032b1
2023-02-11 11:01:44.374 [DEBUG] [.zigbee.handler.ZigBeeIsAliveTracker] - IsAlive Tracker scheduled task for thingUID=zigbee:device:e8b9c7232b:04cd15fffee032b1 in 14430 seconds

I don’t know if

Updating ZigBee channel state zigbee:device:e8b9c7232b:04cd15fffee032b1:04CD15FFFEE032B1_1_color to 0,0,100

is the correct value, but seems more correct than UNDEF. Unfortunately it is changed to UNDEF immediately.