Just out of curiosity, are you seeing your Rings double report battery status? I'm seeing the Rings send a battery report, and then another report 20 seconds later.
At noon I removed the 4 Ring Gen2 Extenders, as I stated earlier I showed only 1 device out of my 56 routing through any of the 4. But now that strange thing I had about 20 devices showing 9.6kbps before I removed the extenders now I only have 6 with the majority of the nodes now showing 100kbps. Now this is interesting all 6 that are showing 9.6kbps either route through the Aeotec Siren or the Aeotec Heavy Duty Relay both of which are showing S0 security. So it would seem all this likely has to do with the SO and S2 security.
1 Like
So sure enough I took the siren and put it out in the pole barn (cause it has a battery but no signals get in and out of that metal building) I then ran a repair on the 2 nodes and they both went from 9.6kbps to 100kbps with their new routes. The remaining 4 devices go through the well pump relay and if I screw with that right now I think the family will toss me out of the house. Neither the Aeotec siren or the Aeotec Heavy Duty Relay gave me an option to pair without the S0 but sure hope there is a way to do so.
2 Likes
You might want to get on with that sooner than later--that pole barn is only going to get colder over the next few months. 
Not sure. I turn off debug and descriptive logging for pretty much everything. I'll turn it on for a few and see.
I agree...its already getting cold 
that @syepes can tweak his driver to resolve the issue with that device.
1 Like
I am a new user of Hubitat moving over from ST, my experience so far is horrific. The user experience is junk devices do not add they get hung up in a never ending "initializing". This hub is not ready for primetime. I am truly disappointed with tech support as well nothing but canned responses after feeding them reams of documentation.
Unfortunate, sorry to hear it's been a bad transition. Mine had some painful moments, those are in the past now, fortunately.
If you can summarize the devices you're trying to move over (type/brand) we can see if help from the folks here will get you past the problems. Many of us are ST refugees and have seen/gotten through difficulties.
2 Likes
Sorry for the troubles. I see that we replied once, this morning asking for additional details, but we didn't get a chance to further review the information provided, just yet. We will respond as soon as possible.
2 Likes
@danabw thanks for the support, this just literally should not be this hard. I don't see how this software was ever tested you cant reliably add or remove a device with any level of consistency. The same Zooz 4n1 works one minutes and fails the next. I have around 10 of them, its a long process of adding / excluding rebooting the hub multiple times praying then it finally adds. I desperately want to like this device but so far the C7 isn't ready for prime time. A buddy has an older hubitat unit which he does not see the same issues with, we have many identical devices.
I WANT to be proved wrong!
Found Z-Wave Device with id 10
Initializing
Ughhhhhhhhhhhhhh
That surprises me, I had a few issues with earlier firmware while Moving over but the last couple of versions (since the Zw Radio update) Have been outstanding for me.
Have you updated the Radio firmware?
1 Like
@JDiGangi I won't deny there have been some glitches.
But, I also have some sympathy. This is the first "700 Series" hub to come onto the market.
One of the things that has been seen in spades--is the number of Z-Wave devices that simply do NOT properly support S2 mode. While there have certainly been some things they've needed to address from the hub side, there are a lot of cases where the OTHER things didn't work according to the Z-Wave specifications.
And, because nothing has ever needed to hook up to a 700 Series S2 hub, it hasn't mattered. Until now. 
4 Likes
That was one of my first questions to tech support after reading for forums, I upgraded OS first on the hub itself...literally as it was going I saw the thread about doing the Zwave firmware first. I even tried to roll back the OS and then upgrade the zwave firmware. It says its up to date ????
I am hoping either my hub shipped with it, or its bundled in the OS
1 Like
I did the zwave Radio update after the os firmware update and it worked fine for me.
Yours might already have the latest radio firmware.
That is easy to validate. If you go to the following page, can you share the results?
yourHubIp/hub/zwaveVersion
Replace yourHubIP with actual IP address.
VersionReport(zWaveLibraryType:7, zWaveProtocolVersion:7, zWaveProtocolSubVersion:14, firmware0Version:7, firmware0SubVersion:14, hardwareVersion:1, firmwareTargets:2, targetVersions:[[target:1, version:7, subVersion:14], [target:2, version:2, subVersion:3]])
1 Like
I'm sure we'll get there...definitely not all roses and daffodills when I was getting started, but I'm extremely happy now. (And that's no just because of the ale sitting next to me.) 
One thing I would recommend is read the first four messages in this thread, which will help w/understanding some issues w/moving from ST to HE related to Z-Wave Devices and exclusion. Not necessarily your issues, but takes a few minutes of your time and generally helpul/educational at a minimum, for your future smart home adventures.
TL;DR, if you can, it's best to unplug your ST hub while you're moving devices over to HE, ST can sometimes interfere w/the device when you're trying to include it on HE. Exclude each device on HE first before trying to include it .
Be very patient on the inclusion screen...the device can successfully include long after the 60s timer expires. So if you haven't, sit and wait (or go get another beverage) if the timer runs out and it's still sitting on "initializing."
If it just doesn't finish, look on the Z-Wave Details page for the device (it should be the last device in the list) and if there is a Discover button click it and it may finish the pairing. If not, try the Refresh button and then see if you get a Discover option.
Is it just the Zooz 4 in 1 that are the issue, or are you doing those first? Best approach is to start w/powered devices, from nearest the hub to farther away, and then do battery powered devices last.
4 Likes
VersionReport(zWaveLibraryType:7, zWaveProtocolVersion:7, zWaveProtocolSubVersion:14, firmware0Version:7, firmware0SubVersion:14, hardwareVersion:1, firmwareTargets:2, targetVersions:[[target:1, version:7, subVersion:14], [target:2, version:2, subVersion:3]])
Mine above. You're good.
2 Likes
Zooz is just 1 example of the devices that are giving me a headache, I might need something stronger 
I will follow your advice, I like most here I am sure tend to be the instant gratification type and dont do well with waiting...but I have once device initializing right now I am going to leave it alone and take a look at it again tomorrow.
thanks for everyones input
1 Like
