Why Is Frigate MQTT Event Feed Delayed?
- Broker performance/overload
- Network latency to the broker
- QoS/retained-message handling
Problem Description
Frigate MQTT event messages are delayed — Home Assistant automations trigger minutes after the actual detection, or the MQTT event feed lags behind real-time camera activity. The delay can originate from the MQTT broker, Frigate's internal detection processing lag, large MQTT payloads, or downstream automation engine latency.
Why This Happens in Real Homes
A delayed Frigate MQTT event feed can originate at two points: the event itself being generated late (an overloaded detector delaying detection), or the MQTT delivery being slow (a busy broker, network latency, or Home Assistant taking time to process the message). Distinguishing which is the first step.
If detection is delayed upstream (check Frigate's detect FPS and load), the MQTT message can only be as timely as the event — so reduce detector load. If the event is prompt but the message arrives late, look at the broker (run it on adequate hardware, reduce congestion), the network path to it, and Home Assistant's automation processing. Reducing unnecessary MQTT traffic and keeping the broker responsive tightens the feed.
Symptoms
- MQTT events delayed
- Delayed event feed
- Home Assistant slow to get events
- Lag in MQTT messages
- Events arrive late
- Notification delay from MQTT
- Slow event propagation
- MQTT latency
Recognize these? Here's what usually causes it.
Common Causes
- Broker performance/overload
- Network latency to the broker
- QoS/retained-message handling
- Home Assistant processing delay
- Detector delay upstream (late events)
- Broker on slow hardware
- Congestion/many messages
- Config/keepalive settings
Most fixes happen in the first 3 steps.
Do not overuse high-QoS settings in high-volume camera environments.
Tools & Requirements
Step-by-Step Solution
Check MQTT broker connection and latency
Frigate publishes events to MQTT topics like frigate/events and frigate/CAMERA/OBJECT. If the MQTT broker is slow or overloaded: all event messages are delayed. Check your MQTT broker (Mosquitto, EMQX) logs for connection issues. Test broker latency: mosquitto_sub -h BROKER_IP -t 'frigate/#' -v — this shows MQTT messages in real time. If messages appear here with delays: the broker itself is the bottleneck. Restart the MQTT broker, check its CPU/memory usage, and verify it is not running out of file descriptors on systems with many MQTT clients.
Verify Frigate MQTT configuration
In frigate.yml: mqtt: host: BROKER_IP, port: 1883, client_id: frigate (default). If client_id conflicts with another MQTT client using the same ID: both clients fight for the connection, causing disconnects and message delays. Give Frigate a unique client_id. Also check: mqtt: stats_interval: 60 (publishes stats every 60 seconds). Setting this too low (1-5 seconds) floods the broker with stats messages. Verify the MQTT user has publish permissions on frigate/# topics if your broker uses ACLs.
Check event processing lag in Frigate
MQTT event messages are sent after Frigate processes the detection event internally. If Frigate is lagging due to CPU overload, slow storage writes, or too many cameras: the detection itself is delayed, which means the MQTT message is also delayed. Check detection FPS in the Frigate UI (System page). If detection FPS is below the configured fps value: Frigate is processing frames slower than expected. See the detect FPS troubleshooting guide for solutions — fixing the detection lag also fixes MQTT delay.
Reduce MQTT message payload size
Frigate can include the event thumbnail in the MQTT message payload. Large thumbnails (base64-encoded images) increase the MQTT message size significantly, which slows broker processing. To minimize delays: set frigate.yml mqtt: enabled: true, but check if your Home Assistant or automation system actually uses the embedded thumbnail. If not: you can reduce the snapshot quality: snapshots: quality: 50. Smaller payloads = faster MQTT delivery. Home Assistant's Frigate integration fetches snapshots via the API separately, so the MQTT thumbnail is often redundant.
Test with a direct MQTT subscription
Subscribe directly to Frigate's MQTT topics to measure actual delay: mosquitto_sub -h BROKER_IP -t 'frigate/events' -v. Walk in front of a camera and time the delay between your movement and the MQTT message appearance. Under 2 seconds is normal (detection processing + MQTT publish). If the MQTT message appears quickly via mosquitto_sub but your Home Assistant automation fires late: the delay is in Home Assistant's MQTT processing or automation engine, not Frigate or MQTT. Check HA's system log for automation execution timing.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Low-latency automation depends on broker health and sane QoS.
Notification delays over 2 minutes are almost never the device's fault — background app restrictions quietly re-enable themselves after every OS update.
- Broker performance/overload
- Network latency to the broker
- QoS/retained-message handling
- Home Assistant processing delay
- Detector delay upstream (late events)
Before you go — try one of these (they fix most cases).
Official Manufacturer Manual
Frigate provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Frigate MQTT Delay.
Source: docs.frigate.video
Need More Help? Frigate Support
Note: The contact information below connects you directly to Frigate's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
Accessories owners commonly pair with Frigate MQTT Delay.
SANDISK 64GB Extreme microSDXC UHS-I Memory Card with Ada...
SANDISK 128GB Ultra microSDXC UHS-I Memory Card with Adap...
SANDISK 64GB Ultra microSDXC UHS-I Memory Card with Adapt...
As an Amazon Associate we earn from qualifying purchases.