Thanks for testing. I found the issue (i wasn’t handling friendly names with spaces properly) and you are welcome to try again if you like. I’ve edited the above post with the newer 0.11.0.2 version
I’ll have to think about hyphens too at some point. I saw earlier in this thread some users had them in their names.
The issue was actually the reverse, because the entity name is already in lowercase the mqtt message was not triggering it due to it having capitals (Driveway_South). So what I’ve done is add the toggle to use the friendly name which gives the best flexibility. If someone calles their camera Driveway_south in frigate, using | title would also be problematic because it would capitalise the ‘s’. So at least with the friendly name it is user configurable and as long as it matches frigate ( ‘_’ not required) it should have worked. But apparently not you said. Are you getting a particular error?
The original blueprint by hunterjm just had a text field where the user simply typed the name exactly the same as their configuration in frigate. I can easily revert to that, but liked the idea of having an entity slector that only showed frigate entities. Ultimately i’d like to work out how to exclude all the extra ones ending in _person, _dog etc too
The selector makes it super nice so I would hate to go back to old style. The issue is that Frigate is sending to the MQTT Broker "camera": "Driveway_South", and HA sees the Entity as camera.driveway_south. If there is a way to format the string from Frigate as all lowercase, it would solve our problem.
TLDR - Frigate camera name does not match the HA Entity ID due to case formatting.
Yes but my testing using the template editor indicates i’ve accounted for that. If you paste this into your template editor it should return Driveway_South. setting true or false for the first line is equivalent to toggling the selector.
I’ve done it a different way using the lower command. No idea if it’s a valid way of doing it within a value_template though. Trying to test but i’m not home. Have also updated the code block above that you have been copying if you want to test
No worries, I also just realised the error with the previous method. I was using a variable without defining it properly first. So if this lower method (which is better anyway) fails I can try the previous way with the toggle again, but better.
Reading through some of the latest posts in here after updating my Frigate from 0.10 to the latest stable at 0.11.1, I’m unsure about which version of the blueprint I should be using. Can someone clarify for me what the best version is right now? Thanks.
I’m so sorry, I was wrong. I didn’t recognize that I was in a wrong field (notification instead of entities). I changed the blueprint acc. to your advice and have to test it tomorrow.
Thanks!
Hunterjms has a bug so you’ll need to fix it to work with frigate 0.11 as they have not updated it yet. edit line 164 and change ‘or’ to ‘else’ fps: '{{ fps_value|int if is_number(fps_value) else 5 }}'
I am not trying to replace the one this topic is about but temporarily offering some updates until they return including a cleaner fix for the above. While I was at it I tried to make a few improvements too. Up to you.
I tried to folloq your routes and now a i get
‘’ The automation “Notification_Movement_on_Driveway” (automation.notification_movement_on_driveway ) has an action that calls an unknown service: notify.notificationgroup‘’
I configured my group in the configuration.yaml
But it seems not to see it…
Any ideas?
device_tracker. blah blah is not a valid notification service.
you should use the name of the mobile app notification services excluding the domain. you might need to find them by looking in developer tools > services.
here’s one of mine:
notify:
- name: Me and Her
platform: group
services:
- service: mobile_app_pixel_4a
- service: mobile_app_samsung_s21
Did you call those mobil bla bla or did this come from hass when you onboarded the phones?
I looked through all devices and entites, but no mobile anything.
But thx for the hint…
Will try to find
I have running Home Assistant on a Pi and FriGate because of disk space on my Synology NAS.
It is perfect working together.
I tried the blue print to get my frigate notifications, but is never fired.
If I just make an automation that is fire a text notification on camera motion sensor event it is fired and shown in the app.
Does this blueprint not work if frigate is not on the same system like home assistant?
Oh great, with this hint i was able to find them.
Havent been able to test yet, but let you know…
Next on my list woulb be how i can tell the blueprint that the same group i want to notify needs to be not home to trigger notifocations…
Can i just replace any device in that field with the group name?
Thx in advance
It works fine, my own setup is different machines like yours.
To troubleshoot compare the entity id of the camera with the frigate config. Are they identical?
Is mqtt working? Can you see mqtt messages
of events making it to home assistant? Check mqtt logs.
Check home assistant logs for errors.
You need to create another group, you can have device groups, people groups etc just needs to only be entities that have the home or not home states. Then use this entity for that field.
Very nice! I just tested it and it worked with the mobile app so app services! And with your hint towards device group I will get the absence filthe absence filter set as well! Commission mark only thing not working now is playing the clip from N from android! http://url:8123/api/frigate/notifications/1666347172.617492-141xhv/driveway_cam/clip.mp4
The link it creates looks kinda OK sokay so I will need to find what’s missing