IIRC the cloud backups briefly stop and restart the Zwave radio to ensure that it gets a good backup of the radio database. Since the backup noted that it failed on the ZWave portion and subsequently you are experiencing issues with the Zwave mesh I would recommend a shutdown and removal of power from the hub (at the wall) for about 30-45 seconds. This should force a reload of the hub's cached Zwave information from the radio database.
Why you had an issue I'll leave for @gopher.ny or @bobbyD to look into as they may want to look at the engineering logs.
Thanks for your message. We checked your hub's engineering log and the Z-Wave problems started as result of the cloud backup-up failure. Our engineers are aware of occasional backup failures that can lead to Z-Wave radio going offline. We do not have a solution at this point. The problem is now listed on Known Issues in Release 2.3.7.139 . If the backup fails again, you may want to power cycle the hub by shutting it down from Settings, then when the hub's LED turns red, unplug the hub for 30 seconds before plugging back in. Running a manual cloud backup is recommended following a cloud backup failure.
I had this same issue, C7 running 2.3.7.139. Would not complete a cloud backup, would error saying incomplete backup due to Zwave. I did a shutdown and then unplugged the power for 45 seconds. Reconnected power and once booted up ran cloud backup, finished successfully. Just upgraded to 2.3.7.140 and crossing my fingers.
The latest release doesn't have a fix. The problem with this issue is its inconsistency. You can run 100 manual backups and/or scheduled backups and they'll complete successfully, but the 101 fails (the number of successful backups failures varies).
Hi @bobbyD I got another failure 2 days ago and my Z-wave network started to have issues since. Power cycling actually didn't help unfortunately. Is this something the team can take a look thank you!
We are actively investigating some edge cases that have not been resolved by the recent updates. Thank you for your patience and understanding while our engineers narrow down the root cause. At this time we do not have an estimated resolution timeframe.