On a device where there isn’t necessarily a clear open/closed, on/off I find it easiest to run tail and grep against the OZW_Log.txt.
something like tail -f OZW_log.txt | grep Node003 >Node003.txt
Then operate the Zwave device to trigger the behavior (open the door/trip the PIR etc).
CTRL C will kill the grep process. You can now view the Node003.txt file and look for changing state from likely “0” to “255” and back again to “0”. It could be the reverse, and it could well be a different number pair.
Thank you, Yes you are right, the state changes from 22 to 23 and reverse.
Now I get another sensor linked to it which shows 254, probably the battery, but I do not know how what would be the value if the battery was near the end.
What should all be gathered? HA exposes each of the sensors and controls for each device separately, to make life easier for writing automations.
As for the burglar entity, that does appear to be for the tamper sensor, but the manual doesn’t make it clear what triggers it (probably opening the case).
You’ve got a name, it’s kaipule_im20_doorwindow_sensor. If you restart that’ll also show for the zwave. entity. You should also find a matching binary_sensor entity you can use to tell if the door is open or closed.