@brendan @toby We're really sorry about the delay in API V2. However, the good news is that we were able to fix the issue with manual lock/unlock not updating Sesame's lock state correctly. It can take 5-15 seconds for the status to update, but the primary issue in this thread's OP has been fixed! We apologize deeply for neglecting to update you regarding this bug. It turns out we were able to fix it without waiting for v2 to be released. We take full responsibility for the lack of clarity and updates regarding this bug - we failed to communicate clearly regarding the fix and its limitations, and for that we apologize. Manual changes to lock state are now reflected in Sesame API after 5-15 second delay.
The V2 API will have even more features as mentioned by Jerming and we're really excited to make it available in May. We also wish we had more resources so we could put in all the features on our to-do list ASAP, and will be working hard to implement new features as quickly as we can. Please let us know if you still notice inaccurate lock states via the API - it should always be accurate now as long as you give it a few seconds to update. We hope to cut down the delay in V2 API which will be released soon.
We understand that we failed to communicate clearly regarding updates, fixes, and changes to our timeline, and we apologize for the frustration caused by our lack of transparency. We will be working to improve our communication so important community members aren't left in the dark regarding changes to our API or timeline. Thanks for keeping us accountable, we know we have a lot to improve and appreciate that you care enough to share your opinion with us. Please let us know if you have further thoughts or suggestions for us, we want to improve and are grateful to have community members like you! - CANDY HOUSE