Smart Lock Touch (TR8520) is not locking/unlocking #681
Comments
|
I had a similar issue with my lock over the past few days. After disabling the add-on and integration I was able to confirm that the eufy app was still misbehaving, so it was unrelated to my HA config. Following on from that, I discovered that the smart lock touch + wifi is hard coded to use google DNS, which I was blocked in my router. Maybe not helpful for you... maybe it is. |
|
@fuatakgun did I do something incorrectly? If so, please pardon my ignorance. I don’t have any updates to apply, and it is still not working. I’m a little confused. |
|
I'm also having the same issue. My lock will appear in Home Assistant, but clicking on Unlock or Lock won't actually work. But the lock is working from my Eufy app. The error that appears is: |
|
same issue for me on v6.2.0. @fuatakgun this issue shouldn't have been closed |
|
Same issue for me on v6.2.0 |
|
Same issue here also on 6.2.0. I also note no battery levels are being reported from my cameras anymore. |
|
Same with TR8520 on HA 6.2.0. Everything seems to work except Supported devices specifies:
I'm on 1.4.2.8 |
The T8520 issue is listed here, I don't think it's a problem with the integration. bropat/eufy-security-ws#209 You can see in that issue thread that you can get the lock working at the expense of downgrading add-on and integration. |
|
cant do anything with my to my T8520 Firmware: 1.4.2.8 s6-rc: info: service s6rc-oneshot-runner: starting |
|
I am having the same issue with my T8503. Adding the "devide" line to the YAML file in the custom_component folder did not work for me. I can see that HA is updating the status of the lock when I am locking it manually or with the EUFY app, but locking from HA will give the error described earlier in here from other users |
same here, just locking/unlocking with HA generates that error. |
Describe the bug
Lock (T8520N) is not controllable.
To reproduce
Steps to reproduce the behavior:
Expected behavior
Expect lock to lock (or unlock)
Additional information
Hardware Information;
Smart Touch Lock (Wi-Fi model): T8520N
Debug Logs from Home Assistant:
2023-01-10 21:16:16.425 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration eufy_security which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2023-01-11 10:01:29.602 ERROR (MainThread) [homeassistant.components.hassio.handler] /addons/3a26b21d_eufy_security_addon/changelog return code 500 2023-01-11 10:01:29.603 WARNING (MainThread) [homeassistant.components.hassio] Could not fetch changelog for 3a26b21d_eufy_security_addon:Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):
2023-01-11 22:20:11.262 INFO Eufy Security server listening on host 0.0.0.0, port 3000 2023-01-11 22:20:13.854 INFO MQTT connection successfully established 2023-01-11 22:20:13.910 INFO Successfully registered to MQTT notifications for lock T8520Q2522120B6C 2023-01-11 22:20:21.763 INFO Push notification connection successfully established 2023-01-11 22:20:38.679 WARN Station T8520Q2522120B6C - Tried all hosts, no connection could be established 2023-01-11 22:20:38.681 INFO Timeout connecting to station T8520Q2522120B6C 2023-01-11 22:21:00.926 WARN Station T8520Q2522120B6C - Tried all hosts, no connection could be established 2023-01-11 22:21:00.926 INFO Timeout connecting to station T8520Q2522120B6C 2023-01-11 22:21:27.784 WARN Station T8520Q2522120B6C - Tried all hosts, no connection could be established 2023-01-11 22:21:27.784 INFO Timeout connecting to station T8520Q2522120B6C 2023-01-11 22:21:53.735 INFO Client disconnected with ip: {hassio interface IP} port: 60168 code: 1006 reason: Abnormal Closure 2023-01-11 22:21:53.736 INFO Client disconnected with ip: {hassio interface IP} port: 60176 code: 1006 reason: Abnormal Closure 2023-01-11 22:22:04.841 WARN Station T8520Q2522120B6C - Tried all hosts, no connection could be established 2023-01-11 22:22:04.844 INFO Timeout connecting to station T8520Q2522120B6C 2023-01-11 22:22:49.868 ERROR Station T8520Q2522120B6C - All address lookup tentatives failed. 2023-01-11 22:22:49.869 INFO Timeout connecting to station T8520Q2522120B6C 2023-01-11 22:23:37.015 INFO Connected to station T8520Q2522120B6C on host {lock IP} and port 18928 2023-01-11 22:24:07.088 INFO Initiated closing of connection to station T8520Q2522120B6C for saving battery. 2023-01-11 22:24:07.089 INFO Disconnected from station T8520Q2522120B6C 2023-01-11 22:27:49.229 INFO Client disconnected with ip: {hassio interface IP} port: 55748 code: 1000 reason: Normal Closure 2023-01-11 22:28:12.559 INFO Client disconnected with ip: {hassio interface IP} port: 39978 code: 1000 reason: Normal ClosureWould you share your device with me in case further debugging required? (Yes/No):
Sure
Additional context
While the log files show a failed attempt to connect to the lock, the device is reporting the accurate battery percentage and lock/unlock status.
UPDATE:
Accidentally closed issue. Literally just received a notification of an updated HACS integration for Eufy. Updated and have the same issue as described above.
Eufy Security Integration Version: v6.2.0
The text was updated successfully, but these errors were encountered: