Frigate Mobile App Notifications 2.0

@SgtBatten any thoughts?

It’s actually much easier to glance at the trace tree. It’s a long screenshot but can you share a look at the tree


Hopefully this works, had to zoom out a bit to get it all.

It skipped both notification blocks. Where it branches to the right column that is a bypass due to conditions not being met.

To see what conditions are not met you can click the empty square one step below the branch and view which condition was false.

First one was

[Zone Filter]
Executed: February 9, 2026 at 1:55:49 PM
Result:

result: false entities:

2nd one was

Option 0

Executed: February 9, 2026 at 1:56:21 PM
Result:

result: false

conditions/0

[If 7 conditions match]
Executed: February 9, 2026 at 1:56:21 PM
Result:

result: false

conditions/0/conditions/0

[If 7 conditions match]
Executed: February 9, 2026 at 1:56:21 PM
Result:

result: true entities:

conditions/0/conditions/1

[If 7 conditions match]
Executed: February 9, 2026 at 1:56:21 PM
Result:

result: true entities:

conditions/0/conditions/2

[If 7 conditions match]
Executed: February 9, 2026 at 1:56:21 PM
Result:

result: false entities:

Executed: February 9, 2026 at 1:56:21 PM
Result:

result: true

Executed: February 9, 2026 at 1:56:21 PM
Result:

result: true entities:


I uploaded pics of what I have the zones named…I think its correct unless it changed and I need it like Front_Porch vs Front Porch now.

On the second one, I’m not sure which section got the false report.

Thank you!

I prefer to use the alerts by zone kind of setup using frigate directly. But it should still work the way you are trying it. Have you tried putting them lowercase with underscores as per the description for that zone filter.

Ok, got it to work by doing everything lowercase and using the _ in between, which is different than it used to be.

Can you elaborate on the Alerts by zone kind of setup? I’ve only ever done this way, but it seems to have issues/or need corrected frequently, so maybe I need to change it to the way you are doing it, but this is the only way I’ve ever done it.

Hello;

Getting this message:

The target parameter is being deprecated. You should update any automations and scripts that use that parameter in Telegram bot actions. Use entity_id to specify Telegram bot notify entities or chat_id to replace target .

I have updated to version 0.17 and have started setting up classification, but now I don’t receive notifications.

Is this blueprint compatible with classifications?

Probably not considering it hasn’t been updated in a long time… hopefully normal notifications still work though.

They generally do work.

I have found that classification didn’t work as I thought so getting rid of it for now.

1 Like

Hello. Any idea how to get face recognition with snapshot?

In my case the {{ label }} is filled with the name, so it was working natively without any change.

I’m tinkering if I can use this blueprint for my doorbell notification, letting it trigger on a button_press or something? Anyone did something similar?

Yeah same, is the blueprint going to be updated to remove target?

I hope it is… been waiting for a fix. Not sure if there’s others that can help if the original dev is unavailable.

I fixed mine. Go to the blueprint using File Editor / VSCode or whatever editor you choose.

Under /homeassistant/blueprints/automation/SgtBatten/Stable.yaml change where it says target in the action step to chat_id.

So

    - alias: Send Notification
      sequence:
      - choose:
        - conditions: '{{ telegram }}'
          sequence:
          - action: telegram_bot.send_photo
            data:
              target: '{{telegram_chat_id}}'
              caption: '{{message}}'
              url: '{{attachment|replace( base_url, telegram_base_url )}}'

to

    - alias: Send Notification
      sequence:
      - choose:
        - conditions: '{{ telegram }}'
          sequence:
          - action: telegram_bot.send_photo
            data:
              chat_id: '{{telegram_chat_id}}'
              caption: '{{message}}'
              url: '{{attachment|replace( base_url, telegram_base_url )}}'

restart and the errors should go away

1 Like

It would be awesome if you could do the same thing on GitHub and fix it for everybody

1 Like

Unfortunatley I haven’t the faintest clue on how to post something to github

1 Like

It’s not too hard, I’ll give it a go and give you screenshots if nobody beats me to it to make the change