aschzero / homebridge-sesame Goto Github PK

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

At the moment SesameOS 2.0 support and therefore Sesame 3 control is not available. Any plans/timelines about this issue?

Hello, is it hard to implement V3 API ?
https://docs.candyhouse.co/#introduction

I was debugging some other Homebridge plugin so I had a debug instance running when I got the following error from Sesame. I think it was caused by my wifi dongle being offline at that time. Just posting it here in case anyone would be interested in fixing it.

[7/15/2019, 9:21:25 PM] [Sesame] Sesame is unresponsive, forcing a status sync...
[7/15/2019, 9:21:28 PM] [Sesame] Unable to get lock state. Error: Task failed, got error BRIDGE_CONNECTION_ERROR
(node:5843) UnhandledPromiseRejectionWarning: Error: Task failed, got error BRIDGE_CONNECTION_ERROR
    at Client.<anonymous> (/opt/nodejs/lib/node_modules/homebridge-sesame/dist/lib/Client.js:82:27)
    at Generator.next (<anonymous>)
    at fulfilled (/opt/nodejs/lib/node_modules/homebridge-sesame/dist/lib/Client.js:4:58)
(node:5843) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:5843) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Preemptively creating this issue incase others visit this repo to report this error.

This is due to a known issue with the Sesame API and I've reported it here: https://community.candyhouse.co/t/v1-sesames-endpoint-returning-400-bad-request-but-others-still-work/1265/2

Unfortunately there doesn't appear to be any workaround so hopefully this gets fixed very soon.

Not sure if it's this plugin or homebridge: homebridge/homebridge#1876

Whenever we manually open the lock, HomeKit doesn’t seem to be aware of it until the Home app is actually open. I have an automation set to automatically lock the door after 10 minutes, which has stopped firing over the last few days if the door was unlocked manually. However, if you unlock the door by hand, wait a few minutes, then open the Home app, the door will relock ten minutes after you open the home app. The lock state is always accurately reflected in the Sesame app, though.

I have multiple sesame locks, would it be possible to only include only specific locks in homebridge? Some are at other locations and I don’t want them in the same home

Ever since updating to iOS 13 (beta and public release) I’ve been getting this error almost every 2 weeks. I just restart homebridge and it works but after a while it comes up again. See the picture for more info.

Is it possible to set a timeout period for sesame locks? Most often I get a “not responding” message but the lock eventually locks. I’d love to increase the timeout to 15s so HomeKit would get a confirmation of the transaction.

thanks!

I am always grateful for your help.
The other day, I tried to run homebridge-sesame on another terminal, deleted the description of config.json and uninstalled the plug-in, but the lock icon does not disappear from the list of Home applications.

Please advise how to remove the lock icon.
Thank you.

I’ve just installed the plugin and when I restarted homebridge, it wasn’t able to detect my lock. While it’s starting up, there’s an error that reads:

Unable to retrieve locks. response.map is not a function