Sesame / SmartThings Integration

[chris.thro]

Yep those are mine findings also. When I refresh the state in smartthings the logging shows it successfully gets the state but it does not match the current state. When I look at the dashboard it also shows the incorrect state so obviously that is why it is getting the wrong state in smartthings. The question now is why is the state not correct in the dashboard it only changes when a command is sent through the app. It is not refreshing if the lock autolocks. Will probably open a separate thread about that.

[chris.thro]

The thread helped with the status not updating; maybe it will help for you:

Dashboard not reporting the current status of the lock

The dashboard only shows changes made through the app. If the lock autolocks it still reports as unlocked.Is there no way for the dashboard to be updated to the correct state? This breaks the smartthings integration as it is always reporting unlocked even through the lock has autolocked.

[coolineho]

Thanks! finally got it working. The status is now showing correctly, i can also use smartthings to lock/unlock sesame lock.

The lock/unlock happens pretty much within 10 seconds. But the status update takes a bit of time to process... like 30+ seconds.

Thanks for your help.

[mikey0426]

I followed the above directions, and everything appears to be working. SmartThings accurately reports the status of the lock. I can lock and unlock the lock from the sesame app. But SmartThings refuses to operate the lock, neither lock or unlock. Anyone else having this problem? Thanks for any assistance.....

[bryan.lawren]

Same! @mikey0426
Fixed it. Because of the way that we set it up it means everything in the settings menu needs to be hardcoded.
So when you go into the code and hardcode the api key you also need to hard code the threshold, I just erased it cause 60 sec threshold is fine with me.
Because Toby isn't supporting this I will fork it and take a look and try and fix it properly.