Z-Wave Universal Smoke/CO Detector Driver, built for the First Alert ZCombo-G (aka ZCOMBO). Handles all Smoke, CO and System notifications with a warning tracker so you can setup alerts when that attribute gets updated for other status messages from the device.
If you are using this driver PLEASE like this post
Current Version: v1.0.0
Supported Products:
First Alert ZCombo-G (aka ZCOMBO), must be Z-Wave PLUS model
Should work with any other Z-wave battery powered Smoke or CO Device
Features List:
Supports all smoke / co standard z-wave alerts
Supports all other smoke, co, and system notifications, translates the codes to plain English and posts an event with the text for use in notifications.
Reporting Issues
Please use GitHub to report any issues so each one can have its own conversation and tracking. Please provide as much info as you can including model, firmware and the "configVals" data string. Issues · jtp10181/Hubitat · GitHub
Must PRESS CONFIGURE BUTTON and check all your parameters after changing to this driver.
I bought two of these (v2, zwave plus) fairly recently. One (loft) is reporting hourly, and the other (hallway) only every 7 days. Also, missing Z-Wave device info. Any idea what may be going on? Should I remove and re-pair to see if I can get a correct join?
Yeah, I’ve done that a received a configure log, but I can try it again. I’m guessing the data is missing because it hasn’t reported in since the last hub reboot/Z-Wave radio power cycle?
Yes, on the z-wave details page that can be blank until the device reports in since the 2.3.9 platform update.
Next thing I would try is as you suggested, exclude, factory reset, then pair again.
The 4200 wake up interval is normal, according to my notes in the code the device actually refuses to take any other values so it should be waking up every 4200 seconds. My driver asks for a battery % every wakeup.
I'm getting a lot of data in my logs from my ZCOMBO's with your driver... I have them set to only report error level in the preferences, but I'm getting debug data... Any ideas?
Its a bug in the version of the logging code in this driver. Error level does not work correctly and defaults to debug. Set it to Warn and it will work.
I’m on a mission to figure out whether the 1044817 Wireless Smoke & Carbon Monoxide Alarm (ZCOMBOA) plays nicely with Jeff’s Z-Wave driver. The catch? Nowhere does it clearly state if it’s using Z-Wave Plus, and I’d rather not roll the dice on this one.
I can grab it from a local hardware chain (Lowe’s-owned) or Amazon, but neither they nor First Alert seem keen on sharing this crucial detail. If anyone can confirm whether this model works with Jeff’s driver, please let me know—I’d really appreciate it!
Looking for Insights on First Alert ZCOMBOA Smoke & CO Detectors
I'm considering upgrading my current Kidde combination Smoke and CO detectors, as they are approaching the 10-year mark, and I'm looking at the First Alert ZCOMBOA as a potential replacement. Before making the switch, I’d really appreciate hearing from those who have experience with this device.
Specifically, I’m interested in:
Ease of pairing – How seamless is the setup process, especially with Hubitat?
False alarms – Have you encountered any unexpected or nuisance alerts?
Battery life – How long do the batteries typically last in real-world use?
Integration with Hubitat – How well does it report and function within the system?
Any insights, experiences, or recommendations would be greatly appreciated. Thanks in advance!
Gave me 3 beeps and then 4 beeps (CO) at the detector.
Logs only gave results for Smoke.
Not sure what's up with that, but I haven't looked at this for a long time.
I think it might be a weakness.
I recall, far back in the sands of time, using a plastic bag filled with lawn mower exhaust gas to test it, and it worked.
Rules ran: Pushover notifications. 1 hours lockout for stuff like water shutoff valves. Ecolink chime/siren worked: 3 beeps for smoke, as in the logs.
I think I recall maybe a minor issue getting it paired.
Battery life has been good. Don't know duration, but I'm not complaining.
NO false alarms. This is for the one I have in the garage. I've had spider problems with hardwired PE detectors in the past. There is firewood in the garage and plenty of spiders.