Sesame constantly fails to connect via REST API

steveisles 2018-09-04 20:10:43 UTC #1

I am using the homebridge-sesame plugin by @andrew.schaper to connect to my Sesame Smart lock via the REST API (I have the WiFi Dongle, and both dongle and door lock are running the latest firmware). Most of the time, when I use HomeKit to send a command to unlock or lock my door via the REST API, I get an iOS notification from the Sesame application:

ATTENTION! Door unlock by Restful API FAILED because of a CONNECTIVITY ISSUE!

Usually, whether the notification happens or not, the door does eventually unlock / lock — though it could take more than one attempt, but the notification is happening 80-90% of the time.

Any idea what is causing this? The Wi-Fi dongle is only 2-2.5 meters away from the lock...

cim 2018-09-05 03:48:28 UTC #2

Thanks for the info! We've passed your feedback to our devs and they're checking out the issue now. We will let you know once we have an update. Thank you! - CANDY HOUSE

cim 2018-09-06 02:38:49 UTC #3

Thanks again for bringing this to our attention! Our devs have made some changes to the API, can you let us know if the issue persists over the next few days? We'd appreciate an update. Thank you! - CANDY HOUSE

steveisles 2018-09-06 03:06:45 UTC #4

Sure, I will keep you posted, and set a reminder to report back in a few days...

steveisles 2018-09-10 20:43:47 UTC #5

So, @cim I have been using the homebridge plugin since your tweaks and I find that the lock is way more likely to succeed when a command is issued via Siri — that is, if I say "unlock the door," @andrew.schaper 's plug-in sits and waits and eventually (a few seconds) says the action succeeds (e.g. "OK, the door is now unlocked.")

More importantly, the "Restful API FAILED because of a CONNECTIVITY ISSUE" messages have all gone away.

It still happens ~5% of the time that issuing a request fails to detect the status change (but the change in door lock/unlock state changes anyway) — but regardless I haven't seen any of the notifications above.

cim 2018-09-11 07:28:37 UTC #6

Thanks so much for the update, glad to hear there was an improvement! Thanks for bringing this issue to our attention so we could get it fixed. Let us know if you notice any other issues with the API so we can take a look. We've just released API V3 which will allow users to sync Sesame status to our server as well as query the status of commands given to Sesame, which are features we've added based on feedback from our users. It's important to us to continue improving the API, so please let us know if you have any further questions or suggestions! - CANDY HOUSE