i've rolled back to 2.3.2 and see what happens tomorrow morning.
1 Like
That's an easy enough test. Change the backup time and see the time the devices stop functioning follows ......
ive already rolled back - so I will see what happened on this version first.
1 Like
woke up this morning, on 2.3.2 - all lights working as previously stated.
As reported, 2.3.3 @bobbyD has an issue.
1 Like
Last time we checked, there was nothing in logs to explain the problem. If you update to latest release and the hub is locking up again, check your logs for warnings and errors.
The hub is Not locking up.
The zwave devices (remotec, aeotec, fibaro), after the nightly backup stop working.
So if I:
- Update my hub
- Have the same issues
Your saying its my hardware, not the software... even though reverting to the older software and it shows no issues ???
Thats what I never get about hubitat staff on these forums.
I show an issue, have proof of the issue, contact you regarding the issue, get no help to resolve the issue.
Its all well and good to get the community to try and help me - but theres an issue in 2.3.3 for C4 hubs running zwave devices - all list on your website as compatible devices..
So - @bobbyD what do I do ?
update the hub and post back the results ?
buy new hardware to fix something that works on 2.3.2 ?
just accept that I am now stuck on 2.3.2 and cant update my hub anymore ?
Like I said, the last time I even had to touch my hub was april this year and ive been stoked with that. But there Is an issue in 2.3.3 that needs to be fixed.
This.
When hundreds of C4s updated to 2.3.3 and their Z-Wave devices work as expected, the only thing that you could do, is helping us figure out why your hub behaves differently. Without any errors in your logs, or ways for us to replicate the problem in our testing environment, it is imperative for the user to provide us sufficient details of what is going on locally, otherwise we are totally blindfolded.
5 Likes
Whatever the underlying problem is, I'm sure this must be frustrating for you, so I hope you're able to get to the bottom of the issue.
But your claim that something is wrong with the latest hub firmware with respect to C4 hubs is still not supported by the evidence you've shared here.
Your testing so far does appear to narrow down your problem to the update you applied to your hub, if the issue indeed resolved when you reverted to a prior firmware. But it still doesn't demonstrate that the problem lies in the new hub firmware itself. As Bobby said, many other C4 users would presumably report something similar after upgrading, but apparently they have not.
Perhaps some sort of hub database corruption occurred around the time you applied the update, and reverting to the previous firmware version cleared that corrupted database. I don't actually know exactly how the firmware reversion process works, I'm simply suggesting plausible alternative hypotheses to yours, which is that:
Good luck working through this. Troubleshooting effectively can be a meticulous process before the true underlying issue is identified.
I would still be concerned about the device with no in and out clusters and seemingly out-of-range values for Device id and Device Type. Would this not be an indicator of potential corruption? The entry for 0x03 is very different in appearance from 0x05 and 0x06 which appear to be the same type of device.
1 Like
Which radio stick do you have connected to the C4?
1 Like
so my question again is, what do I do ?
Stock one that came with the hub originally.
I think he meant brand/model of stick. There were a couple variations if I remember correctly.
1 Like
ah right - I can check when I get home for this.
It would be in the settings or on the actual stick ?
This. I would suggest attaching a photo of the stick. You had probably had two sticks - one for each z-radio.
1 Like
yep - the one is attached directly and the other has an extension.
Both sticks on 2.3.2 are working though - so it feels like a dead end there.
