Add go2rtc workaround for HA managed one until upstream fixes it

[edenhaus]

Breaking change

Proposed change

Currently, there exists a go2rtc endless loop with the config we use it.
The problem is the following line: f"ffmpeg:{camera.entity_id}#audio=opus". By specifying the go2rtc name, go2rtc calls the ffmpeg in an endless loop as it is using itself as a source for the stream, which, of course, will not work.
Until the problem is fixed upstream, I have added with this PR a workaround for the go2rtc instance managed by HA.

It's not possible to add this workaround for self-hosted instances, as we would need to know the port where the internal RTSP server is running. This is not straightforward, as the port can be changed with the config. Getting the config and parsing it is out of the scope of this bug fix.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Flood of warnings from go2rtc server #129988 High CPU load after Update to 2024.11.0 #130009
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (go2rtc) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of go2rtc can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign go2rtc Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[carloda]

@edenhaus edenhaus Hi, are you saying it could be related to this problem? #130202

[frenck]

@carloda This is a PR; if you want to discuss or report an issue, the issue you linked is a more appropriate place.

Please note that pinging people might come across as demanding attention; while you probably mean well, we do discourage it.

Thanks for understanding 👍

../Frenck

[carloda]

@carloda This is a PR; if you want to discuss or report an issue, the issue you linked is a more appropriate place.

Please note that pinging people might come across as demanding attention; while you probably mean well, we do discourage it.

Thanks for understanding 👍

../Frenck

I apologize, my intention was to bring to light an issue and if it was related to the discussion to close it, I apologize again. :/

[frenck]

No worries 👍