Cloud API feedback

brendan 2017-06-06 00:26:45 UTC #1

1) Have Sesame update the API when the lock is manually locked / unlocked or when someone uses the app locally via Bluetooth.

Currently the API takes a a long time to refresh the correct state of the lock. This could be resolved by having Sesame establish a connection with Virtual Station or the access point and push an update when a change is detected.

2) Please allow us to target a specific Sesame when getting status

For example: https://api.candyhouse.co/v1/sesames/ABC123ABC should return the status of that Sesame. Would be great to access it via its own endpoint.

Or could add an device_id index in the Sesames JSON.

toby 2017-06-06 02:59:10 UTC #2

I second this! I've even noticed that when I lock/unlock via the API the lock status never updates either.

I posted about it over here: https://community.candyhouse.co/t/sesame-cloud-apis-is-available/618/23

jerming 2017-06-06 09:56:24 UTC #3

Done ! We've just create the API for you.

brendan 2017-06-06 17:56:28 UTC #4

Thanks for that! I was able to save a lot of hassle using the endpoint. I was also able to implement battery features easily.

As for the "push updates" on lock status: would that require a firmware update for the lock itself?

jerming 2017-06-06 19:38:44 UTC #5

Nope. But it is always recommended to keep the firmware up-to-date

toby 2017-06-09 00:57:03 UTC #6

Any update on getting the lock status (locked/unlocked) to update in the API?

brendan 2017-06-12 07:23:18 UTC #7

@jerming That's great, thanks. Any idea on when lock_status can get fixed? Or whats wrong with it?

cim 2017-06-12 08:34:16 UTC #8

@toby, @brendan - our developer says the bug was fixed today, please take another look and let us know if you're still running into issues! - CANDY HOUSE

toby 2017-06-12 15:10:54 UTC #9

It's still not working for me. When I unlock the door via the API commands, it still shows "is_unlocked" as false

brendan 2017-06-12 18:07:49 UTC #10

It is somewhat better as it returns an unlocked state sometimes. When I use the Sesame app to lock the door, or if I manually turn the knob it is not updating still though.

Let me know if I can do anything to help. It looks like this is working fine in the Sesame app itself, could we just expose that state in the API?

cim 2017-06-13 05:12:38 UTC #11

@toby @brendan Oops, only the lock/unlock via app bug was fixed. Lock/unlock via API should be fixed now as well. We've noticed that there is a 10-30s delay for manual lock/unlock actions to get updated, and we'll be working on shortening the delay. Please let us know if you're still experiencing issues - it's important to us to get the bugs fixed and we really appreciate your feedback! - CANDY HOUSE

brendan 2017-06-13 09:30:43 UTC #12

@cim @jerming That's great! I look forward to trying it out tomorrow.

One more piece of feedback for the API. Can we get one more attribute in the status that says wether the Sesame is currently connected via Virtual Station or WiFi? Or wether it has recently etc?

It would be great to show an error or message instead of a "stale" lock state.

trisk 2017-06-13 17:30:10 UTC #13

@brendan I assumed api_enabled would update in real time to cover this. Should the API differentiate between Virtual Station/AP presence and Sesame presence? (The end result is the same if one isn't connected, though the corrective action is different).

brendan 2017-06-13 19:12:46 UTC #14

It seems api_enabled returns true if the cloud switch is turned on for the Sesame. It stays on even if the the Sesame is not currently connected to the Internet.

Would be nice if there was a separate one like currently_connected or last_seen

brendan 2017-07-06 04:22:52 UTC #15

Any update on this?

I'd like to use this feature to mark a specific Sesame as unreachable when it's Virtual Station is not running or crashes.

cim 2017-07-06 08:48:12 UTC #16

Thanks for following up! We will add this to our list of feature requests so our devs are aware there's a demand for this feature. - CANDY HOUSE

rinat912008 2017-07-07 09:48:27 UTC #17

Hello everyone. I have installed Virtual Station to my ios phone. VS have connected to Sesame lock. The problem is that sesame device receives lock and unlock signal with delay(about 30 seconds). Also sometimes Sesame device doesn't receive the signal from API. API doesn't return any errors, and return status 204. Also when VS disabled we don't get any errors from API(I mean get request for getting sesames and post to control sesame device)

cim 2017-07-07 09:52:23 UTC #18

Thanks for the feedback! We're addressed the 30-second delay in this thread.

Virtual Station can only support one connection at a time, similarly to Sesame. If your app is connected to Virtual Station, it may be blocking your API client from connecting to Virtual Station and passing the command. Try force-closing your Sesame app in this case and see if the speed improves.

Other possibilities include:

Virtual Station needs to re-establish connection with Sesame
Virtual Station is busy uploading logs to server, resulting in delay
Heavy load on server

Please let us know if force-closing the Sesame app reduces the delay. If not, we'll take another look to see what may be causing the issue. Thanks!

Regarding the issue with Sesame and VS not receiving signal from API but no error code being returned, the API currently only checks for successful request from client to API, and doesn't check for VS or Sesame connection. Others in this thread have also requested statuses denoting connection to VS and connection to Sesame, and we will be looking at adding these features to the API. Hope that helps, and thank you again for your suggestions and feedback! - CANDY HOUSE

rinat912008 2017-07-10 10:31:25 UTC #19

thank you, but it didn't help. Sometimes delay is 5 seconds and but sometime 30+ seconds.

cim 2017-07-11 04:28:15 UTC #20

Thanks for the feedback, we will let our devs know and update you if we have any new information! - CANDY HOUSE