no i do not have it, will try ti install it, boothe of the url is not working, so will need some time to figuer it out.
When going to frigate from the add on i can http://homeassistant.local:8123/ccab4aaf_frigate-fa/ingress
but i cant the url to work to install the frigate integration
yes that i know, looks like i did have the wrong link, the likns that they are showing was not working if runnin frigate full
http://ccab4aaf-frigate-fa:5000/ works its hte -fa that was missing
+1 for this
Also, does anyone know how I could clear the notifications? I know how to clear
But the tags used appear to be unique to each notification. What I want to do is clear any/all notifications from my doorbell when I open my door, triggered by my door sensor.
I guess I’d either need a way to get all the tags used in last X hours, or a feature to be able to set a custom tag in this blueprint.
Has anybody found a way to use TTS with the notification to play a message with the name of person detected?
In simple words:
Let’s say that the person’s name detected on the camera is Mark. I want to announce on the speaker that ‘Mark is at the door’.
Should be possible using custom action.
I can’t get the blueprint Frigate Notifications (0.12.0.2) to send a notification to my phone if I click the run option.
I’m running Frigate (0.12.1-367d724) in a docker container with the HACS addon in HA.
My MQTT logs have this error. I don’t know where that IP comes from.
2023-12-20 20:14:02: New connection from 172.30.32.2:33584 on port 1883.
2023-12-20 20:14:02: Client closed its connection.
I was able to setup a manual automation that does work
alias: Notify of events
trigger:
- platform: mqtt
topic: frigate/events
condition:
- condition: template
value_template: "{{ trigger.payload_json['after']['label'] == 'person' }}"
action:
- service: notify.mobile_app_my_iphone
data:
message: Someone is at the door
title: Doorbell
data:
entity_id: camera.camerafrontdoor_person
Kind of new to this so include as much details as you can to help. Thanks
You can’t run it manually, it needs the data from the mqtt message.
works automatically or when you press run? If the former, then there is likely no issues with mqtt.
Post your automation yaml?
I’m guessing you want the yaml for the blueprint automation?
alias: Frigate Notifications (0.12.0.2)
description: ""
use_blueprint:
path: SgtBatten/Stable.yaml
input:
camera: camera.camerafrontdoor
notify_device: xxxxxxxxxxxxxxxxxxxxxxxxxxx
attachment: snapshot
critical: "false"
title: Front Door
silence_timer: 1
debug: true
ios_live_view: true
tap_action: "{{base_url}}/api/frigate/notifications/{{id}}/snapshot.jpg"
url_1: >-
{{base_url}}/api/camera_proxy_stream/camera.{{trigger.payload_json['after']['camera'].lower()}}?token={{state_attr(
'camera.' ~ camera, 'access_token')}}
Looks fine. It doesn’t trigger at all, no traces?
My mistake it does work. Don’t know what I was doing incorrectly. Maybe the other notification automation interfered. Is there a way to see the notification more than once?
even im facing similar issue , automation is not getting triggered, older frigate blueprint 1.0 was working
running everything on docker
HA core: 2023.12.3
frigate HA integration : v4.0.0
frigate : 0.12.1-367D724
mqtt : eclipse-mosquitto:1.6.14
automation configuration :
alias: dummy frigate
description: ""
use_blueprint:
path: SgtBatten/Stable.yaml
input:
camera: camera.frontright_2
base_url: https://home.abc.abc
critical: "true"
labels:
- person
- car
- bus
- motorcycle
notify_device: 876b1565605647606dc65f7e22ee2ba3
message: "test: A Person was detected on the Side camera."
ios_live_view: true
debug: true
color: grey
seeing below error , not sure which client is causing it
2023-12-20T22:06:09.203933730Z 1703109969: New connection from 172.18.0.1 on port 1883.
2023-12-20T22:06:09.204528136Z 1703109969: Client <unknown> disconnected due to protocol error.
2023-12-21T08:46:27.060621137Z 1703148387: Saving in-memory database to /mosquitto/config/mosquitto.db.
Check your camera name
What do you mean?
for the same camera , im able to get notification from old frigate notification blueprint (Frigate Notification Blueprint · GitHub)
camera chosen in 2.0 frigate automation
tried enabling trace , not able to see any activity in log book
notification from older frigate notification blueprint :
In frigate your camera is not numbered 2 right?
It has to match. So delete the _2 from the yaml of the automation, or better yet, rename the entity assuming you don’t have a conflict.
Edit; if you use the beta it would work automatically also.
thanks, beta is working
Being able to click on the notification again and choose clip vs snapshot.
Are you on IOS? Because it already does that on android and I don’t think I can change it for ios
