Closed Rosen01 closed 2 years ago
The problem is likely caused by the following response from the device -:
DiscoverAttributesResponse [Color Control: C211/1 -> 0000/1, cluster=0300, TID=9E, discoveryComplete=true, attributeInformation=[AttributeInformation [dataType=UNSIGNED_16_BIT_INTEGER, identifier=65533]]]
Here the device lists the attributes it supports, and it doesn't include the required info for the channels you're looking for.
Thanks for the fast answer ! If I've correctly anderstood, there is a problem in the response of the capabilities by the controller/lamp. It's a RGB+CCT controller, so I know it's possible to control the cold/warm white leds. Is there a way we can force the creation of this "color temperature" channel ? (ex. by creating XML thing file)
The device is incorrectly reporting what attributes is supports, and this causes the binding not to support this channel.
I've changed the way the binding works now so that it doesn't ask the device what attributes it supports - it just tries to read the attribute. This should work for most devices.
Outline
The channel to control the color temperature (cold/warm white) is not created.
The color channel is working well.
Info on the device from Zigbee2MQTT.
Configuration
OpenHAB: 3.2.0 Coordinator: Ember Coordinator (Elelabs Zigbee adapter ELR023 Firmware 6.10.3.0) Hardware: Raspberry pi 3 B
Logs
openhab.log A4C138A4B750E0DC.zip