Sudden ZW Change to Background RSSI

[GrizzlyAK]

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

What is happening?

So I haven't actively been managing my ZWave NW for a while, since I haven't modified it in any way during that time. I have noticed as I've upgraded over that time a general degradation in "responsiveness" of my ZW devices (lights slow to respond, door sensors slow to update, etc.), even after updates and full system reboots. Exploring today, I noticed this Background RSSI chart in the ZWUI and didn't know what to make of it and wanted to ask how to interpret it. I'm assuming that "Background RSSI" is noise/interference levels, not signal strength between two nodes (which appears on the legs between in the spider graph). In that case, a low BG RSSI is good, right? What I'm wondering about is what happened (or could have happened) at about 11:00 AM in the attached chart that produced such a change? At the time, I was tinkering with a node it showed as failed (red box), even thought it showed as OK in the ZWUI control panel display. I've confirmed that HA is seeing updates from the device (it's not failed).

I have NOT yet done a NW reinterview since that takes a long time on my network with so many battery devices. But I have a good number of 3-4 hop paths and even some 9.6 kb/s connects.

Controller: Aeotec Z-Stick Gen 5+

I'm just looking for some advice or possible explanations of what could be going on here before diving into the logs. Thanks.

Software versions

Driver (node-zwave-js): 12.4.4
Z-Wave JS UI: 9.9.1
Home Assistant Z-Wave Integration: 1.33.0
Home Assistant Z-Wave JS Addon: 3.4.1 (I don't use this)

Device information

Manufacturer: ...
Model name: ...
Node ID: ...

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

No response

[zwave-js-bot]

👋 Hey @GrizzlyAK!

Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues.

Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one:

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