Zwave network becoming increasingly unreliable

[Maes152]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

My Zwave network is becoming increasingly unreliable over the years. I have opened several issues in the past regarding this:

• One in 2022
• One in 2023

In summary, when I attempt to operate a larger number of devices (>=12) simultaneously. Things tend to go wrong.

I've been living in this house now for about 12 years and have had increasing issues for the last 2-3 years. Most importantly, I have 12 shutters that were all connected with a Fibaro FGR222 (roller shutter 2). These were all connected without security. My controller used to be an Aeotec Gen 5.
Every day, the shutters will all open in the morning and close in the evening. When they close, also some zwave lights will turn off.

Things I've tried:

• Aeotec Gen5 connected to an usb extension cord and hung high up on the wall
• Switched to a Z-Net G3 R2 700 series. Using over IP, the controller is now situated dead centre in my house. I heard this device had the best range and reliability so decided to purchase.. I'm based in Europe and had to import this device + duty fees, cost me over €200. Changed absolutely nothing.
• My oldest zwave modules were the Fibaro FGR222, I recently swapped them all out with 12 new Shelly Wave Shutters (zwave 800) and paired them using smart start on S2 Authenticated security. If anything, this is now even more unreliable. The shellys have a knack of reporting a state change when nothing happens in reality. The shutter will indicate to be closed but it's actually still open. At least the Fibaros would just time out and do nothing. The state would still accurately reflect their position...
• Setup priority routing: I've noticed that modules that are directly next to the controller will prefer to hop once or twice to different nodes before going to the controller. Completely nonsensical. Unfortunately even with priority routing the behavior is not improving.
• Tried using multicast instead, always gives a ton of errors about timeouts on all different kinds of nodes, see included log

Only idea I've got left is to wait for Nabu Casa's new controller coming out and hoping that fixes everything..

I'm very invested in zwave, have been for over 10 years and spent more money on this than I care to admit. Even recently I've spent hundreds of euros trying to get things to become more stable and it's only becoming worse. I'm really at my wit's end..

Please ignore the dead node, I've disconnected it myself 2 weeks ago.

Software versions

zwave-js-ui: 9.27.8
zwave-js: 14.3.7

Z-Wave Controller (Stick/Dongle/...)

Z-Net G3 R2 Version 1.0.25

Device information

Many nodes show intermediate issues, mostly the:

• Shelly Wave Shutters (nodeIDs 046 to 053 and 063 to 068). All on FW 12.23.0
• Sunricher ZV9102FA-CCT (nodeIDs 057 & 058) All on FW1.5

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

driver log zwavejs.txt

[zwave-js-bot]

👋 Hey @Maes152!

It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS.

Please double-check that you uploaded the correct logfile. If you did, disregard this comment.

As a reminder, here's how to create one:

• Z-Wave JS UI
• Home Assistant Z-Wave Integration
• ioBroker.zwave2 Adapter

[Maes152]

zwave-js-ui-store.zip