It is enabled. I appreciate your help with this. Worst case, if I can’t get it to work, I’ll get a wi-fi enabled smoke detector that comes with an app. I can’t find any good choices for smartthings. Too bad First Alert stopped making the zcombo. That worked fine.
Don’t. WiFi is never a good idea for devices like that. I have Zigbee smoke detectors from Frient and they are awesome. Built-in temperature sensor and the siren can be controlled:
But since other people are able to connect it, it must be possible for you.
Maybe you’ll find an answer here:
https://community.smartthings.com/search?q=First%20alert%20smoke
Thanks. I’ll check it out. I did consider the Frient, but haven’t found a US based distributor. $18 shipping otherwise.
Just another shit show. A wave compatible device not working with a z wave hub. Stuck processing when trying to add
I spent hours yesterday trying to get this to work on my V2, with the new driver and without.. no good will not connect properly. What a joke - back they go
If anyone figures this out please let us know. I purchased 2 of these assuming (incorrectly, it seems) they should work with my V2 but I’ve spent a couple hours attempting to get this done and the best I’ve been able to do - once - was get SmartThings to connect a Z-Wave Sensor with the same 0000-0000-0000 Manufacturer Code and Model. Unfortunately, I haven’t been able to get it connected properly since. And I haven’t been able to connect the second one at all. I’ve tried holding for one beep to wake up the detector, 2 beeps for inclusion/exclusion mode, 3 beeps to reset, and every combination of those you can think of to no avail. I’m about at my wit’s end.
I have a Secure SRT 323 Z-Wave thermostat (heating only with built in relay) that is connecting as 0000-0000-0000.
Because I was writing my own Edge device driver, I added 0000-0000-0000 to the Edge device driver fingerprint and it works perfectly.
Based on reading elsewhere in this forum, I probably should have paired the SRT 323 very close to my hub, where it likely would have used it’s correct fingerprint, before moving it to its operating location.
@Klober If you are up to it, there is something else to try. This is not a long-term solution.
Sign in to the Smartthings developer portal: Let’s Build a Connected Future - SmartThings Developers. I can’t remember if you have to register first, but use the same credentials as your Smartthings account.
Then select “Tools” from the menu at the top and select “Edge driver builder”. You should now get a display of all your devices. Select the z-wave sensor that was created when you tried to pair the SMCO 410.
Once the device is selected, you will see a “Modify Device Configuration” option at the bottom of the page. Then select “Z-Wave Smoke Alarm” and select “Carbon Monoxide Detector” and select “smoke-co-battery” under the profile matches.
Now select “Apply changes” and a new driver will be assigned to your device on your hub. If all goes well you should now have a driver with the correct capabilities. If this works, we can investigate further.
1 Like
Thank you for the info! I already have a developer account but never delved into it to become familiar with its capabilities. I will definitely give this a try……..as soon as I’m able to reconnect one of my SMCO410s. I tried excluding the SMCO410 and re-adding it (as recommended in "First Alert Z-Wave Smoke and Carbon Monoxide" adding as "Z-Wave Sensor" - #6 by mlchelp ) after installing the driver from @Andreas_Roedl but now I’ve been unable to re-add it again. Once I’m able to try it I’ll definitely let you know my results!
Maybe try rebooting your hub from the advanced web app before trying again.
1 Like
Can’t forget the Wake Up Procedure (according to the Z-Wave Alliance page) which could also be helpful to someone.
I think part of the problem may be the limited 25-30 seconds or so the detector seems to allow (5s classic mode either concurrent with, or followed by, 25s awake time) for it to be detected, authenticated, and paired which requires multiple actions to accomplish. At the same time, I’m not an expert in Z-Wave so I don’t really understand what network wide inclusion/exclusion is.
I am also not a Z-wave expert but here is my understanding. This device is certified to work with Ring alarm systems and supports SmartStart. SmartStart is a later Z-Wave development that allows one to just scan the QR code of a new device in the controller app without having to touch the device and it would then get included in the network.
Although I have read that Smartthings supports SmartStart on the later hubs like the Aeotec V3 hub, I am not 100% sure how well it works and it might only work with some certified “works with Smartthings” devices. I don’t think it is supported on the V2 hub. Smartthings seems to not have Z-Wave in their future plans, so there hasn’t been a lot of development from a Z-wave perspective.
Classic mode is when you put the hub and device into inclusion mode. In the classic inclusion mode, the device sends a NIF (Node Information Frame” to advertise itself to the network, which should include its capabilities. This is the learn mode. After that the Network inclusion can start. This is where I think things are going wrong with SMCO410 device. Maybe that 5 seconds is just too short but I am speculating.
I have Ring Z-wave contact sensors and I remember, that I also struggled to pair them. What worked for me was activating “scan nearby” first and then then put the device into classic inclusion mode. If you look on the forum for the Ring sensors, you will see that there were people with the similar issues, where the device would not pickup the correct driver with the correct finger print and then added the device as a generic sensor.
@JDRoberts, is a Z-wave expert and can maybe explain the Z-wave process better.
Anyways, like I said before, what worked for me in the past with my Z-wave devices is to first reboot the hub, then put the hub into :scan nearby and then activate inclusion mode on the device.
Let us know how things pan out.
3 Likes
Thank you for that thoughtful post. I hope someone here can mention whether they got it to work on a v2 hub or not.
I just bought one to replace an 8+ year old FA ZCOMBO. I got it installed on my v2 hub but it came up as a generic Zwave device. I have installed the aforementioned drivers but they are not selectable in the web UI. I am done testing for tonight. Ill try to clear everything out. ST App/Device/Drivers and then try it all again with the device right next to the hub to see what happens. Hopefully something will work because I dont want to be too long without one.
Hi @roomie76, there definitely seems to be an issue with the pairing process for this device on the v2 hub. Try using the Edge driver builder, from the Developer portal that I mentioned in a previous post, to create a new driver. For that process, the device must be paired with the generic driver like you have now.