Zwave Sensor State not changing

Configuration Z-Wave
1

Hi All,

I’m trying to get data from a zwave sensor, HA picks up the sensor and it is showing just fine in HA however, the state is not changing when the item changes. The logs are showing an “event” that changes, but no state change. Does anyone happen to have any ideas how to get that info?

Here’s the OZW log entry:

Device OPEN

2017-10-08 12:26:45.905 Detail, Node036,   Received: 0x01, 0x13, 0x00, 0x04, 0x00, 0x24, 0x0d, 0x60, 0x0d, 0x02, 0x00, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x16, 0x00, 0x35
2017-10-08 12:26:45.905 Info, Node036, Received a MultiChannelEncap from node 36, endpoint 2 for Command Class COMMAND_CLASS_ALARM
2017-10-08 12:26:45.905 Info, Node036, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:22, status=255
2017-10-08 12:26:45.905 Detail, Node036, Refreshed Value: old value=0, new value=0, type=byte
2017-10-08 12:26:45.905 Detail, Node036, Changes to this value are not verified
2017-10-08 12:26:45.905 Detail, Node036, Refreshed Value: old value=0, new value=0, type=byte
2017-10-08 12:26:45.905 Detail, Node036, Changes to this value are not verified
2017-10-08 12:26:45.906 Detail, Node036, Notification: ValueChanged
2017-10-08 12:26:45.911 Detail, Node036, Notification: ValueChanged

Device CLOSE:

2017-10-08 12:26:48.954 Detail, Node036,   Received: 0x01, 0x13, 0x00, 0x04, 0x00, 0x24, 0x0d, 0x60, 0x0d, 0x02, 0x00, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x17, 0x00, 0x34
2017-10-08 12:26:48.954 Info, Node036, Received a MultiChannelEncap from node 36, endpoint 2 for Command Class COMMAND_CLASS_ALARM
2017-10-08 12:26:48.954 Info, Node036, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:23, status=255
2017-10-08 12:26:48.954 Detail, Node036, Refreshed Value: old value=0, new value=0, type=byte
2017-10-08 12:26:48.955 Detail, Node036, Changes to this value are not verified
2017-10-08 12:26:48.955 Detail, Node036, Refreshed Value: old value=0, new value=0, type=byte
2017-10-08 12:26:48.955 Detail, Node036, Changes to this value are not verified
2017-10-08 12:26:48.955 Detail, Node036, Notification: ValueChanged
2017-10-08 12:26:48.962 Detail, Node036, Notification: ValueChanged

As you can see the “event” changes 22 vs. 23 however there doesn’t seem to be any way I can get that data into HA.

2017-10-08 12:26:45.905 Info, Node036, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:22, status=255

Any tips or help would be appreciated!

Chris

2

It should be showing up in an entity called sensor.THING_access_control

3

Hmmm. Nope not there.

I see…

sensor.THING_alarm_level
sensor.THING_alarm_type
sensor.THING_power_management

4

this sounds like a z wave secure device like a lock. These require a security key be configured under zwave: Without a security key it may show up as entities and sensors, but won’t physically function.

I have a z wave door lock and these are what the entities correspond to for my lock, which may or may not be the same as your device, but I think these are part of the z wave standard/specification.

lock.garage_door_lock.alarm_level - user code that last interacted with the lock
lock.garage_door_lock.alarm_type - current mode of the lock (manually un/locked, un/locked by RF, or critical battery level)

there should also be an attribute of the z wave device something like .lock_status. So there’s two ways I grab the status of my lock. I use a sensor template. I could look at the “alarm_level” and set a text value, or I can extract the text of the “.lock_status”. I do use the value of “.alarm_level” to change the icon accordingly.

  - platform: template
    sensors:
      garage_door_lock_mode:
        friendly_name: 'Garage Door Lock Mode'
        entity_id: sensor.garage_door_lock_alarm_type
        value_template: '{{ states.lock.garage_door_lock_locked.attributes.lock_status }}'
        icon_template: >-
          {%- if is_state("sensor.garage_door_lock_alarm_type", "21") %}
              mdi:lock-outline
          {% elif is_state("sensor.garage_door_lock_alarm_type", "22") %}
              mdi:lock-open-outline
          {% elif is_state("sensor.garage_door_lock_alarm_type", "24") %}
              mdi:lock
          {% elif is_state("sensor.garage_door_lock_alarm_type", "25") %}
              mdi:lock-open
          {% else %}
              mdi:cancel
          {%- endif %}
5

Yeah, it was added as a secure device (my other secure devices are working fine). Also, I can see the data coming in via the OZW logs…I just can’t get access to it for automations / etc

6

Nothing else, not even a binary_sensor.THING node? None of them change?

What’s the device? Is it detected correctly, or does it have a generic name?

7

I’m running into this issue too. The device is a Andersen Translator used to link to their window and door sensors. It shows up as a generic device.

here is my Node Information:

averageRequestRTT: 36
averageResponseRTT: 5087
battery_level: 100
capabilities: routing,beaming,listening
friendly_name: Nexia Unknown: type=5a44, id=414e
homebridge_hidden: true
is_awake: true
is_failed: false
is_info_received: true
is_ready: true
is_zwave_plus: true
lastRequestRTT: 26
lastResponseRTT: 6065
manufacturer_name: Nexia
max_baud_rate: 40000
neighbors: 4
new_entity_id: zwave.nexia_unknown_type5a44_id414e
node_id: 14
node_name: Nexia Unknown: type=5a44, id=414e
old_entity_id: zwave.nexia_unknown_type5a44_id414e_14
product_name: Unknown: type=5a44, id=414e
query_stage: Complete
receivedCnt: 83
receivedDups: 7
receivedTS: 2017-10-10 10:28:58:148
receivedUnsolicited: 78
retries: 0
sentCnt: 9
sentFailed: 0
sentTS: 2017-10-09 21:46:49:991
8

That says that OpenZWave doesn’t know what this is. You would want to read this guide.

The trouble is, this isn’t a normal Z-Wave device, it’s a gateway. That means that there’s no defaults that’ll work. You might be better off returning this and buying a normal Z-Wave sensor.

9

Did not know it would be so difficult. I got it working with smartthings (though trying to decommission that hub) and can get the states via mqtt.

The cool thing about the Verilock sensors, is they report both the opening status and also the locked status, which another sensor would not be able to accomplish. My goal was not only to know if the door was open, but also and more importantly know if it is left shut but unlocked.

1 Like
10

Unless you get support in OpenZWave (which will require your active involvement) the only option is to keep the SmartThings hub I’m afraid.

It certainly should be possible to get it supported in OpenZWave - it may just take a bit of work.

1 Like