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.
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?
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?
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.
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.
(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.
@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.
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.
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.