Thanks, took a look at your hub's engineering log and it looks like you had an app stuck in a schedule loop, but that is clear now and the hub appears in good shape.
The problem might just be with the stick. There is nothing at hub level to indicate that you have any systematic problems.
but after its restarted it has 0 issues.
and the issue only started after the update.
You mean Room Lighting? That was in the previous release, 2.3.2.
I wonder if you have a device or an app that is going whacky? If you go to App Stats and Device Stats in the Logs tab, does anything stick out as using a lot of processor time?
Anything in your logs just before the time it quits? Errors? Warnings?
Backup before restoring the prior firmware version.
If the problem persists, it’s not the firmware update anyway. So restore your most recent backup that includes the work you’ve done with room lighting (assuming that’s the app you’re talking about).
That doesn’t necessarily mean that one thing caused the other. Only way to test out that theory is to restore a backup from before the upgrade, as others have suggested.
2 Likes
Continuing the discussion from Rev c4 z-wave 2.3.3.122:
all the zwave devices seem to register at the time of the nightly that the hub does, and then Not respond after that.
do i restore to 233.122 or 232.141
and after reboot - works no issue.
time stamp bottom right to verify
there is nothing in the system alerts saying any excess load is on the hub or extra devices.
@marktheknife @bobbyD The last time ive needed to even login and touch the hub/its settings was the 1st of april 2022. I have changed nothing and done nothing since then. Thats how i know its the update that has borked something.
I am suspicious of your Aeon Multi 6a (0x03). It has been a long time since I studied the earlier routing tables, but there are no clusters, and those Device Type and Device ID look wrong, like there is corruption or some issue with the Zwave mapping. If this is the same device as your 0x05, shouldn't the Device ID/Type be identical? Compare your extenders and how they are the same ID and Type.
Maybe. But maybe not. You’ve identified a correlation, the way to verify that one thing caused the other is to revert.
Whichever version you upgraded from, when the devices were working as expected.
2 Likes
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.
