After testing some of the possible solutions described in this post and some others without luck, I decided to try Zigbee2MQTT
They worked without any extra configuration, I was able to turn it on, off, change the melody … the volume.
Setting up Zigbee2MQTT was not as easy as ZHA but worth the try, also I have a Tuya Scene Switch 4 gangs, with ZHA it only recognized 4 actions (single click in each button), but in Z2MQTT Home Assistant had the full 12 actions (Single, Double, Hold in each button)
Good to know the z2m implementation works. I have a second zigbee stick arriving today and plan to run both zha and z2m side by side before deciding which to keep.
The siren alone is not enough to make me switch, but device support does seem better with z2m. On the other hand, ZHA has always “just worked” for me until now, but all my other stuff is pretty vanilla.
The ZHA devs were quick with an initial quirk to to test, unfortunately it didn’t work.
Not sure. Works in z2m here. Have you tried removing/re-adding? Some of the other devices I tested under Z2M (Aqara) didn’t seem to complete the interview completely.
Can’t say that’s been the case with the siren though, I’ve moved it back and forth between Z2M and ZHA at least a dozen time now.
I’m using the latest production (NOT edge) Z2M add-on under HA 2022.3:
I found the cause ! The problem was that I had an old setting in the docker that referred to a bad directory and even though I was updating Z2M, it was reading the database from the wrong location. I deleted this bad setting and it is now good.
With a little luck and many thanks to @javicalle this should be in ZHA soon. Not sure how long it takes for ZHA updates to work their way through to HA.
A pull request with the in integrated quirk version is pending merge.
I got the v3 of this sirens which happens to “pair” in ZHA but actually the sirens keeps blinking and not finishing the pairing. It just reports link to ZHA and ZHA just reports a switch entity. This was reported in Z2M here:
Currently considering buying this product but seems like the issues still haven’t been solved?
Also (not sure if related?) I see several people reporting on Ali that it doesn’t pair with Conbee 2? I have a “Sonoff ZigBee 3.0 USB Dongle Plus (CC2652P)” so am wondering if that would cause additional issues.
Unless there’s been a firmware update in the past few months, the “no sensors” version works in ZHA and Z2M with the Sonoff dongle.
The “with sensors” version was working at one point a few months ago, but now seems broken in ZHA after a VERY quick test. I might be doing something dumb, but I don’t have time now to debug (and doubt I will - it works fine under Z2M which is now my primary zigbee network).
My biggest issue was the device sometimes misses commands. The Z2M version of the above script (that I actually use) sends each command twice with a 50ms delay, which seems stable so far.
If if is the same device with exact same identifier and same there now is a quirk in ZHA Device Handlers and the device is not working even if try remove and pair it again then suggest submitting new bug report issues to both HA’s core and to ZHA Device Handlers:
Refer to that old closed feature request and merged pull request for a reference if it is the same device, however, if it is the same device but not the exact same identifier then need a feature request instead.
I just got the no sensor version the other day, I’m using it with Z2M and find it does miss the turn on command. I’m just using a simple script to set doorbell chime and duration and then triggering, what seems to have worked so far is putting a 1 second delay between setting the duration and triggering the switch. Will report back if this breaks over the longer term.
Did anyone manage to get it working. I can see on github some people have had success witha custom quirk, but i can’t seem to follow their steps being a n00b. If someone can dumb it down for me?
It is now 2023 and I have the same problem as in this post. Was this ever resolved.
I update the cluster attributes to change the melody and get a green tick. But the melody on the device does not change.
Is there something else I need to do??
The problem was that I had an old setting in the docker that referred to a bad directory and even though I was updating Z2M, it was reading the database from the wrong location. I deleted this bad setting and it is now good.