[Support]: After upgrading to Frigate 0.13 "new" MQTT events do not have zones #9967
Replies: 3 comments 6 replies
-
previous versions of frigate worked the same way as many messages are sent. It was never a guarantee that the first message would contain zones. It is generally recommended to check before and after for a different in zones regardless of if the message type is new or update. You can adjust the zone intertia to affect how long it takes for an object to be considered part of a zone https://docs.frigate.video/configuration/zones#zone-inertia |
Beta Was this translation helpful? Give feedback.
-
Thank you for such a quick response! There is definitely a difference after the upgrade from 0.12 to 0.13. With 0.13 I only very seldom see zones in the "new" event. With 0.12 I was consistently getting zones with the "new" event. Is zone-inertia going to help with a "new" event? |
Beta Was this translation helpful? Give feedback.
-
Got it, thank you. Having no zones in the "new" events makes it hard to code a notification logic since a simple logic would be notify on "new" events only. I will play with the inertia configuration. I understand that the default is 3. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
After upgrading to Frigate 0.13 "new" MQTT events have empty before and after zone lists. The next "update" message arrives with zones populated.
Version
0.13.2
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Other Linux
Install method
Docker Compose
Coral version
CPU (no coral)
Network connection
Wired
Camera make and model
cam1 - hikvision, doorbell - reolink
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions