This has also happened to me now 3 times in last 6 or so months I have been on C8. Before that I was on C4 and never encountered such issues. I have cloud backups enabled
@bobbyD can you help take a look as well. Let me know what info is needed. I will PM you as well
Happened just now again. Reboot didn't work, but power off / on did. Nothing meaningful in the logs.
Resist the initial urge to roll your eyes, but are you using a POE adapter? There are posts about weird issues with zwave+c8 and starting to see some chatter about POE. If so, try the factory plug and see if it can go a while without happening...
1 Like
nope, usb connected to the power strip.
The only chatter I’ve seen has to do with the C8, z-wave and Unifi PoE switches. It’s an unexplained issue, but so far has only been reported with that specific combination of devices.
Or were you referring to other chatter?
And it happened overnight again. Now I definitely can confirm that the remedy is to pull the plug on hubitat and then power it on.
But also I suspect "the outside interference in our elections" 
The case is that in 3 out of 4 occurrences (I am not sure about the 4th - don't remember) there was a Zooz 800 Z-Wave stick on the network, and very VERY close to the hub. I am wondering if there might be some connection there. I will keep it offline for the next several days and see if the same thing repeats.
Any thoughts?
1 Like
You don't by chance have any zooz 4-in-1 sensors do you? Or zooz zen 25's?
had to google both - no, I don't. Why?
They can cause crashes with the c7/c8. The 4-in-1's need to be paired without security as their implementation of s0 is overly chatty (s0 is chatty but that device is horrible) and the zen-25's flood everything with their power reporting.
...but not connected as secondary controller on the Hubitat, right, just in the vicinity of the hub?
correct. I included it before the migration to remove ghosts, and then I was playing around with it on my HA box. But I never made it a secondary controller - I don't know how to do it (yet? :))
The fact it's included... leave the driver as device.
Be aware that it is a repeater as well so removing it (disconnecting it) it will hamper your mesh. To exclude it run exclusion on hubitat then NWE on the software
1 Like
so just the fact that it is included might potentially mess up hubitat into f'd up zwave?
Disconnecting it while included in hubitat can mess it up as it's a repeater. If you need to disconnect it, exclude it first.
Understood. I presume if I don't see it on the zwave details page as a part of any other device route, it is safe to assume that it's not repeating anything?
It's still a repeater and because it's in the table at some point it will be tried to routed though and hang your mesh. When you are done with it just exclude it.
And so it happened again - I guess it's true what they say - consistency is a sign of mastery.
I am trying to put in place some nightly shutdown / powerup measures so that if it is f'd at least on my terms... But it's definitely annoying.
I know there's a rebooter app, But is there a shutdown command that can be issued?
umm nevermind... search makes wonders sometimes 
I've had the same problem and was able to recover with a shutdown, power disconnect, and restart.
I hope Hubitat has a permanent solution soon.
