You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, great solution and I did have this working nicely. However, I have got 6 cameras in Frigate and I've setup a zone on one of the cameras on my driveway now called "drive".
What I'm seeing is that Frigate is correctly logging alerts/detections when someone enters a zone, but it still writes the events into mqtt. This means that Frigate-Notify is still sending me alerts.
Looking at the documentation, I can set:
unzoned: drop
allow: drive
But then I only get alerts from the driveway zone and not my other 5 cameras because they are "unzoned". Is the only solution here to create a zones for every other camera?
The text was updated successfully, but these errors were encountered:
Hi @djdd87 - Yes at the moment the unzoned setting is all-or-nothing across all cameras. Perhaps this may change in the future to allow more granular settings per camera, but for now the solution you suggested would be one way of working around this.
Hey @0x2142 , that's fine then as long as I know that's the way I have to use it. I've just zoned all my cameras now and it seems to be working as intended. I'm no longer getting bombarded with the daily school traffic walking in front of my house.
Hey, great solution and I did have this working nicely. However, I have got 6 cameras in Frigate and I've setup a zone on one of the cameras on my driveway now called "drive".
What I'm seeing is that Frigate is correctly logging alerts/detections when someone enters a zone, but it still writes the events into mqtt. This means that Frigate-Notify is still sending me alerts.
Looking at the documentation, I can set:
But then I only get alerts from the driveway zone and not my other 5 cameras because they are "unzoned". Is the only solution here to create a zones for every other camera?
The text was updated successfully, but these errors were encountered: