Sigh - so I was having Zwave issues (yet again) on 2.2.4.147, so I decided to upgrade to 2.2.4.148 before I deployed my Range Extender 7. I noticed some of my Zwave devices didn't work and imagine my surprise when I see this:
Please tell me there's an easy way to get them back.
See above...
Shut down your hub using the Shut Down option, wait until the light goes red, pull power, wait 30s to a minute, reconnect power and let it boot up.
Cool, thanks, I'll give it a shot. I noticed one of my remotes still worked even though no routing info....
.148?
I wonder if this will clear up my issues?
And after all that time on the workarounds.
Yea, I’m seeing a bunch of background route improvements (unprompted by any repair attempts). Looks like Z-Wave Plus auto route assessments are improved in 2.2.4.147 and 2.2.4.148. Getting close to what I would manually pick if that were possible.
Yeah, .148 was just released a few hours ago. I am having issues with a Zooz ZEN25 hub but I think it's related to the location so I decided to upgrade first and then drop my Range Extender 7 in and see if that helps.
They're baaaaaaaaaaaaaaaaaack!
I’ve updated 7 hubs to .147 yesterday, then to .148 again this morning.
It’s daytime so the number of automations that run with a visible result are few, but I do have a downstairs bathroom light triggered by motion and it’s the ‘canary in the coal mine’ for me. That light MUST come on within 300 ms or else @bobbyD gets a message from me. 
It’s working fine, a ZWave Motion triggers one half of a Qubino Dual switch. It’s not complicated but it’s all ZWave and I watch it always.
Said another way, with 7 hubs, a C-3, two C-4, two C-5 and two C-7, if there was a systemic problem, surely one of my hubs would see it, right?
Don't jinx it now. My bird is still not ready and I really don't want to miss it before it flies out of the plates. 
Happy Thanksgiving!
@csteele what hub model is this on?
This has also just happened with me running a C5 on 2.2.4.148.
Last night I noticed on of my Z-Wave light switches wasn’t working so I thought it was that device, rebooted the hub this morning and now there are no Z-Wave Devices in the list 
This fixed it - thanks!
I guess because the Z-Wave stick is passively powered through the micro-USB splitter it doesn’t get rebooted with the hub unless you remove the power?
Probably...as I understand it, it takes a power down to restart the Z-Wave radio, which appears to have been what you needed to sort things out.
If it works I just chalk it up to magical elves. 
The Hub, light and tiny, makes one think it's a simple device.. but it's a complete computer with OS (Linux) and Java environment we call the Hubitat Platform. There's also the 'peripherals': aka Z-Radios. Obviously then, the Groovy stuff of Apps and Drivers are sandboxed by the Platform.
The image in my head looks something like this:
A "reboot" recycles the Platform (and Groovy) but never touches the Z-Radios or the Linux OS. To cycle those, requires a shutdown of the platform (to a Red LED) then removing the power for a few seconds.. long enough to dissipate the power left in the capacitors. We usually recommend 30 seconds.
Great graphic, thanks @csteele. Saved to my personal KB.
The image in my head looks like this, which people have claimed is not as helpful.
It's very useful...
Just not for THIS topic.
Save it though, it might answer some other topic.
Download the Hubitat app
