FirstAlert New SMCO410 Smoke/CO detector

🛎️ Get Help Devices
1

Has anyone use one of First Alerts new SMCO410 Smoke/CO detectors with HE? (Amazon.com)

I have a pair of the ZCombo Gen2s but I just had another one of my Nest Protects age out. So it was time to replace it with another First Alert. This seems to be their new model.

It paired easily, but HE defaulted it to the "Generic Z-Wave DT Multilevel Sensor" instead of the "Generic Z-Wave Plus Smoke/CO Detector" that the Gen2's use. I switched it to that driver.

I haven't noticed any problems with it but wondered if anyone else had tried out this model yet?

2

I have two coming in tomorrow. But I'm going to hook them up to my Ring alarm. Then hopefully bring them into Hubitat. That's how all my window/door sensors work now. Think of it as a fail safe. My Ring never goes down and has cellular backup. :grin:

3

It looks like the smartthings community might be in the same boat. I managed to find a pull request to add this device to their existing FirstAlert driver. Seeing as how the previous version of the FirstAlert detectors use the built in Generic Smoke/CO driver, I'm guessing the HE staff would have to tackle that.

Just so I don't have to look it up again later, here's the z-wave alliance page on the product.

4

I have two sitting in front of me, and there is only one instruction: "Use the app to scan the barcode." That's... just so helpful. /s Google led me here, so fingers crossed!

5

Yeah, the documentation is a bit lacking and we don’t have a great driver yet. I’ll be posting anything i figure out here.

2 Likes
6

Looks like my driver is working? [DRIVER] Z-Wave Universal Smoke/CO Detector (ZCombo) - #40 by chowell . It just shows as unknown but that is harmless really.

If you switch the driver to “Device” and then press the get info command it should log the fingerprint. If you give me that I can get it added to my driver officially.

1 Like
7

here's the fingerprint

fingerprint mfr:"041B", prod:"0001", deviceId:"0410", inClusters:"0x5E,0x9F,0x55,0x85,0x59,0x8E,0x80,0x70,0x5A,0x7A,0x87,0x72,0x71,0x73,0x6C,0x86,0x84", controllerType: "ZWV"

1 Like
8

Other than the Unknown device message, this is the only error its throwing in the logs.

Unhandled zwaveEvent: IndicatorReport(value:null, indicatorCount:null, indicatorValues:[[indicatorId:80, propertyId:5, value:0]]) (ep 0)

For reference I'm on a C8-Pro that's up to date and using ZWaveJS.

9

That is a debug log, not an error. The indicator class is not used in this driver. The device might just be reporting that its LED is flashing or something. Once debug is turned off you wont see it and the driver just drops it.

3 Likes
10

Did you figure out how to get it into inclusion mode? The only thing I was able to find is "hold the test button for as long as 20 seconds until [some number of] chirps" to reset it.

11

I should have written that down. But Yes, I believe all I did was hold down the button for 20ish seconds. Then I started HE's Zwave inclusion after hearing the 3 chirps. I didn't do smart start. It took me a try or 2. I think First Alert was really counting on this only being used with a Ring system. Their general z-wave documentation is sorely lacking.

1 Like
12

SmartStart would be the easy way to go. Here are my tips I included with my custom SmartStart hub app. Just scan the code and power up the device.

13

They work great with Ring, setup was quick and easy and they work great with the Unofficial Ring Intergration! Best of both worlds.

14

Ok, that seems to have done it, and after the first check-in I was able to see more details about it. Turns out you don't have to do the full reset unless you're having issues or changing hubs or doing exclusion. The "hold until 2 chirps then start inclusion" point is sufficient. I wasn't even near the hub, I have enough relay devices, the hub picked it up pretty quick (C8, 2.4.2.119). So... one down, I have another that I'm going to mount to my 3D printer enclosure for early warning (Zigbee power outlet will power the printer as a fail-safe).