Yes, this automation has many variables that are not accessible when tested manually. Doubt it could possibly work.
Can someone confirm this?
I am running Frigate container in Unraid, along with Frigate NVR Proxy in Home Assistant. From my reading I think this should still work, but after installing it, and setting it up absolutely nothing happens when I walk in front of a camera to test it.
Do I need to do something special with this do to me not running Frigate directly in Home Assistant and running it in Unraid, even though I am running the Frigate proxy version? At first I thought I needed to update the IP in the blueprint yml file, but reading something else made me think I didnt need to.
Thanks
About a week ago i moved from the frigate addon on HAOS to running frigate on my unraid server. No configuration changes were needed. When you say IP do you mean your base URL in the automation? Mine did not need changing as the frigate proxy ensures HA still sees the media in exactly the same location.
Work your way through the workflow of a notificationâŚ
Is frigate itself working i.e do you get events in frigate? if not, the issue is with your frigate config on unraid.
Is frigate proxy working i.e can you see frigate events and recordings using the HA media browser?
if yes to both above, check the last few posts about the camera entity name.
To answer your questionsâŚ
In unraid, Frigate, under events I see the events I want to see.
TBH, I had never even checked under the HA media browser, I was just looking under Frigate on my side panel, so I just went and looked and there are recordings there of the notifications/events I would expect to see.
So then to camer entity name, I found that yesterday. In the blueprint, I wasnât sure if it was looking for the name, or entity ID, so the automation I was testing (the doorbell) I originally just had it listed as Doorbell, because that is what it was labeled as, but after I read that, I updated it to camera.doorbell.
Still no go. I donât understand what could be happening.
Thanks!
The autmations are showing as never being triggered, so some how, something isnât getting to it to let it know it needs to trigger.
I had the same problem. Frigate container in a LXC container and Frigate NVR Proxy Add-On in Home Assistant. No notification.
Then I tryed to install the frigate-hass-integration and notification started to work right after!
You mean the frigate integration from HACS? I didnât realize I needed that at first as wellâŚinstalled that yesterday, and still nothing 
That is how I was able to get the camera entity, before that I didnât know what it was.
So read the entities againâŚapparenty the camera.doorbell was not what it would be looking for, because when I search it in entities, nothing pulls up, but when I search Doorbell it does pull up. So I changed the camera name back to that in the automation. Unfortunately, it didnât fix the issue. Still no notification, and nothing at all in the trace.
What it needs to be is everything in the entity id after camera.
So try doorbell
Iâm not sure if it is case sensitive but someone a few days ago had success with changing to lowercase among a few other things.
Then again if camera.doorbell doesnât show any results, that is an issue
yeah, i tried both, no go
So Iâm assuming its okâŚnow looking at mqtt to see if maybe there is an issue there?
Finally got it working, I ended up uninstalling MQTT on the server, and on home assistant, installed it on the server, setup user ID and pw, and then installed it on HA. I then pointed the HA host at my server, and used the same user id and pw.
Once done, they connected and seemed to be talking. Then the notifications started coming through.
1 Like
Frigate 0.11 is out!
I upgraded from 0.10.1 to 0.11, and the HACS integration from v2.7.0 to v3.0
I see MQTT messages firing on detection on both the camera and the events topics. Notifications arenât being registered as triggered, but there are traces recorded with the text
Stopped because of unknown reason ânullâ at September 24, 2022 at 00:15:59 (runtime: 0.01 seconds)
I donât have _2 states in developer tools, reconfigured both the MQTT and HACS frigate integrations so entities would regenerate.
It would seem notifications with this blueprint are no longer working with the new release, can anyone else confirm?
Found in logs:
Error rendering variables: ValueError: Template error: int got invalid input âunknownâ when rendering template â{{ fps_value|int if is_number(fps_value) or 5 }}â but no default was specified
changed or to else as described in many posts above, itâs now working flawlessly, at least getting the notification + snapshot, and being able to watch the clip.
Nevermind, need more coffee.
Well if this is the case Iâm gonna hold out on updating frigate for now⌠damn
same gonna wait on a blueprint update, this blueprint is just legit too good to not have it married up with frigate
1 Like
Using the file editor plugin, you can modify the copy of the blueprint that has been saved on your device.
Specifically, look for this line:
{{ fps_value|int if is_number(fps_value) or 5 }}
then change or to else so it looks like this:
{{ fps_value|int if is_number(fps_value) else 5 }}
Save the file, and this should get you up and going for the time being until an update is out. I donât know if the rest of the blueprint works, but at least what I use (phone notification + snapshot â touch to watch the clip) works.
1 Like
I have not updated yet but will try to troubleshoot the template with you,
Please check if these entities still exist in your updated version of frigate
based on your specific 2nd error the likely edit should be as simple as:
{{ fps_value|int(5) }}
Edit: In fact i believe these two lines could be replaced
fps_value: "{{ states('sensor.' + camera + '_camera_fps') }}"
fps: "{{ fps_value|int if is_number(fps_value) or 5 }}"
with
fps: "{{ states('sensor.' + camera + '_camera_fps')|int(5) }}"
Post the errors you see and iâll try to assist.
Logger: homeassistant.components.automation.basement_camera_notifications_frigate
Source: components/automation/__init__.py:500
Integration: Automation (documentation, issues)
First occurred: 6:51:19 PM (2 occurrences)
Last logged: 6:51:36 PM
Error rendering variables: ValueError: Template error: int got invalid input 'unknown' when rendering template '{{ fps_value|int if is_number(fps_value) or 5 }}' but no default was specified
Firstly can you confirm the camera_fps entities still exist as per my screenshot above.
If they do, please edit the blueprint as per my or @lolwut posts above and that error will be resolved.
This error doesnât make sense to me as being caused by this update as this change was made several versions ago in home assistant and should have been occurring for many months. I suspect it is a side effect at most. Anyway, see how you go with the above and let us know.