So a few weeks back I had major problems with my C8 which I resolved by completely trashing my z-wave and starting from scratch. I only have 6 z-wave devices so wasn't too bad. One thing I noticed at the time my z-wave devices stopped at pretty much the exact time my cloud backup ran.
Anyway everything has been humming along fine for two or three weeks now until last night when again my z-wave has become a big problem. Just like last time the time coincides with the cloud backup.
See below screenshots.
I'll admit my natural response would be... If the backup was the problem, then I expect we'd likely have a mutiny on our hands with many other Z-Wave users (not me) also experiencing the same behaviour.... Now, back to reality 
, in the end you are seeing what you are... but again, let's not assume like I normally do...
Like has been floated recently, I would suggest capturing some of the key aspects of your setup... e.g. What platform version are you running? etc...
I'd also suggest expanding on what you mean by:
What was working but then stopped working? i.e. what devices / drivers were involved? What routing devices (hopefully less important). What apps / automations are affected, how are they configured and what are logs for the devices and apps involved?
So the problem seems to revolve around a aeotec energy monitor gen5. When everything is 'humming along' there are no known or obvious problems. All devices respond and all apps do as they should.
Zigbee and z-wave mesh topology looks as it should with each z-wave device showing more than one neighbour. Then when the problem hits the energy monitor just stops completely and the z-wave mesh just shows each device directly connected to the hub but no neighbours.
Apart from that other stuff seems to work as do the other z-wave devices as far as I can tell. You'd kind of think that the energy monitor is faulty but I have an inline switch to the power source so I can just turn it off. You'd think in doing so the mesh would return to a previous state where devices see their neighbours but it doesn't. It just seems most odd that it works perfectly for a while and then when it does go bad it coincides with the nightly backup, to within a few seconds.
If you are seeing such a significant drop in comm's, the lack of comm's for one device is not likely to be an indicator of some cause for the issue, imho... i.e. the energy monitor device.
In my relatively inexperienced opinion in this space, I would start by listing some of the routing devices you are using in both your Zigbee and Z-Wave meshes. I get that is does seem odd for both of them to be affected at the same time.. that certainly does seem weird, but best to set the base-level info before leaping to conclusions (me included )
BTW, my time for offering assistance on this is quickly running out.... if i want to be an effective employee tomorrow.... Not that I won't offer any support in the coming hours... 
I would suggest capturing some of this base-level info before involving HE support if needed to better understand what may be happening.
This is a job for the Z-Man, @bcopeland .
This was a problem a while ago but has re-surfaced for me several times, including this morning.
I wrote about it in the section I can't talk about.
Needless to say, this issue is still hanging around, even in production.
So you can confirm that backup can affect z-wave?
Also I did a restore from the backup before the one that seems to have caused the issue and also selected to restore the z-wave radio. This has fixed it for now at least. I would however like to understand the underlying problem and know if it is fixable.
Yes.
There was a thread that culminated in a fix, but apparently, it still persists.
What is/was the fix and how many people does this affect, is it device specific? If so I think everyone would appreciate a bit of upfront honesty here from hubitat so we can at least be aware of any potential problems. For me with just 6 z-wave devices it's not such a big issue, some people have dozens of devices.
It was a change they made in the hub software.
As I said-it persists. It happened to me this morning again.
I am on that hub version I can't talk about, but not sure that makes a difference.
I'm on 2.3.6.146.
Other details may also be contributing to the issues being faced with both meshes being affected. I would zero in on a specific rule / automation to work out what the issue is likely to be....
You'd think you'd be good to go, but alas...
edit: I just saw that was for C-5. I think C-8 fix predated that.
Only z-wave is affected. It's sorted for the time being as the restore fixed it for now at least. I think we'd all like to know some more about this underlying issue though. If there us a known issue I think we should be told about it. I think a bug tracker within these forums would be a good idea.
Seems the issue goes beyond the C5. I wonder if the fix for the C5 is having the opposite effect on the C8. I think my problems only started after the last update.
As I said, this is a job for the Z-Man, @bcopeland .
That's good that it is resolved, if only temporarily...
They have introduced known issues in the current release, which I think is a goo inclusion, I can understand that maintaining that for historical versions could be complicated, and encouraging people onto the current platform version would be advanageous.
Or anyone else in the dev-team...?
I think as I don't have and changes to make at the moment or for the foreseeable future I will stop backups until this gets fixed.
Personally I would feel uncomfortable enough to engage with HE support to troubleshoot the issue, but if you are happy for someone else in the future to encounter what appears to be an uncommon issue and work through it then,... that's up to you... but who knows when that may get resolved... Which may include the need for multiple platform updates / backups....
Seems to me they are already aware of the problem. If they weren't they are now. If they want my assistance then I'm sure they'll reach out. Although I'm sure there are enough more knowledgeable people than me that are already involved in working on the problem.
1 Like
