mirror of
https://github.com/blakeblackshear/frigate.git
synced 2026-10-31 19:00:30 +03:00
add configurable ttl for active alert notifications
Notifications sent while an alert was active always used a TTL of 0, so the push service dropped them if the device wasn't reachable at that moment and users only received the notification sent when the alert ended. A new `ttl` notifications option, settable globally or per camera, lets the push service retry these notifications for that many seconds. It defaults to 0, and the settings UI warns that a non-zero value can deliver stale notifications.
This commit is contained in:
@@ -858,6 +858,10 @@
|
||||
"label": "Cooldown period",
|
||||
"description": "Cooldown (seconds) between notifications to avoid spamming recipients."
|
||||
},
|
||||
"ttl": {
|
||||
"label": "Notification TTL",
|
||||
"description": "Seconds the push service keeps retrying a notification sent while an alert is active if your device can't be reached. 0 delivers immediately or drops it. The notification sent when an alert ends is always kept for up to an hour."
|
||||
},
|
||||
"enabled_in_config": {
|
||||
"label": "Original notifications state",
|
||||
"description": "Indicates whether notifications were enabled in the original static configuration."
|
||||
|
||||
@@ -154,6 +154,10 @@
|
||||
"label": "Cooldown period",
|
||||
"description": "Cooldown (seconds) between notifications to avoid spamming recipients."
|
||||
},
|
||||
"ttl": {
|
||||
"label": "Notification TTL",
|
||||
"description": "Seconds the push service keeps retrying a notification sent while an alert is active if your device can't be reached. 0 delivers immediately or drops it. The notification sent when an alert ends is always kept for up to an hour."
|
||||
},
|
||||
"enabled_in_config": {
|
||||
"label": "Original notifications state",
|
||||
"description": "Indicates whether notifications were enabled in the original static configuration."
|
||||
|
||||
Reference in New Issue
Block a user