Schlage Z-Wave lock does not update state if manipulated digitally

🛎️ Get Help
1

I have a Schlage BE469 Z-Wave door lock. When I PHYSICALLY manipulate the lock it generates events and updates the state correctly in hubitat. However, a DIGITAL lock command send from hubitat, despite the action working correctly, does NOT update the state of the lock, or produce a log line.

SOLUTION: Go to the lock device page and disable "Ignore door Operation Reports"

2

Do all the events show up on the events tab for your Schlage lock? The ones that triggered and the ones that didn't?

Also, is your lock using a built-in driver or a community driver?

2 Likes
5

Hi, can anyone help me troubleshoot this or try to replicate themselves?

6

Based on this, I guess I'd just trash the existing rule and build it as new again. Maybe a long shot, but might work.

2 Likes
7

Why the If statement? No matter what, you want it locked after 3 minutes.

2 Likes
8

And why delay the rule instead of delaying the lock command ?

Capture d’écran du 2024-12-11 20-34-02
Capture d’écran du 2024-12-11 20-34-02710×119 9.29 KB

Maybe try that to see if the problem still occurs.

3 Likes
9

I think the problem might be a missing Cancel Delayed Actions as your first action, as every unlock event within that 3 minute period will re-trigger the rule and create a new instance of the rule with another 3 minute delay

Alternatively change your delay for a Wait for Event - elapsed time. That will get cancelled upon rule retriggering.

Best if you turn on full logging (triggers, events, actions) to see what is going on

3 Likes
10

The reasoning for this was to save battery and machine part wear as the state of the lock (locked/unlock) is always correct.

11

Thank you for the suggestion, I have the same problem regardless of where I put the delay.

12

Thank you for the reply. Full logging has been on since I've been troubleshooting this problem.

While going through your suggestions and doing more testing I discovered the problem. Any lock actions that are not physical actions, are not logged and do not change the known state of the lock. I hadn't noticed this before because I always manipulated the lock physically. I'll do some searching on this.

1 Like
13

This problem was fixed by going to the device page for the lock and disabling "Ignore door Operation Reports"

Thanks everyone!

1 Like
14

This is not an option in the built-in driver.

Apparently it is a built-in driver option.

15

It's built in, I just did the standard device add method nothing special.