Replies: 1 comment 3 replies
-
In your logs, you have a nearly 40 dBm fluctuation in background RSSI on multiple channels. With spikes around -74dBm. At times, those values appear to exceed the RSSI of the devices you're having issues with. My guess is your issue is related to interference going on? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is in:
I have a badly zoned heating system and control it from Node-Red by controller Z-Wave T6 thermostats.
I've had some flakiness occasionally but last night at about 9am UTC all four went "dead" at about the same time. Partial log extract:
The death and resurrection went on for quite some time. When I woke up (because the temp went from about 65 to 80 F in my bedroom), not knowing what was wrong, I restarted the docker image with zwavejs. This got most back but a couple continue to go dead and come back.
I happened to have logging at debug level enabled but the logs are massive. I am attaching a truncated portion of about 10 minutes, after the reboot, where two nodes (003 and 005) are dying and coming back.
Can I beg some help from those that understand the protocol and this software to give me a clue what is causing this?
This is a new problem: I searched logs before last night though, and have zero records where these were marked dead. The first instance began at the T09:07 time above. I was fast asleep, and there was nothing I could see that might cause it (no storms, no power failures per my UPS, etc.). The only thing I know is when the heat comes on, soon after as temperature sensors change, Node-Red is sending a lot more updates to the T6's (basically it just refreshes the proper state (heat, cool, setpoints) everytime something changes). But it's been doing that for months -- if it's a volume issue no idea why it just happened last night.
As of this moment 75 minutes has gone by since the last "dead", and 3 hours for one (Node 011) and four hours for another (Node 013).
I can't think of anything that preferentially impacts one vs the other (when I send updates, I update all four together, so they get exactly the same number of updates sent from Node-Red).
I'm hoping there is an indication of what causes this in the logs. With apologies for how thick they are, and appreciation in advance, if someone could look it would be great.
The USB stick is a ZST39LR 800 series from Zooz, and this is all running on a rPi 3B with Ubuntu 24.04.01 (current).
Linwood
zwavejs_2025-02-04.log-Truncate.txt
Beta Was this translation helpful? Give feedback.
All reactions