Closed nickmarko closed 11 months ago
nickmarko
commented
11 months ago Update: Just found yet another thread about this and it appears that someone had success finding the entity in the deactivated entities list and manually enabling it. I did that and the lock entity now seems to work. However, this behavior is still strange. Thank you for your hard work on this integration, generally it is amazing!
fuatakgun
commented
11 months ago Is fixed on the latest master branch (do not get it as it has many other things to be fixed)
shieldmaiden95
commented
11 months ago I've been having the same issue and haven't figured anything out. I had given up until I saw your issue here.
Mine used to work fine but has been broken since the migration to eufy-security-ws add on. Now everything is just unavailable. The integration is finding the device because the logs show it connected to it successfully just like yours does:
INFO Successfully registered to MQTT notifications for lock T8520Q*****
INFO Connected to station T8520Q***** on host ***** and port *****
INFO Push notification connection successfully established
INFO Initiated closing of connection to station T8520Q***** for saving battery.etc.
Its just not loading the entities and shows them all as unavailable.
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.I just added another Eufy Door Lock 8520N to my home, and the only entities available are the debug entities. The various lock / unlock entities show as unavailable. Interestingly, I have the exact same lock that I installed on a different door about 1 year ago and it is working fine. Both locks are on firmware version 1.4.2.8. Reviewing various info on these boards it appears multiple people are having problems with the exact same issues on the 8520N locks, with entities being unavailable, but no resolution seems to have been achieved and the issues appear to be stagnant.
A clear and concise description of what the bug is.
Install Eufy lock 8520N according to instructions
Expected behavior
The entities will be available
Additional information
Hardware Information; s/n T8520Q***** model T8520N
ADD-ON LOG:
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-29 01:26:54.270 INFO Eufy Security server listening on host 0.0.0.0, port 3000 2023-11-29 01:26:57.458 INFO Connected to station T8010N1 on host and port 10587 2023-11-29 01:26:57.485 INFO Connected to station T8010P1 on host and port 27929 2023-11-29 01:26:57.495 INFO MQTT connection successfully established 2023-11-29 01:26:57.530 INFO Successfully registered to MQTT notifications for lock T8520Q 2023-11-29 01:26:57.531 INFO Successfully registered to MQTT notifications for lock T8520Q 2023-11-29 01:26:57.685 INFO Connected to station T8520Q on host 1 and port 18744 2023-11-29 01:27:08.800 INFO Push notification connection successfully established 2023-11-29 01:27:27.984 INFO Initiated closing of connection to station T8520Q for saving battery. 2023-11-29 01:27:27.985 INFO Disconnected from station T8520Q 2023-11-29 01:27:29.668 INFO Client disconnected with ip: 127.0.0.1 port: 49476 code: 1000 reason: Normal Closure 2023-11-29 01:28:19.965 INFO Client disconnected with ip: 127.0.0.1 port: 49490 code: 1000 reason: Normal Closure 2023-11-29 01:28:50.176 INFO Client disconnected with ip: 127.0.0.1 port: 44152 code: 1000 reason: Normal Closure 2023-11-29 01:28:52.684 INFO Client disconnected with ip: 127.0.0.1 port: 36874 code: 1000 reason: Normal Closure 2023-11-29 01:29:29.241 INFO Client disconnected with ip: 127.0.0.1 port: 36884 code: 1006 reason: Abnormal Closure 2023-11-29 01:32:35.021 INFO Client disconnected with ip: 127.0.0.1 port: 36186 code: 1000 reason: Normal Closure 2023-11-29 01:32:39.592 INFO Client disconnected with ip: 127.0.0.1 port: 39350 code: 1000 reason: Normal Closure