Single defective zwave node can flood complete zwave network

[mgugu]

My ozw network/50 nodes was running silent for many years.
Yesterday it appears that nothing was working anymore in the zwave network.
ozwCP seemed OK, few errors in the log, zwave messages were received but not sent.
I unplugged z-stick and put it on another machine running docker/zwave2MQTT in log mode.
All nodes were discovered but the interview never finished. In the log window, one can see permanent error messages concerning the same node, a Nodon Smart Plug.
I unplugged the Nodon smart plug, deleted it in the z-stick and magically everyting went OK again.
So what I leaned is that a single defective zwave node can flood complete zwave network.
OZW was not the culprit. In fact in my opinion ozw core works very stable, only some troubleshouting features are missing.
But for new installation I recommand zwavejs2MQTT much more flexible and friendly
Hope my feedback can avoid some nightmares to ozw users

[solarboy]

Yep, I had this with a Fibaro Rollershutter2. Luckily resetting and re-including the device cured it.

[user4563]

I have seen this with the older Z-Wave (non-plus) networks. The newer Z-Wave plus have a lot more bandwidth and haven't seen it yet. What is yours?

[mgugu]

My AEOTEC z-ztick is of first generation (2015) so non-plus and not upgradable.
In my case also, resetting the node and including it again make the problem disappearing so finally it was not defective. I do not understand what can make the network to enter in such a fatal loop.
In the past I had a similar problem at 433 MHz with a RFX Oregon Rain sensor which transmitted permanently and jamming the complete Network. But it was irreversible in that case