I've updated to the latest firmware and performed a manual cloud backup which was successful. I've now also re-enabled scheduled backups too which seem to be good so far. I"m not that worried by it now that I know it's easy to fix by just shutting the hub down for a minute or so.
1 Like
It is still very inconvenient for those who experience this issue, as they can wake up with a non-functional Z-Wave radio. Resolving this for good and for all, is a high priority. We really appreciate everyone's patience and understanding.
7 Likes
My coffee maker is controlled by a z-wave plug. This morning was a little more than an inconvenience! 
2 Likes
Besides the no morning Java for you, I am wondering why file manager failed. Mind sending me a PM with your hub id?
1 Like
Sure, thanks!
1 Like
Funnily enough I spoke too soon in my previous post. Mine has the exact same error message and z-wave was down again.
The horror!! 
Starting a go-fund-me for you right now, don't worry, we'll raise the money for a Starbucks card, I swear it!!
4 Likes
It wasn't pretty. I awoke and wondered where the aroma of a fresh brew was. Seconds later, was greeted with, "Honey, the bathroom lights aren't working."
"Did you forget how to use a f#$%ing switch?" was not what I wanted to say but what defensively came out of my mouth. Oops!
4 Likes
Oops indeed!
Been there, said something sort of like that (though not quite as direct) and it was not pretty. Burned hand learns best...I'm inflicting my hobby on her, so I need to cut her more slack. 
2 Likes
"It's the winter solstice, don't you know? The darkest night of the year (for a little longer)!"
4 Likes
Well, @bobbyD , knocking on wood was the kiss of death.
I have Pushover notifications as well as voice announcements via Ecolink Chime/Siren.
My phone is on Do Not Disturb overnight, and, thankfully, I did not hear the voice announcements.
I think I'm going to disable that overnight as well.
Having the spare C7 hub help out and power cycle after the C8 shuts down leads to a painless experience...if I can't hear the announcements. If I do, I get curious, and next thing I'm on the phone checking on what went wrong in the early early morning.
Same error as noted abovem post-cloud backup.
2.3.7.140, C-8
edit: .140 is providing more error info, anyway, which is a good thing.
edit2: A subsequent manual cloud backup was successful.
Also, @bobbyD , it would be nice if a location event was added for this situation.
zWaveCrash doesn't kick off here.
I do a test for a trigger which involves a zWave device not reporting for more than 32 minutes.
It would be nice if something more timely, and foolproof, was available.
There is a cloudbackup event that, while it is actually a location event, is displayed in the Hub Events tab. It will show success or failure of the cloud back up, and if it failed what areas failed.
Don’t think it is available in RM yet, but I wrote a small notification app to trap it and kick out a notification.
Edit: included the code below for those not in the Beta group. Would be an easy add to set a switch or similar activity if desired.
Cloud Backup Notification
definition (
name: "Cloud Backup Subscribe",
namespace: "thebearmay",
author: "Jean P. May, Jr.",
description: "Subscribe to cloud backup event",
category: "Utility",
importUrl: "https://raw.githubusercontent.com/thebearmay/hubitat/main/apps/xxxxx.groovy",
installOnOpen: true,
oauth: false,
iconUrl: "",
iconX2Url: ""
)
preferences {
page name: "mainPage"
}
mappings {
}
def installed() {
// log.trace "installed()"
state?.isInstalled = true
initialize()
}
def updated(){
// log.trace "updated()"
if(!state?.isInstalled) { state?.isInstalled = true }
if(debugEnable) runIn(1800,logsOff)
}
def initialize(){
}
void logsOff(){
app.updateSetting("debugEnable",[value:"false",type:"bool"])
}
def mainPage(){
dynamicPage (name: "mainPage", title: "", install: true, uninstall: true) {
if (app.getInstallationState() == 'COMPLETE') {
section("Main")
{
subscribe(location, "cloudBackup", "cldBuHandler")
input "notifyDevice", "capability.notification", title: "Notification Devices:", multiple:true
}
}
}
}
def cldBuHandler(evt){
//log.debug evt.properties
if(evt.value != 'true' || evt.descriptionText.toLowerCase().contains('fail')){
notifyDevice.each {
it.deviceNotification("Cloud Backup Failed on ${hub.location.name}")
}
}
}
2 Likes
RM is usually @bravenel.
That's because it hasn't officially crashed yet, as far as the radio knows.
How long does that usually take?
I think I had to do the rule because zwaveCrash didn't kick off in this scenario, Zwave failure after cloud backup.
Just speculation, but think that the destinction is that when the backup fails the Zwave is briefly off and doesn’t turn back on.
Yet, there are location events for both zigbeeOn and zigbeeOff, and only for zwaveCrashed, which is less than responsive, and I would say, maybe even unresponsive, in this situtation.
