Why Is Frigate MQTT Event Feed Delayed?
- Broker congestion
- QoS/retain mismatch
- network latency between Frigate and broker
Problem Description
When your Frigate Frigate MQTT Delay isn't working as expected, it usually traces back to one of a small number of causes — this guide covers them in order, starting with the most likely.
Symptoms
- MQTT lag
- automation delayed
- broker queue growth
Recognize these? Here's what usually causes it.
Common Causes
- Broker congestion
- QoS/retain mismatch
- network latency between Frigate and broker
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
Measure event publish latency
Compare detect timestamp to MQTT subscriber receipt time.
Tune broker settings
Adjust QoS/retained policy for event throughput.
Validate automation responsiveness
Retest end-to-end alert timing after tuning.
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 congestion
- QoS/retain mismatch
- network latency between Frigate and broker
Before you go — try one of these (they fix most cases).
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.