Any plans to integrate any sort of notofcations (say email / webhooks) from Frigate natively ?

[vw-kombi]

The frigate AI stuff is coming along nicely. I have frigate adding the face and the AI description to its alerting, but to get that added to email / webhooks, I also have to have home assistant doing the same thing - using up the AI credits. I was wondering if you plan to add an option so that the AI description can be sent out (ideal email / webhooks to discord as that is what I use in HA).

[inkeep-ai-assistant[bot]]

Frigate supports native notifications using the WebPush protocol, which can deliver notifications directly to web browsers, but does not natively support sending notifications via email or webhooks out-of-the-box(1). The configuration allows you to set an email address, but this is only used for push service registration, not for sending standard email alerts(1), (2).

For advanced workflows—such as integrating the AI description, face data, or other alert details into notifications sent to email, Discord, or webhooks—you currently need to use Home Assistant or another automation platform. Frigate provides MQTT topics (such as frigate/tracked_object_update and frigate/events) that can be used to trigger automations in Home Assistant, which can then forward notifications containing the AI description to your preferred channels(3), (4), (5), (6). This does mean that if Home Assistant is also calling external AI services, you may use additional AI credits.

There is no documented plan or feature for Frigate to natively send notifications with AI descriptions via email or webhooks at this time. All current examples and guides rely on external automation (like Home Assistant) to relay and enrich Frigate alerts to email, Discord, or similar services(1), (3), (4), (6).

📚 Sources:

1. Notifications
2. Full Reference Config
3. Generative AI
4. Home Assistant notifications
5. MQTT
6. 0.16 beta 4 generative AI home assistant notification. For use with telegram.

---

Have another question? Just tag @inkeep.

[NickM-27]

The AI is correct here, other than the Frigate notifications will support AI generated title and description using the review summary feature in 0.17

[vw-kombi]

I read some of the doco that the AI reference and noticed this below - which could halve my AI requests if I can pull this out of mqtt in HA and email / webhook that instead. Have to have a conversation with your AI on how to do that as I get completely lost with the mqtt stuff.

Frigate provides an MQTT topic, frigate/tracked_object_update, that is updated with a JSON payload containing event_id and description when your AI provider returns a description for a tracked object. This description could be used directly in notifications, such as sending alerts to your phone or making audio announcements. If additional details from the tracked object are needed, you can query the HTTP API using the event_id, eg: http://frigate_ip:5000/api/events/<event_id>.

[vw-kombi]

So - I connected via cloudflare so using ssl to turn on notifications as per doco - and seemed to have stuffed the frigate system now - I just get a spinning circle on startup. Cant even get logs up trhough the gui - but below is what was shown via the docker container logs. I am able to go into the config of the docker container and removed all references to notifications, saved and restarted the container. All back working again now.

025-11-11 10:58:13.337182395 2025/11/11 10:58:13 [error] 210#210: *216 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.10, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "10.10.10.10:5000"
2025-11-11 10:58:13.337223702 2025/11/11 10:58:13 [error] 210#210: *216 auth request unexpected status: 502 while sending to client, client: 192.168.1.10, server: , request: "GET /ws HTTP/1.1", host: "10.10.10.10:5000"
2025-11-11 10:58:13.337279075 192.168.1.10 - - [11/Nov/2025:10:58:13 +1000] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36" "-"
2025-11-11 10:58:15.222287972 2025/11/11 10:58:15 [error] 210#210: *218 connect() failed (111: Connection refused) while connecting to upstream, client: 10.10.10.9, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "10.10.10.10:5000"
2025-11-11 10:58:15.222297611 2025/11/11 10:58:15 [error] 210#210: *218 auth request unexpected status: 502 while sending to client, client: 10.10.10.9, server: , request: "GET /api/stats HTTP/1.1", host: "10.10.10.10:5000"
2025-11-11 10:58:16.334238744 2025/11/11 10:58:16 [error] 210#210: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2025-11-11 10:58:16.334285627 2025/11/11 10:58:16 [error] 210#210: *220 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2025-11-11 10:58:19.333625466 2025/11/11 10:58:19 [error] 210#210: *222 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.10, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "10.10.10.10:5000"
2025-11-11 10:58:19.333664955 2025/11/11 10:58:19 [error] 210#210: *222 auth request unexpected status: 502 while sending to client, client: 192.168.1.10, server: , request: "GET /ws HTTP/1.1", host: "10.10.10.10:5000"
2025-11-11 10:58:19.333709160 192.168.1.10 - - [11/Nov/2025:10:58:19 +1000] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36" "-"
2025-11-11 10:58:20.222230764 2025/11/11 10:58:20 [error] 210#210: *224 connect() failed (111: Connection refused) while connecting to upstream, client: 10.10.10.9, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "10.10.10.10:5000"
2025-11-11 10:58:20.222275141 2025/11/11 10:58:20 [error] 210#210: *224 auth request unexpected status: 502 while sending to client, client: 10.10.10.9, server: , request: "GET /api/stats HTTP/1.1", host: "10.10.10.10:5000"
2025-11-11 10:58:21.395112704 2025/11/11 10:58:21 [error] 210#210: *226 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2025-11-11 10:58:21.395129118 2025/11/11 10:58:21 [error] 210#210: *226 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"

[NickM-27]

We'll need to see full logs

[vw-kombi]

@inkeep

write a home assistant automation so that is a person is detected in binary_sensor.pathway_person_occupancy, then wait for a person to be detected in binary_sensor.doorway_person_occupancy, and then send a discord message via rest_command.discord_message_frigate with the frigate person name if known, the frigate face confidence percentage and the frigate generated ASI description.

[inkeep-ai-assistant[bot]]

To accomplish this automation with Home Assistant and Frigate, you will need to:

1. Trigger on binary_sensor.pathway_person_occupancy turning on.
2. Wait for binary_sensor.doorway_person_occupancy to turn on.
3. Listen for the frigate/tracked_object_update MQTT topic to get the event_id and description when the GenAI description is available.
4. Use the event_id to retrieve the person name, face confidence, and GenAI description via the Frigate HTTP API.
5. Send these details to Discord using your rest_command.discord_message_frigate.

The sources show that the frigate/tracked_object_update MQTT topic provides a payload like:

{
  "type": "description",
  "id": "event_id",
  "description": "The car is a red sedan moving away from the camera."
}

(1), (2)

You can then use the event_id to query the HTTP API for more details:

http://frigate_ip:5000/api/events/<event_id>

(2)

The automation logic would be as follows (pseudocode, as exact YAML depends on your Home Assistant setup):

• Trigger: pathway_person_occupancy turns on
• Wait: doorway_person_occupancy turns on
• Action:
  • Subscribe to frigate/tracked_object_update MQTT topic.
  • When a message with type "description" and the correct camera is received, extract event_id and description.
  • Use a REST call to Frigate API /api/events/<event_id> to get face and label data.
  • Send Discord message with person name (if available), face confidence, and ASI description.

You can find further details about the MQTT topic structure and API usage at:

• MQTT topic documentation
• Generative AI configuration
• Discussion on matching events and GenAI descriptions

📚 Sources:

1. MQTT
2. "How to Match Frigate Object Detection Events with GenAI Descriptions

---

Have another question? Just tag @inkeep.

[vw-kombi]

@inkeep
Can you show me the full automation

[inkeep-ai-assistant[bot]]

There is no directly quoted, complete Home Assistant automation YAML in the provided sources that matches your scenario. However, the sources do describe the required steps and logic, including how to use MQTT triggers, REST API calls, and Home Assistant sensors to achieve your goal with Frigate and GenAI descriptions(1)(2)(3)(4).

Check out these potentially useful sources:
Home Assistant Integration, Full Reference Config, "How to Match Frigate Object Detection Events with GenAI Descriptions

Would you like a general answer with an example automation based on my knowledge instead?

📚 Sources:

1. Full Reference Config
2. "How to Match Frigate Object Detection Events with GenAI Descriptions
3. Home Assistant Integration
4. Add the event_id that triggered the person_occupancy sensor

---

Have another question? Just tag @inkeep.

[vw-kombi]

@inkeep -

I have been using a different AI but they keep getting it close, then break it again, and it gets too complex for me to understand. Can you check the logic on this :

alias: Frigate - Discord Alert on Pathway-to-Doorway Detection
description: >
Sends Discord message when a person walks up the pathway and reaches the doorway,
including Frigate face match and ASI description via MQTT.

trigger:

• platform: state
  entity_id:
  • binary_sensor.pathway_person_occupancy
  • binary_sensor.front_pathway_person_occupancy
    to: "on"

action:

• variables:
  person_name: "Unknown"
  face_score: "N/A"
  asi_description: "No description"

• parallel:

  • sequence:

    • wait_for_trigger:

      • platform: mqtt
        topic: frigate/tracked_object_update
        value_template: "{{ value_json['camera'] }}"
        payload: Front-Door
        timeout: 15
        continue_on_timeout: true

    • choose:

      • conditions:

        • condition: template
          value_template: >
          {{ wait.trigger is defined and
          wait.trigger.payload_json.get('type') == 'face' and
          wait.trigger.payload_json.get('camera') == 'Front-Door' and
          wait.trigger.payload_json.get('name') }}
          sequence:
        • variables:
          person_name: "{{ wait.trigger.payload_json.get('name', 'Unknown') }}"
          face_score: "{{ (wait.trigger.payload_json.get('score', 0) * 100) | round(1) }}"

      • conditions:

        • condition: template
          value_template: >
          {{ wait.trigger is defined and
          wait.trigger.payload_json.get('type') == 'description' and
          wait.trigger.payload_json.get('camera') == 'Front-Door' and
          wait.trigger.payload_json.get('description') }}
          sequence:
        • variables:
          asi_description: "{{ wait.trigger.payload_json.get('description', 'No description') }}"

  • sequence:

    • wait_for_trigger:
      • platform: state
        entity_id: binary_sensor.doorway_person_occupancy
        to: "on"
        timeout: 15
        continue_on_timeout: false

• service: rest_command.discord_message_frigate
  data:
  message: >
  🚶 Person detected moving from pathway to doorway.
  Name: {{ person_name }}
  Confidence: {{ face_score }}%
  Description: {{ asi_description }}

mode: restart

[inkeep-ai-assistant[bot]]

There is no complete, directly quoted Home Assistant automation YAML covering your scenario in the provided sources, so I cannot fully verify or correct every line as a supported answer.

However, your core logic aligns with how Frigate publishes face and GenAI description updates to the frigate/tracked_object_update MQTT topic. The payload structure you’re checking for (type: "face" or "description", camera, name, score, description) matches the documented Frigate MQTT messages for face recognition and generative AI description updates(1)(2). Waiting for occupancy sensors and then dispatching a Discord message via rest_command is a standard Home Assistant approach.

For MQTT triggers, ensure that your topic and payload matching logic are correct. The camera value in the MQTT payload must match exactly what Frigate publishes (e.g., "front_door_cam" vs "Front-Door")—check your Frigate camera names for exact case and spelling(1). The value_template and payload usage in your wait_for_trigger should reflect the actual MQTT payload structure.

The variables person_name, face_score, and asi_description are set according to the presence of those fields in the MQTT message payload, which is consistent with the documented examples(1)(2). Your approach to send a message with these variables via rest_command.discord_message_frigate is also appropriate.

Summary: Your logic is sound and matches how Frigate’s MQTT topics for face and generative AI description updates work. Just ensure your camera names and MQTT topic matching are exact, and that the payload fields in your automation correspond to the actual Frigate MQTT messages(1)(2).

📚 Sources:

1. MQTT
2. Generative AI

---

Have another question? Just tag @inkeep.

[vw-kombi]

Just to close this off, I worked for a while with some AI's to get this data, and we ended upon three separate automations -

One runs as a passive listener on AI DEescriptions on the front door camera and updates a sensor.
One runs on the last face detection only and updates a sensor. This send discord message if face is recognised or not.
One runs on the last AI description and updates a sensor. This send discord message but only if one is generated.

These are also added to a markdown card with the alert times for the dashboard.

The automations are shown below if this helps anyone else - The AI tried its hardest to do the face and description in one automation but it was always one step forward, one step back and keeping them separate seems to be the safest option.

Passive Listener for AI Descriptions at Front Door

alias: Frigate - (13112025) - Passive Listener for AI Descriptions at Front Door
description: Updates dashboard helpers when Frigate publishes a description for Front-Door
triggers:

• topic: frigate/tracked_object_update
  trigger: mqtt
  conditions:
• condition: template
  value_template: |-
  {{ camera == 'Front-Door' and
  description_type == 'description' and
  ai_description != 'No description available' }}
  actions:
• condition: template
  value_template: "{{ states('input_text.last_description') != ai_description }}"
• target:
  entity_id: input_text.last_description
  data:
  value: "{{ ai_description }}"
  action: input_text.set_value
• target:
  entity_id: input_text.last_ai_alert_time
  data:
  value: "{{ timestamp }}"
  action: input_text.set_value
  variables:
  camera: "{{ trigger.payload_json.get('camera', '') }}"
  description_type: "{{ trigger.payload_json.get('type', '') }}"
  ai_description: |-
  {% if trigger.payload_json is defined and
  trigger.payload_json.get('type') == 'description' %}
  {{ trigger.payload_json.get('description', 'No description available') | replace('\n', ' ') | trim }}
  {% else %}
  No description available
  {% endif %}
  raw_id: "{{ trigger.payload_json.get('id', '') }}"
  timestamp: |-
  {% if raw_id %}
  {{ (raw_id.split('-')[0] | float | timestamp_custom('%Y-%m-%d %H:%M:%S', true)) }}
  {% else %}
  "Unknown time"
  {% endif %}
  mode: single

Log last face and send discord message

alias: Frigate - (11112025) - Log last face and send discord message
description: ""
triggers:

• entity_id: binary_sensor.pathway_person_occupancy
  to: "on"
  trigger: state
  actions:

• wait_for_trigger:

  • entity_id: binary_sensor.doorway_person_occupancy
    to: "on"
    trigger: state
    timeout: "00:00:10"
    continue_on_timeout: false

• wait_for_trigger:

  • topic: frigate/tracked_object_update
    value_template: "{{ value_json['camera'] }}"
    payload: Front-Door
    trigger: mqtt
    timeout: "00:00:05"
    continue_on_timeout: true

• variables:
  person_name: >
  {% if wait.trigger is defined and wait.trigger.payload_json.get('type')
  == 'face' %}
  {{ wait.trigger.payload_json.get('name','Unknown') }}
  {% else %}
  Unknown
  {% endif %}
  confidence: >
  {% if wait.trigger is defined and wait.trigger.payload_json.get('type')
  == 'face' %}
  {{ (wait.trigger.payload_json.get('score',0) * 100) | round(1) }}
  {% else %}
  0
  {% endif %}
  raw_id: |-
  {% if wait.trigger is defined and wait.trigger.payload_json.get('id') %}
  {{ wait.trigger.payload_json.get('id') }}
  {% else %}
  ""
  {% endif %}
  timestamp: |-
  {% if raw_id %}
  {{ (raw_id.split('-')[0] | float | timestamp_custom('%Y-%m-%d %H:%M:%S', true)) }}
  {% else %}
  "Unknown time"
  {% endif %}

• target:
  entity_id: input_text.last_face_name
  data:
  value: "{{ person_name }}"
  action: input_text.set_value

• target:
  entity_id:
  - input_text.last_alert_time
  data:
  value: "{{ timestamp }}"
  action: input_text.set_value

• data:
  title: Front Door Detection
  message: >
  Camera: Front-Door

  {% if person_name != 'Unknown' %} **Recognized as:** {{ person_name }}
  **Confidence:** {{ confidence }}% {% else %} No face recognition data
  available. {% endif %}
  

  action: rest_command.discord_message_frigate
  mode: restart

Log AI Descriptions and Send discord message if changed

alias: Frigate - (11112025) - Log AI Descriptions and Send discord message if changed
description: ""
triggers:

• entity_id: binary_sensor.pathway_person_occupancy
  to: "on"
  trigger: state
  actions:
• wait_for_trigger:
  • entity_id: binary_sensor.doorway_person_occupancy
    to: "on"
    trigger: state
    timeout: "00:00:10"
    continue_on_timeout: false
• wait_for_trigger:
  • topic: frigate/tracked_object_update
    value_template: "{{ value_json['type'] }}"
    payload: description
    trigger: mqtt
    timeout: "00:00:15"
    continue_on_timeout: true
• variables:
  ai_description: >-
  {% if wait.trigger is defined and wait.trigger.payload_json is defined
  %}
  {{ wait.trigger.payload_json.get('description', 'No description available') }}
  {% else %}
  No description available
  {% endif %}
• choose:
  • conditions:
    • condition: template
      value_template: "{{ ai_description != 'No description available' }}"
      sequence:
    • target:
      entity_id: input_text.last_description
      data:
      value: "{{ ai_description }}"
      action: input_text.set_value
    • target:
      entity_id:
      - input_text.last_ai_alert_time
      data:
      value: "{{ timestamp }}"
      action: input_text.set_value
    • data:
      title: Front Door Detection
      message: Front-Door - {{ ai_description }}
      action: rest_command.discord_message_frigate
      mode: restart

And the dashboard -