When I look at Hub/Information in the App, both hubs say Model_Name is V3_HUB
Thanks Bruce! I have a V2 and I think mow4cash is right that this device will not pair to a V2 hub.
Hmmm. Doesnāt make sense, but hey what does sometimes with Technology. Have you tried ST support? First Alert Support? It is possible you have a bad one, although in my case it was driver related since both the original and replacement are working just fine with the latest driver. I initially had installed a beta drive from ARoehl which seems to have allowed the Snapshot version to be applied. The reason I say this is my other home that I havenāt installed the Beta driver, the Snapshot show up. I will be at that home after Oct 31 and will try to what happens. Of course, that home only has ZComboās (6 of them), but my ZCombo at the the home Iām currently at did magically pull the same snapshot driver so who knows
So just install that ARoedl driver for First Alert and I was able to switch drivers on the fly. Weāll see if I have any communication issues
I read through this entire form I have the V2 hub. I have tried for hours to get this thing to work. Back to Amazon and goes. The older version were great this one sucks
1 Like
Hi all, I purchased 3 of these alarms (SMC0410) and never could get these to work on my V2 hub. So I upgraded to V3 and got them to connect. However, I am having the similar issue that Bruce was, where they are going offline / online continuously throughout the day and I get notifications on my phone constantly. The driver used is the Snapshot First alert 2025 and I tested all alarms then did a zwave repair, it hasnāt helped. So I called First Alert and they said to call SmartThings.. Was curious if there were any ideas on how to fix this conditionā¦ @ Bruce - did they tell you replacing the unit would fix the issue? Maybe I should request replacements from First Alert? Or would trying a different driver help? Thanks
Having the same issue I tried and tried. I get stuck at the āVerify your deviceā page. I put the pin or I scan QR and it gets stuck processing. I installed the mentioned drivers in this thread and still stuckā¦ Any new options? Appreciated!
HI Bruce, please see my post around 104. DO you think the new unit fixed your problem with the old oneā¦ (maybe the structure of your network)? I have 3 of these and keep getting offline / online constantly through the day. Did First Alert say there was some actual issue on the replaced unit? Thank you for your thoughtsā¦ Best Regards
First Alert told me on the phone that their engineering team acknowledged an issue and that I probably get a replacement unit. When the replacement arrived, I paired it and noted the newer driver. I then removed and re-added the original faulty unit and noted that it also pulled the new driver as well as a ZCombo unit I had. All three havenāt given me an issue since. To answer your question on my ZEave network, I donāt think so since I had the unit in the same room less than 12ā away from my ST Hub. I have over 15 ZWave devices through out this house and have a Zooz ZWave relay that acts as Zwave Repeater in the basement and rarely see any drops on any ZWave devices. It would be handy if ST added ZWave mapping like they did with zigbee devices so you could see what is connecting where.
Note my hubs are both V3 (IM6001-V3P01).
Hi Bruce, thank you for your reply and the details 
, Iāll contact first alert and post later if Iām able to get this resolved.
Given that my ZCOMBO started going offline/online all day and I replaced it with SMCO410 and the same thing happens I sort doubt its an issue with the first alert device. It started happening around the time the last firmware update came through near the first week of October. A TEST of the device always brings it back online for me so I know communications are making it through (It has to go through several repeaters to get to my garage).
What version hub? Have you reached out to ST? Do any of your other ZWave Devices have connection issues? What driver is the FA device pulling?
I just got some of these (the new 2025 ver) and had a similar issue getting them to pair. I had to hold down the test button for 20 seconds to get them into pairing mode, even though the instructions said that putting the unit on the base and āactivatingā it should start the pairing process. I didnāt have to exclude them, but I just had issues getting them into pairing mode.
One issue Iāve run into is testing the devices, in STās the device is āstuckā showing ādevice testedā as the status, it doesnāt go back to clear and I canāt find a way to reset it. Have you had this issue? Iām using the ARoedl driver and havenāt had any other issues besides this status glitch.