How do I generate Alerts through API? #20794
-
|
Hey, mqtt:
enabled: false
tls:
enabled: false
cameras:
Loods-1:
enabled: true
ffmpeg:
inputs:
- path:
rtsp://frigate:[email protected]:554/Streaming/channels/102
roles:
- record
- detect
review:
detections:
labels:
- POI
motion:
threshold: 46
contour_area: 10
improve_contrast: true
mask:
- 0.335,0.065,0.029,0.067,0.027,0.016,0.332,0.013
- 0.336,0,0.357,1,0,1,0,0
detect:
enabled: false
review:
alerts:
enabled: true
labels:
- POI
record:
enabled: true
retain:
days: 1
alerts:
retain:
days: 30
detections:
retain:
days: 30
snapshots:
enabled: true
retain:
default: 30
version: 0.16-0I think I'm just missing something really simple.. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
You use the create event API https://docs.frigate.video/integrations/api/create-event-events-camera-name-label-create-post |
Beta Was this translation helpful? Give feedback.
-
|
The issue is that creating a manual event does not automatically trigger an update to the review interface(1). Manual events created via API won't appear in the review tab the same way tracked objects do. To create a manual event that will be retained according to your alert retention settings, use the POST endpoint: With a request body like: {
"duration": 10,
"include_recording": true
}However, creating a manual event does not trigger an update to /events MQTT topic(2), and similarly, these events don't automatically populate in the review interface as alerts would from actual detections. Your configuration looks correct - you have The review system is designed primarily for events generated by Frigate's detection pipeline, not manual API-created events. While your manual events will be retained according to your retention policies, they won't appear in the review tab as expected. ** 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
You should not be setting source type