We have a Schlage BE468/BE469 z-wave Lock. It works just fine except Alex reports it as "UNLOCKED" when it's locked.
If I command "Lock the door" Alexa will lock and then report "Door is unlocked"
Same if I ask "What is the status of the front door". Ans: "The front door is unlocked"
I'm using the driver Schlage BE468/BE469 Lock and tried the Generic Z-wave lock driver.
Is this an Amazon problem, driver problem or Schlage problem?
If I UNLOCK using Alexa...it asks my PIN, unlocks and says "Front Door is Unlocked" as it should.
Open the Lock's device details page on the hub. Lock and Unlock the Schlage lock from the that Hubitat device details page. Does the lock status on that page properly reflect the actual lock status? If not, click CONFIGURE and see if that corrects the issue.
Try manually locking and unlocking the lock at the physical lock itself. Does the Hubitat device details page properly reflect the actual lock status?
If both of the above are working properly, then try using Alexa again. You can try removing the lock from the Amazon Echo Skill app on the Hubitat hub, and click DONE. Then, make sure the lock device has been removed from the Alexa mobile phone app as well. Then add the lock back into the Amazon Echo Skill app on the Hubitat hub, and click DONE. Try the voice commands again.
I've had this problem for years. It seems like Alexa reports the state of the lock at the time the command is issued and not what the lock ends up with.
Somewhat improvement. It appears Alexa gets the status BEFORE executing the command.
So, when asked to lock, it sees the current status of UNLOCKED, then locks the door, then reports the status of UNLOCKED. When I ask "What is the status of the front door" it reports "LOCKED".
Which is better. I can ask the status and it will report that correctly.
What it won't do is execute a command and report status after the commend is complete correctly.
I can reproduce @russ-baker's observations with my Yale Zigbee locks, so it isn't a z-wave/zigbee difference - could still be driver dependent, because the Yale lock uses a different driver.
I captured the conversation using one of the Alexa-Remote nodes for node-red.
I hadn’t done your second test, so I just ran it. It worked as one would hope it would. My lock completed locking before Alexa starting responding, and she stated that my lock was locked.
I have had the issue of Alexa responding "the lock is unlocked" before she carries out the command since I've moved from SmartThings over 2 years ago.
I have watched the status of the lock on both the Hubitat hub and the Alexa app. Alexa responses that this lock is unlocked before the lock status changes on either app.
I'm using a Yale YRL220 with the Generic Z-wave Lock driver.
My problems are with webcore. Well, maybe not webcore itself, but webcore telling me a lock did not lock when I am standing there watching it lock. I have tried various webcore waits (10,30,60) seconds and it still tells me the lock did not lock even though I know it did.
