I try the Laurent’s workaround but it failed. The automation never trigger. I think this is previous Laurent’s operations on the device which allow the trigger.
“change it from 0x00 to 0x01” → ok, made in ozwadmin
“The device external alarm wasn’t associated, so I did what they recommend (associate with controler node 1)” → ??? how to do that ?
If someone has another tip for recognise this Benext door sensor in HA, I’m listening !
I stumbled on this old tread as I tried to use my BeNext door sensor in Home Assistant.
I am happy to report that this is possible with the Z-Wave JS integration.
For anyone who is looking to get this working (including my future self )
As I include my sensor, 7 entities were created, 3 of which were disabled.
You need to enable the Door Sensor: Basic entity. This will hold a value of 0 (closed) or 255 (open).
Based on this I made a binary sensor.
template:
- binary_sensor:
- name: "Deur"
device_class: door
state: >
{% if is_state('sensor.door_sensor_basic','255.0')%}
on
{% else %}
off
{% endif %}
You have 7 entities for a door sensor, yet none of them are for the door status itself? What entities are you provided with? Do you happen to have a binary_sensor that doesn’t change state?
Your device needs a compatibility flag in order to map the Basic Set value to the Binary Sensor. With this flag enabled the driver will perform the 0/255 to off/on mapping you’ve done manually with your template sensor and the default binary_sensor will function properly. I would submit an issue to the node-zwave-js project. The fix is the same as this one.