@diySmartHomeGuy did a review and April (who is no longer here) did a review.
Love my Schlage on HE... Clearly a YMMV situation.
4 Likes
I think I was simply having issues on C7 due to it being non-plus and being paired with S0.
On C5 for almost 18 months it could be a little slow to respond but I only had to pop the battery twice for 30 seconds to get it back online.
I did check on eBay for upgrade options but I couldn’t find anything and since it’s my front door lock I wasn’t willing to wait and search another day. So I made the jump now just to make my life easier.
Yep same issue - non-S2 devices get set to max security by default. This is per spec I think. I use a Z-stick as a secondary controller to pair mine as unauthenticated.
1 Like
@erktrek Eric, would you mind explainig this process to me? You created a secondary controller using a Z-Stick how? And then you joined the device by placing it behind the secondary controller? I've got some issues with Fibaro FGMS-001 that join as a 'Device' but always join secure (which I don't want).
Thanks. P
Sure! Including a device does not join it to the secondary controller but to the primary one. You will not be able to include S2 devices. You need a Z-Stick or equivalent and the Z-Wave PC Controller Software by SiLabs (you have to create a free account).
@sebastien posted some instructions about converting over here:
In my case I just made sure the device was removed from the hub (fibaro key fob FGKF-601ZW5) and then like in his instructions put the hub into inclusion mode then used "Add" (although I think I used "NWI") then put the device into pairing mode. Wait a bit and it should add, if not hit the "abort" and either try again or sometimes it will add the device - you can see this by looking at the last entry on the device column on the left. On the hub side it becomes a little more fuzzy - sometimes I go into inclusion mode to see if anything pops up. Also reboot and see what comes up. If you don't see your device then go to the Z-Wave details page and at the bottom should be an undefined device, hit repair/refresh/discover a few times then reboot - you can watch the logs. Takes some combination of the above but your device should appear... if all else fails try again.
Good luck!!!
1 Like
Great. Thanks. I'll give it a try later. I've also pinged sport with the situation, if they offer anything else up I'll post here, appreciate the response.
1 Like
My understanding is that pairing non-S2 devices as S0 is per the 700 series spec. It's weird though that you can include S2 devices with no security why not non-S2?
This is a real issue though especially for people not inclined to set up a secondary controller and pair things that way. They will end up with a bunch of chatty devices that some may or may not respond properly.
I need to figure it out. I don't think my repeaters are capable of relaying the traffic, They (the FGMS-001) work when sat near the hub but if I move them beyond some of my z-wave sockets they stop working. What's confusing me is that somehow at least one of 5 of this devices has joined in a non-secure way?????
Probably the non-secured one has an incorrect pairing would exclude and try again. When I originally paired my Fibaro Key Fob to the Hub it paired as S0 and was not responsive. After finally getting it paired unsecured works great.
You might do the exclude then shutdown the hub, pull the plug temporarily then start it back up again and try the include. I would also consider just excluding all of them and adding them back in via the secondary controller (do the shutdown thing after exclusion!).
Has anybody seen this...?
Finally broke my Day 1 C7 out of it's shipping envelope, updated the software and the ZW firmware, and attempted to include my first 700-series device via Smartstart. Only, after taking the picture of the QR code, the app (ios) simply returned me to a blank Smartstart page and never filled any of the details in. Two devices included properly via S2 using the traditional inclusion methods, but was curious if anyone knew why Smartstart wouldn't work for me. TIA!
I encountered similar issues on Friday migrating from a C4 > C7. I made sure both hubs were running the latest release (2.2.4.148), and spent about 4 hours trying to get anything to pair/work. It didn't seem to matter what the device was or how I attempted to connect it (smartstart or not).
After spending WAY too much time troubleshooting I finally realized it was like an issue with the release. I tried reverting to 2.2.4.141 and magically everything started working. Every device giving me trouble pairing adopted normally in seconds.
The best I can tell there was a bug introduced somewhere between those two versions. I've been meaning to reach out to support about it, but it's taken me a few days to get things mostly functional. I was originally trying to use @bravenel technique of editing the DNIs, but after a few hours fighting adopted the torch it all approach.
I'm going to take the ~2 days of rebuilding automations as a sign I might have a slight problem...
I've seen some weird pairing behavior on these releases as well. I bought a Zooz double plug and the thing never stopped "initializing" before the Zwave inclusion time ended. Fortunately, one of those times did result in the device being added and it seems to mostly work. I saw the same with the Aeotec Range Extender 7 but this time it created a Ghost node, which fortunately was easy to remove with a simple exclusion. I haven't tried to add it back yet.
Also, while my Zwave devices and automations mostly work, I still see occasions where a device just suddenly stops working. It seems to fix itself later, but it is pretty annoying. I'm on .148 as well.
1 Like
My experiences as a recent (~6 weeks?) convert from Smartthings:
So I recently migrated ~90 Zwave devices from Smartthings to Hubitat. And then after that, I've been replacing a lot of first-gen Zwave devices with Zwave Plus & S2-capable devices (shout out to Inovelli & their Red Series Dimmers). So I've spent a lot of time fighting with Zwave inclusion/exclusion issues.
When it acts up, I experience:
- Intermittent behavior wherein Hubitat simply doesn't find the device
- Intermittent behavior wherein Hubitat includes the device, but never offered me S2 Authenticated options. This requires me to exclude and then re-include (trying again).
- Intermittent behavior wherein Hubitat is in exclusion mode, but doesn't find the device.
I seem to have the best luck if I first do an exclusion. If Hubitat immediately finds/excludes the device ("Unknown Z-wave device removed"), the inclusion process run immediatley after will find the device about half the time. Of those instances, I'll only get asked about S2 options half of the time. So it usually takes me roughly ~3-5 exclude/include cycles to get an S2 devices hooked up and connected S2 Authenticated.
If Hubitat, after repeated (failed) exclusion attempts, absolutely positively will not find the device I'm trying to exclude, I'll try the shutdown/unplug/re-plug process that I've seen suggested on these community forums. After that process completes, the first exclude/includes almost always goes perfectly. Sometimes I can get 1 more to go smooth before I'm back to the "Try, Try Again(tm)" behavior I outline above.
As I said I've only been a Hubitat user for ~6 weeks. I think I started on build .141, and I've been accepting the new ones as they've come along -- so I think that puts me on build .148 at the moment (Dec 1, 2020). I don't feel like the behavior has changed amongst the 3 or 4 builds. I've had these struggles from the get-go.
If you haven't already, make sure your Inovelli switches have the most recent firmware. I had a black series switch that was pretty much wrecking my Zwave network and since I upgraded the firmware, it seems OK.
Thanks for the suggestion.
I just recently bought the switches, so they all came with the newest version (1.48, I believe?) on them.
(That said, my issue is not just with Inovelli -- having it with contact sensors, Aeotec Trisensors, etc.)
Check your past logs for zwave busy messages. If you see them then do a safe shutdown and pull the power for a minute.
This doesn't address your larger problem, but I do have a suggestion to simplify your ongoing exclusion/inclusion activities a little bit. You might consider joining your devices w/out security - uncheck all boxes in the Security dialog that appears. Many of us (myself included) don't feel the small risks are worth the hassle of finding/ tracking S2 codes per unit, particularly when going through problems like you are.
Totally a personal choice, obviously, but joining w/out security will make things a little easier to mange.
3 Likes
Good call, yes, I always start to get Zwave Network Busy messages when the problem occurs.
There appears to be two ways I can trigger this behavior:
- Try to include more than 1 or 2 devices (will trigger immediately), or
- Wait 4-12 hours (haven't figured out the timing yet) and it'll happen on its' own
As I outlined in another thread, what specifically happens is I'm unable to tx Zwave messages from the hub. The hub continues to rx Zwave messages, such as switch presses, motion sensors, contact sensors, etc.
Related: Since the upgrade to 2.2.4.158, I can't seem to include S2 Authenticated devices as such. The pop-up that appears only has S2 Unauthenticated checked, and if I manually check S2 Authenticated I get a complaint about key mismatch (although I was never prompted to input the key).
I'm thinking about putting a reboot on a 6 hour timer or something, but if I have any motion sensors triggered when rebooting they get out of sync until they next detect motion. So then I have lights all over the house on that aren't supposed to be.
-jd
Those messages typically pop up when there is a failed pair but a bunch of stuff can cause it. Weak mesh with a bunch of unack's or whatever.
1 Like
