Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: App says "unlocked" when device is actually locked #29

Open
ghost opened this issue Apr 12, 2017 · 1 comment
Open

Bug: App says "unlocked" when device is actually locked #29

ghost opened this issue Apr 12, 2017 · 1 comment

Comments

@ghost
Copy link

ghost commented Apr 12, 2017

The Schlage FE599 has two modes: "locked" which means visitors must enter a PIN in order to release the latch, or "unlocked" which means visitors can release the latch without typing a PIN.

In the "My Home" section of the SmartThings app, it shows my lock device as "UNLOCKED", but when I walk to the door and turn the handle, the latch does not move, which means the device is actually LOCKED. It seems the displayed status is not in sync with the lock. If I tap UNLOCKED, the text changes to LOCKED and the actual lock stays silent (because nothing changed in it). Then, when I tap LOCKED, the text changes back to UNLOCKED and I hear a metallic click in the actual lock because it changed from LOCKED to UNLOCKED.

I guess when the app opens, it may need to query the lock to get its status, unless the SmartThings hub can somehow store that status to prevent unnecessary battery drain on the lock. It might be a bug with the custom device handler.

@cariacou
Copy link

cariacou commented May 9, 2017

Same issue herr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant