Tried soft restart doesn’t fix the problem. Happens once a week. Hard restart fixes it for a while.
Could you please send us a private message to @support_team along with your hub id so we can further investigate?
1 Like
Sent
I've now had this happen 3 times with a month or 2 in betweee.. The first 2 times restoring the backup fixed it....im restoring again now.
Seems wrong 
You should not have to do any restores of backups...if this happens try:
Shut down hub
Pull power 30s
Restore power
That should sort any issues after this occurs.
It is wrong, HE engineers have squashed this but for majority of users but for some it keeps whack-a-moling back up, unfortunately...
First time, the power cut didnt fix it. I will try it again though if it happens again.
1 Like
Thanks...make sure you wait for at least 10s or so...I say 30s so that folks who are little impatient (like me) give enough time for the radio to clear. 
That should work and interesting to HE staff if it doesn't.
Happened again and cutting the power DID fix it.
There's no permanent way to stop it?
Just to be sure, what happened was another Z-Wave failure after a cloud backup failure?
yes exactly that. Backup fails...then ZWave stops functioning
Do this... Explain what you experienced and provide them your hub UID. HE staff may be able to look at your engineering logs to see if they see anything...
2 Likes
I had the exaxt same issue, wrote support as recommended with my Hub ID, 4 days not even recognition it was received.
Disabled cloud backups until this is sorted out. That's what I did when it happened to me while out of town.
I just manually do a cloud backup once or twice a week.
Sorry it's taking a while - limited staff, and lots going on with a complex current beta, on top of support queue. You're not being ignored...
2 Likes
I think the cause of the issue is now known, and the focus is on engineering a solution.
3 Likes
We are aware of this issue, and while it has been resolved for most users, a small number may still experience it.
Our engineers are actively working on this problem, but a permanent solution is not yet available. In the meantime, the only known workaround is to shut down the hub from the Settings menu, then unplug it for 1 minute before plugging it back in. While we understand this is not an ideal solution, please be assured that a permanent fix is in development, though we are not sure at this time when development might be completed.
4 Likes
So, is one minute the official timeout?
