aschzero
commented
5 years ago Hi Sam, thanks for letting me know about this issue. I just did some digging and I believe I was able to replicate the issue you're experiencing – several minutes after changing the lock state, the API is still returning the incorrect (old) lock state.
If you wouldn't mind doing the following steps, it would be very helpful in confirming that the behavior you're experiencing is due to the API:
- Update homebridge-sesame to
2.0.2 - In your homebridge config file, add the line
"debug": truein the Sesame config – this will enable debug logging. - Restart homebridge
- Open the Home app, lock or unlock your Sesame, then close and re-open the Home app to force a call to retrieve the lock status
- Paste the debug logs here
Thanks!
samsonrosen
Heya!
I've been a big fan of this plugin for a while, however I noticed since a recent(ish) update and API changes that often the home app through Homebridge will show the door as unlocked.
If I open the Sesame app it will show as Locked. If I press the lock within the Home app to lock it, it will 'lock' on the app and as expected not physically do anything to the door lock. Then this allows me to unlock the door once locked on home.
I am using a Sesame Smart Lock with the WiFi Hub. I've got the latest plugin and I'm using an API key generated from the sesame website.
Is there anything else I could provide to give more information? Not sure where this issue lies! Whether it's the homebridge plugin, the smart lock itself or maybe the API (I feel like most problems stem from the API).
Hope you can help!
Thanks,
Sam