chris/frigate
1
0
Fork 0
forked from Github/frigate
Code Pull Requests Packages Activity

Use tracked object instead of event language in docs and UI (#13685)

Browse Source 
* Verbiage update: use tracked object instead of event

* tweaks
This commit is contained in:
Josh Hawkins
2024-09-11 19:53:58 -05:00
committed by GitHub
parent 62657ad05a
commit b4acf4f341
25 changed files with 97 additions and 98 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/docs/guides/ha_notifications.md
View File

@@ -7,11 +7,11 @@ The best way to get started with notifications for Frigate is to use the [Bluepr
It is generally recommended to trigger notifications based on the `frigate/reviews` mqtt topic. This provides the event_id(s) needed to fetch [thumbnails/snapshots/clips](../integrations/home-assistant.md#notification-api) and other useful information to customize when and where you want to receive alerts. The data is published in the form of a change feed, which means you can reference the "previous state" of the object in the `before` section and the "current state" of the object in the `after` section. You can see an example [here](../integrations/mqtt.md#frigateevents).
Here is a simple example of a notification automation of events which will update the existing notification for each change. This means the image you see in the notification will update as Frigate finds a "better" image.
Here is a simple example of a notification automation of tracked objects which will update the existing notification for each change. This means the image you see in the notification will update as Frigate finds a "better" image.
```yaml
automation:
- alias: Notify of events
- alias: Notify of tracked object
trigger:
platform: mqtt
topic: frigate/events