Since few days ago, the plugin cannot open/lock Sesame.
It can fetch status of Sesame if it is locked or opened, but when try to open/lock Sesame in the Home app(or Homebridge menu), it is said that the lock could not be controlled.
Any idea?

Wondering if you can help me solve an issue. I have a new install of Hoobs and have installed your Sesame plug-in. However, I keep getting the following error in my logs:
"21/03/2022, 15:42:38Open Sesame BridgeOpen SesameERRORFailed to getMechStatus."

Webhooks is enabled on my Candyhouse dashboard:
Webhook Enabled POST URL: http://XXXXXX:33892

The plug-in is configured as follows:
{
"platform": "OpenSesame",
"name": "Open Sesame",
"port": 33892,
"apiKey": "XXXXXY",
"locks": [
{
"name": "Backdoor",
"uuid": "XXXXXXXXX",
"port": 33892,
"battery": 100,
"debug": true
},
{
"name": "Frontdoor",
"uuid": "XXXXXX",
"port": 33892,
"battery": 100,
"debug": true
}
]
}

In 0.4.0-beta.0, real-time status update are supported.
but, CLIENT_ID was already removed.
According to Sesame support, "CLIENT_ID is no longer needed by developing via Sesame SDK."

Is it possible to update real-time status without CLIENT_ID?

I have the lock setup in my HomeKit app. When trying to operate (lock/unlock) the status changes to Jammed. I was unable to figure out what the secret key is. The QR reader needs an image but what QR am I using?

Everything is clear to me, except how to get a QR code to submit to the QR website in order to get a KEY Secret. Anything you can provide there would be helpful.

It seems Client ID is no longer used for SESAME 3 and 4, so it should not be required.

The URL to get Candyhouse's API Key is changed to https://partners.candyhouse.co/, and it shows only API Key, and not Client ID anymore.

According to Candyhouse, they have deleted Client ID because their Web API does not use Client ID anymore.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update dependency @types/aws-iot-device-sdk to v2.2.8
• Update dependency @types/jest to v29.5.12
• Update dependency @types/node to v16.18.96
• Update dependency @types/uuid to v9.0.8
• Update dependency aws-iot-device-sdk to v2.2.13
• Update dependency ts-jest to v29.1.2
• Update dependency ts-node to v10.9.2
• Update dependency @aws-sdk/client-cognito-identity to v3.568.0
• Update dependency @trivago/prettier-plugin-sort-imports to v4.3.0
• Update dependency async-mutex to ^0.5.0
• Update dependency eslint to v8.57.0
• Update dependency homebridge to v1.8.1
• Update actions/setup-node action to v4
• Update dependency @types/node to v20
• Update dependency eslint to v9
• Update dependency eslint-config-prettier to v9
• Update dependency nodemon to v3
• Update dependency release-it to v17
• Update github/codeql-action action to v3
• Update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency axios to ^0.28.0 [SECURITY]
• Update actions/checkout action to v4
• Update dependency aws4-axios to v3
• Update dependency prettier to v3
• Update dependency rimraf to v5
• Update dependency typescript to v5
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository