Seeing this with Kwikset locks too. I have a Kwikset 910 lock and am experiencing the same exact issue. I used zwavejs2mqtt to setup polling of the lock’s status value which helps but is not ideal.
The bug is now fixed in the last release! I disabled my workaround and the update is VERY fast now.
1 Like
I just converted from OZW to Zwave-JS and one of the issues I am seeing is that my Schlage BE469 lock doesn’t appear to have all the sensors that I see others have with the same lock. In addition my battery level is only shows 0%, the alarmtype and alarmlevel show as “unknown” and the lock status sensor always shows as open. The bug fix listed above in this issue doesn’t show the correct status when the lock is manually opened or closed. I included a screenshot of the sensor I have showing for this lock.
Should I be seeing additional sensors and how would I get the battery and my others sensors to work correctly?
Still doesn’t work on my Kwikset 910s
I’ve noticed something similar …
I have 4 Schalge Connect locks: 2 report as be469 and 2 as be469zp.
According to the Schalge website, the be469 (cnx) was originally made in 2013, while the be469zp was originally released in 2019. The website further says the be469zp is Z-Wave Plus while the be469 is just Z-wave.
The newer Z-Wave Plus model only exposes these 3 entities:
…while the older model reports several more (new user so I can’t post a 2nd image).
I’ve also noticed in the User Codes section of Z-Wave-JS that the older version exposes the actual user code, while the ZP version masks it out.
Guess I’ll apologize for taking the long route in saying: I think it depends on which version of BE469 you have.
I suspect the info you want is in CONTEXT {ID} further down in the object.
Here are three separate events I captured:
- Manual Unlock (internal thumb wheel)
- Unlocking with Keypad
- Locking with Schalge button
Event 2 fired 9:39 AM:
###
### Manually Locking with Thumb Wheel
###
{
"event_type": "zwave_js_event",
"data": {
"type": "notification",
"domain": "zwave_js",
"node_id": 5,
"home_id": <manually removed - just in case it's useful for hacking>,
"device_id": <manually removed - just in case it's useful for hacking>,
"label": "Manual lock operation",
"parameters": {}
},
"origin": "LOCAL",
"time_fired": "2021-03-22T13:39:38.445446+00:00",
"context": {
"id": "6bf71240126ed4841d97769a42c3a612",
"parent_id": null,
"user_id": null
}
}
Event 1 fired 9:39 AM:
###
### Unlocking with my usercode
###
{
"event_type": "zwave_js_event",
"data": {
"type": "notification",
"domain": "zwave_js",
"node_id": 5,
"home_id": <manually removed - just in case it's useful for hacking>,
"device_id": <manually removed - just in case it's useful for hacking>,
"label": "Keypad unlock operation",
"parameters": {
"userId": 2
}
},
"origin": "LOCAL",
"time_fired": "2021-03-22T13:39:34.024107+00:00",
"context": {
"id": "93f4981787e5fb94699aaa544db9bc30",
"parent_id": null,
"user_id": null
}
}
Event 0 fired 9:39 AM:
###
### Locking with Touch and Go (Schlage Button)
###
{
"event_type": "zwave_js_event",
"data": {
"type": "notification",
"domain": "zwave_js",
"node_id": 5,
"home_id": <manually removed - just in case it's useful for hacking>,
"device_id": <manually removed - just in case it's useful for hacking>,
"label": "Keypad lock operation",
"parameters": {}
},
"origin": "LOCAL",
"time_fired": "2021-03-22T13:39:24.107645+00:00",
"context": {
"id": "749e0c44a8ef38f3016dce651e73280f",
"parent_id": null,
"user_id": null
Though I’m guessing the purpose here, it’s conveniently coincidental that the only thing in the message that changes is the DATA:{Label} and the CONTEXT:{ID} for each event.
Hope that helps / makes sense.
Thanks for responding. I have the be469 non zwave plus. I actually integrated the zwave-js2mqtt to take advantage of the web ui and when I did the additional entities appeared. It seems to be working correctly.
Is anyone else still having this issue? Mt Schlage BE469Z locks pair correctly, but, periodically seem to go unavailable and don’t have the correct lock/unlock values in Home Assistant.
I’m using zwave2mqtt + ZwaveJS, all other devices work properly and I had no issues before on ZHA. Thanks