Can you post your z-wave details page in it's entirety? (use windows snip)
1 Like
...
My details page is so long that screenshots are not an option as far as I can tell.
Please try viewing this PDF of the page -
I did redact the device names.
As many S0 and S2 devices you have, you could say that you have 100 x 3 devices in your mesh. Fibaro, Zooz and Inovelli have had issues reported with their encryption for both S0 and S2 firmware. Unless you have updated the firmware on those devices, the probability that those are causing problems is very high.
Oof, have heard something like this before.
I had included them with these security settings before I knew any better. I could start to go around excluding and reincluding them without security. Based on past experience I expect this would cause my mesh to go wild for a few days, and possibly lead to some ghost nodes I'd have to remove with the silicon labs software. They do not make this easy! I wonder if this would be worth doing to try and fix the radio crash I am having. I hesitate since this issue is new and was not occurring for years with all these same devices setup this way.
Yes it would be worth it. Also, if you are thinking to split your mesh as we discussed in private, this may be your opportunity to redesign your home automation approach and move around devices by floors/required encryption (isolate S0 on one hub and keep the other devices on another hub). Just remember, only locks and garage doors require encryption, everything else can be included without it. Doing so will reduce the number of events that the radio must handle when it communicates with encrypted devices, so the end result would be a faster, more robust mesh experience.
1 Like
Thank you bobbyD and everyone else for your time and help today. I will take this advice and hopefully in the near future buy a C8 hub and split the mesh in the way you stated. I can certainly remove security on nearly all the devices in my home. I have less than 5 devices where it is necessary.
Not any real reason to. Unless there is something in there with your home address there is no identifying information on this page
I see customers running into problems when they use smartstart to include devices. While SmartStart is a convenient way of including devices, by default it connects the device with highest security level, so if the device has a firmware problem and fails to encrypt the device, then the possibility of creating ghosts increases exponentially. I always include devices using conventional inclusion mode that gives me the option to include devices without encrypting them.
2 Likes
I have found this to be true myself and stopped using smartstart.
1 Like
I'm sorry, but to snip and get screenshots I would have to manually scroll the page and take around 30 individual screenshots. This forum only allows 5 files to be uploaded at a time. Hence the (ugly) PDF. Unless I am missing something?
Funny you posted this. I actually attempted this (in Chrome) and it did not work due to the iframe the hubitat webpage uses. Maybe it works in Edge? Before I go trying that, can you tell me if this satisfies what you are looking for? Names not redacted this time...
2 Likes
Much better on my aging brain lol... Yeah, have to agree with bobby, all that s0 in there could certainly be creating issues. One option you could try if you have a z-wave stick handy, is to re pair all those s0 devices as none (use the stick as a secondary controller on hubitat). That would certainly clean stuff up. (note, hubitat mandates that garage door openers and locks maintain encryption regardless of s0 or s2... ) Your mesh though except for that looks fine.
Just an idea.
Also
You can craft a rule similar to this for z-wave and zigbee to keep on top of things.
1 Like
Thank you - great ideas!
Question - is there a way to re-pair them with the stick (I do have one handy along with the Silicon Labs software) that does not involve the torture of manually excluding and re-including all of them? These S0 devices are mostly battery powered door/window sensors.
Create virtual devices as place holders
Use swap apps device
Exclude and re pair all affected devices
Use swap apps device
After all is said and done, shut down hub, unplug power for 2 mins and then power back up and see how things shake out.
1 Like
Seems like this would be roughly as labor intensive to do with the hubitat instead of the z-wave stick unless I misunderstand. If you want to really get a good laugh (as I cry), these stupid Fibaro sensors have the button necessary to exclude and include them ON THE BOTTOM - they are all screwed down into window and door trim 
You can downgrade S2 to None without a USB stick
- Factory reset the device (do not exclude).
- Refresh on Zwave details page until you get the remove/replace options.
- Use replace to include it again.
- You should get security options prompt, de-select all security.
I do not think this works for S0 though.
That being said there are a few of us who include everything with S2 and do not have any issues. I also use Smart Start, with no issues. S0 is still good to avoid when possible, but unless the device is very chatty (or you have a lot of mildly chatty devices) it really should not cause much of a problem IMO.
3 Likes
I have a pretty sketchy bubble-gum and paperclips fix that I am thinking about (admittedly out of laziness). Maybe I can power-cycle the hubitat with a rule whenever the log shows zwavecrash. I have to think about a safe way to do that though. If I simply cut power to the hub I expect I will create database corruption over time. If I simply reboot the hubitat, the z-wave radio does NOT recover - it needs to have power disconnected. Damn it Silicon Labs!
