Skip to content

More issue from built-in vs external go2rtc #37766

@solarpush

Description

@solarpush

Feedback

Hello,
Thank you for your work,
I would like to point out some problems with the addition of go2rtc built-in.

It's rather good news to have go2rtc included for the management of the different protocols and the low latency (if the rendering allows it...).

Also, direct access via the pod simplifies things for direct access to streams in the same pod (for those running via docker or k3s / k8s).

on the other hand, there's the WebRtc Camera custom card and I don't think it works with this version of go2rtc.

there's also a lack of information about config management.

For my example, ha is launched in docker with a volume but I've noticed that it doesn't save the config updated via :
go2rtc:
debug_ui: true

I understand that the aim is to simplify, but why not add /config/go2rtc.yaml to the pod to ensure management in the volume when users mount it for HA.

I also find myself using a card type: picture-entity to display a video stream, but apart from the naming problem, there's above all the loss of low-latency functionality provided by webrtc.

Do you have a configuration example or recent information about using the WebRtc camera card with integrated go2rtc?

Thank you.

URL

https://www.home-assistant.io/integrations/go2rtc/

Version

2025.2.5

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    integration: go2rtcstaleThe PR had no activity for quite some time, and is marked as Stale

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions