Since this device is not trivial to setup/understand, I thought I’d document my findings for posterity’s sake. Would be great if others can join and share their experience and wisdom.
Note: all of this refers to the “new” device (firmware 3.2 and above, Z-Wave+ Gen 5)
It took some hassle to get this to work right. Immediately after the inclusion all of the entities were there, but after restarting HASS they were gone, and only the binary sensor was there. After that, it was a hit and miss, and after about a day it settled down. Don’t really know what fixed it - I went through lots of restarts, exclusions and inclusions, etc…
Additionally, some of the sensors (e.g. Alarm Type) did not have a prefix (was simply named
sensor.alarm_type), and I had to edit in the entity registry.
The device has 5 association groups:
- Motion (Backwards Compatible)
- Tamper (Backwards Compatible)
Your controller should always be associated with group 1. Groups 4 & 5 are for backwards compatibility with non z-wave+ devices, and they seem to control the binary sensor. If you want the binary sensor to be on when there’s motion, the controller should be associated with group 4, if tampering should turn it on, group 5, and if either, then both groups.
I’m not sure what association groups 2 & 3 do.
The following sensors were created:
A binary sensor (with the suffix
_sensor_sensor). As mentioned above, it turns on when there’s motion, tampering, or either, probably depending on the 4th and 5th association groups. It also seems more reliable when it comes to cancelation frames than the burglar sensor (see below).
Alarm sensor (
alarm_level). I’m not sure what these do and haven’t seen them turn on. Perhaps this is related to association groups 2 & 3.
- SourceNodeId sensor. No idea what this does. Like the alarm sensors, it seems to always be at zero.
- General sensor. No idea what this does either. Seems to be at 255 on vibration, and 0 otherwise.
- Burglar sensor. I’ve seen it at 3 (tamper, i.e. vibration), 8 (motion), and 255 (Case open), as mentioned in the docs. If you want individual binary sensors for the different states, you can define template binary sensors that check for the relevant state. This sensor seems less reliable with cancelations (i.e. stays on for too long) than the binary sensor.
- Luminance and Temperature sensors. These are self explanatory and work as expected.
- Seismic Intensity sensor. By default the device does not report this. If you change configuration parameter 24 to the value 1, then this sensor would work as expected (scale seems to be 1 to 10).
That’s all I have. Would love to hear other people’s experiences.