So I get this debug message from my Smoke/CO sensor. Is it something that needs addressed?
Bumping. It doesn't seem to cause a problem. I just noticed it in the logs. Then again, my smoke/CO detectors aren't activated often than goodness.
What is the device and what driver is it using?
It also may be helpful to specify what hub platform version you're on, and (assuming this is a ZW device), if you're on ZIP or JS.
1 Like
It’s First Alert smoke/CO detector and zwave. It is a battery device. I’m on a C8pro with the 2.4.2.158. I have two of these detectors and both report the same debug message. I’m using the universal smoke/CO detector driver.
I’m using the out-of-the-box zip/js
1 Like
Its one or the other, need to know which. It is referring to the Zwave gateway service on the hub, with the Pro they now default to Zwave JS for new installs, but you can switch back and forth freely. You can determine which you are on by looking for the button on Zwave details page. If it says "Switch to Legacy Gateway" (or something like that) on the button you are on Zwave JS.
So you are using this driver? [DRIVER] Z-Wave Universal Smoke/CO Detector (ZCombo)
Please post the info from the Device Pager > Device Info > Device Details section
I need to at least see the ID, Type, and MFG codes.
Then I can possibly determine what it is trying to tell us.
It has a button “Switch to ZwaveJS”. I guess that means I’m on zip.
Ok that's the older original ZCOMBO unit. My driver was built on a more modern ZCOMBO-G unit which uses a newer more standardized messaging protocol.
Info here: Z-Wave JS Config DB Browser
Alarm 13 is smoke idle according to those docs.
I am not totally sure if my driver will even pick up a smoke alert from that thing. Have you tested it on that driver? If not I would suggest doing so to confirm if that driver even picks up the alarms.
Since it does not even have command class 0x5E I assume it is not even Zwave Plus, and thus you may need to use this built in driver in order for it to work correctly.
1 Like
It has worked in the past when cooking bacon but I think I’ve since updated the driver. I can’t leave well enough alone. I think I should go back to the old driver. Any guidance?
I updated both to the “ Generic Z-Wave Smoke/CO Detector”. Good enough?
Yes that should be the correct one which I stated above. You can watch the logs for any more errors. I would also run a test cycle on it when you can, with debug logging enabled on the driver, and make sure the hub picks it up.
I really appreciate your help. Thanks
