First Alert Zwave Plus Combo smoke/CO detector... Which driver?

I installed some of these, but they were not detected by Hubitat as I would have expected. I just want to make sure I am not missing something.

There appears to be an entry under the First Alert manufacturer:

But, when I tried to add a device via the Gen 2 & 3 driver, nothing was detected. (Gen 2 was a couple of years ago and these are new devices, so I reckon they have to be Gen 2 or 3.)

I did a manual Zwave inclusion, not picking a driver at all, and the device was added as a generic "Device." I looked for a better driver, but the device page does not list anything for First Alert devices.

image

I chose "Generic Zwave Plus Smoke/CO Detector" and now the devices are reporting battery and smoke status -- but no CO. OK, CO started showing up after a few more minutes, no problem.

Anyway... Is the generic driver the best one for this device?

I use the Generic Zwave Plus Smoke/CO Detector driver and, for me, it reports CO with no issues.

Controller Type ZWV
Data * deviceId: 3
  • deviceType: 1
  • firmware1Version: 7.0
  • firmwareVersion: 11.0
  • hardwareVersion: 2
  • inClusters: 0x5E,0x85,0x8E,0x59,0x55,0x86,0x72,0x5A,0x73,0x80,0x9F,0x71,0x84,0x70,0x6C
  • manufacturer: 312
  • MSR: 0138-0001-0003
  • protocolVersion: 6.07
  • zwNNUR: 12
  • zwNodeInfo: 53 9C 00 04 07 01 5E 85 5C 8E 59 55 86 72 5A 73 80 9F 71 84 70 6C 68 23
  • zwWakeupInterval: 4200|

Yes the ZCOMBO detector uses the generic z-wave driver.

It should’ve automatically assigned the correct driver, although I suppose it’s possible there’s a newer hardware revision out there that uses a different fingerprint and so isn’t identified correctly when pairing?

Couple weeks ago I paired two with a date code 2016, on a C8pro and it didn’t assign the correct driver.

Thanks for confirming that this is the right driver.

Strangely only 1 of my 3 detectors is reporting CO. They have all been up now as long as the first one was, which is still the only one reporting. So I thought there was just a delay until the first report, but perhaps something else is happening.

OK, this must be related. The unit that does report CO has this device info.

  • deviceId: 3
  • deviceType: 1
  • firmware1Version: 7.0
  • firmwareVersion: 11.0
  • hardwareVersion: 2
  • inClusters: 0x5E,0x85,0x8E,0x59,0x55,0x86,0x72,0x5A,0x73,0x80,0x9F,0x71,0x84,0x70,0x6C
  • manufacturer: 312
  • protocolVersion: 6.07

The devices that do not report CO have this info instead.

  • deviceId: 3
  • deviceType: 1
  • inClusters: 0x5E,0x85,0x8E,0x59,0x55,0x86,0x72,0x5A,0x73,0x80,0x9F,0x71,0x84,0x70,0x6C
  • manufacturer: 312

Do I need to re-add them?

After reassigning drivers, did you click the “configure” command on each device’s settings page? I’m not sure that should be required for a z-wave device like this, but it probably wouldn’t hurt.

This device doesn't have a Configure button, which I thought was weird. First time I have seen a device like that.

(The one that does report CO, and which has the different device data, has the same lack of Commands.)

But that makes me think, I could try going back to the totally generic Device driver and then picking the right driver again, maybe that will shake it loose. EDIT: Nope

OK one last edit: Now 2 of the 3 devices are showing CO, and the longer device data. And this new one that is reporting properly, I didn't mess with it at all, just left it alone once I picked the generic Zwave Plus smoke/CO driver. So my conclusion for now is that the devices will start to report CO when they darn well please.

1 Like

And the last, last update: detector #3 is now showing all the expected values. So, it looks like you just need to be patient after all.

@jtp10181 Jeff is one of the best developers in this community and extremely helpful with others. I use a lot of his drivers. This one is working great for me. His drivers usually have a configure button to do the very things you were trying to do. Because its a battery powered device, you might have to wake it up to sync or wait until it does on its own.

Give my driver a try on it, and once you run the configure you just need to pull the battery and re-insert it to force a wake up. That should get it all setup, refreshed and ready to go.

Then you can run a test on it to check the Smoke alert. This is possibly the device that does not send a CO Test alert for some reason so you would need to put it in a trash bag with some engine exhaust to test the CO alert, I think is what I have seen people do before.

1 Like

That would be me, lol.
"Pro" tip, use a dirty gasoline engine, like a lawn tractor, not a car.
edit: Might not be good for the sensor. Gave me a weird message, then straightened itself out.

Giving it a try, thanks!

I don't want to high jack this thread but will the Zcombo devices report ppm CO?

Not the one I have, it only reports if there is a smoke or CO alarm, no readings.

Same.

image

1 Like

Nope. Most CO detectors can’t report a specific CO level to a dwelling occupant. Some can.

AFAIK, the ZCOMBO uses a standard electrochemical sensor, same as most dumb detectors on the market. The CO levels at which it will alarm are standardized, but it has no way to report a measured ppm concentration to you.

1 Like