
So I dumped my Z Wave details into ChatGPT and it gave this explanation:
"Thanks—that dump is actually very telling, and it lets us move from guessing to something much more concrete."
The headline: your RF is fine
These three lines matter far more than the RSSI numbers:
- PER: 0 (Packet Error Rate = 0) across the board
- RTT Avg: 1–3 ms for most nodes
- Almost everything at 100 kbps direct
That is a textbook healthy Z-Wave network.
If your RF were genuinely degraded, you would see:
- non-zero PER
- RTT spikes (10–100 ms+)
- lots of route changes
- fallback to 40 kbps / 9.6 kbps
You have none of that.
So why does the RSSI look “wrong”?
The key clue is this pattern:
- Values range from 0 dB → ~39 dB
- Many direct nodes sit in the 1–10 dB range
- A few are much higher (20–40 dB)
- No correlation with performance
That is not how real signal strength behaves.
What you’re seeing is almost certainly:
LWR RSSI = “Last Working Route RSSI” (not raw signal)
On Hubitat’s newer Z-Wave stack, this value is:
- Taken from the last successful transmission
- Not continuously updated
- Influenced by:
- noise at that moment
- retries (even if PER ends up 0)
- device firmware quirks
- timing of last packet
So:
- A device that hasn’t talked much → stale/low value
- A chatty device → more “representative” value
- A sleepy 500-series sensor → often garbage values
Your “red flag” example explained
1m device ~45 dB vs 5m device <10 dB
Looking at your table, that fits perfectly with:
- High-message devices (e.g. powered switches, energy meter) → higher values
- Low-traffic or sleepy devices → low/near-zero values
Example from your data:
- Node 0x00e2 (Energy Meter) → 27 dB, 22,000+ messages
- Node 0x0066 (Kitchen Spotlights) → 8 dB, only 4 messages
That’s not distance—that’s data freshness and reporting context.
The real smoking gun
This line alone disproves an RF issue:
0x0009 (Garden Steps)
RTT Avg: 4ms, LWR RSSI: 1dB, direct 100kbps
If RSSI were truly that low:
- it would not sustain 100 kbps
- RTT would be much higher
- PER would not be 0
So that “1 dB” is clearly not physical signal strength.
What changed with the C-8 Pro
Even with “identical firmware,” you likely have:
- A newer Z-Wave SDK build or radio firmware
- Slightly different interpretation of LWR RSSI
- Less smoothing / more raw last-hop reporting
Result:
The old hub showed nicer-looking, averaged values
The new hub shows noisier, more situational values
What you should trust instead
For Z-Wave health, prioritise:
- PER (yours = perfect)
- RTT (yours = excellent)
- Route stability (yours = stable)
- Data rate (100 kbps = optimal)
RSSI on Hubitat (especially “LWR RSSI”) is:
diagnostic at best, misleading at worst
Bottom line
- Your network is objectively healthy
- The low RSSI values are not real signal degradation
- They are artifacts of how the new hub reports “last working route” conditions
If you want a definitive sanity check
Pick one “bad” node (e.g. 1–5 dB):
- Hammer it with commands (on/off 20–30 times)
- Then refresh stats
You’ll likely see:
RSSI jump significantly
with zero change in real behaviour