I am also curious if anyone has successfully paired a SMCO410 (2025) detector with a V2 hub, securely. My pairing attempts either spin indefinitely, or time-out. On rare attempts I got an unsecure pairing to happen, but it was unusable (sent no info to hub and eventually disconnected itself due to lack of responses).
I’m aware another firmware update (59.6) is coming out to fix the online/offline issue on V3 hubs. I may try pairing again after this update, but I’m guessing it won’t help the V2 issue. Is SmartThings engineering aware of the V2 pairing issue? Is there work happening to fix it?
Never could get it to work with V2, updated to V3 and now it works except I get constant online/offline notifications, but the alarm works / test works
1 Like
Try a Z-Wave repair.
1 Like
This worked! Thank you! what needs to be done from here to make the driver available in the dropdown?
FYI the device did register as Z-Wave Sensor. On the dropdown I see Z-Wave Sensor and Z-Wave Switch.
I applied your method and updated the driver from the edge driver builder portal, then applied it and it worked great.
Can you suggest how to modify the Z-Wave Smoke Alarm driver as “generic” so it shows on the dropdown for change driver on the app? The manufacturer and model are now 0000-… ?
@Andreas_Roedl is there a way to make your driver also as generic fingerprint to capture empty manufacturer and model? The device registers as Z-Wave Sensor and in the drop down I only see Z-Wave Sensor and Z-Wave Switch, it would be great if you can add your driver so it shows in the dropdown when manufacturer and model are not found.
I have SmartThings hub v2.
Have you deleted and added the device back again?
Read this FAQ. You should see the correct manufacturer/model with one of the other drivers and if it’s a different model, I can add it to my driver.
BTW: There’s absolutely no difference between my driver and the current stock driver now since the fingerprint for this device was added. I’ll double check tomorrow if there were any other changes in the meantime, though.
Edit: taking notes - please ignore.
- id: 041B/0001/0410
deviceLabel: First Alert Smoke & CO Alarm (SMCO410)
manufacturerId: 0x041B
productType: 0x0001
productId: 0x0410
deviceProfileName: smoke-co-battery
- id: 0138/0001/0410
deviceLabel: First Alert Smoke & CO Alarm (SMCO410)
manufacturerId: 0x0138
productType: 0x0001
productId: 0x0410
deviceProfileName: smoke-co-battery
2 Likes
We have first alert smoke and co2 alarms hardwired throughout the house.
I installed this…Zooz Z-Wave Plus Smoke and CO Detector Bridge ZEN55 800LR - The Smartest House into one of the boxes and works great.
Posting this just for reference.
@jelez , I assume you have a V2 hub. If that is the case, it seems that the pairing process doesn’t work properly for some reason, as others have stated previously. In a functional pairing process, Smartthings will look up the received fingerprint information and assign the matched driver for that fingerprint to the device.
It is the same with the drop down. It will only show drivers with similar fingerprints to the device fingerprint.
Now, because the pairing process doesn’t complete properly, it assigns a generic Z-wave driver as it never picked up the fingerprint information during pairing. That is why you are seeing 0000’s
The developer portal assigns a driver to your device without looking at fingerprints, for testing purposes. The driver is the exact stock driver that will be assigned if the pairing worked as long as you selected the correct capabilities. This is a fully functional driver and should not pose any problems.
To my knowledge, there is not much else you can do if the pairing never completes properly unless you create your own driver with 0000- fingerprint.
Folks, thank you so much for your prompt replies. My thinking was in along those lines:
@Andreas_Roedl already has a working driver on his channel that is customizable.
@Andreas_Roedl is there a way to add an id for the driver that is generic with the 000 as manufacturer and model?
I assume that if I have it installed then once the hub identifies the Smoke Alarm sensor as Z-Wave Sensor, I will be able to go to the app and in the drop down see your driver next to the other 2 generic drivers (Z-Wave Sensor, Z-Wave Switch), this way people like me can just pick it from there and replace the Z-Wave driver from the app rather than via the builder tools. What do you think?
The Z-Wave switch driver matches, because of this fingerprint:
zwaveThing :
- id: SmartThings/Z-WaveThing
deviceLabel: Z-Wave Device
deviceProfileName: switch-level
isJoinable: true
The Z-Wave sensor, because of this:
zwaveGeneric:
- id: "GenericSensorAlarm"
deviceLabel: Z-Wave Sensor
genericType: 0xA1 # GENERIC_TYPE_SENSOR_ALARM
deviceProfileName: generic-sensor
- id: "GenericSensorMultilevel"
deviceLabel: Z-Wave Sensor
genericType: 0x21 # GENERIC_TYPE_SENSOR_MULTILEVEL
deviceProfileName: generic-sensor
- id: "GenericSensorBinary"
deviceLabel: Z-Wave Sensor
genericType: 0x20 # GENERIC_TYPE_SENSOR_BINARY
deviceProfileName: generic-sensor
- id: "GenericSensorNotification"
deviceLabel: Z-Wave Sensor
genericType: 0x07 # GENERIC_TYPE_SENSOR_NOTIFICATION
deviceProfileName: generic-sensor
Extremely generic, but anyway… Give me 20 minutes…
Edit: done. Re-install the driver. For everyone else: do not use this driver!
You really should try to pair the device properly so that the manufacturer and model are detected correctly. The FAQ linked above explains why “0000” is shown and what you can do about it. If the device is already mounted on the ceiling, take it down and pair it right next to the hub (about 30 cm away).
Once the manufacturer and model are identified correctly, the stock driver should match, and we won’t need any awkward workarounds with generic fingerprints. After all, this is a safety-critical device.
1 Like
Works! Thank you!
”You really should try to pair the device properly so that the manufacturer and model are detected correctly.” - not working, tried everything. Called Samsung - they confirmed that the manufacturer needs to register it with smartthings and that is not done apparently.
The Samsung support is clueless. The manufacturer “registered it with SmartThings” (it is WWST certified), but your device doesn’t send the manufacturer/model ID for whatever reason.
Anyway. Glad it works for you.
Hi Andreas, Unfortunately that is one of the first things I have tried, but I tried again, both after the devices stated “offline” and also when “online” by pushing the buttons to wake them up. This sadly did not help. So I’m really not sure how Bruce was able to get it working w/o these notifications. I was also concerned about turning notifications off for these devices…
Thank you
I bought one and tried to connect it a few weeks ago and only received the sensor and switch options with my v2 hub. I’m still in my return window. I’m thinking I need to return it and find something else unless the last week of posts by andreas and jelez meant that they were successful with a v2 hub.