You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: