Closed q5BWr6gN closed 11 months ago
Maybe try using go2rtc 1.6.2
Maybe try using go2rtc 1.6.2
The issue continues, even when using go2rtc 1.6.2's go2rtc_linux_amd64 build
Do you have any other suggestions I could try?
2023-08-28 20:55:27.860227157 [INFO] Preparing go2rtc config... 2023-08-28 20:55:27.905530281 [INFO] Got IP address from supervisor: 192.168.0.254 2023-08-28 20:55:27.943194225 [INFO] Got WebRTC port from supervisor: 8555 2023-08-28 20:55:28.256416731 [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually 2023-08-28 20:55:28.294403186 [WARN] Using go2rtc binary from '/config/go2rtc' instead of the embedded one 2023-08-28 20:55:28.294407774 [INFO] Starting go2rtc... 2023-08-28 20:55:28.395610992 16:55:28.395 INF go2rtc version 1.6.2 linux/amd64 2023-08-28 20:55:28.396034084 16:55:28.395 INF [api] listen addr=0.0.0.0:1984 2023-08-28 20:55:28.396802874 16:55:28.396 INF [rtsp] listen addr=0.0.0.0:8554 2023-08-28 20:55:28.397074821 16:55:28.397 INF [webrtc] listen addr=0.0.0.0:8555/tcp 2023-08-28 20:55:28.397930147 16:55:28.397 INF [srtp] listen addr=0.0.0.0:8443 2023-08-28 20:55:37.864942044 [INFO] Starting go2rtc healthcheck service... 2023-08-28 20:55:44.921119316 16:55:44.920 WRN [rtsp] error="wrong response on DESCRIBE,exec: exit status 1" stream=TapoC200-Kitchen 2023-08-28 20:56:00.282660598 16:56:00.282 WRN [rtsp] error="wrong response on DESCRIBE,exec: exit status 1" stream=TapoC200-Kitchen 2023-08-28 20:56:05.404131236 16:56:05.403 WRN [rtsp] error="wrong response on DESCRIBE,exec: exit status 1" stream=TapoC200-Kitchen 2023-08-28 20:56:07.877120364 16:56:07.876 WRN [streams] json locked 2023-08-28 20:56:15.642015201 16:56:15.641 WRN [rtsp] error="wrong response on DESCRIBE,exec: exit status 1" stream=TapoC200-Kitchen
Make an issue on go2rtc repo
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the problem you are having
At some point, both of my Tapo C200 cameras stopped working with WebRTC/MSE. I did not notice this issue right away, but it may be due to having both of their firmwares updated.
Audio works fine via VLC RTSP streaming, and in recordings.
My Reolink WiFi Doorbell camera continues to work with WebRTC/MSE.
Any help would be appreciated!
Version
Frigate 0.12.1-367d724 per the logs
Frigate config file
Relevant log output
Frigate stats
No response
Operating system
HassOS
Install method
HassOS Addon
Coral version
CPU (no coral)
Any other information that may be helpful
This is probably not relevant, but I recently had an issue with Frigate not loading the config section. It would perpetually load, even after restarting the device running Home Assistant or using different devices/browsers, and was only resolved after reinstalling Frigate.
I also recently updated to a slightly newer version of Home Assistant and the Visual Studio addon.
For privacy reasons, I have turned on parental controls at the modem level to restrict traffic for the Tapo C200 cameras, but the issue persists when this is disabled.