Sesame lock component is using an old API version and state goes out of sync

[bogdanalexe90]

Home Assistant release with the issue:

Last working Home Assistant release (if known):

Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform:
https://www.home-assistant.io/components/lock.sesame/

Description of problem:
The sesame lock component is using an old API version. This is causing the lock component to be out of sync with the actual lock status. In the new API they fixed that by introducing new methods.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[bogdanalexe90]

Any update on this? Sesame just announced that they will soon drop support for the V2 API.

[zanglang]

I forked the old sesame component and updated it to use pysesame2, which looks to be written by a Candy House engineer, but short of being officially published on PyPi. Not sure that would be a blocker.

Clone https://github.com/zanglang/sesame2 into custom_components, and get an API key from https://my.candyhouse.co/#/credentials

Example:

lock:
  - platform: sesame2
    api_key: !secret sesame_api_key

[zanglang]

With Candy House's pysesame2 library being on PyPi it is possible to update this component now. I've opened a PR for review.