-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Double event processing for "unzoned: allow" and having zones defined in Frigate #66
Comments
Hmm - So based on the logs, it seems like an initial notification is sent out when the object is outside a zone - then a follow up once the object enters the zone. Is the issue that the snapshots are identical between them? It looks like it for me, but I want to confirm since they've been pixelated for the issue upload. If so, I wonder if this might be an issue of grabbing the snapshot from Frigate too quickly? Maybe Frigate hasn't updated the snapshot yet by the time we grab it for the notification. |
Hi @0x2142,
That's the thing, they're not identical, but only slightly different, as expected.
Those snapshots were pixelated intentionally (today's internet is not about privacy at all). I see the behavior as follows:
The trouble may be hiding under https://github.com/0x2142/frigate-notify/blob/main/events/mqtt.go#L98-L100 where transitions Firstly, good question here: is this Secondly, realizing the difficulty of how to properly calculate |
Description
The system duplicates event processing for zoned and unzoned areas while the configuration has default
unzoned: allow
.This bug is floating (heisenbug).
Scene
Notification
ZoneA is colored by pink.
![image](https://private-user-images.githubusercontent.com/133116/334100571-c190d365-94f6-4471-8447-58d44f403396.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU4MTg2MDQsIm5iZiI6MTcyNTgxODMwNCwicGF0aCI6Ii8xMzMxMTYvMzM0MTAwNTcxLWMxOTBkMzY1LTk0ZjYtNDQ3MS04NDQ3LTU4ZDQ0ZjQwMzM5Ni5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTA4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkwOFQxNzU4MjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iMjlmYTk0ZWFhNDdkMGU5MGUyZTFiNTAwMDVhNDE5YjdiZWMzOTI0YjY2ODZkMDlmMjQ1NTQzMjM1YjkxYzIyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.whmi2GGmmDRa1ndURBYTxynx4x316ckR4KDGoOY4WRg)
Path for ObjectA is colored by green.
ZoneA is colored by pink.
![image](https://private-user-images.githubusercontent.com/133116/334103783-75ef225d-4299-4bf1-8ccf-43380ba897ed.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU4MTg2MDQsIm5iZiI6MTcyNTgxODMwNCwicGF0aCI6Ii8xMzMxMTYvMzM0MTAzNzgzLTc1ZWYyMjVkLTQyOTktNGJmMS04Y2NmLTQzMzgwYmE4OTdlZC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwOTA4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDkwOFQxNzU4MjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hYTdmYTc5Yzc3ZDliMjFhZWY4YTRhZDIxYmJiM2U3NTFkNDNiMTYwN2FlYmFiNzdmMzg1NWY3MzNjODA0MGQ5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.sPviAWZ6bzgo_TEgfpYPeS7YbkLFJ6sOlmDBA8K2JmY)
Path for ObjectB is colored by blue.
Frigate-Notify Version:
v0.2.8
Configuration
Logs
ObjectA path
ObjectB path
Expected behavior
The system processes a particular event only once and regardless of existing zones if configuration
unzoned: allow
is set.The text was updated successfully, but these errors were encountered: