On the other hand, we're paying a bit of a premium for cloud backup.
I understand recovering from a radio database failure, or whatever it's called, is a nightmare without the cloud backup.
That's why I'm continuing to do it.
I wonder if restoring the backup that caused the problem would work ok or is it best to use one that completed without causing a problem? I guess if the most recent backup even if it did cause the problem restores everything to working order and that until a permanent fix is implemented and a restore will ALWAYS resolve the problem then it is probably best to continue with backups since the restore is such a simple process. I would like confirmation of the above though before I reinstate the backup process.
Can anyone confirm or otherwise?
At this point few if any devices are suffering from the backup z-wave radio shutting down issue. Most didn't have the issue, it was a low number that did. Once .145 was released things seem to normalize. I would start looking at apps running high at the same time or spammy z-wave devices....But as said Victor and Bryan are the ones to look at it...
Yet I don't seem to be the only person with the issue. I would hazard a guess there are quite a few more that just haven't worked out the cause yet.
But now, as Z-Man is more MatterMan, perhaps don't hold your breath.
As I said, it happened to me this morning, as discussed in that section of the forum I can mention.
You don’t have to be coy.
Cloud backup failures causing z-wave radio issues is something they were working on and was being discussed in beta threads (and non-beta threads).
A fix was applied at some point. I do not know the current status, or if there could be a new issue that’s related, or a new issue that’s not related but may have similar symptoms.
1 Like
Ok. @bcopeland asked for my hub ID number the first time it happened.
That was 14 days ago.
It's happened twice since, once this morning.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
