Twice since upgrading to 2.3.6.144 Zwave disappears overnight

🛎️ Get Help Devices
1

Previously running 2.3.5.141 on my C5 hub and had 100% no issues with either zwave or zigbee in months other than the Life 360 issue with login lately.

A few days ago updated to 2.3.6.144 and the next morning when opening our pantry door found the light didn't come on, investigating I noticed in the hub all zwave devices were gone and not showing up under zwave details. I ran the repair, they showed back up and all was good till last night again.

Woke up this morning the bathroom light did not come on, went into settings zwave details page all zwave devices were gone again. Ran the zwave repair and all devices showed back up again. I notice when the repair is done each time, it has entries for device 33 only this is the wall unit dimmer that is powered by AC and never shows other devices. Is this telling me something is wrong with it possibly or something else with the software on the C5 hub? Thoughts

2

Zwave crashed which sometimes happens after major updates.
You need to do a shut down of the hub, remove power for around 20 seconds, then power back up.
That will fully discharge the zwave radio and allow it to reboot.

Should be back to normal after that, if it keeps on crashing then you have something else going on with devices that is causing it.

3

I did the power done and wait for 30 seconds the first time, I would think if a zwave device was causing the issue it would have acted up before the upgrade not just after the upgrade.

4

:person_shrugging:
Just went through this with another user and he found that each crash was after a certain sensor reported in the temperature. He excluded and reincluded that sensor and it fixed it. You might have something similar going on. Do you happen to have any Aeotec MS6 devices?

1 Like
5

Do not have any of those devices at all. The only common things I've seen is so far it happens at night between midnight and 330am when I get up for work. And its only the zwave devices this affects.

I've just reset the hub and let it sit again for a full minute. We'll see what happens in the next few days now. I'll pay attention to what reports during the time frame if it happens again.

6

From my logs last night

10/16/23 zwave devices missing from zwave page

Last time zwave was active is when wife went to bed at 2am, she went into the mcloset and triggered motion sensor, that turned on the zigbee bulbs then went to the master bath and trigged the mtoilet motion that turned on the zigbee bulbs.

At 345am I got up for work, went to the bathroom saw the mtoilet sense I was there but it did not turn on the zigbee lights went to the dashboard and manually turned on the master bathroom lights and master closet lights and they worked fine

logged into hubitat page and went to settings/zwave settings and page was empty. Ran zwave repair, all devices showed back up. shut down hub for 1 min, then turned back on and everything is working. (everything was working before shutdown as well after doing zwave repair)

The last zwave device triggered was the hallway temp gauge at 315am when it reported its temperature

dev:4512023-10-16 03:58:33.348 AMinfoMCloset Light 2 was turned off
dev:4502023-10-16 03:58:33.299 AMinfoMCloset Light 1 was turned off
dev:2362023-10-16 03:58:32.271 AMinfoMaster Closet lights switch was turned off
dev:4512023-10-16 03:58:26.887 AMinfoMCloset Light 2 was turned on
dev:4502023-10-16 03:58:26.839 AMinfoMCloset Light 1 was turned on
dev:2362023-10-16 03:58:26.809 AMinfoMaster Closet lights switch was turned on
dev:2442023-10-16 03:58:24.599 AMinfoMToilet Light 2 was turned off
dev:2312023-10-16 03:58:24.577 AMinfoMToilet LIght 1 was turned off
dev:2352023-10-16 03:58:23.491 AMinfoBathroom lights switch was turned off
dev:2352023-10-16 03:58:14.553 AMinfoBathroom lights switch was turned on
dev:2442023-10-16 03:58:14.489 AMinfoMToilet Light 2 was turned on
dev:2312023-10-16 03:58:14.465 AMinfoMToilet LIght 1 was turned on

Here is where I triggered the mtoilet motion but nothing happened, went to the dashboard and manually turned on the mtoilet lights and closet lights and turned back off

dev:742023-10-16 03:58:07.630 AMinfoLaundry door is inactive
dev:742023-10-16 03:57:57.964 AMinfoLaundry door three Axis is [x:-1010,y:32,z:29]
dev:742023-10-16 03:45:32.077 AMinfoLaundry door temperature is 80.93°F
dev:2122023-10-16 03:21:06.703 AMinfoPantry Light 2 color temperature is 5000°K
dev:2122023-10-16 03:21:06.700 AMinfoPantry Light 2 color is Horizon

dev:4492023-10-16 03:15:46.983 AMinfoHallway Temp-Humidity: Temperature is 80.2°F

dev:2432023-10-16 03:07:53.123 AMinfoMToilet Motion : temperature is 59.0
dev:1902023-10-16 03:02:31.567 AMinfoPatio light saturation is 100%
dev:1902023-10-16 03:02:30.063 AMinfoPatio light hue was set to 0%
dev:1902023-10-16 03:01:16.917 AMinfoPatio light colorTemperature is 2702°K
dev:742023-10-16 02:58:01.613 AMinfoLaundry door is inactive
dev:742023-10-16 02:57:51.679 AMinfoLaundry door three Axis is [x:-1010,y:32,z:29]
dev:4492023-10-16 02:56:56.599 AMinfoHallway Temp-Humidity: Humidity is 32%
dev:1402023-10-16 02:54:25.299 AMinfoWSensor WHeater temperature is 83.83°F
dev:4492023-10-16 02:46:01.926 AMinfoHallway Temp-Humidity: Temperature is 79.6°F
dev:1002023-10-16 02:38:52.293 AMinfoPatio door battery is 99%
dev:2432023-10-16 02:37:27.762 AMinfoMToilet Motion : temperature is 56.9
dev:742023-10-16 02:33:24.602 AMinfoLaundry door temperature is 80.03°F
dev:4492023-10-16 02:27:11.683 AMinfoHallway Temp-Humidity: Humidity is 32%
dev:1412023-10-16 02:26:34.907 AMinfoWSensor Attic temperature is 73.03°F
dev:2462023-10-16 02:25:46.792 AMinfoWSensor Refrigerator temperature is 80.80°F
dev:2122023-10-16 02:20:59.685 AMinfoPantry Light 2 color temperature is 5000°K
dev:2122023-10-16 02:20:59.675 AMinfoPantry Light 2 color is Horizon
dev:4492023-10-16 02:16:15.788 AMinfoHallway Temp-Humidity: Temperature is 80.5°F
dev:2432023-10-16 02:07:02.942 AMinfoMToilet Motion : temperature is 59.8

dev:4512023-10-16 02:05:57.493 AMinfoMCloset Light 2 was turned off
dev:4502023-10-16 02:05:57.446 AMinfoMCloset Light 1 was turned off
dev:992023-10-16 02:05:53.030 AMinfoFront door battery is 99%

dev:2442023-10-16 02:04:26.987 AMinfoMToilet Light 2 was turned off
dev:2312023-10-16 02:04:26.855 AMinfoMToilet LIght 1 was turned off
dev:1902023-10-16 02:02:40.919 AMinfoPatio light saturation is 100%
dev:1902023-10-16 02:02:39.409 AMinfoPatio light hue was set to 0%
dev:2432023-10-16 02:02:25.464 AMinfoMToilet Motion : motion is inactive
dev:2432023-10-16 02:01:59.838 AMinfoMToilet Motion : motion is active
dev:2432023-10-16 02:01:51.044 AMinfoMToilet Motion : motion is inactive
dev:2432023-10-16 02:01:35.108 AMinfoMToilet Motion : motion is active
dev:1902023-10-16 02:01:26.243 AMinfoPatio light colorTemperature is 2702°K
dev:2432023-10-16 02:01:24.720 AMinfoMToilet Motion : motion is inactive
dev:1922023-10-16 02:00:56.166 AMdebugMotion inactive
dev:2432023-10-16 02:00:40.706 AMinfoMToilet Motion : motion is active
dev:2432023-10-16 02:00:34.106 AMinfoMToilet Motion : motion is inactive
dev:1922023-10-16 02:00:19.673 AMdebugMotion active
dev:2442023-10-16 02:00:18.706 AMinfoMToilet Light 2 was turned on
dev:2312023-10-16 02:00:18.649 AMinfoMToilet LIght 1 was turned on
dev:2432023-10-16 02:00:18.381 AMinfoMToilet Motion : motion is active

dev:1922023-10-16 02:00:00.131 AMdebugMotion inactive
dev:4512023-10-16 01:59:32.420 AMinfoMCloset Light 2 level was set to 5%
dev:4502023-10-16 01:59:32.372 AMinfoMCloset Light 1 level was set to 5%
dev:4512023-10-16 01:59:26.447 AMinfoMCloset Light 2 was turned on
dev:4502023-10-16 01:59:26.376 AMinfoMCloset Light 1 was turned on
dev:1922023-10-16 01:59:26.102 AMdebugMotion active

7

Check Logs > Hub Events, to see if it says anything about zwave crashing. I think thats where it logs it, check Location Events also just in case.

You could also do a backup / restore to rule a database issue out, although it does not usually impact Zwave like that. You just download a local backup and then restore it right away which will clean up any database corruption.

8

Just reviewed the hub events, nothing except the 13 and 16 when I had the issue and shutdown the hub and restarted it. Will monitor and on the next occurrence try the restore of the DB to see if this stops it.

|systemStart|System startup with build: 2.3.6.144|2.3.6.144||10/16/2023 04:26:17.530 am|
|systemStart|System startup with build: 2.3.6.144|2.3.6.144||10/13/2023 04:25:01.186 am|
|systemStart|System startup with build: 2.3.6.144|2.3.6.144||10/11/2023 04:42:25.528 pm|
|update|Updated with build: 2.3.6.144|2.3.6.144||10/11/2023 04:40:24.398 pm|

9

When is your backup set for and did you get a good one that night?

10

Oh might be onto something here, 3:15am is when the backup happens and its every three days. Lockup today 16th and before 13th

I don't see anything different in the backup last night than one done when the zwave didn't disappear on me but then again its only done 2 since the upgrade as I have it scheduled for every three days

I've turned off all backups for now to see how the next few days go, then will turn on local only for daily and test and see if I get the lockup or not. Besides restoring a DB for possible corruption any other suggestions of going down this road?

Manual backup locally seems to work fine and I don't see the zwave devices disappear

11

Might ask @gopher.ny if he'll take a look at the engineering logs. Pretty sure he was trying to shake a lasso at a similar issue a while back.

12

@gopher.ny not sure you want to take a look at this, the last two backups at 3:15am seem to remove all zwave devics possibly and I have to rebuild zwave network for them to show back up and work. Right now I have backups turned off to verify this but since the update to latest, its happened both times it backup locally and to cloud. Thanks

13

Yes and it was only during cloud backups that would crash zwave. I thought he had it fixed? So this might be a different but very similar.

14

I've heard via PM from another user that they had the same issue and turning off the cloud backup will stop the issue from happening. They've stated it should be resolved in the next release. For now I've turned off backups and will go from there.

15

Like @jtp10181 said above, I thought it was fixed in this release? There was a fix put out and tested in Beta. So is this something different than what was fixed?

16

I'd suggest you stop doing all the repairs when your devices disappear... Just do the shut down\restart. If that doesn't restore your Z-Wave devices that would be good to know.

The bug was with cloud backups, and was thought fixed in a recent release, 2.3.6.134, but recently HE staff noted that there may be a small number of people still affected.

If you're doing local backups and this issue is related to that, then this is different. If you're doing cloud backups the this could be some special case related to that issue that the fix didn't cover, or it's something new.

Can you clarify if you have subscribed to Hub Protect and are doing cloud backups or local?

@gopher.ny looking at your logs could be good. PM him your hub UID so he can access them if necessary.

17

I do have hub protect, I am doing local and cloud backups every three days and its failed in both instances at the three day mark at backup. I have turned off cloud backups and just using local backups now. Its scheduled either tonight or tomorrow to do a local backup so we'll see what happens then

18

Perfect, thanks for confirming.

19

Local backup worked fine last night and all zwave devices are working after

2 Likes
20

Updated to the .146 build for the backup fix and this morning all was good. However I'm curious why the backup size is half of what it used to be. Was always 1 MB in size for backups now 556 KB

Image3
Image3973×374 64.1 KB

2 Likes