Im sorry I typed it a bit confusing.
It started working when I created a 2nd zone, when the zone filtering was on.
And you’re right, the entity was named oprit_2, but it was just oprit in frigate.
Which version are you using?
The beta from your op
When you edit the automation what is the version number at the top?
Is it ending in the letter o?
In HA the blueprint is the o one.
Here is the automation config from a recent trace:
Yep 0.12.0.1o
404 is file not found error but you say the action buttons work fine so I’m not sure what would be happening there. You could try implementing an initial delay
I’m on mobile so difficult to read that whole Pastebin. Can you just copy the yaml from yaml mode when editing the automation please. Thanks
Can you please go back to 1 zone and enable debug. Then trigger it and paste the automation config and the debug output which I’ve written a guide for here HA_blueprints/Frigate Camera Notifications/Guide: Debug Option.md at 41e51b30a8d9fe56b71640d2034a8c3c6805dfad · SgtBatten/HA_blueprints · GitHub
I already have the delay setup via the “Update Image (Optional)” according to your documentation. Here is the automation configuration:
id: '1693083002925'
alias: 'Frigate Notifications: Front Walkway'
description: ''
use_blueprint:
path: SgtBatten/Beta.yaml
input:
camera: camera.front_walkway
base_url: https://ha.url.com
notify_group: all_mobile_devices
message: >-
{{ label }} detected - {{ camera_name }} at
{{event['after']['start_time']|timestamp_custom('%H:%M')}}
update_thumbnail: true
attachment: snapshot.jpg?bbox=1&crop=1
tap_action: '{{base_url}}/api/frigate{{client_id}}/notifications/{{id}}/snapshot.jpg'
Could it be the attachment isn’t doing the right full link like the tap_action does?
Maybe. Can you try with just one parameter on the image, just crop or just bbox etc.
Edit. tap action isn’t using the crop or bbox so that is a point of difference. Though shouldn’t matter
That worked with Snapshot, didn’t try with bbox.
id: '1693083002925'
alias: 'Frigate Notifications: Front Walkway'
description: ''
use_blueprint:
path: SgtBatten/Beta.yaml
input:
camera: camera.front_walkway
base_url: https://ha.url.com
notify_group: all_mobile_devices
message: >-
{{ label }} detected - {{ camera_name }} at
{{event['after']['start_time']|timestamp_custom('%H:%M')}}
update_thumbnail: true
attachment: snapshot.jpg
tap_action: '{{base_url}}/api/frigate{{client_id}}/notifications/{{id}}/snapshot.jpg'
Edit:
I wonder if this is an iOS issue in the smaller preview window. If I swipe down on the notification without clicking on it the preview loads. The smaller rectangle box shows a graphic on the far right and that shows some generic 404 image but can’t see it fully due to the size.
Thanks,
So with just snapshot set it worked as expected in both the preview and the expanded view?
From the beta notes:
### Beta Changes:
- Add 10s delay to final notification update to ensure frigate has time to save snapshot edits (crop, bounding box etc) if update thumbnail is enabled.
I think you mean, if update thumbnail ISNT enabled, right?
I was able to capture the example live.
From what I see in experience even if updated image is checked it fires an initial warning then the updated works. In my example shown this is the second, updated image notification. I saw the first one and thought I had a screenshot of it but didn’t save. It showed a 404 error screen.
UPDATE: Caught the error as shown.
Can you please try setting a 5 second initial delay. I wonder if the image simply isn’t ready.
No. If update thumbnail isn’t enabled most people won’t get any follow up notifications. This is just to try and get the final image right as some people were complaining of it not being the final snapshot.
However, now that the options for cropping and snapshot are configurable, perhaps we don’t need this. I will reassess once people have tested more.
Right. If update thumbnail isn’t enabled, it will wait 10 seconds. That’s not how I read whats currently in your changelog.
Where is this set?
I have the updated image setup which I thought, per the changelog would delay for 10 seconds to begin with.
It’s the last item in the filter section.
Correct, it delays the final notification (actually only 5s I need to update the change log). Your final notification is working fine, it’s your initial notification that isn’t.
I’ve confused you again. I was explaining why having update thumbnail false would not work.
The change log is correct, albeit not the full description of what happens.
Here are the conditions
- alias: "Update thumbnail at end of event"
choose:
- conditions:
- "{{wait.trigger.payload_json['type'] == 'end' }}"
- "{{('snapshot' in attachment and update_thumbnail) or video|length > 0}}"
It must be the end of the event
You must have attachment set to snapshot, not thumbnail and update thumbnail must be true. OR. Video is enabled.
The idea is to give frigate time to finish processing the image or video before sending the final one.
Found it, do I need to toggle the FILTER section on for it to work properly or are those timings OUTSIDE of the filter toggle?
No the toggles are for specific ones
1 Like