v2.0.4

• Improved overall error handling
• More descriptive error messages in cases where the API returns unexpected responses

v2.0.3

• Reduced amount of API calls when retrieving lock state
• Force the API to sync lock state when a lock is unresponsive. Useful for situations in which the WiFi module loses and then later regains connectivity.

v2.0.2

• Show "No Response" for lock accessories in HomeKit when the API returns an unresponsive status
• Added additional debug logging
• Upgrade dependencies to fix security vulnerability

v2.0.1

• Accessory UUIDs are now generated using the lock ID instead of the lock name to guarantee UUID uniqueness. This also prevents a possible issue of duplicate accessories being created if a lock name changes.
• Reduced the API polling delay interval which allows for the lock accessories to more quickly update the lock state after a lock or unlock action is performed.

v2.0.0

⚠️ This release contains breaking changes.

Changes:

• Uses the newest version of the Sesame API (v3) 🎉
• Supplying username/password credentials in the homebridge config is no longer supported. Instead, you will only need to supply an API token. Read the updated README for more info.
• Uses the new execution status endpoint in the API to accurately show when a lock has finished locking or unlocking.
• Major code refactor resulting in more lightweight and cleaner code as well as fewer dependencies.

v1.1.2

Uses newest version of the request dependency to remove security vulnerabilities.

v1.1.1

• Reduces logging verbosity of the current lock state when debug is set to false
• Additional debug logging
• Authentication flow refactoring

v1.1.0

This release fixes an issue when controlling Sesame using Siri, most notably when using the Apple Watch.

Details: When using Siri to control a lock, she would respond saying she was unable to lock or unlock the Sesame despite the Sesame successfully changing state. After a Sesame is controlled via HomeKit, the plugin would make an immediate request to the Sesame API to retrieve the new lock state. However, it takes a few seconds for the new lock state to be reflected in the API so the old lock state was being returned. This incorrect state was causing HomeKit/Siri to think the action wasn't successful. To fix this issue, the plugin now polls the API for the new state whenever the lock is controlled and it doesn't consider the action complete until the correct state is returned.

Additional changes:

• Optional debug config option for additional logging
• Major code cleanup and refactoring throughout the codebase

v1.0.3

• Fixes an issue where the state would not be accurately reflected if the lock is controlled manually

v1.0.2

• Removes unnecessary config name option