Z-Wave smart plugs randomly dead after restart

Configuration Z-Wave
1

Yes, I saw posts about this before but none of them seemed to match what I’m seeing.

Here’s what happens…
Sometimes after I restart HA, some z-wave smart plugs are marked as dead. They’re rarely the same ones and don’t seem to be in the same area or even from the same manufacturer. Sometimes if I restart Z-Wave JS UI, the “dead” plugs come back. Other times, they don’t. Or some do but new ones end up dead. I seem to reliably be able to recover a “dead” plug by pushing the button on the plug itself.

I sure could use some help figuring out what’s going on.

I am using these versions:
zwave-js-ui: 11.8.2
zwave-js: 15.17.1

I’m running HAOS on a raspberry pi.
HA Core and OS are up to date.

2

its probably a bugg in the kernel if this is on newer devices on z-wave 700-800. for exempel on shelly wave 1pm, the firmware 11.10 made them reboot, in firmware 13.10 they died and had to be power cycled, this is fixt in the latest z-wave kernel. 14.99.00 fixes this in shelly, if your plugs state dead after a reboot is probably that the controller is checking the status after reboot, so they are probably dead before the reboot but the controller haven’t ping them. if its older pluggs running 500 series its probably a meash problem, or that the power reporting is set to high that ju have problems with que.

3

Thanks.
They are 700-800. I don’t have any really old ones. And I don’t think they were already dead. Prior to the reboot, I can still see them. They just appear dead after the reboot.

4

Go through these steps first.

5

I will take a look at this in more detail. However, overall my z-wave network seems very reliable. I never notice any flakiness. I would think that if I were having the issues described in that document, I would see problems during normal operation. Literally the only z-wave issue I see is the one I described.

6

that almost garati its the kernel bugg, that’s how my devices behave before updating the z-wav kernel.

7

I don’t know what you mean by “Z-Wave Kernel”. I believe I have the latest versions of z-wave JS and z-wave JS UI. Or, at least, HA is not telling me there is something newer.

8

its the firmware in the devices, if its 700-800 devices its a bug in the kernel, if you use a 500 controller this will probably stop the kernel bug from appearing, otherwise you need a firmware file from the producer of the devices. the problem is that not many producers have released the new firmware. I had to ask shelly support for a beta to fix the problem, when i talk to zooz support they say they will release the updated firmware early next year.

9

Oh, I understand now. I guess I missed that you were talking about the devices. I will look into that. Thanks.

10

I thought I would update this…
I just discovered today that I’m having some performance issues with HA. I’m running on a pi4. CPU, memory, and I/O performance are kind of maxed out. Now I’m wondering if this could be causing the issue. I’m in the process of figuring out how to migrate to a higher performance system.

1 Like
11

Absolutely. Zwave comms require quick responses from the controller (zwavejs) so if the CPU is maxed out, you’ll get dead nodes.

12

I’ve the same issue with Shelly’s Plug S(7.23.1) -going dead only after reboot and the come back after manual interaction.
It’s 800 series, and the are only going dead when I reboot zwave-js.
This doesn’t happen during normal operation, even over several weeks, but if I restart more often, I can provoke it more frequently in a short period of time.
So I’m not 100% sure that is only a firmware problem.

Now i’ve downgraded the plugs to 7.21.4 and I’ll see if it really is just the firmware.
Regards Olli

13

update to 7.23.4 the problem is in the kernel and is fixt in this firmware, go to shelly github and download the firmware if ha dosent show it.