[Support]: Unable to publish to mqtt-topic: client is not connected

[icicimov]

Describe the problem you are having

Seems this has come up several times before, i can see similar issues in 8083 and 10023 without any conclusion as why is it not working.

Running Frigate 0.14 in a Docker container on Debian 12 Bookworm. This is the host IP:

igorc@mini01:~/frigate-docker$ ip -br a s eno1
eno1             UP             192.168.1.212/24

This is a snippet of the frigate errors:

2024-09-04 17:54:00.373540187  [2024-09-04 17:54:00] frigate.comms.mqtt  ERROR  : Unable to publish to camera1/all: client is not connected
2024-09-04 17:54:03.916911180  [2024-09-04 17:54:03] frigate.comms.mqtt  ERROR  : Unable to publish to camera2/audio/rms: client is not connected

and this is the mqtt config from config.yml:

mqtt:
  enabled: true
  host: 192.168.122.211
  port: 1883
  user: mqtt_user
  password: mqtt_passwd
  stats_interval: 300

Testing the connectivity and functionality of the mqtt server that's running as an add-on inside HASSOS vm on the 192.168.122.211 host with TCP/1883 port forwarded to the VM. Login to the frigate container, install and test the connectivity plus publish to a test topic:

user@host:~/frigate-docker$ docker exec -it frigate bash
root@2389089c0fbd:/opt/frigate# nc -v -w1 192.168.1.211 1883
Connection to 192.168.1.211 1883 port [tcp/*] succeeded!
root@2389089c0fbd:/opt/frigate# apt install mosquitto-clients
root@2389089c0fbd:/opt/frigate# dpkg -l | grep mosq
ii  libmosquitto1:amd64                  2.0.11-1+deb11u1               amd64        MQTT version 5.0/3.1.1/3.1 client library
ii  mosquitto-clients                    2.0.11-1+deb11u1               amd64        Mosquitto command line MQTT clients
root@2389089c0fbd:/opt/frigate# mosquitto_pub -h 192.168.1.211 -p 1883 -u mqtt_user -P mqtt_passwd -t 'test/topic' -m "`date` Hello from Frigate docker"
root@2389089c0fbd:/opt/frigate#

In a mosquitto subscriber started in another console:

user@host:~/frigate-docker$ mosquitto_sub -v -h 192.168.1.211 -p 1883 -u mqtt_user -P mqtt_passwd -t 'test/topic'
test/topic Wed Sep  4 20:04:25 AEST 2024 Hello from Frigate docker

So, all is working. I'm able to connect to mqtt and publish to a topic from inside Frigate container and pickup the messages via a subscriber to the same topic. Yet frigate itself is struggling for some reason.

Version

0.14.0-da913d8

What browser(s) are you using?

No response

Frigate config file

mqtt:
  enabled: true
  host: 192.168.122.211
  port: 1883
  user: mqtt_user
  password: mqtt_passwd
  stats_interval: 300

Relevant Frigate log output

2024-09-04 17:54:00.209727639  [2024-09-04 17:54:00] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/audio/dBFS: client is not connected
2024-09-04 17:54:00.211250021  [2024-09-04 17:54:00] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/audio/rms: client is not connected
2024-09-04 17:54:00.373540187  [2024-09-04 17:54:00] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/all: client is not connected
2024-09-04 17:54:00.373704739  [2024-09-04 17:54:00] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/motion: client is not connected
2024-09-04 17:54:00.999063272  [2024-09-04 17:54:00] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/audio/dBFS: client is not connected
2024-09-04 17:54:01.000054465  [2024-09-04 17:54:00] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/audio/rms: client is not connected
2024-09-04 17:54:01.958751860  [2024-09-04 17:54:01] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/audio/dBFS: client is not connected
2024-09-04 17:54:01.959971187  [2024-09-04 17:54:01] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/audio/rms: client is not connected
2024-09-04 17:54:02.930393613  [2024-09-04 17:54:02] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/audio/dBFS: client is not connected
2024-09-04 17:54:02.931039367  [2024-09-04 17:54:02] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/audio/rms: client is not connected
2024-09-04 17:54:03.916149157  [2024-09-04 17:54:03] frigate.comms.mqtt             ERROR   : Unable to publish to camera2/audio/dBFS: client is not connected
2024-09-04 17:54:03.916911180  [2024-09-04 17:54:03] frigate.comms.mqtt             ERROR   : Unable to publish to camera2/audio/rms: client is not connected
2024-09-04 17:54:03.956713052  [2024-09-04 17:54:03] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/audio/dBFS: client is not connected
2024-09-04 17:54:03.960409453  [2024-09-04 17:54:03] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/audio/rms: client is not connected
2024-09-04 17:54:04.025584933  [2024-09-04 17:54:04] frigate.comms.mqtt             ERROR   : Unable to publish to camera2/all: client is not connected
2024-09-04 17:54:04.025802047  [2024-09-04 17:54:04] frigate.comms.mqtt             ERROR   : Unable to publish to camera2/motion: client is not connected
2024-09-04 17:54:04.216046782  [2024-09-04 17:54:04] frigate.comms.mqtt             ERROR   : Unable to publish to camera2/audio/dBFS: client is not connected
2024-09-04 17:54:04.217210472  [2024-09-04 17:54:04] frigate.comms.mqtt             ERROR   : Unable to publish to camera2/audio/rms: client is not connected
2024-09-04 17:54:04.918192799  [2024-09-04 17:54:04] frigate.comms.mqtt             ERROR   : Unable to publish to camera1/audio/dBFS: client is not connected

Relevant go2rtc log output

It is not about the cameras.

FFprobe output from your camera

It is not about the cameras.

Frigate stats

user@host:~/frigate-docker$ sudo docker stats --no-stream frigate
CONTAINER ID   NAME      CPU %     MEM USAGE / LIMIT     MEM %     NET I/O          BLOCK I/O        PIDS
2389089c0fbd   frigate   36.33%    717.5MiB / 15.51GiB   4.52%     522MB / 24.4MB   283kB / 22.3MB   354

Operating system

Debian

Install method

Docker Compose

Object Detector

Coral

Network connection

Wired

Camera make and model

It is not about the cameras.

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

[NickM-27]

Maybe try putting quotes around the user / pass

[icicimov]

Thanks for the suggestion but it didn't work. Setting frigate.comms.mqtt: debug also didn't print out any debug messages really so not sure how to troubleshoot this further.

[icicimov]

Ok, this is incredibly embarrassing the mistake was staring at my face all this time:

mqtt:
  enabled: true
  host: 192.168.122.211  <===== WRONG IP ADDRESS :-/
  port: 1883
  user: mqtt_user
  password: mqtt_passwd
  stats_interval: 300

Copy/paste error from another frigate instance i had running on a different VLAN 🥺 . After fixing it to 192.168.1.211 it is all working:

2024-09-06 14:54:35: New client connected from 192.168.1.212:44439

Thanks for having a look and sorry for wasting your time.

[psCLE]

Your mistake helped me, I was using localhost then 127.0.0.1, nothing worked. Then I read your post and put in the actual LAN address 192.168.88.10 and it worked.