search

fuatakgun / eufy_security

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

Setting the mode of multiple Homebase units. Stops working and then needs to be reloaded to make it work again. #975

Closed RonnieRocket2 closed 1 year ago

RonnieRocket2 commented 1 year ago

I am usinf the eufy_security integration together with the eufy-security-ws add on.

I have three Homebase Units 1,2 and 3.

I have one Eufy Keypad connected to Homebase 1 and have written automation rountines to set two other Homebase units (2 and 3) to whatever mode Homebase 1 is set to with the keypad (Home, Away, Off)

This all works fine but for some reason stops working on a daily basis (one thing to note is that my Homeassisant PC automatically reboots every day just after midnight) which might be connected?

I do not know the cause of what makes it stop working but restarting eufy-security-ws and reloading the eufy_security integration fixes it.

Anyone have any ideas?

Hardware Information;

Additional context This error was noted....

Error: <Task finished name='Task-483716' coro=<WebSocketClient._process_messages() done, defined at /config/custom_components/eufy_security/eufy_security_api/web_socket_client.py:62> result=None>

fuatakgun commented 1 year ago

Follow the bug template and fill all the fields. Be sure that you are on the latest version of integration as it is supposed to recover itself from broken connection

xNUTx commented 1 year ago

I am running into this myself. Everything else works for me (which is a doorbell, I do not have a camera or anything else from eufy yet), but eventhough the selection of the guard mode seems to work, it does not apply this setting. I can reboot the homebase from the integration no problem, so there seems to be a working connection.

Restarting both the add-on and reloading the integration fixes it.

I will be updating you as it happens again and will try to gather a little more information for you to work with.

EDIT: I have everything running on the latest version in a Core OS VM.

RonnieRocket2 commented 1 year ago

I added some automation that checks the state of my three homebase units 'whenever there is a state change in one of them'. This returns an 'alarm set correctly' or 'alarm did not set correctly' warning. I linked this to an alexa announcement so at least this will tell me when it did not work and allow me to investigate the log.

RonnieRocket2 commented 1 year ago

It failed tonight when I went out for dinner. I could not do much investigating..... but 2 out of the 3 homebase units set correctly and the other one was not responding. I changed modes, home, away, off remotely and the homebase that was not responding failed to respond. I then tried to reboot the homebase unit with the Eufy app, and then tried setting the mode via HA, but the unit was still not responding. I then stopped and started eufy-security-ws and the non responding homebase unit started responding normally. It seems to be failing on a daily basis so I may be lucky and get some logs tomorrow.

RonnieRocket2 commented 1 year ago

It failed this morning and here is the log... I have xxxx out the IP and the first part of the station ID I am running eufy-security-ws version: 1.7.1 Core 2023.11.2 Supervisor 2023.11.0 Operating System 11.1 Frontend 20231030.2

} 2023-11-14 02:27:10.430 WARN Heartbeat check failed for station xxxBA. Connection seems lost. Try to reconnect... 2023-11-14 02:27:10.435 INFO Disconnected from station xxxBA 2023-11-14 02:27:30.723 WARN Tried all hosts, no connection could be established to station xxxBA. 2023-11-14 02:27:30.725 INFO Timeout connecting to station xxxBA 2023-11-14 02:27:55.770 WARN Tried all hosts, no connection could be established to station xxxBA. 2023-11-14 02:27:55.773 INFO Timeout connecting to station xxxBA 2023-11-14 02:28:16.083 INFO Connected to station xxxBA on host 192.168.xxx.xxx and port xxxxx 2023-11-14 03:28:36.734 WARN Heartbeat check failed for station xxxBA. Connection seems lost. Try to reconnect... 2023-11-14 03:28:36.736 INFO Disconnected from station xxxBA 2023-11-14 03:28:57.009 WARN Tried all hosts, no connection could be established to station xxxBA. 2023-11-14 03:28:57.011 INFO Timeout connecting to station xxxBA 2023-11-14 03:29:22.058 WARN Tried all hosts, no connection could be established to station xxxBA. 2023-11-14 03:29:22.062 INFO Timeout connecting to station xxxBA 2023-11-14 03:29:57.071 ERROR All address lookup tentatives failed. { stationSN: 'xxxBA' } 2023-11-14 03:29:57.084 INFO Timeout connecting to station xxxBA 2023-11-14 05:50:02.838 INFO Push notification connection closed 2023-11-14 05:50:08.332 INFO Push notification connection successfully established 2023-11-14 06:34:58.336 WARN Heartbeat check failed for station xxx84. Connection seems lost. Try to reconnect... 2023-11-14 06:34:58.338 INFO Disconnected from station xxx84 2023-11-14 06:35:18.637 WARN Tried all hosts, no connection could be established to station xxx84. 2023-11-14 06:35:18.642 INFO Timeout connecting to station xxx84 2023-11-14 06:35:43.689 WARN Tried all hosts, no connection could be established to station xxx84. 2023-11-14 06:35:43.691 INFO Timeout connecting to station xxx84 2023-11-14 06:36:18.703 ERROR All address lookup tentatives failed. { stationSN: 'xxx84' } 2023-11-14 06:36:18.705 INFO Timeout connecting to station xxx84 2023-11-14 06:36:48.728 INFO Connected to station xxx84 on host 192.168.xxx.xxx and port xxxxx 2023-11-14 08:37:37.058 INFO Received push notification for changing guard mode { guard_mode: 3, current_mode: 3, stationSN: 'xxx84' }

Let me know if you need any further info. @fuatakgun

fuatakgun commented 1 year ago

thanks for detailed logs but you see that add-on is having issues communicating with your station devices (home bases) right? Throughout these failures, messages will be lost or commands will not be sent to physical devices.

So, I would blame the network directly and I would suggest you to set up an ping based device tracker on home assistant to check if home base devices are having connection issues at all. If yes, you should fix network issues, if not, you should reach out to bropat to help us the root cause why the connection is dropping.

RonnieRocket2 commented 1 year ago

thanks for detailed logs but you see that add-on is having issues communicating with your station devices (home bases) right? Throughout these failures, messages will be lost or commands will not be sent to physical devices.

So, I would blame the network directly and I would suggest you to set up an ping based device tracker on home assistant to check if home base devices are having connection issues at all. If yes, you should fix network issues, if not, you should reach out to bropat to help us the root cause why the connection is dropping.

I agree the issue is something to do with the homebase connection issues, I have no idea why they are losing connection but I will look at this. However, this is the part of the log from today...

023-11-23 02:03:19.624 WARN Heartbeat check failed for station xxxBA. Connection seems lost. Try to reconnect... 2023-11-23 02:03:19.627 INFO Disconnected from station xxxBA 2023-11-23 02:03:39.944 WARN Tried all hosts, no connection could be established to station xxxBA. 2023-11-23 02:03:39.946 INFO Timeout connecting to station xxxBA 2023-11-23 02:03:50.032 INFO Connected to station xxxBA on host 192.168.18.xxx and port xxxxx

2023-11-23 02:42:55.085 WARN Heartbeat check failed for station xxx84. Connection seems lost. Try to reconnect... 2023-11-23 02:42:55.088 INFO Disconnected from station xxx84 2023-11-23 02:43:15.341 WARN Tried all hosts, no connection could be established to station xxx84. 2023-11-23 02:43:15.344 INFO Timeout connecting to station xxx84 2023-11-23 02:43:25.368 INFO Connected to station xxx84 on host 192.168.18.xxx and port xxxxx

But this time round the xxxBA and xxx84 homebase units re-connected, but in the previous log there was

ERROR All address lookup tentatives failed. I dont know how long the add-on waits to before it decides to fail? And once it fails does it never attempt to connect again?

fuatakgun commented 1 year ago

There is a maximum number of retries before giving up.

RonnieRocket2 commented 1 year ago

I fixed it :-). I added an automation which monitors the state of the hombase units and if they are not syncronised after changing a mode, it uses Home Assistant Supervisor: Restart add-on. to restart the Eufy_security_WS add on.

fuatakgun commented 1 year ago

In the meantime, i am working on a connection sensor to be used for this.

fuatakgun commented 1 year ago

For the true fix, find the culprit if it is the network or hardware:-)

RonnieRocket2 commented 1 year ago

For the true fix, find the culprit if it is the network or hardware:-)

True, the problem is still there and I have just patched over it. But to be honest as the connection issue is on the two homebase units that are using wi-fi and not on the one wired directly to the router it's more than likely a mesh network issue, rather than a hardware issue with the homebase units. I have 5 x M4 Deco Mesh units around the house acting as AP's , they are all in wireless configuration, my intention is to connect them via cat5 but I need to put the switch and cables in to do this. I think that should clean up the network here.

fuatakgun commented 1 year ago

Makes sense, check in next release for connection specific sensor and you can react on it rather than waiting for them to be out of sync.

Resolving as of now