I was getting a database size warning after adding a few new devices (lots of events from my weather station?), so I figured I'd update and reboot. Update seemed to succeed, but on reboot it stuck on upgrading device drivers.
After leaving this a while / rebooting at least once, I went to the diagnostic tool, safe mode, went back to 2.4.3.173, soft reset, and tried to restore from backups (I have 2026-03-14 and 2026-04-10, either is likely fine for my purpose).
I really don't want to do a full reset. I have a lot of devices and restores have completed before on the rare occasion when I've needed to. Any advice or things to try? The fact that I can't even see a log of restore progress is punitive, I can't guess as to why it's not completing.
Don't do anything drastic like a reset, wait for more help to weigh in here. Unfortunately it's the weekend so folks are not here as much as they would be during the week.
Good advice, but the fact that I can even get into this situation makes me want to move immediately to a platform where I can actually troubleshoot it. A black box is only useful if it doesn’t suddenly turn purple.
Diagnostic tool works, and parts of the primary UI work — settings, but not devices, for example. I have not rebooted since the last attempted restore.
I see devices listed in Z-wave details, but nothing in Zigbee. (I think I have a few Zigbee devices, FWIW).
After leaving it overnight, one device has appeared (Open Weather), and two apps (Basic Rules, Visual Rules Builder, but no rules yet). I haven't tried to reboot. Something's definitely timing out / hanging in the restore process.
Why would I do a reboot w/ database rebuild when I already did a soft reset (twice)?
I haven't done a full power down, but I presumed that the soft reboots were already cycling the radio hardware.
In all cases, if I'm forced to reset the radio pairing db, I'm leaving the platform; if I'm going to have to re-pair everything, it might as well be something I can control and troubleshoot.
Also, when you do a soft reset, can I recommend restoring a hub backup that is known to be good - maybe one from a couple weeks ago. There is a possibility that you’re restoring backups with corrupted databases.
This already exists. It’s called a full reset and it can be done from the diagnostic tool.
Z-wave and zigbee radios can each be reset from their respective settings pages independent of a hub full reset as well.
ETA: A full reset is rarely recommended by support staff as a step when troubleshooting a hub issue. It’s intended primarily for use before getting rid of a hub or giving/selling it to someone else.
We are in semantics now. Powering down the hub will (assuming you power it up again), in effect, reboot the radios. They will restart as power is re-applied. Restarting the hub... leaves the radio reset lines high ( so no radio restart occurs). And so if a radio is hosed/locked up/out to lunch, this does nothing. Radio (s)restart should be part of a standard restart (which you also shouldnt need to do on a regular basis)... but when you do, everything (hw) should bounce.
Radio “reset” is the term in the hub UI that refers to completely clearing the Z radios, as if the hub was brand new.
Call this a semantic argument if you’d like, but if you mean something else by “reset” when referring to the hub Z radios then I believe your meaning is unclear to others (perhaps it’s just me).
He is talking about sending a hardware reset signal, i.e togglin a reset line if hw is capable to do this (may not be a case). This will do the same job as power cycling which is annoying and near always forgotten. Normally the reboot assumes full hw reset which is similar to power cycling. But hw must have this capability.
I'd still do it in case one of the failed restores left some baggage behind...
