Alex X
Alex X
I don't like this part: ``` 2025-08-27 15:38:40.269014438 16:38:40.268 DBG [exec] run pipe args=["/usr/lib/ffmpeg/7.0/bin/ffmpeg","-hide_banner","-v","error","-readrate_initial_burst","0.001","-re","-i","http://192.168.0.101:8123/api/tts_proxy/GA7tVW_wsR-crYhuuuXKGw.mp3","-c:a","pcm_mulaw","-ar:a","8000","-ac:a","1","-vn","-f","wav","-"] 2025-08-27 15:38:40.539253774 16:38:40.538 DBG [exec] run pipe launch=269.842713ms 2025-08-27 15:38:40.539257748 16:38:40.538 TRC [rtsp] client request: 2025-08-27...
https://github.com/AlexxIT/SonoffLAN?tab=readme-ov-file#issues
Setup integration once again.
I don't think this is related to the v3.6.0 update. Your camera response with bad content-length. Go2rtc can't do anything with this.
> * is go2rtc actually installed with this extension? Yes. > * where do i configure it? `go2rtc.yaml` near `configuration.yaml` > * how to i add cameras? It depends on...
Show device diagnostics
It is difficult to understand the cause of the problem from this data.
No. It's very old issue about old backend. It not used anymore. There is another issue about H265 + Safari + WebRTC. If you have this "bingo", it's an answer.
It is ideal, of course, to check whether this problem is repeated on the new version of go2rtc. Because the old one is built into the integration.
I assume you use Firefox?