[OH5] How to recognize new Zigbee siren/alarm device

Hello,

Not sure where this topic would better fit - here, or under Hardware, or somewhere else. Please move it as needed :slight_smile:

I want to add a Zigbee alarm/siren to my small network. I bought the NEO NAS-AB02B siren which is advertised as Zigbee 3.0, Tuya, ZHA compatible. It runs on USB power and can be fitted with 2 Lithium batteries type CR123A as backup.

It has joined the network, but its status in openHAB is Offline, “HANDLER_INITIALIZING_ERROR, No supported clusters found”.

The Thing identifies the vendor as “_TZE204_t1blo2bj” and the model as “TS0601”. It is mains powered, so its logical type is Router. But the device isn’t properly identified, so there are no channels visible, although it should have a few including the ability to select the tone.

Some google searches revealed that this is a spin-off of a generic Zigbee alarm that comes in several flavors, some being delivered with batteries and including a temperature and humidity sensors, others (like mine) not.

The seller (first link) states that compatibility with ZHA is possible through defining a custom quirk in HomeAssistant with the definition file on this link. Is there something similar to these quirks in openHAB?

Other similar requests for compatibility with possibly some more technical info:

https://github.com/Koenkk/zigbee2mqtt/issues/15718

I’d be happy to provide any additional info about the thing as needed (just tell me how to get the info, I’m still a noob).

My setup: openHAB 5 running in a Docker container on a Lenovo tiny computer with Ubuntu, SLZB-06M as coordinator on Ethernet/PoE, Zigbee binding working.

Many thanks in advance!

Answering myself - upon further reading through older discussions, the “quirks” approach in Home Assistant is apparently not possible, and not a priority to get implemented.

The Zigbee binding carries over the limitations of the Zigbee Java library, which follows the principle of implementing the strict Zigbee standard. That’s a fine approach, but it also means that the Zigbee binding cannot make use of cheap devices which do not fully conform to the Zigbee certification - and there are a LOT of them.

Most likely the only viable option to circumvent these limitations is to use zigbee2mqtt. It’s a bit more work, but avoids these issues altogether.

Off to spin up a mosquitto container…