[DRIVER] Zooz ZEN55 DC Sensor (for Smoke/CO Alarms)

[jeff.lilliquist]

@user139

may sound like a stupid question, but how can I test this without smoking my house and breaking my earbuds?
from what I have read, the smoke detector send 9Vdc on the red wire when smoke is found.
it does not appear safe to connect the negative terminal of a 9vdc power supply to the neutral of the 120Vac (white wire) and the positive side of the 9Vdc to the red wire...

I mean, 120v neutral and negative side of 9Vdc should be the same: nothing. but something I found that theoretical can be, a time, different than reality... lol

Not sure what you are doing but AC and DC are NEVER used together without a power inverter !!

[jeff.lilliquist]

@user139

and bumb question, I see hubitat read smoke and Co2 as clear (or something like that) how can it diferentiate smoke from CO2? is it a different signal that is sent on the red wire and the zen55 can read both?

Yes, different signal and the alarms have different noises as well. The sound for CO and not the same as for smoke, It is defined is some standard but I do not know where I can reference them.

[jeff.lilliquist]

@jtp10181

Yes, it can tell the difference when Smoke detector is triggered or CO detector is triggered. We tested with Kiddie and First Alert 2 in 1 smoke/co sensors.

Both of them are using 9 volts; however, if you would connect this to oscilloscope than you would see the difference in the voltage waveform. The smoke has a different voltage waveform than CO voltage waveform.

The audio is different too. When the interlink sends the signal the audio will be different as well.

[jeff.lilliquist]

@hydro311

As far as the last one-in-the-chain thing... More than anything, I think it's just a box-fill issue... Outside of the last box, the upstream j-boxes are commonly pretty stuffed with junctioning connections, so the last one is typically the j-box with the most open space to comfortably fit in the Zen55. That was true in my case anyway. Aside from that, I don't see a reason why it'd matter where you put it.

I had no problem fitting the Zen55 in a middle box. They appear to have use standard metal ceiling fan boxes which are actually bigger than a typical switch/receptacle box.

[jeff.lilliquist]

@rlithgow1

Hmmm.... This wouldn't work with Nest Protects sadly. They don't have the interconnect wire since they use wifi and bluetooth to connect with eachother. They have hot and neutral only Guess I'm sticking to my ecolink firefighters...

Which is WHY I removed the one I tried. Outdated junk! Just use the interlink!

[jeff.lilliquist]

@jtp10181

@ArgyrisAnastas

%device% Smoke: %smoke% Carbon: %carbonMonoxide% %date% %time%

You can only use certain key words with the % replacement.

This this instead, the %text% should get the "Description" as shown in the event log.
%device% %text% %date% %time%

Oh bother! Now come the programming! Oh well, at least it should work when I make the App. I really want it to only turn on all the lights and flash others if detected. No text, etc. Between the noises and lights it should be enough. It also allows a safe exit since most fires occur at night.

[rlithgow1]

I use the ecolinks. Very reliable. I love the Nest protects.

[velvetfoot]

A few years ago I bought the BRK relay, link below, that I never installed, yet, lol.

The advantage of this sensor is that it can distinguish between CO and Smoke?

What else can this sensor do? Can it measure the voltage on a 12vdc battery, that might go up to 14v or so?

Even though I've actually purchased it, I haven't done anything with it yet.

RM4 - Relay Module for Smoke and "Smart Interconnect" CO Alarms | BRK

[jtp10181]

UPDATE ZEN55

I posted a minor update to GitHub to fix issues with the fingerprint, so now the driver should properly match to supported devices when they are paired. Did not increase the version since it mostly benefits new installs but if you want to update anyway just run a repair in HPM.

[dyshuk]

They only suggest last one in line to give you most space to install

[velvetfoot]

While I like my BRK relay setup, it doesn't differentiate between CO and Smoke.
I just ordered a ZEN55. I'll put it in one the boxes that used to hold a separate CO alarm.
Thanks for the driver.

[velvetfoot]

Installed. Does indeed differentiate between CO and Smoke, plus a relay that I don't use.
Awesome.

[scubamikejax904]

Not sure how feasible this is (I'm no programmer) but would it be possible to modify the driver to create child devices for Smoke and CO so you could differentiate them through HSM. I know that other companies do it (inovelli does it with their switches to control notifications that other apps can activate). Right now I'm using global variables rule machine and hsm (just setting it up so not sure how it'll actually work together just yet)

[jtp10181]

It would be possible yes, but not something I am really interested in doing.
What is the issue exactly? The smoke and CO alerts are two separate attributes so you can pick them separately in apps.

Are you trying to get a different notification in HSM based on which one alerts by using a different device name? This is an HSM issue/bug, creating child devices would just be a workaround. If HSM supported the %text% variable like RM does then you could use that. Or a way to include the attribute name in the alert would also work.

You could include just the smoke in the main panel and then add a custom alert for the CO, then you could customize the message for each one.

[function12]

Just installed one of these. Will we get any type of alert when the test button is pressed?

[jtp10181]

If the device is able to detect it, you should. The driver is setup to handle it per zwave specs. I have not actually connected mine to an alarm yet, still on my test bench.

[function12]

No change is status when I hit the button. I guess I will bring some canned smoke from work and test it.

[velvetfoot]

Worked for me when I hit test button:

[function12]

I see that now in events. Thanks!! It triggered smoke on mine.

[velvetfoot]

Mine are combos.