You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The homebridge-esplock plugin has been deprecated and is no longer maintained. Unfortunately, due to the deprecation of homebridge-esplock, we removed support for this Homebridge plugin as it requires statusCode and battery percentage in the API response.
This results in the smart lock not functioning correctly with this plugin, leading to a degraded user experience for those who rely on this.
Proposed Solution
To resolve this issue, I suggest searching for an alternative Homebridge plugin that is actively maintained and implementing support for it within the smart lock's API.
Steps to Reproduce
Install and configure homebridge-esplock.
Attempt to control the smart lock using the plugin.
Observe that the plugin fails due to an incompatible JSON response format.
Expected Behavior
The smart lock should provide a compatible JSON response in the following format:
Actual Behavior
The current JSON response does not match the format expected by homebridge-esplock, causing functionality issues.
Temporary Workaround
As a temporary workaround, users can switch to using the homebridge-http-lock-ultimate plugin. This plugin is compatible with the smart lock's current API; however, it does not query for state updates. This means that if the lock is manually operated (e.g., by pressing a physical button), the state change will not be reflected in the Homebridge app.
The text was updated successfully, but these errors were encountered:
Issue Description
The homebridge-esplock plugin has been deprecated and is no longer maintained. Unfortunately, due to the deprecation of homebridge-esplock, we removed support for this Homebridge plugin as it requires statusCode and battery percentage in the API response.
This results in the smart lock not functioning correctly with this plugin, leading to a degraded user experience for those who rely on this.
Proposed Solution
To resolve this issue, I suggest searching for an alternative Homebridge plugin that is actively maintained and implementing support for it within the smart lock's API.
Steps to Reproduce
Expected Behavior
The smart lock should provide a compatible JSON response in the following format:
Actual Behavior
The current JSON response does not match the format expected by homebridge-esplock, causing functionality issues.
Temporary Workaround
As a temporary workaround, users can switch to using the homebridge-http-lock-ultimate plugin. This plugin is compatible with the smart lock's current API; however, it does not query for state updates. This means that if the lock is manually operated (e.g., by pressing a physical button), the state change will not be reflected in the Homebridge app.
The text was updated successfully, but these errors were encountered: