Why Is Frigate Recording But Not Sending Notifications?
- Event topic mismatch
- Automation filter too strict
- Webhook/auth issue
Problem Description
Missing Frigate Frigate Notification Pipeline notifications are almost always a phone-level permission issue, not a device problem — the fix takes under two minutes once you know where to look.
Symptoms
- Recordings exist
- No push alerts
- Only some cameras notify
Recognize these? Here's what usually causes it.
Common Causes
- Event topic mismatch
- Automation filter too strict
- Webhook/auth issue
Most fixes happen in the first 3 steps.
Do not debug complex conditions before proving basic event flow.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Verify event emission
Confirm Frigate emits expected events to your automation platform.
Test minimal automation
Create a simple notification trigger to isolate complex condition filters.
Needed for this step
5 Pack WiFi Wireless Door Window Sensor,TUYA Sm...
$48.59Validate endpoint auth
Check webhook tokens or service credentials for failed delivery.
Quick Solutions
Still having issues? This is usually the deeper cause below.
Notification delays almost always return after a major iOS or Android update — background app refresh gets reset to restricted on every major OS version.
Keep one baseline alert automation for regression checks.
Notification delays over 2 minutes are almost never the device's fault — background app restrictions quietly re-enable themselves after every OS update.
- Event topic mismatch
- Automation filter too strict
- Webhook/auth issue
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.