blakeblackshear / frigate

NVR with realtime local object detection for IP cameras
https://frigate.video
MIT License
18.78k stars 1.71k forks source link

[Config Support]: frigate.comms.mqtt ERROR : Unable to publish to stats: client is not connected #9224

Closed albotroz closed 9 months ago

albotroz commented 9 months ago

Describe the problem you are having

I can access my surveillance cameras, they are displayed, etc.

But what do these error messages mean and how to fix it?

And btw, I cannot access go2rtc dashboard because of 404: Not Found.

Version

0.12.1-367D724

Frigate config file

mqtt:
  # Optional: Enable mqtt server (default: shown below)
  enabled: True  
  # HA-OS IP
  host: 192.xxx.xxx.xx
  # Optional: port (default: shown below)
  port: 1883
  # mqttuser - hier dein username rein ohne "" o.ä
  user: xx
  # mqttpassword - hier dein pw rein ohne "" o.ä
  password: xx
database:
  path: /config/frigate.db       

detectors:
#  coral:
#    type: edgetpu
#    device: usb
  cpu1:
    type: cpu
    num_threads: 3
  cpu2:
    type: cpu
    num_threads: 3

ffmpeg:
  hwaccel_args: preset-rpi-64-h264

go2rtc:
  streams:
    front:
      - rtsp://USER:PW@192.xxx.xxx.xxx:554/h264Preview_01_main # <- stream which supports video & aac audio.
      - "ffmpeg:front#audio=opus" # <- copy of the stream which transcodes audio to opus 
    front_sub:
      - rtsp://USER:PW@192.xxx.xxx.xxx:554/h264Preview_01_sub # <- stream which supports video & aac audio.
      - "ffmpeg:front_sub#audio=opus" # <- copy of the stream which transcodes audio to opus
    hof:
      - rtsp://USER:PW@192.xxx.xxx.xxx:554/11 # <- stream which supports video & aac audio.
    hof_sub:
      - rtsp://USER:PW@192.xxx.xxx.xxx:554/12 # <- stream which supports video & aac audio.

##############################################################################################
# Kamera von Front
##############################################################################################

cameras:
  # Kameraname
  front:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
        - path: rtsp://127.0.0.1:8554/front # RTSP Stream High Res
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/front_sub # RTPS Stream Low Res
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      enabled: True # <---- disable detection until you have a working camera feed                                                        
      width: 640
      height: 360
    objects:
      track:
        - person
      filters:
        person:
          threshold: 0.74
    snapshots:
      enabled: False
#      timestamp: True
#      bounding_box: True
      retain:
        default: 7
    record:
      enabled: False
      events:
        retain:
          default: 7
#    motion:
#      mask:
#        - 2024,238,1528,171,1330,189,1124,214,1081,342,751,336,748,379,379,385,0,407,0,192,0,0,837,0,2560,0,2560,157,2560,360
#        - 1194,1920,1041,1783,0,1791,0,1920
#      zones:
#        Bewegung Front:
#        coordinates: 0,1920,0,0,2560,0,2560,1920
    live:
      stream_name: front_sub

##############################################################################################
# Kamera vom Hof
##############################################################################################

  hof:                                                            #Kameraname
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
        - path: rtsp://127.0.0.1:8554/hof    #RTSP Stream High Res
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/hof_sub          #RTPS Stream Low Res
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      enabled: True # <---- disable detection until you have a working camera feed                                                       
      width: 640
      height: 352
    objects:
      track:
        - person
      filters:
        person:
          threshold: 0.74
    snapshots:
      enabled: False
#      timestamp: True
#      bounding_box: True
      retain:
        default: 7
    record:
      enabled: False
      events:
        retain:
          default: 7
#    motion:
#      mask:
#        - 2024,238,1528,171,1330,189,1124,214,1081,342,751,336,748,379,379,385,0,407,0,192,0,0,837,0,2560,0,2560,157,2560,360
#        - 1194,1920,1041,1783,0,1791,0,1920
#      zones:
#        Bewegung Hof:
#        coordinates: 0,1920,0,0,2560,0,2560,1920
    live:
      stream_name: hof_sub

##############################################################################################

# Optional: birdseye configuration
# NOTE: Can (enabled, mode) be overridden at the camera level
birdseye:
  # Optional: Enable birdseye view (default: True)
  enabled: True
  # Optional: Restream birdseye via RTSP (default: False)
  # NOTE: Enabling this will set birdseye to run 24/7 which may increase CPU usage somewhat.
  restream: False
  # Optional: Width of the output resolution (default: 1280)
  width: 1280
  # Optional: Height of the output resolution (default: 720)
  height: 720
  # Optional: Encoding quality of the mpeg1 feed (default: 8)
  # 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
  quality: 15
  # Optional: Mode of the view. Available options are: objects, motion, and continuous
  #   objects - cameras are included if they have had a tracked object within the last 30 seconds
  #   motion - cameras are included if motion was detected in the last 30 seconds
  #   continuous - all cameras are included always
  mode: continuous

# Optional
ui:
  # Optional: Set the default live mode for cameras in the UI (default: mse)
  live_mode: webrtc
  # Optional: Set a timezone to use in the UI (default: use browser local time)
  timezone: Europe/Berlin
  # Optional: Use an experimental recordings / camera view UI (default: false)
  use_experimental: False
  # Optional: Set the time format used.
  # Options are browser, 12hour, or 24hour (default: browser)
  time_format: 24hour
  # Optional: Set the date style for a specified length.
  # Options are: full, long, medium, short
  # Examples:
  #    short: 2/11/23
  #    medium: Feb 11, 2023
  #    full: Saturday, February 11, 2023
  # (default: short).
  date_style: full
  # Optional: Set the time style for a specified length.
  # Options are: full, long, medium, short
  # Examples:
  #    short: 8:14 PM
  #    medium: 8:15:22 PM
  #    full: 8:15:22 PM Mountain Standard Time
  # (default: medium).
  time_style: medium
  # Optional: Ability to manually override the date / time styling to use strftime format
  # https://www.gnu.org/software/libc/manual/html_node/Formatting-Calendar-Time.html
  # possible values are shown above (default: not set)
  strftime_fmt: "%d/%m/%Y %H:%M"

Relevant log output

2024-01-06 04:02:43.768523663  [INFO] Starting Frigate...
2024-01-06 04:02:47.868700960  [2024-01-06 05:02:47] frigate.app                    INFO    : Starting Frigate (0.12.1-367d724)
2024-01-06 04:02:47.966518363  [2024-01-06 05:02:47] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-01-06 04:02:47.974094503  [2024-01-06 05:02:47] peewee_migrate                 INFO    : Starting migrations
2024-01-06 04:02:47.987558160  [2024-01-06 05:02:47] peewee_migrate                 INFO    : There is nothing to migrate
2024-01-06 04:02:48.047523934  [2024-01-06 05:02:48] detector.cpu1                  INFO    : Starting detection process: 300
2024-01-06 04:02:48.053930264  [2024-01-06 05:02:48] frigate.detectors              WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2024-01-06 04:02:48.068642176  [2024-01-06 05:02:48] frigate.app                    INFO    : Output process started: 303
2024-01-06 04:02:48.080092710  [2024-01-06 05:02:48] detector.cpu2                  INFO    : Starting detection process: 302
2024-01-06 04:02:48.081048744  [2024-01-06 05:02:48] frigate.detectors              WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2024-01-06 04:02:48.090828451  [2024-01-06 05:02:48] frigate.app                    INFO    : Camera processor started for front: 307
2024-01-06 04:02:48.110918585  [2024-01-06 05:02:48] frigate.app                    INFO    : Camera processor started for hof: 309
2024-01-06 04:02:48.129162892  [2024-01-06 05:02:48] frigate.app                    INFO    : Capture process started for front: 310
2024-01-06 04:02:48.148708565  [2024-01-06 05:02:48] frigate.app                    INFO    : Capture process started for hof: 312
2024-01-06 04:02:51.446799985  [2024-01-06 05:02:51] frigate.comms.mqtt             ERROR   : Unable to publish to front/all: client is not connected
2024-01-06 04:02:53.300549198  [2024-01-06 05:02:53] frigate.comms.mqtt             ERROR   : Unable to publish to hof/all: client is not connected
2024-01-06 04:02:59.981977821  [2024-01-06 05:02:59] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:04:02.047349407  [2024-01-06 05:04:02] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:04:42.906405556  [2024-01-06 05:04:42] frigate.output                 WARNING : Unable to copy frame hof1704513802.403439 to birdseye.
2024-01-06 04:05:05.357052503  [2024-01-06 05:05:05] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:06:08.660682822  [2024-01-06 05:06:08] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:07:11.966617332  [2024-01-06 05:07:11] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:08:15.269462388  [2024-01-06 05:08:15] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:09:18.565998604  [2024-01-06 05:09:18] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:10:21.863932491  [2024-01-06 05:10:21] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:11:25.164067112  [2024-01-06 05:11:25] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:12:28.455915950  [2024-01-06 05:12:28] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:13:07.086161177  [2024-01-06 05:13:07] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:13:16.951639540  [2024-01-06 05:13:16] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:13:31.757009032  [2024-01-06 05:13:31] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:14:35.061942312  [2024-01-06 05:14:35] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:14:40.301262260  [2024-01-06 05:14:40] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:15:29.768300405  [2024-01-06 05:15:29] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:15:38.375897699  [2024-01-06 05:15:38] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:16:02.293837467  [2024-01-06 05:16:02] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:16:06.416714827  [2024-01-06 05:16:06] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:16:41.744023307  [2024-01-06 05:16:41] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:17:45.058426223  [2024-01-06 05:17:45] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:18:48.402816653  [2024-01-06 05:18:48] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:19:51.737079231  [2024-01-06 05:19:51] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:20:55.054265725  [2024-01-06 05:20:55] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:21:58.356846219  [2024-01-06 05:21:58] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:23:01.678206424  [2024-01-06 05:23:01] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:23:15.917181026  [2024-01-06 05:23:15] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:23:22.824756522  [2024-01-06 05:23:22] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:24:04.980576122  [2024-01-06 05:24:04] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:25:08.282636035  [2024-01-06 05:25:08] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:26:11.588960179  [2024-01-06 05:26:11] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:27:14.901946702  [2024-01-06 05:27:14] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:28:02.874308599  [2024-01-06 05:28:02] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:28:12.457571830  [2024-01-06 05:28:12] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:28:18.206702074  [2024-01-06 05:28:18] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:29:21.512610233  [2024-01-06 05:29:21] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:29:55.131189042  [2024-01-06 05:29:55] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:30:13.785552654  [2024-01-06 05:30:13] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:30:24.812118436  [2024-01-06 05:30:24] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:31:02.853695052  [2024-01-06 05:31:02] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:31:04.846068416  [2024-01-06 05:31:04] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:31:28.126044261  [2024-01-06 05:31:28] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:31:44.455806355  [2024-01-06 05:31:44] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:32:31.428451512  [2024-01-06 05:32:31] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:33:17.791438942  [2024-01-06 05:33:17] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:33:34.748881290  [2024-01-06 05:33:34] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:33:48.727682261  [2024-01-06 05:33:48] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:34:02.999957727  [2024-01-06 05:34:02] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:34:38.110507866  [2024-01-06 05:34:38] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:35:41.419344503  [2024-01-06 05:35:41] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:36:44.711424839  [2024-01-06 05:36:44] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:37:48.025571150  [2024-01-06 05:37:48] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:38:51.347015980  [2024-01-06 05:38:51] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:39:42.747714901  [2024-01-06 05:39:42] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:39:51.424851130  [2024-01-06 05:39:51] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:39:54.664082907  [2024-01-06 05:39:54] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:40:57.976691489  [2024-01-06 05:40:57] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:41:15.548431613  [2024-01-06 05:41:15] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:41:37.410960254  [2024-01-06 05:41:37] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:42:01.284224082  [2024-01-06 05:42:01] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:42:21.948293972  [2024-01-06 05:42:21] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:42:29.409863612  [2024-01-06 05:42:29] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:43:04.582141723  [2024-01-06 05:43:04] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:44:07.886013926  [2024-01-06 05:44:07] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected
2024-01-06 04:44:30.357316073  [2024-01-06 05:44:30] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:44:35.813904521  [2024-01-06 05:44:35] frigate.comms.mqtt             ERROR   : Unable to publish to hof/motion: client is not connected
2024-01-06 04:45:11.225033033  [2024-01-06 05:45:11] frigate.comms.mqtt             ERROR   : Unable to publish to stats: client is not connected

Frigate stats

No response

Operating system

HassOS

Install method

HassOS Addon

Coral version

CPU (no coral)

Any other information that may be helpful

No response

NickM-27 commented 9 months ago

they mean that mqtt is not connection, I'd suggest checking your mqtt broker logs

albotroz commented 9 months ago

Thanks. Can be closed. MQTT was not active.