Frigate MQTT connection issue

[KimSchehl]

Hello, (Passwords are changed)
I try to set up a new frigate Add On instance.
I created a MQTT user like that:

logins:
  - username: mqtt_frigate
    password: D7gf2iHs35
require_certificate: false
certfile: fullchain.pem
keyfile: privkey.pem
customize:
  active: false
  folder: mosquitto

Then I created the config.yml as told in frigate:
You must create a config file at: /addon_configs/ccab4aaf_frigate/config.yml

Config Looks Like:

# Für MQTT nutze ich das Mosquitto Add-On
# Benutzer anlegen nicht vergessen!
mqtt:
  enabled: True
  host: core-mosquitto
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: mqtt_frigate
  password: D7gf2iHs35
  stats_interval: 30

database:
  path: /config/frigate.db

detectors:
  coral:
    type: edgetpu
    device: usb

birdseye:
  enabled: True
  restream: True
  mode: continuous

objects:
  track:
    - person
  filters:
    person:
      min_score: 0.6
      min_area: 20000
    car:
      min_score: 0.6
      min_area: 30000

# Kann auf Kamera-Level überschrieben werden
detect:
  width: 1280
  height: 720
  # 5 FPS ist der optimale Wert - am besten direkt im Stream festlegen
  fps: 5

# Kann auf Kamera-Level überschrieben werden
record:
  enabled: True
  events:
    pre_capture: 5
    post_capture: 5
    objects:
      - person
    retain:
      default: 14
      objects:
        person: 28

snapshots:
  enabled: True
  clean_copy: True
  timestamp: False
  bounding_box: True
  retain:
    default: 14
    objects:
      person: 28

go2rtc:
  streams:
    supply_room:
      - rtsp://admin:[email protected]:554/live/ch00_0

cameras:
  cam_supply_room:
    enabled: True
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/supply_room
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/supply_room
          roles:
            - detect
    detect:
      enabled: True
    birdseye:
      order: 0

ui:
  timezone: Europe/Berlin
  time_format: 24hour
  strftime_fmt: "%d.%m.%Y- %H:%M"

What am I doing wrong, that I get that Log error in Frigate?

s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service prepare: starting
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service certsync-log: starting
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service nginx-log successfully started
s6-rc: info: service certsync-log successfully started
s6-rc: info: service frigate-log successfully started
s6-rc: info: service prepare successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2025-11-13 23:39:41.969450312  [INFO] Starting NGINX...
2025-11-13 23:39:41.993300678  [INFO] No TLS certificate found. Generating a self signed certificate...
2025-11-13 23:39:42.310710978  [INFO] Preparing Frigate...
2025-11-13 23:39:42.589475570  [INFO] Preparing new go2rtc config...
2025-11-13 23:39:42.634172479  [INFO] Got IP address from supervisor: 192.168.20.188
2025-11-13 23:39:42.678592323  [INFO] Got WebRTC port from supervisor: 8555
2025-11-13 23:39:42.978351320  [INFO] Starting Frigate...
2025-11-13 23:39:43.231828583  [INFO] Starting go2rtc...
2025-11-13 23:39:43.355338455  00:39:43.354 INF go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
2025-11-13 23:39:43.356064715  00:39:43.355 INF config path=/dev/shm/go2rtc.yaml
2025-11-13 23:39:43.356116382  00:39:43.355 INF [api] listen addr=:1984
2025-11-13 23:39:43.356663123  00:39:43.356 INF [rtsp] listen addr=:8554
2025-11-13 23:39:43.357841239  00:39:43.357 INF [webrtc] listen addr=:8555
2025-11-13 23:39:47.787984465  [2025-11-14 00:39:47] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-11-13 23:39:47.819770132  [2025-11-14 00:39:47] frigate.util.config            INFO    : frigate config does not need migration...
2025-11-13 23:39:47.932203819  [2025-11-14 00:39:47] frigate.util.services          WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended
2025-11-13 23:39:47.961776244  [2025-11-14 00:39:47] frigate.app                    INFO    : Starting Frigate (0.16.2-4d58206)
2025-11-13 23:39:47.962549583  [2025-11-14 00:39:47] frigate.app                    INFO    : Creating directory: /tmp/cache
2025-11-13 23:39:47.986720517  [2025-11-14 00:39:47] peewee_migrate.logs            INFO    : Starting migrations
2025-11-13 23:39:47.988711400  [2025-11-14 00:39:47] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-11-13 23:39:48.002750496  [2025-11-14 00:39:47] frigate.app                    INFO    : Recording process started: 383
2025-11-13 23:39:48.010862432  [2025-11-14 00:39:48] frigate.app                    INFO    : Review process started: 385
2025-11-13 23:39:48.018823243  [2025-11-14 00:39:48] frigate.app                    INFO    : go2rtc process pid: 118
2025-11-13 23:39:48.047679362  [2025-11-14 00:39:48] detector.cpu                   INFO    : Starting detection process: 408
2025-11-13 23:39:48.049578606  [2025-11-14 00:39:48] frigate.detectors              WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2025-11-13 23:39:48.056063535  INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
2025-11-13 23:39:48.071522656  [2025-11-14 00:39:48] frigate.comms.mqtt             ERROR   : Unable to connect to MQTT server: MQTT Not authorized
2025-11-13 23:39:48.079696985  [2025-11-14 00:39:48] frigate.app                    INFO    : Output process started: 427
2025-11-13 23:39:48.082598649  [2025-11-14 00:39:48] frigate.comms.mqtt             ERROR   : MQTT disconnected
2025-11-13 23:39:48.107698431  [2025-11-14 00:39:48] frigate.app                    INFO    : Camera processor started for cam_supply_room: 449
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
s6-rc: info: service certsync successfully started
s6-rc: info: service legacy-services: starting
2025-11-13 23:39:48.125483974  [INFO] Starting certsync...
2025-11-13 23:39:48.129167753  [2025-11-14 00:39:48] frigate.app                    INFO    : Capture process started for cam_supply_room: 455
s6-rc: info: service legacy-services successfully started
2025-11-13 23:39:48.343733211  [2025-11-14 00:39:48] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2025-11-13 23:39:48.824087783  127.0.0.1 - - [14/Nov/2025:00:39:48 +0100] "" 400 0 "-" "-" "-"
2025-11-13 23:39:48.854952832  [2025-11-14 00:39:48] frigate.api.fastapi_app        INFO    : FastAPI started
2025-11-13 23:39:49.092740353  [2025-11-14 00:39:49] frigate.comms.mqtt             ERROR   : Unable to connect to MQTT server: MQTT Not authorized
2025-11-13 23:39:49.093955002  [2025-11-14 00:39:49] frigate.comms.mqtt             ERROR   : MQTT disconnected
2025-11-13 23:39:51.098989259  [2025-11-14 00:39:51] frigate.comms.mqtt             ERROR   : Unable to connect to MQTT server: MQTT Not authorized
2025-11-13 23:39:51.101087816  [2025-11-14 00:39:51] frigate.comms.mqtt             ERROR   : MQTT disconnected
2025-11-13 23:39:51.964702650  [INFO] Starting go2rtc healthcheck service...
2025-11-13 23:39:55.105445045  [2025-11-14 00:39:55] frigate.comms.mqtt             ERROR   : Unable to connect to MQTT server: MQTT Not authorized
2025-11-13 23:39:55.107355867  [2025-11-14 00:39:55] frigate.comms.mqtt             ERROR   : MQTT disconnected
2025-11-13 23:40:03.114492774  [2025-11-14 00:40:03] frigate.comms.mqtt             ERROR   : Unable to connect to MQTT server: MQTT Not authorized
2025-11-13 23:40:03.117209447  [2025-11-14 00:40:03] frigate.comms.mqtt             ERROR   : MQTT disconnected
2025-11-13 23:40:12.930964547  172.30.32.2 - - [14/Nov/2025:00:40:12 +0100] "GET / HTTP/1.1" 200 2649 "-" "HomeAssistantSupervisor/2025.11.2 aiohttp/3.13.2 Python/3.13" "-"
2025-11-13 23:40:19.120102819  [2025-11-14 00:40:19] frigate.comms.mqtt             ERROR   : Unable to connect to MQTT server: MQTT Not authorized
2025-11-13 23:40:19.122004205  [2025-11-14 00:40:19] frigate.comms.mqtt             ERROR   : MQTT disconnected
2025-11-13 23:40:48.966867130  127.0.0.1 - - [14/Nov/2025:00:40:48 +0100] "" 400 0 "-" "-" "-"
2025-11-13 23:40:51.125161940  [2025-11-14 00:40:51] frigate.comms.mqtt             ERROR   : Unable to connect to MQTT server: MQTT Not authorized
2025-11-13 23:40:51.126988384  [2025-11-14 00:40:51] frigate.comms.mqtt             ERROR   : MQTT disconnected
2025-11-13 23:41:49.106020750  127.0.0.1 - - [14/Nov/2025:00:41:49 +0100] "" 400 0 "-" "-" "-"
2025-11-13 23:41:55.130552315  [2025-11-14 00:41:55] frigate.comms.mqtt             ERROR   : Unable to connect to MQTT server: MQTT Not authorized
2025-11-13 23:41:55.132810712  [2025-11-14 00:41:55] frigate.comms.mqtt             ERROR   : MQTT disconnected

[hawkeye217]

Your Frigate config looks fine. You'll want to check your MQTT broker logs.

[KimSchehl]

I guess so?

[hawkeye217]

The connection from mqtt_user does not seem to be from Frigate. The logs show a different IP address for the connections from Frigate. I'd look again at how you have credentials set up with the broker.

[KimSchehl]

Before installing frigate using the git Repository in the Add-Ons, I tried the HACS frigate install. But I uninstalled the HACS frigate and try to use the Add-On directly. Could it be some kind of remains of the HACS install?
How can I check where this mqtt_user is coming from?

[hawkeye217]

Whatever is running on the Docker network as 172.30.32.1 is what is using mqtt_user. Your Frigate connection is an IPv6 address, fd0c:ac1e:2100::9.

[KimSchehl]

I uninstalled it now in my home assistant and installed in my docherhost. It works there. I connected the HA integration to the dockerhost container. It works fine now.
But thanks a lot for your detailed help.

[inkeep-ai-assistant[bot]]

The "MQTT Not authorized" error you're seeing is a common issue when connecting Frigate to MQTT in Home Assistant. Based on the documentation and similar cases, here are the most likely causes:

Try using localhost or 127.0.0.1 instead of core-mosquitto

The FAQ addresses this specific issue: if MQTT isn't working in docker, try using the IP of the device hosting the MQTT server instead of localhost, 127.0.0.1, or mosquitto.ix-mosquitto.svc.cluster.local. This is because Frigate does not run in host mode so localhost points to the Frigate container and not the host device's network(1).

However, for Home Assistant Add-ons specifically, core-mosquitto should work. If it doesn't, try:

mqtt:
  enabled: True
  host: 127.0.0.1
  port: 1883
  user: mqtt_frigate
  password: D7gf2iHs35

(1)

Verify your Mosquitto user configuration

The user credentials must be properly configured in the Mosquitto broker. From the discussions, users have reported that creating a Home Assistant user (with either user or admin role) and using those credentials in the Frigate config resolved the authorization issue(2).

Make sure the mqtt_frigate user you created has the correct permissions in your Mosquitto broker configuration.

Check for SSL/TLS configuration issues

One discussion revealed that when TLS certificates are specified but not properly configured, it can cause authorization failures. The error Must configure SSL context before using tls_insecure_set indicates SSL configuration problems(2).

Since your config doesn't include TLS settings, this shouldn't be your issue, but if you add them later, ensure they're properly configured.

Alternative: Disable client ID requirements

One user found that setting use_username_as_clientid to false in the Mosquitto broker configuration resolved authorization issues when username and password weren't being used(3). While your setup uses credentials, if the issue persists, you might check your Mosquitto broker's client ID requirements.

Try these steps in order and check your Frigate logs after each change to see if the connection succeeds.

📚 Sources:

1. Frequently Asked Questions
2. [Config Support]: mqtt config with nginx and duckdns setup in HAOS
3. [Config Support]:MQTT Not Authorized/use_username_as_clientid

---

Have another question? Just tag @inkeep.