search

fuatakgun / eufy_security

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

Eufy Floodlight Cam 2K T8422 Device no longer Controllable via Home Assistant #1028

Closed Brembo427 closed 7 months ago

Brembo427 commented 7 months 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

Camera is present and all exposed in HA, Can change setting within Eufy APP and HA will reflect the changes, But can no longer change anything via HA. For example, I cannot change guard modes or even toggle on or off the spotlight. Sometime rebooting HA restores control breifly but then stops again. have tried resetting the camera with no success. all over devices on my eufy system work perfectly.

Additional information

Go to Settings -> System -> Repairs -> Click on 3 dots (...) -> System Information and get Version and Installation Type to below fields;

Hardware Information;

Additional context

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

albuchan commented 7 months ago

Adding my own info to this issue. Also looks similar to closed issue "motion detection switch doesnt work #1022" except that no kind of restart or reboot fixes it. Pretty much as confirming as described by brembo427 raising the issue. I have 2 cameras (and a doorbell camera) are present and all exposed in HA Can change settings within Eufy APP and HA will reflect the changes, But can no longer change anything via HA. As another example, I have several automations to enable or disable motion detect on these execute leave no errors in HA logfile but do not change the states. Have tried resetting a camera with no success. On the whole devices on my eufy system appear to work fine but as "read-only". Example of this : if I open the device page for a T8124 camera device name "Garden" and under "configuration" I can see a toggle related to switch.garden_motion_detection - if I toggle it from off to on... after a few seconds it will return itself to off. see below some output from the docker log when I do this (there is a lot of output but this ties into the time frame). image

Additional information

Go to Settings -> System -> Repairs -> Click on 3 dots (...) -> System Information and get Version and Installation Type to below fields;

Home Assistant Installation Type: Core Home Assistant Core Version: 2023.11.3 Eufy Security Add-on Version: 1.7.1 Eufy Security Integration Version: 1.7.7 Hardware Information; Running on qnap container station as docker image.

Camera Models: T8124, T8131

Live Streaming Protocol (RTSP/P2P):aler9/rtsp-simple-server:v0.22.2

Debug Logs from Home Assistant (How to enable debug logs for eufy_security integration? #624) - Without this, I will automatically resolve this issue

Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):

****Output from Docker container log for HA*** 2023-12-04 12:07:52.603 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'station', 'event': 'connection error', 'serialNumber': 'T8124P20223204FF'}} 2023-12-04 12:08:01.156 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'station', 'event': 'connected', 'serialNumber': 'T8124P20223204FF'}} 2023-12-04 12:08:06.153 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'station', 'event': 'command result', 'serialNumber': 'T8124P20223204FF', 'command': 'download_image', 'returnCode': -134, 'returnCodeName': 'ERROR_CONNECT_TIMEOUT', 'customData': {'command': {'name': 'stationDownloadImage', 'value': 'https://zhixin-security-eu.s3.eu-central-1.amazonaws.com/thumb/2023/01/28/station/T8124P20223204FF/bjvUb1W3jSeW1mO2./20230128151746.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJYLV2KOLW6PU4FSA%2F20231203%2Feu-central-1%2Fs3%2Faws4_request&X-Amz-Date=20231203T021331Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Signature=14b08580a23a4dda32d10dc61a68460dd1f2c582e357e5d1fc4d4ae1fc82590b'}}}} 2023-12-04 12:08:10.964 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'station', 'event': 'disconnected', 'serialNumber': 'T8124P20223204FF'}}

Would you share your device with me in case further debugging required? (Yes/No): Yes but not sure how to do that...

Additional context

output from security add-on 1.7.1 running in seperate container

2023-12-04 12:04:53.129 WARN Command aged out from send queue for station T8124P20223204FF { commandType: 1350, nestedCommandType: 1306, channel: 0, ageing: 122455531, maxAgeing: 120000 } 2023-12-04 12:04:53.197 INFO Disconnected from station T8124P20223204FF 2023-12-04 12:07:52.600 WARN Tried all hosts, no connection could be established to station T8124P20223204FF. 2023-12-04 12:07:52.602 INFO Timeout connecting to station T8124P20223204FF 2023-12-04 12:08:01.152 INFO Connected to station T8124P20223204FF on host 192.168.0.62 and port 13804 2023-12-04 12:08:01.405 WARN Command aged out from send queue for station T8124P20223204FF { commandType: 1103, nestedCommandType: undefined, channel: 255, ageing: 122643562, maxAgeing: 120000 } 2023-12-04 12:08:06.151 WARN Command aged out from send queue for station T8124P20223204FF { commandType: 1350, nestedCommandType: 1308, channel: 255, ageing: 122070075, maxAgeing: 120000 } 2023-12-04 12:08:10.963 INFO Disconnected from station T8124P20223204FF 2023-12-04 12:14:53.262 WARN Command aged out from send queue for station T8010P2320281C4D { commandType: 1144, nestedCommandType: undefined, channel: 255, ageing: 73760007, maxAgeing: 120000

NOTE: there are many of the WARNs being generated both before and after the "toggle" I made around 2023-12-04 12:07:52 in the logs

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

albuchan commented 7 months ago

Forgot to include above: The following appears in Notifications... from time to time. Timing does not seem related to a "write" event. No idea where the source of this notification comes from it is not from my automations. "Eufy Security - Error Connection to Eufy Security add-on is broken, retrying in background!"

fuatakgun commented 7 months ago

there is a connection issue between add-on and your physical device, it is most probably network related but I cannot do anything about it as we are just sending the request to the device but it does not reach or not acknowledged by it.

thanks for detailed information

albuchan commented 6 months ago

I know this was closed as completed - as above related to network issues - but I am struggling to accept that since other functions work and the cameras are specifically reachable. I have tried many things including moving HA from a QNAP based docker container to running currently on a rpi with HassOS. Nothing changed. So I would be interested in understand how to further investigate a network issue. However - I am pasting here a workaround for my automations. Instead of using changing Motion Detection On or Off from the relevant device switch I CAN create new guard modes using the app on the phone. On HA this appears as "custom1" which is basically with a mode with motion OFF and "custom2" as with motion ON. I edited the automation actions to change the guard mode options to either custom1 or custom2. This works, but again makes me wonder then if the issue is truly network related (or this would not work either !) .

mariomaz87 commented 1 month ago

I'm having a similar issue and I couldn't find a workaround. I have an automation where I use the start RTSP command and then take a screenshot. It worked flawlessly until 2 days ago. Now when I send the RTSP on command the camera does not start the streaming and in eufy-ws docker log I have:

2024-05-28 13:46:34.284 WARN eufy-security-ws:eufy-security-client [p2p] [P2PClientProtocol._sendCommand] Command aged out from send queue for station XXX {

commandType: 1144,

nestedCommandType: undefined,

channel: 255,

ageing: 5402094,

maxAgeing: 120000

}

I'm investigating it and I will update this ticket if I have news.

mariomaz87 commented 1 month ago

After several restarts of the eufy-ws container and of Eufy HA add-on, it's working again. I haven't changed anything on my configuration.