I was able to connect the device after some tries.
First with the Z-Stack 1.2 firmware, which didn’t recognize the device and barely managed to connect to it.
Then flashed the cc2531 to Z-Stack 3.0.x firmware since I found the device is Zigbee 3.0.
With Z3.0 I was able to connect the device, but it still doesn’t recognize the clusters properly as I can’t get a signal. The battery cluster doesn’t show any info and the detector cluster doesn’t update when I press the “test” button.
@BFonseca,
not sure if you got it all to work. As they are zigbee I got them to connect with my deConz Phoson. Both CO and smoke detectors connected nicely. No issues so far
I did not.
Meanwhile I changed to Zigbee2MQTT. It seems more stable and with more compatible devices.
At the moment there’s an issue with the Mosquitto Broker addon - version 5.1.1 has compatibility issues with Z2M but v5.1 works fine (here’s a workaround to install 5.1).
I had the Conbee II running on MQTT. With your comment I tried to using Zigbee HomeAutomation. Can’t get it to work yet
I guess there are many ways to Rome. I’m still struggling a bit on getting the CO and Smoke alarms to also connect to Telegram.
@nc1264
I’ve had a far less reliable experience with ZHA. It felt really clunky compared to Z2M.
Plus Z2M has a lot more compatible devices: https://zigbee.blakadder.com/
@nguedes
Yes, this sensor only reports true/false when a certain CO treshhold is met.
There’s no way of changing this as far as I know.