[Support]: 0.18.2 – frigate/<camera>/motion MQTT topic and motion debug boxes never fire on 7 of 9 cameras (object detection works)

[LUISBURNAY]

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

On 9 cameras with identical motion settings, only 2 (rampa_portao, porta_rua) publish frigate//motion (ON/OFF) and show motion boxes in the Debug view. The other 7 (jardim_tras, cozinha, escritorio, garagem, sala_lareira, deck_frente, rampa_lavandaria) never publish on frigate//motion, and the Debug view with "Motion boxes" enabled never shows a box, even while a person walks in front of the camera.

Object detection on the same cameras works: person events are created (with clips), appear in Review, and "Bounding boxes" in Debug shows the person. _all_occupancy toggles correctly. Only the motion signal is missing.

Home Assistant (Frigate integration v5.15.6) shows binary_sensor.*_motion stuck: it goes off -> on for a few seconds right after a Frigate restart (that ON was not visible in an MQTT listener on frigate/+/motion), then never changes again. Example: jardim_tras motion on since the 0.18.2 start (13:37 UTC) and unchanged when a person walked past at 14:54 UTC, while all_occupancy went off at 14:54:10.

Timeline: last real ON for jardim_tras was 2026-10-24 23:52:51 UTC, 6 s after a container start. Since then only the restart-time ON. Happened on 0.18.1 and still on 0.18.2 (upgrade did not change it). I don't know whether it worked on 0.16/0.17.

also,
the docs AI listed skip_motion_threshold, lightning_threshold, masks and thresholds; all identical or unset on all cameras.”

Steps to reproduce

1. Run Frigate 0.18.2 (Docker, Proxmox LXC) with 9 cameras, default motion settings and MQTT enabled to a Home Assistant Mosquitto broker.
2. In Home Assistant MQTT > Listen to a topic, subscribe to frigate/+/motion.
3. Walk in front of one of the 7 affected cameras (e.g. jardim_tras).
4. Result: no message for that camera on frigate/+/motion; in Frigate Live > camera > Debug with "Motion boxes" on, no box appears. Only rampa_portao and porta_rua ever show motion messages.
5. Same moment: "Bounding boxes" shows the person, a person event is created, and the _all_occupancy sensor changes in HA.
6. Restarting Frigate, reloading the HA integration, and adding a zone to an affected camera made no difference.

Version

0.18.2-cfa08c5

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

chrome on windows and on android phone

Frigate config file

/tank/frigate-appdata/config/config.yml
# =====================================================================
# Frigate 0.16 - config.yml (cleaned and commented)
# Streams live in /opt/frigate/config/go2rtc.yaml (standalone go2rtc
# container). After editing this file: docker restart frigate
# After editing go2rtc.yaml:           docker restart go2rtc
# =====================================================================

# ---------------------------------------------------------------------
# MQTT - how Frigate talks to Home Assistant (events, occupancy, etc.)
# The password is read from an environment variable instead of being
# written here. Add to the frigate container in docker-compose:
#   environment:
#     FRIGATE_MQTT_PASSWORD: ***
# (Change the broker password too, the old one was shared in chat.)
# ---------------------------------------------------------------------
mqtt:
  enabled: true
  host: 192.168.1.161
  port: 1883
  user: frigate
  password: ***

# ---------------------------------------------------------------------
# DETECTOR - the engine that runs the object-detection model.
# "cpu" works but is the slowest option. Currently ~10 ms per inference
# and ~20% of the CT, so OK for 10 cameras. Upgrade path: OpenVINO on
# the Intel iGPU (needs /dev/dri passed through to the CT).
# ---------------------------------------------------------------------
detectors:
  cpu:
    type: cpu

# ---------------------------------------------------------------------
# go2rtc block REMOVED on purpose.
# The standalone go2rtc container serves all streams on port 8554, and
# Frigate's built-in go2rtc is not used. A go2rtc: section here did
# nothing (and exposed the camera password).
# ---------------------------------------------------------------------

# ---------------------------------------------------------------------
# BIRD CLASSIFICATION - after a "bird" is detected, a second small model
# tries to identify the species. Only works on cameras that track birds
# (cozinha and rampa_lavandaria below).
# ---------------------------------------------------------------------
classification:
  bird:
    enabled: true
    threshold: 0.75

# ---------------------------------------------------------------------
# RECORDING - what footage is kept, and for how long.
# A segment is kept if it qualifies under ANY of the three rules, and
# the longest matching rule wins.
#   retain      -> baseline, applies to everything
#   alerts      -> footage around alerts (person/car by default)
#   detections  -> footage around other tracked objects (dog, bird...)
# mode: all = everything | motion = only segments with motion |
#       active_objects = only segments with a moving tracked object
# ---------------------------------------------------------------------
record:
  enabled: true
  alerts:
    retain:
      days: 15         # person events kept 15 days
      mode: motion
  detections:
    retain:
      days: 10         # dog/bird/etc. events kept 10 days (explicit, same as default)
      mode: motion

# ---------------------------------------------------------------------
# SNAPSHOTS - JPEG of each tracked object, cheap in disk terms.
# ---------------------------------------------------------------------
  continuous:
    days: 7
  motion:
    days: 7
snapshots:
  enabled: true
  retain:
    default: 15

# ---------------------------------------------------------------------
# OBJECT TRACKING (global defaults, cameras can override)
# track   -> labels Frigate looks for
# filters -> reject false positives:
#   min_area / max_area : box size in pixels of the detect stream
#   min_ratio / max_ratio : width / height of the box
#   min_score : lowest score for a detection to count at all
#   threshold : median score needed to confirm the object
# ---------------------------------------------------------------------
objects:
  track:
    - person
    - dog
  filters:
    person:
      min_area: 2000
      min_ratio: 0.35   # normal upright person is taller than wide
      max_ratio: 1.2
      min_score: 0.6
      threshold: 0.75
    dog:
      min_area: 1200
      max_area: 100000
      min_ratio: 0.6
      max_ratio: 1.7
      min_score: 0.5
      threshold: 0.65

# ---------------------------------------------------------------------
# DETECTION - global switch for running object detection.
# ---------------------------------------------------------------------
detect:
  enabled: true

# =====================================================================
# CAMERAS
# Every camera uses the same pattern:
#   record role -> main stream (1080p), used for recordings
#   detect role -> sub stream (640x480), used for object detection
# Both are read from the local go2rtc restream (127.0.0.1:8554).
# detect width/height MUST match the real sub stream resolution.
# =====================================================================
cameras:
  jardim_tras:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/jardim_tras_main
          roles: [record]
        - path: rtsp://127.0.0.1:8554/jardim_tras_sub
          roles: [detect]
    detect:
      width: 640
      height: 480

    zones:
      jardim_tras_zona1:
        coordinates: 0.018,0.057,0.988,0.072,0.982,0.981,0.015,0.976
        enabled: true
        inertia: 3
        loitering_time: 0
  deck_frente:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/deck_frente_main
          roles: [record]
        - path: rtsp://127.0.0.1:8554/deck_frente_sub
          roles: [detect]
    detect:
      width: 640
      height: 480
    # Zone = a polygon on the image (coordinates are fractions 0-1 of
    # width/height). Used for HA sensors/notifications and, optionally,
    # for required_zones. loitering_time 0 = no minimum time inside.
    zones:
      Deck_frente_zona:
        coordinates:
          0.01,0.013,0.051,0.194,0.073,0.186,0.278,0.133,0.319,0.108,0.325,0.119,0.376,0.089,0.994,0.551,0.991,0.994,0.003,0.997
        loitering_time: 0

  garagem:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/garagem_main
          roles: [record]
        - path: rtsp://127.0.0.1:8554/garagem_sub
          roles: [detect]
    detect:
      width: 640
      height: 480
    objects:
      filters:
        person:
          min_score: 0.5
          threshold: 0.6

  # Kitchen: fisheye lens, people appear close and cropped, so the person
  # ratio window is widened (global 0.35-1.2 would reject them).
  # Also tracks birds (bird feeder / window) with its own filter.
  cozinha:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/cozinha_main
          roles: [record]
        - path: rtsp://127.0.0.1:8554/cozinha_sub
          roles: [detect]
    detect:
      width: 640
      height: 480
    objects:
      track:            # overrides the global list, so person+dog are repeated
        - person
        - dog
        - bird
      filters:
        person:
          min_area: 2000
          min_ratio: 0.2
          max_ratio: 2.0
          min_score: 0.6
          threshold: 0.75
        bird:
          min_area: 300
          max_area: 40000
          min_score: 0.5
          threshold: 0.6

  # Living room: same fisheye camera model as cozinha, mounted higher
  # (top-down foreshortening), so it gets the same widened ratio window.
  sala_lareira:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/sala_lareira_main
          roles: [record]
        - path: rtsp://127.0.0.1:8554/sala_lareira_sub
          roles: [detect]
    detect:
      width: 640
      height: 480
    objects:
      filters:
        person:
          min_area: 2000
          min_ratio: 0.2
          max_ratio: 2.0
          min_score: 0.6
          threshold: 0.75

  rampa_lavandaria:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/rampa_lavandaria_main
          roles: [record]
        - path: rtsp://127.0.0.1:8554/rampa_lavandaria_sub
          roles: [detect]
    detect:
      width: 640
      height: 480
    objects:
      track:
        - person
        - dog
        - bird
      filters:
        person:
          min_score: 0.5
          threshold: 0.6
        bird:
          min_area: 300
          max_area: 40000
          min_score: 0.5      # no threshold set -> default 0.7

  # Mostly inside the property, so every person here is a real alert.
  # No required_zones needed.
  rampa_portao:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/rampa_portao_main
          roles: [record]
        - path: rtsp://127.0.0.1:8554/rampa_portao_sub
          roles: [detect]
    detect:
      width: 640
      height: 480
    zones:
      rampa_portao_zona:
        coordinates:
          0.258,0.263,0.211,0.393,0.153,0.569,0.11,0.472,0.007,0.756,0.01,0.985,0.992,0.992,0.99,0.02,0.692,0.011,0.679,0.159,0.542,0.141,0.534,0.298,0.499,0.295,0.498,0.212,0.288,0.192
        loitering_time: 0

  # The only camera facing the street.
  # NOTE: porta_rua_zona covers the WHOLE frame (0.005..0.997), so it
  # cannot separate "street" from "property": every person enters it.
  # To stop passers-by becoming alerts:
  #   1. In the Frigate UI (Settings > Masks / Zones) draw a NEW zone only
  #      over your side (doorstep / gate area), e.g. "porta_rua_entrada".
  #   2. Uncomment the review block below and use that zone name.
  # People who never enter that zone are then listed as detections
  # (kept 10 days) instead of alerts (kept 15 days, notified).
  porta_rua:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/porta_rua_main
          roles: [record]
        - path: rtsp://127.0.0.1:8554/porta_rua_sub
          roles: [detect]
    detect:
      width: 640
      height: 480
    zones:
      porta_rua_zona:
        coordinates: 0.005,0.003,0.997,0.005,0.996,0.995,0.003,0.993
        loitering_time: 0
      # porta_rua_entrada:                # <- draw this one in the UI
      #   coordinates: <paste from UI>
      #   loitering_time: 0
    # review:
    #   alerts:
    #     required_zones: [porta_rua_entrada]
    # Motion mask: ignores movement in the masked area for motion
    # detection (e.g. trees, road). Does not hide the area from recording.
    motion:
      mask:

  # Office camera (Hikvision DS-2CD2420F-IW), added 2026-09-29.
  # The sub stream only offers 4 or 6 fps; with fps: 5 Frigate drops
  # the excess. 5 is also the default, so this line is optional.
        motion_mask_1:
          friendly_name: Motion Mask 1
          enabled: true
          coordinates:
            0,0.008,0.992,0.009,0.986,0.642,0.879,0.76,0.732,0.904,0.462,0.984,0.148,0.925,0,0.76
  escritorio:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/escritorio_main
          roles: [record]
        - path: rtsp://127.0.0.1:8554/escritorio_sub
          roles: [detect]
    detect:
      width: 640
      height: 480
      fps: 5

# ---------------------------------------------------------------------
# Optional, global: make dogs count as alerts too (default is only
# person and car). Uncomment if you want it.
# review:
#   alerts:
#     labels: [person, dog]
# ---------------------------------------------------------------------

version: 0.18-0


root@proxmox:~#


 # NOTE: zone jardim_tras_zona1 was added during testing; it made no difference to the motion problem

docker-compose file or Docker CLI command

/tank/frigate-appdata/config/docker-compose.yml
services:
  frigate:
    container_name: frigate
    image: ghcr.io/blakeblackshear/frigate:0.18.2
    privileged: true
    shm_size: "512mb"
    restart: unless-stopped
    network_mode: host
    volumes:
      - /opt/frigate/config:/config

      #- /media/frigate:/media/frigate
      - /mnt/frigate/recordings:/media/frigate/recordings
      - /mnt/frigate/clips:/media/frigate/clips
      - /mnt/frigate/snapshots:/media/frigate/snapshots



      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    environment:
      FRIGATE_RTSP_PASSWORD: ***
      FRIGATE_MQTT_PASSWORD: ***
      LIBVA_DRIVER_NAME: "iHD"

  go2rtc:
    container_name: go2rtc
    image: alexxit/go2rtc:latest
    restart: unless-stopped
    network_mode: host
    volumes:
      - /opt/frigate/config/go2rtc.yaml:/config/go2rtc.yaml


root@proxmox:~#

Relevant Frigate log output

2026-10-26 15:21:40.129647692  2026/10/26 15:21:40 [warn] 245#245: *7747 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028099635&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:41.134288688  2026/10/26 15:21:41 [warn] 247#247: *7749 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028100625&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:42.126311665  2026/10/26 15:21:42 [warn] 247#247: *7752 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028101630&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:42.766715584  2026/10/26 15:21:42 [warn] 248#248: *2331 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.161, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", host: "192.168.1.180:5000"
2026-10-26 15:21:43.334082394  2026/10/26 15:21:43 [warn] 247#247: *7756 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028102629&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:44.327211827  2026/10/26 15:21:44 [warn] 247#247: *7758 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028103621&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:45.113458165  2026/10/26 15:21:45 [warn] 247#247: *7760 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028104621&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:46.064489638  2026/10/26 15:21:46 [warn] 248#248: *7762 using uninitialized "go2rtc_stream_proxy" variable, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", host: "127.0.0.1:5000"
2026-10-26 15:21:46.129541499  2026/10/26 15:21:46 [warn] 247#247: *7764 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028105634&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:47.122749430  2026/10/26 15:21:47 [warn] 247#247: *7766 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028106625&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:47.766036516  2026/10/26 15:21:47 [warn] 246#246: *3427 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.161, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", host: "192.168.1.180:5000"
2026-10-26 15:21:48.125719052  2026/10/26 15:21:48 [warn] 247#247: *7769 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028107629&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:49.120932382  2026/10/26 15:21:49 [warn] 247#247: *7771 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028108626&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:50.129526617  2026/10/26 15:21:50 [warn] 247#247: *7773 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028109634&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:51.118739460  2026/10/26 15:21:51 [warn] 247#247: *7775 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028110624&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:52.127754339  2026/10/26 15:21:52 [warn] 247#247: *7777 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028111620&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:52.765805521  2026/10/26 15:21:52 [warn] 248#248: *2331 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.161, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", host: "192.168.1.180:5000"
2026-10-26 15:21:53.119944649  2026/10/26 15:21:53 [warn] 247#247: *7781 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028112625&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:54.128410321  2026/10/26 15:21:54 [warn] 247#247: *7783 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028113633&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:55.122196797  2026/10/26 15:21:55 [warn] 247#247: *7785 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028114628&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:56.115137201  2026/10/26 15:21:56 [warn] 247#247: *7787 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028115620&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:57.129446563  2026/10/26 15:21:57 [warn] 248#248: *7789 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028116634&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:57.766008639  2026/10/26 15:21:57 [warn] 246#246: *3427 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.161, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", host: "192.168.1.180:5000"
2026-10-26 15:21:58.124960414  2026/10/26 15:21:58 [warn] 248#248: *7792 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028117630&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
2026-10-26 15:21:59.121014699  2026/10/26 15:21:59 [warn] 248#248: *7794 using uninitialized "go2rtc_stream_proxy" variable, client: 192.168.1.175, server: , request: "GET /api/jardim_tras/latest.webp?height=480&cache=1793028118625&mask=1 HTTP/1.1", subrequest: "/auth", host: "frigate.burnay.top", referrer: "https://frigate.burnay.top/"
root@proxmox:~#

Relevant go2rtc log output

No output in the last 30 minutes (no warnings or errors). go2rtc runs as a separate container (alexxit/go2rtc:latest) serving all streams on :8554.

Operating system

Proxmox

Install method

Proxmox via Docker

Network connection

Wired

Camera make and model

escritorio: Hikvision DS-2CD2420F-IW (works: no, motion silent) cozinha, sala_lareira: same fisheye model (motion silent) porta_rua: different brand (motion works) (fill in the models of the other cameras if you know them)

Screenshots of the Frigate UI's System metrics pages

Screenshots not attached: cameras are all at ~5 fps with 0 skipped frames, CPU detector ~10 ms inference; see "Any other information".

Any other information that may be helpful

Stream comparison (real sub stream via ffprobe; detect is scaled to 640x480 on every camera):

• Motion broken: jardim_tras 1280x720@15, deck_frente 1280x720@15, garagem 640x480@15, sala_lareira 640x480@15, rampa_lavandaria 640x480@15, cozinha 640x480@6, escritorio 640x480@6
• Motion works: rampa_portao 1280x720@15, porta_rua 1920x1080@25
  No correlation with resolution or fps.

Full per-camera config diff between a working (rampa_portao) and broken (jardim_tras) camera: only paths, stream names and zones differ; the generated ffmpeg commands are identical.

Zones: the 2 working cameras have a zone, but deck_frente has one and is still broken. Adding a zone to jardim_tras (jardim_tras_zona1) made no difference.

Checked with no effect: restarting Frigate; upgrading 0.18.1 -> 0.18.2; reloading the HA integration; motion settings identical on all 9 (enabled, threshold 30, contour_area 10, lightning_threshold 0.8, skip_motion_threshold null, improve_contrast true, mqtt_off_delay 30). Only porta_rua has a motion mask.

Question: is there a way to dump per-camera motion state or enable motion debug logging to see where the signal is lost?

[inkeep-ai-assistant[bot]]

Your config is the most likely culprit here, specifically the YAML structure under porta_rua.

Look at this block:

    motion:
      mask:

  # Office camera (Hikvision DS-2CD2420F-IW), added 2026-09-29.
  # The sub stream only offers 4 or 6 fps; with fps: 5 Frigate drops
  # the excess. 5 is also the default, so this line is optional.
        motion_mask_1:
          friendly_name: Motion Mask 1
          enabled: true
          coordinates:
            0,0.008,0.992,0.009,0.986,0.642,0.879,0.76,0.732,0.904,0.462,0.984,0.148,0.925,0,0.76

The motion_mask_1 entry is indented far deeper than the mask: key it belongs to, and it is separated from it by comments. Similarly, your record: section has continuous: and motion: keys appearing after the snapshots comment block, below where the detections: block ends. Indentation errors like these change which camera/section the values attach to. Fix the indentation so the mask sits directly under porta_rua.motion.mask, matching the documented structure:

 motion:  
 mask:  
 timestamp:  
 friendly_name: "Camera timestamp"  
 enabled: true  
 coordinates: "0.000,0.427,0.002,0.000,0.999,0.000,0.999,0.781,0.885,0.456,0.700,0.424,0.701,0.311,0.507,0.294,0.453,0.347,0.451,0.400"  

(1)

A second thing worth checking: masks can be toggled off at runtime via MQTT, and that state is independent of the config. Check frigate/<camera_name>/motion_mask/<mask_name>/state for each camera, and also frigate/<camera_name>/motion/state — motion detection itself can be turned off per camera through frigate/<camera_name>/motion/set, which would explain a camera that detects objects but never reports motion.

(2)

Note on the camera name used in these topics: use the camera's ID from the config, not its friendly_name.

(2)

On the MQTT behavior you're seeing: after motion is initially detected, ON is held until no motion has been detected for mqtt_off_delay seconds (30 by default). A sensor stuck ON with no further transitions is consistent with the topic simply never being republished.

(2)

For the per-camera inspection you asked about, you can read and write the live values directly:

• frigate/<camera_name>/motion_threshold/state — current motion threshold (integer)
• frigate/<camera_name>/motion_contour_area/state — current contour area (integer)
• frigate/<camera_name>/improve_contrast/state — ON/OFF
• frigate/<camera_name>/motion_mask/<mask_name>/state — ON/OFF

(2)

Subscribing to these per camera will tell you whether the effective runtime values on the 7 affected cameras actually match what you believe is in the config, which is the fastest way to confirm whether the YAML is being parsed as you expect.

For visual confirmation of where the signal is lost, the built-in Motion Tuner lets you adjust values live and immediately see the effect on what is detected as motion. Navigate to Settings → Camera configuration → Motion tuner and select an affected camera.

(3)

You can also use Debug Replay to re-run the detection pipeline against a recorded clip from an affected camera. Start it from History → {camera} → Actions → Debug Replay, and use From Timeline or Custom to add padding so motion detection has time to settle into the scene.

(4)

Regarding improve_contrast: if you can't find a balance between desired and undesired motion being detected, try disabling improve contrast and revisiting the threshold and contour area.

(3)

📚 Sources:

1. Frigate Configuration
2. MQTT
3. Tuning Motion Detection
4. Analyzing Object Detection

---

Have another question? Just tag @inkeep.

[hawkeye217]

This is not a Frigate bug.

The AI is partially correct here. Your YAML indentation is fine, and motion can't be turned off while detection is enabled, so neither of those is the cause. Your motion sensors on those cameras aren't broken, they're most likely stuck ON. Frigate only publishes to the motion topic when the state changes, and OFF is only sent after 30 seconds with no motion at all. If something in the frame changes constantly, like an on-screen timestamp/clock overlay, motion never goes OFF, so you never see another ON. That matches your HA sensor sitting "on" since startup. Do those 7 cameras have a timestamp overlay? If so, add a motion mask over it (like you have on porta_rua) or disable the overlay on the camera. The Motion Tuner in Settings will show you the boxes it's picking up.

[LUISBURNAY]

Thanks, that was it.
Every one of my 9 cameras has a burned-in date/time overlay, and it was being picked up as constant motion, so the motion topic never reached OFF and HA showed the sensors stuck "on".

What I did: added a motion mask over the clock on each camera (Settings > Camera configuration > Masks / Zones > Motion Mask). It applied live without a restart, and all 9 binary_sensor.*_motion now cycle on/off normally in Home Assistant when I walk in front of each camera.

Two things that may help others:

• The mask has to cover the whole clock, including the edge pixels. On two cameras it only worked after I enlarged the mask by a pixel or two.
• A zone is not enough: zones don't remove an area from motion detection, only a motion mask does.

I confirmed it with the Motion tuner, where a red box appeared intermittently on the seconds digits with nobody in view. I had earlier assumed the debug view showed no motion boxes at all, so that was my mistake.

One thing I can't fully explain: one camera's motion sensor stayed "off" for about 35 hours while person events were still being created. After adding the masks everything has been consistent, so I'm treating this as not a Frigate bug. Feel free to close.

Huge thank you for the help!
Luis Burnay

[LUISBURNAY]

Thank you! you nailed it! this was a great help to solve the problem. im going to close the issue/hep request with the following "Thanks, that was it. Every one of my 9 cameras has a burned-in date/time overlay, and it was being picked up as constant motion, so the motion topic never reached OFF and HA showed the sensors stuck "on". What I did: added a motion mask over the clock on each camera (Settings > Camera configuration > Masks / Zones > Motion Mask). It applied live without a restart, and all 9 binary_sensor.*_motion now cycle on/off normally in Home Assistant when I walk in front of each camera. Two things that may help others: - The mask has to cover the whole clock, including the edge pixels. On two cameras it only worked after I enlarged the mask by a pixel or two. - A zone is not enough: zones don't remove an area from motion detection, only a motion mask does. I confirmed it with the Motion tuner, where a red box appeared intermittently on the seconds digits with nobody in view. I had earlier assumed the debug view showed no motion boxes at all, so that was my mistake. One thing I can't fully explain: one camera's motion sensor stayed "off" for about 35 hours while person events were still being created. After adding the masks everything has been consistent, so I'm treating this as not a Frigate bug. Feel free to close." Huge thank you! Luis Burnay

…

On Mon, 26 Oct 2026 at 17:41, Josh Hawkins ***@***.***> wrote: This is not a Frigate bug. The AI is partially correct here. Your YAML indentation is fine, and motion can't be turned off while detection is enabled, so neither of those is the cause. Your motion sensors on those cameras aren't broken, they're most likely stuck ON. Frigate only publishes to the motion topic when the state changes, and OFF is only sent after 30 seconds with no motion at all. If something in the frame changes constantly, like an on-screen timestamp/clock overlay, motion never goes OFF, so you never see another ON. That matches your HA sensor sitting "on" since startup. Do those 7 cameras have a timestamp overlay? If so, add a motion mask over it (like you have on porta_rua) or disable the overlay on the camera. The Motion Tuner in Settings will show you the boxes it's picking up. — Reply to this email directly, view it on GitHub <#24805?email_source=notifications&email_token=BGNSFSJIYCBR6BCPBRSG3H35V6EFHA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJSGAYTENRZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-19201269>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGNSFSM4TUYSU3ZAQUTKNRT5V6EFHAVCNFSNUABIKJSXA33TNF2G64TZHMYTMNZWHE2DCOJUHNCGS43DOVZXG2LPNY5TCMJRGM2DIMZYUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BGNSFSMWAQOW7JC7ZEQBLF35V6EFHA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJSGAYTENRZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/BGNSFSMQBQDBUEEI7UW5CBL5V6EFHA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJSGAYTENRZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.*** com>

-- Luis Burnay