[DRIVER] Z-Wave Universal Smoke/CO Detector (ZCombo)

⚙️ Custom Apps and Drivers Custom Drivers
1

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 :heart: this post

Current Version: v1.0.0

:white_check_mark: 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

:ballot_box_with_check: 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.
Notifications Codes List 
ALARM_EVENTS = [
	0x06:"Alarm silenced",
	0x04:"Replacement required",
	0x05:"Replacement required, End-of-life",
	0x07:"Maintenance required, planned periodic inspection",
	0x08:"Maintenance required, dust in device",
	0x09:"Unknown event/state"
]
SYSTEM_EVENTS = [
	0x01:"System hardware failure",
	0x03:"System hardware failure (manufacturer proprietary)",
	0x02:"System software failure",
	0x04:"System software failure (manufacturer proprietary)",
	0x06:"Tampering, product cover removed",
	0x07:"Emergency shutoff",
	0x09:"Digital input high state",
	0x0A:"Digital input low state",
	0x0B:"Digital input open",
	0xFE:"Unknown event/state"
]

Example of Warning Events
(this was for testing only, these types of alerts wont normally show up as warnings)

image
image749×140 3.41 KB

:lady_beetle: Reporting Issues :beetle:
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.

:eight_spoked_asterisk: Manual Download from GitHub
Direct Import URL: [zwave-smoke-co-detector]
Full Repository Link: https://github.com/jtp10181/Hubitat/tree/main/Drivers/generic/

:beer: :coffee: Donations: ---->>>> PayPal.Me <<<<----
:money_with_wings: Never required, always appreciated! :money_with_wings:

14 Likes
2

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?

IMG_0708
IMG_07082319×927 208 KB

IMG_0709
IMG_07092325×1380 355 KB

IMG_0710
IMG_07102732×650 211 KB

3

What is the wake up time listed in the data at the bottom of the device page?

Could try doing a configure then waking up up by pulling and reinstalling batteries.

4
  • zwWakeupInterval: 4200 (Same as other)

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?

5

Perhaps take it down and see if you can get it working correctly close to the hub, to eliminate range issue?

6

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.

1 Like
7

Hey Jeff,

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?

image
image1116×142 31.9 KB

image
image1385×700 39.5 KB

8

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.

9

got it... done... I think I had that setup before, but just re-joined all of them recently... thanks again!

10

Thanks for this driver. I replaced all my 2016 detectors today. I hope these new models report battery better.

1 Like
11

They definitely do, but seem to start chirping once they drop below 80%, which took around a year and a half with alkaline batteries.