Zwave door sensor not updating the frontend

Configuration
1

Hello again! :slight_smile:

quick question:
I have a aeotec recessed door sensor. I made it work (meaning: added to the Zwave network, and showing in the HA frontend), but that is all.
the question is: is the sensor state supposed to change in the frontend once i open/close the sensor?

I though it should, but it does not. the only think i see in the screen in the sensor (SS below)

that icon in the circle never changes… should it?

Also, i tried to play with the template function. but i got the same result. (you can see in the last icon in the right (motion icon) that i tried to use for the multi sensor 6 to identify when/if someone trigger the PIR, but Nothing changes too (only the burglar icon 4th from left to right, that go from 0 to 8).

any directions?

thanks!

Luis

2 Likes
2

For the motion sensor try the below template. For the mutlisensors the only values that change for me are burglar, humidity, luminance and temperature. Fill in the state which correspond to your node ID. For the recessed sensor do you have anything else in your states list which correspond to the same node ID?

  • platform: template
    sensors:
    multisensor_6_motion:
    friendly_name: ‘MultiSensor 6 Motion’
    value_template: >-
    {% if is_state(“sensor.aeotec_zw100_multisensor_6_burglar_2”, “8”) %}
    motion
    {% elif is_state(“sensor.aeotec_zw100_multisensor_6_burglar_2”, “3”) %}
    tamper
    {% else %}
    still
    {% endif %}
1 Like
3

For the multisensor you need to use Open ZWave Control Panel and set its motion reporting to Binary - then it should show up as a binary sensor in H A and work in the front end without any additional work.

2 Likes
4

This. I learned this from watching @brusc’s ZWave video and did it as soon as I got the sensors to show in OZWCP.

1 Like
5

OK!
this is what I got:
multisensor --> FIXED! thank you!

motion - ok.PNG851×263 20.3 KB

on the recessed door: Not ok! any further help?
Please have a look:
On the states part i have:

states.PNG967×511 32.1 KB

on the configuration.yaml i have:

code.PNG852×473 38.3 KB

once i replace the “??” for the states,binary_sensor.aeotec_zw089_recessed_door_sensor_gen5_sensor_9
I got “ON” as result (regardless the magnet position) which seems to be a message saying that the sensor is on…

help? :slight_smile:

thanks!

Luis

6

which video? do you have a link?

7
1 Like
8

Here’s the link to his channel:

Here’s the video in particular on Zwave.

1 Like
9

LOL - within seconds of each other. Ben better buy us a round!

2 Likes
10

I tried to have OZWCP working.
but i got stuck. I am running HA on a docker container, in a synology NAS.
I stop the HA, create a container for OZWCP, but i cant connect to the USBStick, i got an error, cant recall exactly but is the device not found one, even if the docker command was correct, and once i got into the container bash i can find the device there… very weird…
i tried the second route… use domoticz (also under docker)… there i can connect to the stick, i can play with the configs… BUT… it doesnt allow me to save (the button seems broken).
I am in the process to isntall a linux VM on my main PC to try to fix that…

Also, i assume that once i got all configured, i should copy/paste the config files to HA, correct?

if you have any other idea, i am looking forward :slight_smile:

thanks again!

Luis

11

In my experience binary_sensor only works with either on or off. Because these sensors have a value then you won’t be able to use the binary_sensor component. A way around this is that you put the recessed sensor in the sensor component. Set the outputs to either on or off and then set a new binary_sensor component which will display the output correctly. Not sure if i explained this in a clear fashion. Here is an example.

sensor:
platform: template
sensors:
door:
friendly_name: ‘door’
value_template: >-
{% if is_state(“sensor.aeotec_zw089_recessed_door_sensor_gen5_sensor_9”, “0”) %}
off
{% elif is_state(“sensor.aeotec_zw089_recessed_door_sensor_gen5_sensor_9”, “255”) %}
on
{% endif %}

binary_sensor:

  • platform: template
    door_binary:
    movement:
    value_template: “{{ states.sensor_door.state == ‘on’ }}”
    sensor_class: opening
12

Correct - make sure to save in OZWCP after edits.

In fact I use a symbolic link so OZWCP shares the same file as HA.

13

Hi Maaniac,

It doesnt work.
I dont think the problem is the code itself, but something not triggering in the frontend.
after the config you provide i got:

.
and the 3 arrows are the same real sensor (the recessed door), but it never changes states in the front end.
however, in the OZW_Log.txt capture the changes, as below:
.
.

so that is why i have the impression that the front end doesnt capture the state change.
My impression is that the front end just see the sensor “turned on - awake” or “turned off - sleep”, but not the open/close with the magnet (which i can see on the logs).
So i have the impression that i am “monitoring” the wrong variable (or state) in the frontend.

any ideas?

thanks

Luis

1 Like
14

How is your zwave configured in both OZW and HASS? Maybe change the polling intensity? I don’t personally have these sensors so I can’t be 100% sure but my linear door sensors have no problems within HASS.

Does your door_binary change at all?

15

it never changed in HASS.
when i am in OZWCP i see the change state there.
but not in HASS. in the states windows i always get:

states - sensor 9.PNG1000×520 32.4 KB

the state is ALWAYS ON.
since this (and the multi sensor6) are my first sensors, I could swear that the state was telling me that teh sensor was ON, and not the situation on the (OPEN/CLOSE) status.
but again, on the OZW_Logs.txt i see things changing, so that is why i believe the sensor is working fine.

16

In OZW can you change basic report to binary sensor?

17

hello again.
I dont see any option to change from normal to binary (or something to binary) in OZWCP.

I create a new code:

  door:
    friendly_name: 'door'
    value_template: >-
      {% if is_state("binary_sensor.aeotec_zw089_recessed_door_sensor_gen5_sensor_12", "0") %}
      fechada
      {% elif is_state("binary_sensor.aeotec_zw089_recessed_door_sensor_gen5_sensor_12", "255") %}
      aberta
      {% else %}
      {{ states('binary_sensor.aeotec_zw089_recessed_door_sensor_gen5_sensor_12') }}
      {% endif %}

hoping to see what the %else% would return. and again, it always return ON.
is there a way I can see the list of attributes from a sensor? i have the real feeling that i am “picking” the wrong parameter here (as so is HASS on the default setup).

18

FIXED!

thank you all. you pointed in the right direction. the problem was the reporting flag. it was set originally on 0X100 (256) and it should be changed to 0x10 (16).
although it was mentioned that it was the “binary” sensor (it was flagged was report only). I found the solution from another forum and it worked!

Special thanks to Maaniac and aimc!

Luis

5 Likes
19

luismoed,

I have the exact same sensor, but for some reason I can’t get it to show up in HA. I see it perfectly in OZWCP, just not in HA at all.

What configuration changes did you need to make to either HA or the door sensor configuration in order to get it showing up in HA?

20

sry for the delay, i was in holidays and didnt check the mail/forum.
do you still have the issue?
In my case, HA recognize it straight away, i have not change anything in HA. do you have other Z-wave sensors working for you? or is this the 1st one?