Will the reviews topic get more frequent update messages

[SgtBatten]

The reviews topic seems to very rarely get an "update" message despite zones changing, or objects moving around.
This causes significant (IMO) delays in notifications compared to the events topic.

I have an example from today where I setup a notification (using the blueprint) that required two zones to be entered in order.
The object lifecycle shows the following times
01/19 09:58:32am - Person Detected
01/19 09:58:32am - Entered first zone
01/19 09:58:35am - Entered second zone
01/19 09:58:38am - Person Left

So the entire event is over in 6 seconds as i walked through the frame.
The first mqtt message of type "new" occurred right away as expected.
There were no update messages
The end message didn't occur until approximately 09:59:00am

As the "new" message did not meet the notification criteria, nothing was received on my phone until after the end message was sent.

Now this is a short clip, but the same behavior is observed even on objects that spend a bit more time in frame. I have rarely seen an update messages and i have never seen more than 1 update message.

So i'm curious, what are the conditions for such a message to be sent now, and can we consider increasing the frequency or triggers.

[NickM-27]

The /reviews topic represents overall camera activity, it is not a verbose topic that will update when any object has something update about it. It is designed to be a direct reflection of what activity the user has configured they care about via the config (alerts). with increased frequency it would just become another /events topic that updates too frequently for many users requiring filtering which is not appropriate as the topic is directly used for frigate's built in notifications and UI updates via websocket.

An update message will only be sent if the status changes from detection to alert based on the review config or if there are additional objects than previous during the same activity.

In your case, if presence in the second zone is the requirement to create a notification then perhaps the config should be changed such that only the second zone can make a review item be considered an alert.

[SgtBatten]

Makes perfect sense, thanks.

My personal config has alerts = when I want notifications so I generally get them on the "new" update except for the car scenario on the front camera.

This is just my testing for other setups where I see this issue.

It is good to know the criteria for an update. I can actually remove some loop trigger criteria from the blueprint as they will never be true independantly based on this. E.g a zone change may happen, but won't be sent as its own update

[NickM-27]

Sounds good, I anticipate some of this may be addressed in a future update when "line crossing" (zone order transition) is supported directly as a requirement for alerts

[NickM-27]

And by the way saw your update on HA and very excited to hear that the new blueprint is close

[SgtBatten]

Sounds good, I anticipate some of this may be addressed in a future update when "line crossing" (zone order transition) is supported directly as a requirement for alerts

Oh interesting. That will probably take care of most peoples needs. It's really only when people want alerts for more situations than they want notifications for that there is a delay, because we don't get to use the "new" message.