Two Eufy Cameras eventually working
mblasi opened this issue · comments
Please check existing (open or closed) issues before creating a new one. (https://github.com/fuatakgun/eufy_security/issues?q=is%3Aissue+)
I have two eufy cameras: a doorbell (T8210) and an outdoor camera (T8160).
I installed “Eufy Security addon”, "Eufy security integration, “WebRTC addon”, “go2rtc addon” and “EufyP2P addon”… I’m some confused if all this is needed.
The thing is I have both cameras working “eventually”… some times, the doorbell doesn’t work because connection timout, and sometimes outdoor camera doesn’t work with “mse: wrong response on DESCRIBE”…
I use WebRTC with this two configs (one for each):
type: custom:webrtc-camera
url: rtsp://homeassistant:8541/camera1
and
type: custom:webrtc-camera
url: rtsp://user:pass@192.168.68.114/live1
When some camera stop working, It start working again by restarting: Eufy Security Addon, and/or go2rtc addon, and/or eufyp2p, and/or webRTC… and both start working again…
A clear and concise description of what the bug is.
To reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
Both cameras streaming simmulstaneusly.
Additional information
Go to Settings -> System -> Repairs -> Click on 3 dots (...) -> System Information and get Version and Installation Type to below fields;
Versión core-2024.1.5
Tipo de instalación Home Assistant OS
Desarrollo false
Supervisor true
Docker true
Usuario root
Entorno virtual false
Versión de Python 3.11.6
Familia de Sistema Operativo Linux
Versión del Sistema Operativo 6.1.71-haos
Arquitectura de CPU x86_64
Zona horaria America/Montevideo
Directorio de configuración /config
- Eufy Security Add-on Version: 1.7.1
- Eufy Security Integration Version: dont know where see it.
Hardware Information;
-
Camera1 Model: T8210
-
Camera2 Model: T8160
-
Live Streaming Protocol (RTSP/P2P): P2P for first camera and RTSP for second
-
Debug Logs from Home Assistant (#624) - Without this, I will automatically resolve this issue
2024-01-26 14:34:50.352 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs 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
2024-01-26 14:34:50.354 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration smartthinq_sensors 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
2024-01-26 14:34:50.355 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration alexa_media 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
2024-01-26 14:34:50.356 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration webrtc 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
2024-01-26 14:34:50.357 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
2024-01-26 14:34:50.358 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration midea_ac 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
2024-01-26 14:34:50.359 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration midea_dehumidifier_lan 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
2024-01-26 14:35:20.548 WARNING (MainThread) [alexapy.helpers] alexaapi.get_customer_history_records((<alexapy.alexalogin.AlexaLogin object at 0x7fa6e7d502d0>,), {'max_record_size': 10}): Timeout error occurred accessing AlexaAPI: An exception of type CancelledError occurred. Arguments:
()
2024-01-26 14:35:36.075 WARNING (Recorder) [homeassistant.components.sensor.recorder] Entity sensor.energia_reactiva_neta_t from integration modbus has state class total_increasing, but its state is negative. Triggered by state -184.31 with last_updated set to 2024-01-26T17:29:59.999999+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+modbus%22
2024-01-26 14:36:38.713 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/ollo69/ha-smartthinq-sensors/v0.36.2/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 4
2024-01-26 14:36:38.714 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/alandtse/alexa_media_player/v4.9.0/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 4
2024-01-26 14:36:38.715 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/AlexxIT/WebRTC/v3.5.1/README.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 4
2024-01-26 14:36:38.715 WARNING (MainThread) [custom_components.hacs] A timeout of 60! seconds was encountered while downloading https://raw.githubusercontent.com/hacs/integration/1.34.0/info.md, using over 60 seconds to download a single file is not normal. This is not a problem with HACS but how your host communicates with GitHub. Retrying up to 5 times to mask/hide your host/network problems to stop the flow of issues opened about it. Tries left 4
- Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):
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
- Would you share your device with me in case further debugging required? (Yes/No): Yes
Additional context
Add any other context about the problem goes here. Mainly, share everything as log files and use screenshots as last resort.
Can you tell me what eufyp2p add on is? I can't seem to find anything about it.
Hi! The eufyp2pstream add on is this one: https://github.com/oischinger/eufyp2pstream
I installed this to get RTSP working with eufy cameras.
p2p streaming was never reliable enough, it works for me 4 out of 5 times, so 20% of the times, it is not.
Instead of generalizing the issue, put it on simple steps to follow
Thankyou @fuatakgun !
I understand the point about p2p streaming.
The simplest way I have to exlpain my need is: I have two eufy cameras, one with RTSP support and one without. (T8160 and T8210 respectively)
Which is the recommended way to get both working on HA?
Regards,
Matías.
I have similar issue.
Two cameras: T8161 and T8142-R sometimes work, but often not.
Streams show Error mse:streams:wrong response on DESCRIBE. Turning RTSP on and off again and then clickin Start streaming on cameras in the integration helps for some time but then the situation repeats. Feed also has huge lags 4-10seconds. The wifi signal is reported as Strong.
I have the same issue.