[Bug]: Smart Lock R10 - 'Characteristic was supplied illegal value" #465
Comments
|
Did you check this Common Issues pages ? |
|
I also saw this error when trying a 2.3.x release. I do not see it with v2.2.21. However there has been a long running issue with Eufy locks not responding when using Apple Home to request an action (lock/unlock). So, you might see if v2.2.21 resolves the error you see but don't get your hopes up on it actually doing anything useful. |
|
@sparsematrix How long has that issue with the lock/unlock request from Home been going on? That's the only thing I'm really using this plugin for so if it doesn't work I'm stuck. |
|
[homebridge-eufy-security] This plugin generated a warning from the characteristic 'Lock Target State': characteristic was supplied illegal value: number 3 exceeded maximum of 1. if I downgrade to 2.2.21 I get the following [EufySecurity] WARN This accessory is not compatible with HomeBridge Eufy Security plugin: Front Door Type: 180 |
|
hey if you're not using streaming video. you can try 2.3.11 (see https://github.com/homebridge-eufy-security/plugin/wiki/RC---Beta-Version) |
This does allow me to control the lock, but the status of the lock is listed as "Unknown".
|
|
I see this with my locks as well, using |
|
is this 2.3.11 logs version ? can you enable debug on global settings ? |
Yes, mine are being pulled in on the latest version, 2.3.11. I'm also willing to debug this with you as well. |
|
Looks like boolean values are missing from the state mapping here and instead should be: const lockStatusMap: Record<number | boolean, CharacteristicValue> = {
true: this.platform.Characteristic.LockCurrentState.SECURED,
false: this.platform.Characteristic.LockCurrentState.UNSECURED,
4: this.platform.Characteristic.LockCurrentState.SECURED,
3: this.platform.Characteristic.LockCurrentState.UNSECURED,
5: this.platform.Characteristic.LockCurrentState.JAMMED,
};I attempted to reproduce jammed states, but not sure if my lock reports that properly, as it only seems to report target states. The other approach might be to adapt the boolean values into their respective state. |
|
can you try 2.3.14? |
Sorry for the late reply, I've been swamped with PI planning meetings at work and have been exhausted. Seems to have been fixed after the update for me. I won't speak for the others here, but I am seeing the proper states being reproduced in Homebridge and Home Assistant. Thanks for the quick fix, and being quick to integrate 3.0 of the Eufy security library! |
This is working for me as well. Thanks for this! |
What happened?
Trying to use my Eufy Smart Lock R10 with HomeKit. I just want to be able to lock/unlock from my phone. See log detail below for relevant information.
Device Type
other (UnSupported)
Plugin Version
beta (Best Effort)
HomeBridge Version
v1.6.x (Supported)
NodeJS Version
v18 (Supported)
Operating System
Ubuntu 18.04+ (Supported)
Relevant log output
config
{ "bridge": { "name": "Homebridge EC1A", "username": "0E:2E:B1:F4:EC:1A", "port": 51155, "pin": "400-53-109", "advertiser": "bonjour-hap" }, "accessories": [], "platforms": [ { "name": "Config", "port": 8581, "platform": "config" }, { "username": "[email protected]", "password": "password", "country": "US", "deviceName": "arc-homelab-dev01", "platform": "EufySecurity", "ignoreStations": [ "T8410P4223026D1A", "T8503Q10214812E9" ], "ignoreDevices": [ "T8410P4223026D1A" ], "locks": [ { "serialNumber": "T8503Q10214812E9" } ], "cleanCache": true } ], "disabledPlugins": [] }The text was updated successfully, but these errors were encountered: