This thing has happened to me before.
I just updated to .138. The hub rebooted itself as part of the process.
After restart, no zigbee devices worked.
outCosts, all zeros (see below).
A controlled shutddown and power cycle sorted it (see below).
How about you?
Normally just let it do its thing and give it a few minutes for everything to come back online.
I typically pick a window of time with relatively low (or non-critical) activity. For our house, that can be after my wife starts working on weekday mornings. Weekend afternoons work well, too.
If being offline or unstable would cause problems in the next half hour or so, then I just don't do it. I have horrible PTSD every time that my wife yells something like "why didn't the basement stairs turn on?!".
Otherwise, I also just let it run through its standard routine.
I prefer the "Jesus take the wheel approach". I press update and pray. Hasn't failed me yet.
amen
It helps to not require it for essential services. Just nice to have.
A different hub to switch to, can be a fallback, if you need a plan-B.
Yeah, that is how I set mine up. The challenge is there are others in many of our households who define "essential services."
An automation I suggested was met with "We don't need that but if you want to do it fine." So I set it up and now that is has been in use for 6-7 months, I have been informed it is ABSOLUTELY ESSENTIAL.
FWIW, I take @jnosa899 's approach, sans the praying -- I pull the trigger on all 4 hubs (1 C4, 1 C7 & 2 C8's) while sitting in my chair with my feet up on the footstool, lean over and casually tell my wife on the next chair over..."oh, by the way, the automations might act a little funky for a few minutes..." smirk and wait to see what happens...
I do, however make a backup every few updates -- just in case.
So far, the biggest issue I've had, is that sometimes the Hub Mesh doesn't fully repopulate states and the like before an automation on the automation hub kicks off. That is, the 2 C8 (hardware hubs) aren't up before the c5 and c7 (automation hubs).
As others noted, just waiting a bit might solve the Zigbee problem you indicated. As well, just toggling the Zigbee radio on/off might have done the trick as well. However, your solution clearly worked -- win!
It's interesting that it's happened before. I wonder if one of your Zigbee devices is a little odd -- ate the two "bench lights" bulbs?
S.
By any chance had you done a 'rebuild network' at any time prior to the update? This ("this" = rebuild causes loss of connectivity on any subsequent reboot even if it is a firmware update) is an issue that has existed for as long as the 'rebuild network' option has been a thing.
It's already been reported; however I've given up checking for it in the last several releases since it has never been acknowledged.
Only way around it is to wait... Your neighbors will regain connectivity within 45 minutes to an hour and a half based on what I've seen, or reboot again, or after having done a rebuild, reboot your Zigbee radio.. that will also eliminate the loss of neighbor connectivity on subsequent reboots..
No, I didn't. Also, at that time, "rebuild" wasn't chosen upon "reboot"...I think. Next time, I'll document what I'll do, lol.
I'm pretty sure the zeros got there just from the firmware update process.
I know an initial rebuild and reboot didn't help me regain connectivity. Instead, I switched it to rebuild upon reboot, just for the heck of it, and did a shutdown and power cycle.
It might not hurt for the Z-Wave radio to get refreshed as well once in a while. Some Z-Wave routines seem to need exercising, for me, after a normal firmware update, before they act as crisply as before. I'm thinking, maybe, the shutdown/power cycle post-update helped with that.
It's all feelings though. I'll tell myself to take notes the next time, but I never do.
I usually update when I'm the only one home. That's usually during the day during the week. I usually like to be on the bleeding edge and help with betas, but I stopped doing that for my Hubitat. I had a failed update last year sometime and had to do a restore (which wasn't so bad, really), so now I only update when I think there's something that will help my hub. I don't make many changes, so if it hums along happily, I'm not in a hurry.
Mostly try to do above...prefer to update when wife has gone into work, but that's only twice a week so I frequently update while she's home and just warn her that I'm doing a "security update." 
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
