Cant connect mqtt on frigate

[mmaaligema]

Describe the problem you are having

Cant connect mqtt on frigate

Version

0.14.1

Frigate config file

mqtt:
  host: 192.168.1.119:8124
  topic_prefix: frigate
  client_id: frigate
  user: ******
  password: ******
  stats_interval: 60

cameras:
  #simple camera example
  koket:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://admin:Clarence1974%[email protected]:554/axis-media/media.amp
          roles:
            - record
            - detect
    detect:
      height: 720
      fps: 5
  altanen:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://admin:Clarence1974%[email protected]:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
          roles:
            - record
            - detect
    detect:
      height: 720
      fps: 5

record:
  enabled: true
  retain:
    days: 7
    mode: motion
  events:
    retain:
      default: 14
      mode: active_objects

ffmpeg:
  hwaccel_args: preset-rpi-64-h264

objects:
  track:
    - person
    - dog
    - cat
  filters:
    person:
      # Optional: minimum width*height of the bounding box for the detected object (default: 0)
      min_area: 0
      # Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
      max_area: 100000
      # Optional: minimum score for the object to initiate tracking (default: shown below)
      min_score: 0.5
      # Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
      threshold: 0.7
version: 0.14

Relevant Frigate log output

2025-02-06 17:48:07
frigate.comms.mqtt
Unable to publish to events: client is not connected
error
2025-02-06 17:48:08
frigate.comms.mqtt
Unable to publish to koket/person/snapshot: client is not connected
error
2025-02-06 17:48:23
frigate.comms.mqtt
Unable to publish to events: client is not connected
error
2025-02-06 17:48:23
frigate.comms.mqtt
Unable to publish to events: client is not connected
error
2025-02-06 17:48:23
frigate.comms.mqtt
Unable to publish to koket/person/snapshot: client is not connected
error
2025-02-06 17:48:24
frigate.comms.mqtt
Unable to publish to koket/person/snapshot: client is not connected
error
2025-02-06 17:48:32
frigate.comms.mqtt
Unable to publish to events: client is not connected
error
2025-02-06 17:48:32
frigate.comms.mqtt
Unable to publish to events: client is not connected
error
2025-02-06 17:48:33
frigate.comms.mqtt
Unable to publish to koket/person/snapshot: client is not connected
error
2025-02-06 17:48:33
frigate.comms.mqtt
Unable to publish to koket/person/snapshot: client is not connected
error
2025-02-06 17:48:36
frigate.comms.mqtt
Unable to publish to camera_activity: client is not connected
error
2025-02-06 17:48:39
frigate.comms.mqtt
Unable to publish to camera_activity: client is not connected
error
2025-02-06 17:48:39
frigate.comms.mqtt
Unable to publish to camera_activity: client is not connected
error
2025-02-06 17:48:44
frigate.comms.mqtt
Unable to publish to events: client is not connected
error
2025-02-06 17:48:44
frigate.comms.mqtt
Unable to publish to events: client is not connected

Relevant go2rtc log output

Type
Timestamp
Tag
Message
info
2025-02-06 16:34:51
startup
Preparing new go2rtc config...
info
2025-02-06 16:34:52
startup
Got IP address from supervisor: 192.168.1.119
info
2025-02-06 16:34:52
startup
Got WebRTC port from supervisor: 8555
info
2025-02-06 16:34:54
startup
Starting go2rtc...
info
2025-02-06 16:34:54
startup
go2rtc platform=linux/arm64 revision=b2399f3 version=1.9.2
info
2025-02-06 16:34:54
startup
config path=/dev/shm/go2rtc.yaml
info
2025-02-06 16:34:54
api
listen addr=:1984
info
2025-02-06 16:34:54
rtsp
listen addr=:8554
info
2025-02-06 16:34:54
webrtc
listen addr=:8555/tcp
info
2025-02-06 16:35:01
startup
Starting go2rtc healthcheck service...

Frigate stats

No response

Operating system

HassOS

Install method

HassOS Addon

docker-compose file or Docker CLI command

Vet ej

Object Detector

CPU (no coral)

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

[hawkeye217]

See the reference config in the docs.

Don't specify the port in the host line.

mqtt:
  host: 192.168.1.119
  port: 8124
  ...