-
-
Save SgtBatten/10a2dc7f16af9f55f3ba83fe4523d8d7 to your computer and use it in GitHub Desktop.
| blueprint: | |
| name: Frigate Notifications by SgtB have moved | |
| description: | | |
| ## ANNOUNCEMENT | |
| I have moved from this gist to a github repositry. | |
| Please checkout https://github.com/SgtBatten/HA_blueprints for the latest versions | |
| domain: automation | |
| input: | |
| camera: | |
| name: This blueprint has moved. | |
| description: Please checkout https://github.com/SgtBatten/HA_blueprints for the latest versions | |
| selector: | |
| text: | |
| default: https://github.com/SgtBatten/HA_blueprints | |
| trigger: [] | |
| action: [] |
also: Ah, there is where the debugging is going. i expected them in the logging of home assistant somewhere. :)
It goes to the logbook also, but the formatting is hard to read. much easier to read in the trace.
I have just uploaded a fix for your issue.
The issue was capitalisation of your zones in frigate config.
Required zones: ['side', 'examples'],
Entered Zones: ['Side'],
See here that side is not the same as Side
The fix should make everything lowercase behind the scenes, regardless of your configuration. Please try the latest beta and let me know
on it. I was seeing that and so i tried to add the zone's with upper and lowercase. didn't work.
I let you know the result of the fix.
@SgtBatten
IT WORKS! thank you.
now up to finetuning my notifications.
i tried to add the zone's with upper and lowercase. didn't work.
Yep that wouldn't have worked because I was forcing the inputs to be lowercase already (due to users having the opposite problem to you. Now it does both so they should always match.
@mrplow I have a workaround and I really hate how much bigger the blueprint gets but try the latest beta (16a). It sends a final notification 10 seconds after the end of the event which seems to be enough time for my frigate instance to process the snapshot.
It will only send if update thumbnail is true and attachment is set to snapshot.
@Delta1977 forked from an original gist. I could change it for easier conversations/issue tracking though
@SgtBatten Do you have plans or a timeline to move to git?
@SgtBatten IT WORKS! thank you. now up to finetuning my notifications.
and that was it, worked 1 time :/
i am going to start allover, trow away what i have now and start with 1 camera.
let you know what happens.
first i had to restart HA,after that the camera we troubleshoot started working again. so that was something with my homeassist.
it looks like your blueprint doesn't like _ in the camera names. I renamed 1 camera and now it works.
other question, can i edit the zones in the automation yaml?
the tekst glitch is preventing me from typing but i kan paste and hit enter,or i just type it in the automation yaml.
@SgtBatten wow, that was a big change. So far so good though. I had two notifications so far this morning and both had the bounding boxes.
blueprint doesn't like _ in the camera names
I have _ in some of mine. It does handle them fine.
Yes you can edit the zones in yaml, select one of the examples and then edit it in yaml. I have raised an issue on GitHub and someone has already done a fix but it is not yet release in homeassistant.
@Delta1977 I will clean up this repo later today but you can now use https://github.com/SgtBatten/HA_blueprints and people can raise issues there.
@Delta1977 I will clean up this repo later today but you can now use https://github.com/SgtBatten/HA_blueprints and people can raise issues there.
@SgtBatten great. Thank you for your amazing work
also: Ah, there is where the debugging is going. i expected them in the logging of home assistant somewhere. :)