Closed brushmate closed 1 year ago
I just got feedback from Iluminize. According to them this is known behavior and smart home hubs should actively poll the state of the controller. Is there such a functionality in Zigbee2MQTT and can it be enabled for this controller?
I found the corresponding setting in the Zigbee2MQTT frontend. You can find it under Devices > Your device > Reporting. I have configured two reportings for this controller:
Endpoint : 1
Cluster : LevelCtrl
Attribute : currentLevel
Min rep interval : 1
max rep interval : 5
Min rep change : 0
Endpoint : 1
Cluster : OnOff
Attribute : onOff
Min rep interval : 1
max rep interval : 5
Min rep change : 0
I think I also found the related documentation of this feature: https://www.zigbee2mqtt.io/guide/usage/mqtt_topics_and_messages.html#zigbee2mqtt-bridge-request-device-configure-reporting
Since this is not a Zigbee2MQTT issue, I am closing it. I will try to convince the vendor to implement 'native reporting'.
What happened?
The Iluminize 511.012 ZigBee controller supports an external switch to control the state. Unfortunately these state changes do not show up in Zigbee2MQTT.
What did you expect to happen?
I would have expected to see the changes in Zigbee2MQTT / Home Assistant.
How to reproduce it (minimal and precise)
Setup the LED controller and attach an external switch. Press the switch and see that nothing is reported back to Zigbee2MQTT.
Zigbee2MQTT version
1.30.2
Adapter firmware version
20210708
Adapter
cod.m ZigBee CC2652P2 Raspberry Pi Module
Additional info
I found #2502 where someone reported a similar issue. @Koenkk asked to add an external converter for further debugging. I tried to adapt that, but then Zigbee2MQTT fails to start with the following stacktrace: