From 65fe6b610a37ce988e1d1882ef093c479d522082 Mon Sep 17 00:00:00 2001
From: nulledy <254504350+nulledy@users.noreply.github.com>
Date: Mon, 24 Aug 2026 13:50:32 -0400
Subject: [PATCH] Compare severity in send_alert's no-op update check (#24084)

send_alert()'s short circuit for skipping a no-op "update" push only
compared object and zone counts between before/after, never severity.
Both underlying collections are cumulative and deduplicated (objects
is a set of labels, zones only appends a zone not already present),
so a segment being promoted from detection to alert can leave both
counts unchanged, silently dropping the single most notable
transition in a review's life. Add a severity comparison to the same
check so a detection -> alert promotion always notifies.
---
 frigate/comms/webpush.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/frigate/comms/webpush.py b/frigate/comms/webpush.py
index 244f82ca8b..34a0e57508 100644
--- a/frigate/comms/webpush.py
+++ b/frigate/comms/webpush.py
@@ -421,6 +421,7 @@ class WebPushClient(Communicator):
         # Don't notify if message is an update and important fields don't have an update
         if (
             state == "update"
+            and payload["before"]["severity"] == payload["after"]["severity"]
             and len(payload["before"]["data"]["objects"])
             == len(payload["after"]["data"]["objects"])
             and len(payload["before"]["data"]["zones"])