macksie
(Max Cederhage)
February 10, 2022, 10:53pm
1
Basically as in topic.
Have tried including a new Aqara EU power plug but cannot get it to report any measurements.
Controling the actual switch works.
And if I understand previous forum posts it seems like people have it working.
Anyone else experiencing the same.
Tried including it through the ZigBee coordinator
It iterates out six different sensors, power, current,voltage in different ways.
But all of them report “unknown”
Any advice on how to start is appreciated.
Thanks in advance
2 Likes
khvej8
(Khvej8)
February 12, 2022, 7:52am
2
You plug, which version is it. I have a number of them, all the old version using zigbee 1.2 and working perfectly.
There are some reports on the new Aqaba zigbee 3.0 devices, which need to be defined in ZHA. Try and look in the forum for Aqaba T1 devices. If your plug is a new version, that might be the problem.
Hedda
(Hedda)
February 17, 2022, 10:00am
3
There’s many different Aqara/Xiaomi plugs and not all have quirks or quirk fixes for all power metering.
ZHA Device Handlers “quirks” is needed when device don’t follow Zigbee Cluster Library specifications:
https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling
https://www.home-assistant.io/integrations/zha#reporting-issues
Search for your specific Zigbee ID here was there will probably already be an issue reported for it:
https://github.com/zigpy/zha-device-handlers
https://github.com/zigpy/zha-device-handlers/issues
PS: Zigbee2MQTT equivalent to zha-device-handlers/zha-quirks is called zigbee-herdsman-converters:
https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
https://github.com/Koenkk/zigbee-herdsman-converters
These parse/translate/convert non-standard messages to ZCL R6 or R7 (ZCL6/ZCL7) specifications:
https://zigbeealliance.org/wp-content/uploads/2019/12/07-5123-06-zigbee-cluster-library-specification.pdf
macksie
(Max Cederhage)
March 7, 2022, 10:50pm
4
Thanks @khvej8 and @Hedda , sorry for going silent.
There seems to be some bug or version conflict.
When downgrading Home Assistant, we got it working