Camerstream lost, but no connect retry from go2rtc

[vigeland]

I have 3 cameras, one stream is lost. No Error in the log.

I see two tcp connections go2rtc to the left cameras. If I open with go2rtc gui the missing on, nothing happens. ( Black screen :-) ) No logfile error, I see no tcp connections try to the missing camera. Restart of go2rtc, all 3 cameras are working well. Any Idea ?

[AlexxIT]

You need to start with the go2rtc version and stream info.

[vigeland]

Sorry, I am new in go2rtc, what mean "go2rtc version and stream info." "go2rtc version 1.9.4 (a4885c2) linux/amd64"

[AlexxIT]

You can check stream info from go2rtc WebUI

[vigeland]

I try to write it in my first comment. All trys only with the go2rtc web at port 1984 0 Stream used at the third camera, one at camera 1 and 2. Web gui left side. When I click on the right side on the stream link, the stream window open and no stream was displayed ( black ). No Error log writen by go2rtc, no Network Connection displayed with netstat to the camera ip. Restart go2rtc, stream link display the Stream instandly.

[AlexxIT]

Stream info. And stream probe.

[popy2k14]

Same issue as stated here: https://github.com/AlexxIT/WebRTC/issues/631 The issue arised to me because of the webrtc 3.6.0 update, which comes with go2rtc 1.9.4. I downgraded to webrtc 3.5.2 which has go2rtc 1.8.4, and i works flawlessly since a day with my reolink doorbell wifi.

With the new webrtc 3.6.0, every few hours a reconnect/progress circle is shown in front of the last picture, which freezed. But i never reconnects.

How can i provide a log and help debug?

[popy2k14]

@AlexxIT 3.5.2 with go2rtc 1.8.4 works wihtout any reconnect issue since ~4 days. So it seem there is an issue 1.9.4.

Is it possible for you to downgrade the included go2rtc to 1.8.4 until the issues with newer versions are sorted?

[AlexxIT]

You can use any version you want. If you are sure it is compatible with the new integration version. https://github.com/AlexxIT/WebRTC/blob/121d7558d0a2f1d19452f7b51a6237e048153528/custom_components/webrtc/utils.py#L28

[aarnaud]

I have the same issue with 1.9.4 recently update from 1.8.4 2 weeks ago

go2rtc version 1.9.4 (a4885c2) linux/amd64

Works fine with 1.8.4

api:
  origin: '*'
ffmpeg:
  h264/rk: -c:v h264_rkmpp_encoder -g 50 -bf 0
  h265/rk: -c:v hevc_rkmpp_encoder -g 50 -bf 0
hass:
  config: /config
log:
  format: text
rtsp:
  default_query: video
  password: CHANGEME
  username: frigate
streams:
  camera1: ffmpeg:rtsp://root:[email protected]:554/stream=0#video=copy#audio=copy
  camera1-LD: ffmpeg:rtsp://root:[email protected]:554/stream=1#video=copy#audio=copy
  camera2: ffmpeg:rtsp://root:[email protected]:554/stream=0#video=copy#audio=copy
  camera2-LD: ffmpeg:rtsp://root:[email protected]:554/stream=1#video=copy#audio=copy
webrtc:
  candidates:
  - 192.168.xxx.yyy:8555
  - stun:8555
  listen: :8555

[AlexxIT]

Seems like the reconnection problem when using ffmpeg is pretty common. I think bug in v1.9.3 or v1.9.4

[popy2k14]

@AlexxIT just let us know which go2rtc version we should try to give you feedback and we can narrow down the problematic version.

[AlexxIT]

Frigate uses v1.9.2 version

[popy2k14]

Just some curious thing! I have downgraded a week ago to 3.5.2 which has go2rtc 1.8.4 in it.

Now i wanted to upgrade again to 3.6.0 and go2rtc 1.9.4 (current release) and ust opened the 1984 port on my HA maschine. You know what... 1.9.4 is running with 3.5.2 !?!?

I dont know why, but it seems webrtc 3.5.2 runs without an issue with go2rtc 1.9.4.

So i will now upgrade to webrtc 3.6.0 with go2rtc 1.9.4, reboot my maschine, check port 1984 that go2rtc 1.9.4 runs and see how it goes.

[popy2k14]

Ok, so after upgrading to 3.6.0 with 1.9.4 the stream is gone over night.

I have now changed the util file to 1.9.2 and restarted GA but on port 1984 it says 1.9.4.

How can force a go2rtc downgrade?

[popy2k14]

So i was running also the go2rtc addon (which i dont remembered) which was on 1.9.4. I have now uninstalled it, restarted HA an now 1.9.2 is running with webrtc camera 3.6.0. Will now let this combo run.

BUT @AlexxIT, because i have looked with the white from the eye and used 1.9.4 with 3.5.2 without an issue for a week. My assumption is that 3.6.0 is the culprit with reconnect.

What's your thoughts about this?

[AlexxIT]

I'll check this when have time.

[popy2k14]

thx, here are results of my tests with an reolink doorbell wifi cam. I have always checked the go2rtc version with the webinterface running on port 1984.

On the following combinations the issue happens: picture in HA freezes after few minutes, reconnect circle is spinning and reconnects fails:

• webrtc 3.6.0 with go2rtc 1.9.0
• webrtc 3.6.0 with go2rtc 1.9.2
• webrtc 3.6.0 with go2rtc 1.9.4
• webrtc 3.6.0 with go2rtc 1.9.6

With the following combination it runs now for a few days without an issue:

• webrtc 3.5.2 with go2rtc 1.8.4
• webrtc 3.5.2 with go2rtc 1.9.4 (edit utils.py)

Just let me know when i should test something or provide logs.

[popy2k14]

@AlexxIT updated my post above (tested with newer go2rtc versions). But sadly webrtc camera 3.6.0 has the issue for me, regardless which version of go2rtc.

Because HA 2024.11 has now native go2rtc implemented, i switched from webrtc camera to default dashboard live camera feed (which internally now uses go2rtc in HA). Will see how it goes...

[ReX1983]

+1

go2rtc 1.9.4 works, the issue is somehow caused by webrtc 3.6.

I am now with webrtc 3.5.2 modified to use go2rtc 1.9.4 and no reconnect issues.

[popy2k14]

Since using the HA internal go2rtc combined with default dashboard HA camera card, I did not had the issue again. In parallel I am using a second go2rtc installation (via addon) so I can use the streams on my TV with pipup APK. Working nice together.

So yes, the issue is webrtc camera 3.6.0.