Skip to content
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

Fix zone issue #38

Merged
merged 7 commits into from
Apr 1, 2024
Merged

Fix zone issue #38

merged 7 commits into from
Apr 1, 2024

Conversation

0x2142
Copy link
Owner

@0x2142 0x2142 commented Apr 1, 2024

This PR fixes issues with the zone filter raised in #37. Originally, this was built to only alert on new events from Frigate. However, Frigate will send updated event notifications to MQTT upon certain things, like the detected object moving to a different zone.

So with the zone filter built as it was originally, the app would only send an event if there was a new event that contained a zone. If an event started with no zone info, and was updated later, no notification would be sent. App code adjusted to account for event updates, and compare zone details. New alerts will only be sent if the object enters a new zone & also that zone is on the allowed notification list.

Also added the ability to provide custom date / time formats to be used in the notifications. And cleaned up some logs to ensure that all event-related logs should have the event ID attached.

@0x2142 0x2142 added bug Something isn't working enhancement New feature or request labels Apr 1, 2024
@0x2142 0x2142 self-assigned this Apr 1, 2024
@0x2142 0x2142 merged commit 4d2a863 into main Apr 1, 2024
2 checks passed
@0x2142 0x2142 deleted the fix-zone-issue branch April 1, 2024 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant