search

fuatakgun / eufy_security

Home Assistant integration to manage Eufy Security devices as cameras, home base stations, doorbells, motion and contact sensors.
955 stars 80 forks source link

Door Lock / Unlock Commands Fail #973

Open BillyFKidney opened 1 year ago

BillyFKidney commented 1 year ago

Please check existing (open or closed) issues before creating a new one. (https://github.com/fuatakgun/eufy_security/issues?q=is%3Aissue+)

If this is not an issue, you can use Discussions (https://github.com/fuatakgun/eufy_security/discussions) section.

Describe the bug

Attempts to lock or unlock a door lock result in no action from the lock OR logs in Home Assistant.

To reproduce

Steps to reproduce the behavior:

service: lock.lock
data: {}
target:
  entity_id: lock.front_door

Expected behavior

The door should lock ;)

I restarted the HA Add-On, waited 60s, then restarted the integration to ensure there was not a timeout issue.

Additional information

Go to Settings -> System -> Repairs -> Click on 3 dots (...) -> System Information and get Version and Installation Type to below fields; Core 2023.11.0 Supervisor 2023.10.1 Operating System 11.1 Frontend 20231030.1

{
  "domain": "eufy_security",
  "name": "Eufy Security",
  "codeowners": ["@fuatakgun"],
  "config_flow": true,
  "dependencies": ["ffmpeg", "stream"],
  "documentation": "https://github.com/fuatakgun/eufy_security",
  "integration_type": "hub",
  "iot_class": "cloud_push",
  "issue_tracker": "https://github.com/fuatakgun/eufy_security/issues",
  "requirements": ["websocket-client==1.4.2", "aiortsp==1.3.6"],
  "version": "7.0.4"
}

Hardware Information;

Door Lock: image

HomeBase: image

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started 2023-11-01 21:42:29.077 INFO Eufy Security server listening on host 0.0.0.0, port 3000 2023-11-01 21:42:32.761 INFO Connected to station T8030P1322330E06 on host 192.168.40.35 and port 14217 2023-11-01 21:42:33.325 INFO MQTT connection successfully established 2023-11-01 21:42:33.421 INFO Successfully registered to MQTT notifications for lock T8520Q2522350A02 2023-11-01 21:42:33.424 INFO Successfully registered to MQTT notifications for lock T8520Q20220807CF 2023-11-01 21:42:34.634 INFO Push notification connection successfully established 2023-11-01 21:42:53.568 WARN Tried all hosts, no connection could be established to station T8520Q20220807CF. 2023-11-01 21:42:53.571 INFO Timeout connecting to station T8520Q20220807CF 2023-11-01 21:42:54.067 WARN Tried all hosts, no connection could be established to station T8520Q2522350A02. 2023-11-01 21:42:54.068 INFO Timeout connecting to station T8520Q2522350A02 2023-11-01 21:43:04.252 INFO Connected to station T8520Q2522350A02 on host 54.219.251.168 and port 14713 2023-11-01 21:43:34.677 INFO Initiated closing of connection to station T8520Q2522350A02 for saving battery. 2023-11-01 21:43:34.679 INFO Disconnected from station T8520Q2522350A02

Additional context

Add any other context about the problem goes here. Mainly, share everything as log files and use screenshots as last resort.

robinhood-code commented 1 year ago

I have the same issue occasionally and when it happened I got the same warning message in the Add On log as well:

WARN Tried all hosts, no connection could be established to station T8520XXXX. INFO Timeout connecting to station T8520XXXXX

I would need to restart the Add On and Integration a few times until it works again.

fuatakgun commented 1 year ago

if you can, please share your device with me following README?

and mention about your timezone and what specific times of the day, I can tinker with it?

ys27 commented 1 day ago

I'm having issues with the lock.lock command with a C220