Device support request: Zooz ZEN55LR DC Signal Sensor (relay + smoke/CO, zwave-js-ui integration)

Development
,
1

Hi, I have a Zooz ZEN55LR DC Signal Sensor (also sold as « Smoke & CO Detector Bridge ») that’s fully recognized and interviewed in zwave-js-ui but shows as « not yet supported » in Gladys.

Device details:

  • Manufacturer: Zooz
  • Product: DC Signal Sensor
  • Product code: ZEN55LR
  • Device ID (from zwave-js-ui): 0x027a 0x0004-0x0110
  • Firmware: v1.50.0, SDK v7.18.8
  • Security: S2 Authenticated, fully paired
  • Z-Wave+ certified, standard Z-Wave protocol (not using Long Range mode in my setup)

What the device does:
It’s a multi-endpoint device with three functions on one node:

  1. A relay/binary switch output (for controlling lights, sirens, etc.)
  2. Smoke alarm detection, reported via Notification Command Class
  3. CO alarm detection, also via Notification Command Class

Configuration parameter 8 (« Enabled Features ») is set to [4] « Relay, smoke & CO sensor » so all three are active and reporting.

Current status:
zwave-js-ui shows the device fully interviewed with all endpoints populated and reporting correctly. Gladys connects to the same MQTT broker and topic prefix and sees the device, but flags it « not yet supported » with no option to expose any of its features, only a generic Migrate option that doesn’t map it to a usable device class.

Happy to provide the JSON export from zwave-js-ui’s « Export json » function, MQTT topic dumps, or anything else useful. Let me know what would help.

2

Welcome to the forum @itsalljustaride!

@Sescandell what information would you need to add these features?

3

Hello,

I need the Debug Info section from the zwavejs UI device here:

image
image2514×855 112 KB

And while you’re at it, since you say you see the « Migrate » button, we’ll need to move to the community version of the zwave integration:

image
image1591×1178 234 KB

That’s where developments are happening now