NEO tuya Zigbee siren

I bought on a wim what is branded as a NEO coocam siren, but i cant get ti to work on HE i guess its non standard, could anyone help decode some of the messages these some to come quit frequently
catchall: 0104 EF00 01 01 0040 00 002A 01 00 0000 01 01 C2E7690200040000009A
catchall: 0104 EF00 01 01 0040 00 002A 01 00 0000 01 01 C2E6690200040000009B
catchall: 0104 EF00 01 01 0040 00 002A 01 00 0000 01 01 C2D0690200040000009C
catchall: 0104 0502 01 01 0040 00 002A 00 00 0000 01 01
catchall: 0104 0001 01 01 0040 00 002A 00 00 0000 01 01


1 Like


Hello @markus, I just received my own Tuya device as mentioned.

I have a couple of questions for you; Do I need to reflash it with Tasmota drivers? I will use it with HE, which is the platform I use.

You mention that you developed your own drivers for this device. Are they already available?
Thank you for your work and your help.

Welcome to the community!

Check this thread for more info re the Tuya Neo Coolcam NAS-AB02B0 ZigBee device.
The Zigbee - Tuya Alarm driver is available using Hubitat Package Manager or: driver

PS No flashing needed, Tasmota is for Wi-Fi devices not ZigBee.

Forgot to mention that the version I received is the WiFi version of this alarm device. Any comments?

@markus do I need to reflash (at least try to) this device? What happens if I am able to reflash it to Tasmota? Will it work? will it be recognized by Tasmota? I´ll appreciate your comments and suggestions.
Rodolfo Grun

Not sure what chip this device would use for the wifi version, if it’s ESP8266 based that could work. In terms of if it will work in Tasmota and which features in that case, there is no way of knowing without at the very least having photos of the interiors of the device. There’s probably a secondary MCU in there for the sound effects, if that one is controlled with the Tuya serial protocol and you can figure out what is actually sent there, it could be done. The “easiest” way to know what to send is to physically tap into the serial connection while still on the original firmware and then dump the transmitted data, when performing different operations like setting alarm type, for analysis.
None of this will be easy if you’re not used to this type of reverse-engineering of electronics.

Thanks, later in the day/weekend I will take a look at this device, physically, to better understand what it is all about.