I just purchased the device off eBay. Once pairing it displayed as “_TZE200_t1blo2bj”. Was able to pair the device but I get 0 entities found and I am clueless as how to proceeded.
`
I’ve also just purchased one of these devices, Once paired in HA using ZHA it is recognized as “TS0601
by _TZE200_t1blo2bj”, but no entities available, I removed it and paired again, no changes, I’ve read multiple threads regarding a similar device (_TZE200_d0yu2xgi) but I was unable to follow what processes were followed to get of the entities working, especially the siren switch, which is the one I am interested in, if someone can share what steps can be followed to use custom quirks and test and the similar device can also use the same custom quirk it would be great, I am lost on what options i can try.
No i think neo just monkeyed with the ID, it seems they have done it in the past and a new quirk needs to be made but i have no idea how to do it myself or apply it.
Just checked in version 2022.2 and still no entities to control “TS0601
by _TZE200_t1blo2bj”, there are 2 disabled entities for diagnostics but no entities to control, also tested with Zigbee Home Automation: Warning device warn service, using multiple parameters and no luck on triggering the device.
I am not sure how to test custom zha quirks but will keep trying.
It seems the TS0601 by _TZE200_t1blo2bj is the cheaper Tuya siren without temp and humidity sensors. Mine was sold wrongly described as a 3-in-1 sensor. This is supported under zigbee2mq. See this thread: https://giters.com/Koenkk/zigbee2mqtt/issues/10348
I have setup my environment for testing new zha quirk, but currently do not know how to port this from zigbee2mqtt to zha.
Tried my hand at changing the _TZE200_d0yu2xgi quirk without luck (but didn’t really know what I was doing). Happy to test any quirk you may come up with.
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.
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.