[Bug]: frigate wizard camera naming breaks ha addon streaming

[jeffborg]

Checklist

• I have updated to the latest available Frigate version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in incognito mode to rule out problems with any third party extensions or plugins I have installed.
• I have asked the AI at https://docs.frigate.video about my issue.

Describe the problem you are having

with the ha addon Latest 15.15.1 but I think the error has been in there for a while and using the wizard to add a camera the go2rtc names don't match the camera names, this breaks home assistant ability to restream the camera

Configuration

When your go2rtc name is not the same as the camera name, this occurs if you use the wizard to setup a camera in frigate now.

go2rtc:
  streams:
    cam_1:
      - rtsp://...
cameras:
  cam:
     ...

Describe the bug

Camera has supported_features: 0 so home assistant won't restream the camera, this is because there is an assumption that the go2rtc name and the camera name are the same
https://github.com/blakeblackshear/frigate-hass-integration/blob/master/custom_components/frigate/camera.py#L224

Once I renamed to make it match you get supported_features: 2 and streaming via homekit via home assistant works.

Probably should get stream name from live/streams config and failing that the path under ffmpeg if using go2rtc

see blakeblackshear/frigate-hass-integration#1066 for initial report - I believe bug exists in the HA addon not frigate but was told to post here.

Steps to reproduce

1. setup ha addon
2. homekit camera exposed via home assistant
3. add new camera via wizard

Version

0.17.1

In which browser(s) are you experiencing the issue with?

N/A

Frigate config file

go2rtc:
  streams:
    cam_1:
      - rtsp://...
cameras:
  cam:
     ...

docker-compose file or Docker CLI command

N/A

Relevant Frigate log output

N/A

Relevant go2rtc log output

N/A

Operating system

Other

Install method

Docker CLI

Network connection

Wired

Camera make and model

N/A

Screenshots of the Frigate UI's System metrics pages

N/A

Any other information that may be helpful

Nothing in the docs says you need to name the go2rtc stream the same as the camera name yet this breaks home assistant entity flags for the camera if you do name differently

[inkeep-ai-assistant[bot]]

You've correctly identified the issue. The go2rtc stream name must match the camera name for Home Assistant streaming to work properly.
(1)

For the best experience, you should set the stream name under go2rtc to match the name of your camera so that Frigate will automatically map it and be able to use better live view options for the camera.
(1)

To fix your configuration, rename your go2rtc stream to match the camera name:

go2rtc:
  streams:
    cam:  # Must match camera name below
      - rtsp://...

cameras:
  cam:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/cam
          input_args: preset-rtsp-restream
          roles:
            - detect
            - record

(2), (3)

This naming requirement exists because the Home Assistant integration assumes the go2rtc stream name matches the camera name to determine streaming capabilities.
(3)

If you need multiple streams (main/sub), you can add additional streams with suffixes while keeping one that matches exactly:

go2rtc:
  streams:
    cam_main:
      - rtsp://<username, password, and camera ip>/cam/realmonitor?channel=1&subtype=0
    cam:  # This one matches the camera name
      - rtsp://<username, password, and camera ip>/cam/realmonitor?channel=1&subtype=1

(3)

Regarding the wizard creating mismatched names—this appears to be a bug worth reporting to the frigate-hass-integration repository since the integration code makes this assumption about name matching.
(3)

📚 Sources:

1. Configuring go2rtc
2. Restream
3. [Config Support]: how to choose which stream gets shown in Home Assistant

---

Have another question? Just tag @inkeep.

[jeffborg]

2 suggestions

docs to be updated
2 ha addon should at least print a warning saying no go2rtc stream found for cam - if the addon did this I would have fixed this without searching yesterday

[jeffborg]

Bug reopened in addon repo so this can be closed, there was some confusion initially