#RSSI Value missing

1 messages · Page 1 of 1 (latest)

calm flame
#

I have Sensative AB door open/close sensor that is working but the RSSI value has gone missing in HA. It's being sent, I see it in the JSUI logs, and it used to be work, I see it in history. Any ideas?

versed garnet
#

How are you able to see the history if it's missing?

calm flame
#

"and it used to be work, I see it in history."

versed garnet
#

Maybe I'm doing something wrong, but I can't see non-existant entities in history.

#

the entity picker doesn't give me the option for those entities

calm flame
#

It's not that complicated It used to have value, and now it's unknown

versed garnet
#

Perhaps you should have said that in the first place.

#

words matter

#

what version of ZUI are you using?

calm flame
#

zwave-js-ui: 10.5.0
zwave-js: 15.4.1

versed garnet
#

driver v15.4.0 had a related fix. either it hasn't fixed for you, or the device isn't reporting valid values.

#

see if you are getting any errors related to RSSI in the HA logs

calm flame
#
2025-05-15 12:20:58.371 CNTRLR   [Node 022] [~] [Notification] alarmType: 0 => 0                   [Endpoint 0]
2025-05-15 12:20:58.372 CNTRLR   [Node 022] [~] [Notification] alarmLevel: 0 => 0                  [Endpoint 0]
2025-05-15 12:20:58.374 DRIVER « [Node 022] [REQ] [BridgeApplicationCommand]
                                 │ RSSI: -56 dBm
                                 └─[NotificationCCReport]
                                     notification type:   Access Control
                                     notification status: 255
                                     notification state:  Window/door is closed
2025-05-15 12:20:58.375 CNTRLR   [Node 022] [~] [Notification] Access Control[Door state (simple)] [Endpoint 0]
                                 : 22 => 23
2025-05-15 12:20:58.376 CNTRLR   [Node 022] [~] [Notification] Access Control[Door state]: 22 => 2 [Endpoint 0]
                                 3
#

All of my other Z-Wave devices have RSSI values

versed garnet
#

You could check the device diagnostic file and see if HA is aware of the rssi

#

and/or turn on the integration debug logging and see if the "statistics" message for the node is being received.

#

did you ever check the HA logs for RSSI errors?

calm flame
#

Those seem to be gone now

#

The only reference to RSSI in the device diagnostic

 "interviewStage": "Complete",
      "deviceDatabaseUrl": "https://devices.zwave-js.io/?jumpTo=0x019a:0x0004:0x0004:54.39.0",
      "statistics": {
        "commandsTX": 1,
        "commandsRX": 67,
        "commandsDroppedRX": 0,
        "commandsDroppedTX": 0,
        "timeoutResponse": 0,
        "lwr": {
          "protocolDataRate": 3,
          "repeaters": [],
          "repeaterRSSI": []
        },
        "lastSeen": "2025-05-15T18:18:21.904Z",
        "rtt": 18.3
      },
versed garnet
#

Ok, that's why it's unknown. There's no value.

calm flame
#

From the integration log

2025-05-15 13:56:44.553 DEBUG (MainThread) [homeassistant.components.zwave_js] [binary_sensor.front_door_sensor_state_any] Value Any/None changed to: False
2025-05-15 13:56:44.556 DEBUG (MainThread) [zwave_js_server.server] 2025-05-15 13:56:44.552:
2025-05-15 13:56:44.552 DRIVER « [Node 022] [REQ] [BridgeApplicationCommand]
                                 │ RSSI: -57 dBm
                                 └─[BinarySensorCCReport]
                                     type:  Any
                                     value: false
2025-05-15 13:56:44.561 DEBUG (MainThread) [zwave_js_server.server] 2025-05-15 13:56:44.560:
2025-05-15 13:56:44.560 SERIAL « 0x011700a80000010016097105000000ff06170000c7007f7f03                (25 bytes)
2025-05-15 13:56:44.564 DEBUG (MainThread) [zwave_js_server.server] 2025-05-15 13:56:44.562:
2025-05-15 13:56:44.562 SERIAL » [ACK]                                                                   (0x06)
versed garnet
#

there's no statistic log there

calm flame
#

Is that something I need to enable in addition to enabling logging? I have no idea what a "statistics log" looks like.

versed garnet
#

no

#

it's a message with event "statistics updated"

calm flame
#

2025-05-15 13:56:44.579 DEBUG (MainThread) [homeassistant.components.zwave_js] [binary_sensor.front_door_window_door_is_open] Value Access Control/Door state changed to: 23
2025-05-15 13:56:44.580 DEBUG (MainThread) [homeassistant.components.zwave_js] [binary_sensor.front_door_window_door_is_open_in_regular_position] Value Access Control/Door state changed to: 23
2025-05-15 13:56:44.580 DEBUG (MainThread) [homeassistant.components.zwave_js] [binary_sensor.front_door_window_door_is_open_in_tilt_position] Value Access Control/Door state changed to: 23
2025-05-15 13:56:44.800 DEBUG (MainThread) [zwave_js_server] Received message:
WSMessage(type=<WSMsgType.TEXT: 1>, data='{"type":"event","event":{"source":"node","event":"statistics updated","nodeId":22,"statistics":{"commandsTX":1,"commandsRX":76,"commandsDroppedRX":0,"commandsDroppedTX":0,"timeoutResponse":0,"lwr":{"protocolDataRate":3,"repeaters":[],"repeaterRSSI":[]},"lastSeen":"2025-05-15T18:56:44.562Z","rtt":18.3}}}', extra='')
versed garnet
#

yep, no RSSI reported there. I'm not sure if it it's only updated for commands from the controller.

calm flame
#

it was present briefly recently on the 12th and earlier

versed garnet
#

yes, but there was a bug fixed that I mentioned before. if RSSI is obtained from ACKs from controller commands, then maybe one hasnt' been sent since you upgraded.

#

anyways, the problem is not in HA at this point

#

you could try something like update a battery entity, and then manually wake up the device, see if that fills in the RSSI

calm flame
#

Are you saying RSSI is only updated after a command? That doesn't make sense for a sensor going back RSSI was being reported regularly

versed garnet
#

and what are the intervals between those points?

#

you can test it yourself. turn a light switch on from the wall. does the statistic message include rssi?

#

my mains-powered devices that are automated have much more fluctuation than that battery sensors

calm flame
#

hard to tell on interval this is door sensor that never gets commands

versed garnet
#

zoom in

#

if you think my explanation doesn't make sense, why doesn't your history fluctuate more?

#

I don't know. You'll have to try that experiment yourself.

#

I might be wrong in the above, but regardless Z-Wave JS isn't sending RSSI to HA for your device so that's why it's Unknown.

calm flame
#

Clearly the integration has RSSI because it shows up in the log

versed garnet
#

the log is from Z-Wave JS...

#

the statistics message, without any RSSI is in HA

#

the diagnostic, without any RSSI is in HA

#

HA does not parse driver debug logs for information

calm flame
#

So who owns the bug?

versed garnet
#

did you try the experiment i suggested?

#

you can post a discussion in Z-Wave JS project, or ask in their Discord, if you think there's an issue

calm flame
#

I open and closed door and tried to ping

versed garnet
#

ping does nothing for battery devices

#

opening and closing a door does not involve a command from the controller

#

refreshing a battery entity, then waking up the device would a) have the controller send a command and b) receive an ACK with the RSSI

calm flame
#

Not sure how to send commanfd to a door sensor that's asleep

versed garnet
#

you can also check with a powered device like I suggested

calm flame
#

all my orther the devies work

versed garnet
#

or click "Refresh" on the Battery CC in Z-Wave JS UI

#

If you'd rather not try my suggestions, then this thread is pretty much completed. You'll have to go to Z-Wave JS for more info.

calm flame
#

I dont usder stand how turinog o nlight has anything to do withthe door sensor

versed garnet
#

It's an experiment

#

It's called debugging

calm flame
#

words do matter

versed garnet
calm flame
#

refreshing battery did nothing

versed garnet
#

Did you wake it up?

calm flame
#

I opend and closed the door after issuing the refresh

versed garnet
#

the wake up procedure would be in your manual

#

or sometimes the z-wave js help

calm flame
#

I thinkl I've wasted enpough of your time

calm flame
#

I sent an email support request to Sensative asking why I'm not seeing RSSI upates in HA. They informed me that the controller creates the RSSI value, whick makes sense becasue the contoller measures the received signal strength

acoustic bane
#

Which controller do you have?

calm flame
#

Z-Station

acoustic bane
#

Hm that should support RSSI readings.

#

Can you make a driver log of some communication with a node where you are missing RSSI values?

#

I'll check, not that I introduced a bug recently

calm flame
#

I does for eveyone of my other devices. I created bug #145231 with that information

acoustic bane
#

Can you mention me there so I see it?

calm flame
#

Done

calm flame