@pcgirl support@hubitat.com is your best bet now.
You can fix the 401 error easily yourself if you want to try another soft reset. Go to hub http://hubip:8081 , click log off and then log in again and try the soft reset. The 401 means that your login expired
1 Like
Since has done earlier resets I still think she should try support.
1 Like
Hubitat replaced my hub, which is when I discovered a "restore" doesn't rebuild the z-wave network, so I'd be forced to manually exclude and add back every single z-wave device, even with a backup. Prior to starting this work, I plugged the new virgin hub into my network, and a few hours later, the new hub with no z-wave devices, essentially doing nothing, crashed and became unresponsive on my network, inaccessible from the web interface.
So Black Friday came around, I purchased an Eero Router system for my home (3 wired Eero Pro's, and 4 Eero Beacons) to replace my original router setup (1 Airport Time Capsule, and 3 wired Airport Extremes as extenders). With the Eero setup my original Hubitat Elevation device hasn't crashed once, nearly 3 weeks of uptime. I contacted Hubitat technical support about a Week ago, but they never responded to this discovery.
So Hubitat pushed an update which bricked their device on certain types of legacy routers / networks, namely Apple, didn't realize it, and isn't interested in troubleshooting it. Life moves on, my Hub is back online, although after about two weeks my Amazon Echo connector crashed, forcing a reboot, the hub itself hasn't crashed once with the Eero mesh router system.
3 Likes
I'm sorry to say, but I'm really glad you had this issue, because I think I'm in the same boat. I've been struggling with the exact problem set you've described above. I have a C7 that started locking up almost hourly a few days ago (after running flawlessly for 9 days straight following the v.145 update).
I have ~70 Zwave devices, 3 Zigbee, and no LAN devices. No integration with any cloud services other than what HE provides from the mobile app... so I have even less LAN interaction with my hub than it sounds like you did. I also have different network equipment from the sounds of it (Asus router, netgear unmanaged switches). I'm going to plug the HE into another switch to see if the issues go away... I had changed ports on the same switch, but have not changed out the switch outright (unmanaged Netgear 5 port).
The only oddity is timing of the issue beginning... yours sounds like it lined up with an update, mine doesn't.
You can roll back firmware if you think another is more stable. But you shouldn't be having lockups.
Do you have lots of power reporting devices? Those if misconfigured can take down an otherwise healthy hub.
The other thing you probably should look for is ghost devices in the Zwave menu. I don't have a C7, but I think that the last column will be blank I think?
Yup - that is one of the key symptoms. No routing in the last column.
When the issue first started, I was on v.145 (had been for 9 days straight, no reboots, rock solid). Once the lock ups started, I eventually did get to a point where I was getting stuck at blue light. I performed a soft reset at that time and reverted back to v.142. While that got me back to green light, the roughly hourly freezing persisted.
I believe I only have a few devices that report power (and I think they're all Aeon / Aeotec outlets, but I'm using the Generic Z-wave smart dimmer driver... not sure if they're actually reporting with that, I'll need to double check). I can confirm that the logs have been less than helpful in troubleshooting... nothing obvious stands out, no errors outside of the other known Z-wave inclusion issues, but I have had little issue in that space thankfully.
I do have two lingering ghost devices that I have been unable to remove. I've attempted the recommended steps by others but can't seem to shake those two (I had more previously, I think my highest total was 5 at one point). Those two have persisted since I was done migrating all of my devices over from ST, so I assumed they were similar to what others have been seeing with the C7s. The remaining two could absolutely be a part of the issue, but I believe I've exhausted my options there short of a hard reset, which I'd rather not do just yet.
Its far too early to celebrate, but I moved my C7 to a different switch roughly 3.5 hours ago, and haven't had a lock up... that's a record since the issue started. If I get to 24 hours, I'll move it back to the original switch to see what happens.
That won't do a thing. Unless directed to do so by support, that should never be done.
You mean network switch? Or power switch?
The hard reset is just throwing in the towel, discarding the current Z-wave mesh, and starting fresh. No guarantee I won't end up with ghost devices again, but it's the only way to remove the two I have presently. Totally get it though: last resort only.
And network switch... and it survived the night and is still humming along... makes no sense to me how this could be the resolution to the issue without understanding how the C7 interacts with a LAN when the only interaction, in my case, is HE cloud.
I don't think that is the case. You should contact support and follow what they say to eliminate the ghosts. 
There are other options by using a Zwave stick and a computer, but to me, that isn't the first step I would do.
There is also a network fix that you may need to apply. Certain brands of networking equipment seem to have issues negotiating proper speeds with Hubitat. When you contact support, see if they say to do this fix. Describe what happened, and tell them what brand switch/router you are using.
I'll definitely ask support about the ghost devices when I update my ticket related to the freezing issue.
I've now passed the 24 hour mark without the C7 freezing, so I'm confident there's something to the network switch it was attached to... still doesn't explain why it worked fine for 9 days before that though. I'm reluctant to move it back to the "bad" switch tonight to see what happens, so I'll do that tomorrow after I'm home from work.
I wouldn’t use it with that switch. I believe that was one of the switches first identified as not autonegotiating with the hub correctly. I can confirm that the unmanaged TP-Link 5 port switch works well with it (and is cheap).
1 Like
So now I'm having this same issue with my new dual C-7 setup. The exact same issue, except it's only affecting one of the two hubs. I'm on Eero wifi, both hubitat's have assigned static IP's, I'm using a rack mount TP-Link 24-port unmanaged switch, and with all of this hardware, I can't even turn off the damn porch light.
Any suggestions?
I've had an issue over the past few weeks with my C7 crashing and then having issues rebooting and issues doing restores..... eventually I would get it running, only for it to crash again after a few hours.
I think I discovered the culprit. When we were having all the C7 Z-Wave issues I took the C7 off of my nice equipment shelf which has UPS etc and I put it on my desk where I could easily pull the power to it to get Z-Wave going again... It was powered from a USB hub - I think the USB hub was not supplying enough juice for the C7, I've now moved the C7 to a different power supply and fingers crossed no issues so far.
3 Likes
So what is different between the two? Apps? Devices? Why do you have two hubs?
I think you will have to give some more detail before anyone can make a suggestion of what could be wrong.
I have two hubs because my C5 was also unreliable. I burned out installing smart home devices when my hubitat would become non-responsive every few days. Dual C7's was supposed to add more processing power, and ideally reliability, to my setup.
So back when I was troubleshooting my C5, Hubitat support said it was a defective hub and replaced it. The problems persisted, and a forum member said it was my Apple Routers. So I upgraded to Eero mesh. After this I had several months of uptime, before an update caused my hub to crash every few days, or be sluggish. Now I put in my two C7 hubs, and with 3 (three) simple native automations I'm crashing in 4-6 hours on the second hub.
When I say "crashing" I mean crashing. Automations stop running. Light rules don't activate. The hub is unresponsive via the portal or direct IP. Recovery console doesn't load. My router shows the hub is dropped off the network. The hub itself is sitting in the closet with a green light, as though nothing was wrong.
I'm using the supplied power adapters on a power strip.
How hot does it get in that closet?
1 Like
Or maybe a bad device that's spamming the hub?
2 Likes
