WTH go2rtc errors galore but I don't use/have cameras?

So I have like 180 error messages logged, this started at 2024.11, I thought it would eventually go away but it never did.

I’m running the latest version 2024.12.3 and it still has not gone away :frowning:

2024-12-11 18:35:50.314 WARNING (MainThread) [homeassistant.components.go2rtc.server] exit with signal: terminated

2024-12-11 18:36:33.980 WARNING (MainThread) [homeassistant.components.go2rtc.server] exit with signal: terminated

2024-12-11 18:36:33.982 WARNING (MainThread) [homeassistant.components.go2rtc.server] Go2rtc unexpectedly stopped, server log:

2024-12-11 18:36:33.982 WARNING (MainThread) [homeassistant.components.go2rtc.server] 18:35:50.671 INF go2rtc platform=linux/amd64 revision=dbe9e4a version=1.9.7

2024-12-11 18:36:33.982 WARNING (MainThread) [homeassistant.components.go2rtc.server] 18:35:50.671 INF config path=/tmp/go2rtc_frnw_rkq.yaml

2024-12-11 18:36:33.982 WARNING (MainThread) [homeassistant.components.go2rtc.server] 18:35:50.672 INF [rtsp] listen addr=127.0.0.1:18554

2024-12-11 18:36:33.982 WARNING (MainThread) [homeassistant.components.go2rtc.server] 18:35:50.672 INF [api] listen addr=127.0.0.1:11984

2024-12-11 18:36:33.982 WARNING (MainThread) [homeassistant.components.go2rtc.server] 18:35:50.672 INF [webrtc] listen addr=:18555/tcp

2024-12-11 18:36:33.982 WARNING (MainThread) [homeassistant.components.go2rtc.server] exit with signal: terminated

2024-12-11 18:38:07.681 WARNING (MainThread) [hass_nabucasa.iot] Connection closed: Cannot write to closing transport

2024-12-11 18:38:58.634 ERROR (MainThread) [homeassistant.components.spotify.coordinator] Error fetching spotify data: Error communicating with Spotify API

Help? :confused:

Go2rtc may have been setup by default for you. 2024.11 is when this integration was added. I cant see a cause for the errors

If you are using the default_config and run Home Assistant using one of the following installation methods, the go2rtc integration will be set up automatically and you don’t need to do anything:

  • Home Assistant Operating System
  • Home Assistant Supervised
  • Home Assistant Container

That is the point:

  1. Either that integration should be excluded from default config
  2. Or this integration should be fixed.

My log is flooded by a similar junk and I do not have cameras.

1 Like

Ditto, I started noticing them recently and I have no cameras. @Ildar_Gabdullin do you have a github issue open for that?

Sometimes registering an issue in Core is like a sending smth into a black hole.
This issue was closed w/o a solve.
This issue is still open with no movement. In this issue I reported this error when using a “generic camera” for Kodi screenshots - but in fact I see this error w/o any generic cameras ))).
I consider this whole “go2rtc improvement” as a disgrace.

Have you voted?

FWIW I have many cameras, frigate etc and go2rtc is working swimmingly here. Hope you get your issues resolved.

Good, but I do not have cameras - and yet I am spammed by these errors)))

Could this be a workaround then? Add a generic camera, you just need to link to a local image, no camera needed. Then it would find a ‘camera’ and stop spamming with errors?

This is exactly what I did. And it worked fine.
The problem is that I see that go2rtc spam EVEN WITHOUT any generic cameras.

2 Likes

Those are not errors, those are warnings. The only quoted error is from Spotify.

No idea what you are talking about. If you do not mean my post - then please point to an exact case.

Also, to add something to the topic, I don’t have any logs like this since my last HA restart. Seeing as that Spotify error happened around the same time as the warnings, this must be about internet connection problems HA was having at the time.

Do you have HA cloud webRTC connection turned on? You can check and disable it in HA cloud settings. I suspect you may have it enabled, which makes HA establish the connection even if you don’t have any cameras in use. Which then triggers a warning if the connection was disturbed for some reason.

Sorry, I was referring to the first post on the thread, which has a quote from the log.

I see. I have errors + warnings both ))))

1 Like

For the record - see no go2rtc messages in 2025.1 (even with generic camera for Kodi screenshots).

1 Like