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
I think this should be a config option in homebridge-august.
This will not fix the device discovery. Im then getting this in the log: [August] Total August Locks Found: 1
But no ID to be seen in the log and no device in the device list.
By enabling debug logging I found the ID. So now my Yale Linus lock actually work. There still persist one issue. When the service starts in homebridge, it's not able to pull the lock status. You need to try to unlock the lock and it will update correctly. Until then sensor and lock status is not correct and the following is shown in the log: [August] Lock: xxx pushChanges: Cannot read properties of undefined (reading 'details')
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Problem
It's not possible to use the plug-in in EU (only tested in DK) as a different API endpoint is used here
Solution
For me the fix is to change setting in:
homebridge/node_modules/homebridge-august/node_modules/august-yale/dist/settings.js
From:
export const DEFAULT_BRAND = Brand.AUGUST;
To:
export const DEFAULT_BRAND = Brand.YALE_HOME;
I think this should be a config option in homebridge-august.
This will not fix the device discovery. Im then getting this in the log:
[August] Total August Locks Found: 1
But no ID to be seen in the log and no device in the device list.
By enabling debug logging I found the ID. So now my Yale Linus lock actually work. There still persist one issue. When the service starts in homebridge, it's not able to pull the lock status. You need to try to unlock the lock and it will update correctly. Until then sensor and lock status is not correct and the following is shown in the log:
[August] Lock: xxx pushChanges: Cannot read properties of undefined (reading 'details')
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: