Yes.
To expand a bit on this, there is some work in Beta regarding a whole slew of Z-wave issues.
I am not sure if every Z-wave issue will get solved in this Beta, or whether the fixes will even apply to all hub versions, but in general, this is on the radar of Hubitat staff.
To try to add a little more information, I don't think cloud backup is the issue, I think cloud backup is just the tell-tale sign..
I had my Z-Wave "freeze" (?) at around 2pm and I had to shut down, unplug, and plug back in to get the Z-wave to come back.
Makes me wonder if it's more of a Z-wave controller issue, rather than a cloud backup related issue.
Cloud backup may not be your specific issue, but cloud backups are most certainly an issue that causes the zwave radio to go offline at times. That has already been verified and proven.
You might update to 2.4.1.151 and switch to z-wavejs and see if it helps. It's been pretty solid for me..
I was replying to @dvdptr1
Unfortunately, i have a C8 as well. Not a pro...
That was a snip of his post.
Doesn't mean I wasn't replying to him and not you
Oy
So, not sure if this is helpful, but, I just had the backup/z-wave failure again last night (in case failure rate/timing may help in any debugging). Once again, physical hub shut down and unplug seems to have restored the functionality.
And as a reminder, I can't use the new Z-wave JS option as it only seems to work with a C8pro, and I have a C8.
I have at least one zwave crash each week. I trap the event with a RM rule, turn on a virtual switch, then from a second hub when that swtich turns on it sends a shut down, waits, turns off the matter plug behind the hub, waits, turns it back on - and zwave is back online.
I've had 3 separate z-wave radio offline/crash events in the last 10 days, I've coded a shutdown-power off-turn on sequence inside HomeKit with the help of a HomeKit plug attached to my C-7. While that works, these events do seem to be happening much more frequently (after a 3-4 month break from these issues). Not sure if the latest code is the issue?
Another failure today. From the Hubitat event log:
cloudBackup Failed steps: Z-Wave FAILED 5/21/2025 2:21:27.606 am
Just an observation... but, this thread was originally posted in August of 2023, and from what I can tell, the only solution/work around offered to date was to switch to Z-Wave JS to see if that works, but it can only be done on a C-8 Pro, which wasn't released until Jan, 2024.. So, those of use with the OG C8 are kinda out of luck...
if a C8 Pro is the solution, should there be an upgrade path to a C-8 Pro, rather than just buying a new one for $200?
Thank you for your observation and for revisiting this thread. To clarify, the issue isnāt hardware-relatedāitās likely a timing-related issue introduced by the additional Hub Protect service layer, not a limitation of the C-8 hardware itself. The C-8 continues to function as expected, and the behavior you're seeing is not due to any hardware fault or deficiency.
While Z-Wave JS was mentioned as part of the troubleshooting process, it wasnāt presented as the only workaround, nor is the C-8 Pro required for resolution. That said, the C-8 Pro does offer some advantages in handling certain edge cases more gracefully due to its newer architecture, but again, is not a requirement for resolving this issue.
Our engineers have resolved most of these edge cases but if you continue to experience backup failures on regular basis, weād be happy to offer you a full credit of the cost of your Hub Protect serviceāup to 30% of the C-8 Pro's listing priceātowards replacing your existing C-8 with a C-8 Pro. If you're interested in this option, please create a subscription case by visiting the following page: Subscriptions ā Hubitat Support
We do appreciate your feedback on upgrade options and understand the sentiment.
Hi, @bobbyD, i appreciate the candid information sharing... I am still confused how a timing issue requires a full power disconnect to correct, and have it not be at least partially hardware related....
I have been trying to watch all of the release notes to see if a fix is included with each update, but haven't much in the form of changes related to the issue outside of the Z-Wave JS... And as my last occurrence was on 5/21, my hub must be one of the more remote edge cases, or maybe I have too many 3rd party apps running that is (favorite word incoming!) exacerbate the issue within my hub...
I really appreciate the Hub Protect rebate towards the Pro, but, I'm a bit reluctant not knowing if that will definitely address the issue. I know myself, and I'd be very frustrated to go that route and find out that the problem persists...
And, unless I have just missed the option, the only way to do an automated, off-box backup is via cloud backup. I can create automatic local backups to the box itself, but then have to manually go in to download them to store them off box.
One of my biggest concerns is, should something short out on the box and I have to start from scratch (or from an old backup), it would take a couple weeks to get everything back (resetting and repairing devices, rebuilding automatons, reestablishing external apps (Hue, Govee, etc.), etc. So, the backup is super important to me.
I currently have a Home Assistant hub set up as well (to support the RATGDO and devices that HE doesn't directly support), and I'm debating moving stuff (at a minimum, the Z-Wave) to HA, and relying on the HE/HA bridge to get things back into HE. Seems like a lot of work to do it, but, it's very frustrating for the other members in my house to have half the devices stop working until I can shut down, unplug, and restart my hub..
It'd be really nice if alerts got pushed as a mobile app notification so I don't have to do a connect-to-hub to check.
Overall correct, but you can setup automated ways to pull local backups off your hub. But to restore to a new hub you really want a cloud backup to avoid having to deal w/getting all your devices fully restored.
You are one of the remaining unforunate edge-cases w/the backup crash. I got one a few months back (first in a very long time) on a C7, and do the following to ensure I can always restore a full cloud backup to my current or replacement hub:
Not ideal, but not a big deal either, so I've been managing it w/above process.
My hub is also on a wi-fi plug (that also has cloud-capability) so I can always power cylce my hub if I need to, either after I remotely shut it down via Settings, or hard power cycle if something went badly wrong.
The timing issue is related to a cloud backup failure, not for the fact that radio is frozen. The freezing of the radio as result of a cloud backup has been resolved. But the same symptom may occur in certain conditions like excessive power reporting that may coincide with the timing of the cloud backup. In fact, that could itself cause the backup to fail.
This post, for example talks about freezing radio and is from 2022: Dos and Don'ts of Z-Wave Power Reporting (repost)
Seems "contrary" to have to do manual backups of my home automation system... LOL
Download the Hubitat app
