Picked up a few of these for $6/each (like a lot of folks I see). They work great! However, I see in the past others have had issues with the battery status not reporting but it was fixed in a later version of HA, 2022.2 I think.
I just installed a bunch, I’m on current 2023.2.4 with ZHA on a ConbeeII, and mine aren’t reporting battery status. Is there a parameter I need to flip or something?
It probably needs a “quirk”, but should try to upgrade the ConBee firmware before doing anything else.
Zigbee devices that do not only use standard configuration and parameters (default ZCL clusters and attributes) but instead also implement custom manufacturer clusters and attributes (also known as “quirks”) will need a custom handler/converter/parser/translator as Python script code in the upstream “ZHA Device Handlers” library repository to extend custom manufacturer device “quirk” support for specific non-standard ZCL clusters and attributes (which Zigbee gateway implementations that depends on zigpy and the ZHA Device Handlers library, like Home Assistant s ZHA integration, then can make use of).
https://github.com/zigpy/zha-device-handlers/#readme
If you can not code that Python script code yourself to write the needed custom handler/converter/parser/translator for adding that specific device to the “ZHA Device Handlers” repository/library then suggest submitting a “device support request” (with device signature and diagnostic information) as new issues → https://github.com/zigpy/zha-device-handlers/issues
Without a “device support request” as a new issue posted to the “ZHA Device Handlers” repository/library requesting support for an unsupported device or device feature with Device signature and Diagnostic information the ZHA integration developers will not even know about the device unless they by random chance happened to have bought it themselves.
The reason is why non-standard devices need a custom handler/converter/translator is explained in ZHA integration documentation here → https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling
Zigbee devices that use clusters and attributes that are standard in the official ZCL (Zigbee Cluster Library) do not need custom handlers/converters/translators as explained in the ZHA integration documentation here → https://www.home-assistant.io/integrations/zha#knowing-which-devices-are-supported
PS: Off-topic but FYI, this also works kind of similarly for Zigbee2MQTT which also requires a custom handlers/converters/parsers/translators for specific devices → https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
1 Like
Just an update. I think I need a quirk. Just went through the process of upgrading the firmware on the ConbeeII. (Doing that on my Windows laptop because I use zha on my HA setup was a bit unnerving having flashbacks of having to rebuild my entire 103 device zigbee network when a major change went haywire) Anyway… no joy. The firmware is current, everything is operational, but the battery status still reports “unknown”… not “unavailable” but “unknown”… so, it looks like a quirk issue.
The batteries in these type of sensors have in the past on my zwave sensors give me about 3 years so I’m just gunna wait for the Home Assistant development folks to get around to this 'cause I’m too old and lazy to learn how to write quirks. 
Anyway… thank you very much for your assistance.
I am trying to get this to work using ConBee II with deCONZ, but no luck. Several people have reported them working on ZHA and zigbee2mqtt.
Anyone tried these on deCONZ? Mine won’t even pair or show up at all.