BE469ZP Schlage not reporting RF lock/unlock Events

[jazzyisj]

The problem

• BE469ZP Schlage locks not reporting lock/unlock events initiated by HASS (UI, dev tools service call).
• These events were reported at one time as "RF unlock operation" and "RF unlock operation"
• This has been an issue for a while. It may have started when locks were re-added with S2 security
• I have several of this locks, behavior is consistent with all of them.
• Events initiated by the physical lock (Manual lock/unlock operation, Keypad lock/unlock) operation are still reported as shown.

2022-09-26T14:35:59.541Z CNTRLR   [Node 095] [Notification]
                                    type:  Access Control
                                    event: Manual lock operation

What version of Home Assistant Core has the issue?

v2022.9.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z-Wave JS

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Diagnostics information

Diagnostic file too long. (There was an error creating your Issue: body is too long (maximum is 65536 characters).

https://pastebin.com/4FMHkJ7j

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Nothing in Z-Wave/Core logs

Additional information

No response

[homeassistant]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

---

zwave_js documentation zwave_js source _{^{(message by IssueLinks)}}

[jazzyisj]

Still not resolved.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jazzyisj]

Not resolved.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jazzyisj]

Not resolved.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jazzyisj]

Not resolved.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[raman325]

thanks for being patient about this issue. Unfortunately, this isn't something we control. You'd have to create an issue in the zwave-js/node-zwave-js repository