Schlage BE469 - Zwave binding with security - missing features

[5iver (Scott Rushworth)]

@bdm

I didn’t have the ALARM_RAW items as part of the gLock group, which has been suggested elsewhere. Done now

Remove them from there, add a gLockRaw group and put them in there. Add that group to persistence. Then use one trigger…

Member of gLockRaw received update

It seems like your locks are not persisting their data. My guess is that your default persistence is mapdb (you can check/change this in Paper UI or runtime.cfg. You do not have any strategies defined in your mapdb persist. You will need to add them…

Persistence

Another thing you can try is to use…

if (transform("JSONPATH", "$.event", triggeringItem.previousState(true, "influxdb").state.toString) == "11" && transform("JSONPATH", "$.event", triggeringItem.state.toString) != "11") {

There are some related discussions in this thread around post 145…

Zwave - Yale YRD220 Lock

Here is my current rule for parsing alarm_raw. My locks (Schlage BE469) do not update the lock_door channel, so I use alarm_raw to update the items linked to lock_door, and base rules off of that item’s state. Maybe all locks behave this way? You’ll find several examples of using the JSONPATH transform to parse the data in the lambda. This can be tricky though, because JSONPATH will throw an exception if the element name you are searching for does not exist in the JSON. I haven’t had any issues…