Z-Wave JS device stops communicating after a few hours

Un4Seen · January 1, 2022, 9:41am

Hi!

A few days ago I have updated HA (core, supervisor, OS, etc.) from 2021 March versions to the latest 2021 December versions and migrated my Z-Wave devices from the deprecated Z-Wave integration to the Z-Wave JS integration.

I have a total of 9 Z-Wave devices in my network. Ever since the updates and Z-Wave JS migration one of them stops communicating after a few hours. It is an Aeotec Home energy Meter. This one measures the electric energy consumption of half of my house, so it’s pretty disturbing that after a few hours it stops sending data. I have another such Aeotec Home Energy meter for the other half of my house, that one works fine. Also this problematic one worked just fine before the updates and migration to Z-Wave JS.

When the communication stops, the only way to fix it is to go into the Z-Wave configuration of the device and change one of its Z-Wave parameter values. This action “wakes it up” (it’s not battery powered, so it does not actually sleep). Rebooting or restarting HA does not fix it. Healing the Z-Wave network does not fix it. Healing this specific device does not fix it.

Does anybody else experience similar problems in their Z-Wave network? Any idea what I could try to fix it?

Thank you!

HA Core version: 2021.12.7
Supervisor version: 2021.12.2.
HA OS version: 7.0
Running on Raspberry Pi 4.

Prodigyplace · January 1, 2022, 10:35am

If you are using a 700 Series controller that may be the issue. Silicon Labs, the firmware vendor, is working to determine the cause.

github.com/zwave-js/node-zwave-js

🚧 META-Issue: Problems with 700 series (healing, delays, neighbors, ...) 🚧

opened 03:56PM - 15 Dec 21 UTC

AlCalzone

It seems that **700-series sticks** (including the currently latest firmware 7.1…7) have some problems which mostly appear on networks that: * are relatively busy (lots of unsolicited reports like motion sensor, power meters) * are large and/or * contain some battery-powered devices When lots of reports reach the controller in a short time, the 700-series sticks are not able to send any message. It looks like the stick is somehow blocked and simply doesn’t send anything, maybe not even the protocol level acknowledgements for receiving the messages, causing end nodes to repeat their messages over and over, making the situation even worse. ### We're working with Silabs to get to the bottom of this. Please don't open any further issues. --- We believe the following symptoms are all caused by this: - Huge delays (up to 60 seconds) when sending messages - Failure to send anything (`TransmitStatus: Fail`) - Floods of incoming reports that are transmitted over and over - Incorrect neighbor information (e.g. controller doesn't list some/any nodes as neighbors, etc.) - Failure to heal the network or individual nodes, especially in busy situations --- Additional background info: https://forums.homeseer.com/forum/homeseer-products-services/homeseer-z-wave-products/smartstick/1483440-does-anyone-have-a-solid-working-g3-system-at-this-time/page4#post1510687

Un4Seen · January 1, 2022, 12:15pm

Thanks!

I’m using a Z-Wave Vision USB stick, no idea what series the controller in it is. One thing is for sure, it was working well with the old (deprecated) Z-Wave integration and before the HA updates, so it can’t just be the controller’s fault, perhaps a compatibility problem with Z-Wave JS? But then why are all other Z-Wave devices in my network working fine? Why does it affect only this one Aeotec Home Energy Meter and not the other one too? Very strange…

Here is another link to the Vision Z-Wave USB stick details.

this is what it looks like:
VisionStick

Prodigyplace · January 1, 2022, 12:38pm

OK it looks like a 500 Series ( Z-Wave Plus) controller so that is not your issue. It is strange they are not using the Z-Wave Plus logo though. That link I posted does not affect you.

You could try starting a discussion on the node-zwavejs GitHub repo The developers there are very helpful.

Un4Seen · January 1, 2022, 12:54pm

Thank you for your help!
Yeah, I guess I’ll try GitHub then.

There’s one other thing I could try… to factory reset the Aeotec Home Energy Meter which is having problems… not sure if it would solve anything, but might be worth a try…

Prodigyplace · January 1, 2022, 1:32pm

That could be worth a try. Exclude it from the network first. I habe some cheap Chinese devices that do not seem to include properly unless factory reset first.

If the device is using any Z-Wave security, it must be freshly factory reset before inclusion The inclusion process, once started must be completed within 11 seconds, I believe. Some people find the device needs a stronger than normal signal for successful secure inclusion.