LOL! Hahahaha… 
Well but my question was more how you configured frigate to also detect dogs (wifes) etc can you post your config for me ? Using beta hassio add-on
Sorry, but i recently moved over to Deepstack and Zoneminder object detection.
So unfortunately I dont have the confs anymore…
thank anyway … got it 
So my Media Browser shows all the clips but still can’t play them. I can play them directly (if I download them from the Clips folder). I can even drag/drop them to my web browser (Edge for Mac) and it plays correctly.
The stream that it is supposed to be recorded for clips is the same as the RTMP stream. The RTMP streams play correctly in Home Assistant (when using the stream component), so I can’t really understand why the Media Browser can’t play it.
Am I supposed to add additional folders or something to my Home Assistant setup? I have Frigate running on a separate host than the VM where Home Assistant is running.
It literally just loads for 1, 2 seconds, then shows me this:
Does anybody know where I can debug this?
EDIT: OK, in the chrome/Edge debug tools i get this:
That’s odd. Try setting the log level for werkzeug to info in the frigate config to see what the request looks like to frigate.
Has anyone updated to Core 2021.1.4? I want to make sure that integration and custom components are still working with this release.
I had the same issues when it was using the wrong hwaccl options. Now it works fine…
Yeah works fine, except for my media browser issue (see above) but it’s been the problem from 0.117.
1 Like
logger:
# Optional: default log level (default: shown below)
default: info
# Optional: module by module log level configuration
logs:
frigate.werkzeug: info
Like this? Sorry couldn’t find a sample after searching this thread or the Github repo.
Release candidate 1 is now available: https://github.com/blakeblackshear/frigate/releases/tag/v0.8.0-rc1
Note that this requires an update to the custom component as well.
1 Like
Actually, there probably wont be any messages there. See what the nginx logs say at /var/log/nginx/error.log inside the container. How are you mounting your volume for the clips folder?
Thanks for the great work ! Quick one: now, masks for detect role have to be defined for each camera and each object in the objects -> filters -> <object_name> section, right ? I’ve tried to setup it in motion but objects are still detected, even with the mask.
Here is an example.
cameras:
front_door:
...
motion:
mask: '0,900,1080,900,1080,1920,0,1920'
...
objects:
filters:
person:
min_area: 5000
threshold: 0.6
mask: '574,1058,772,1072,768,632,439,636,34,600'
You can also provide a list of masks:
cameras:
front_door:
...
motion:
mask:
- '0,900,1080,900,1080,1920,0,1920'
- '574,1058,772,1072,768,632,439,636,34,600'
...
1 Like
Thanks for the quick reply ! Masks defined in the mask section do not seems to filter object for camera with the detect or clips role, I still get events. There, I guess I have to add them, object by object, in the filters section.
Another question: with the notifications API (https://your.public.hass.address.com/api/frigate/notifications/{{trigger.payload_json["after"]["id"]}}/thumbnail.jpg), how do you get a full size snapshot of an event instead of the thumbnail.jpg ?
The old https://url.com/api/frigate/notifications/{{trigger.payload_json['after']['id']}}.jpg do not seem to work anymore.
Sorry for a bit of a wishy-washy question… however I run frigate alongside zoneminder… I simply run zoneminder as it does all that I want but for a couple of cameras I run frigate because it does realtime detection where as zm only processes an event once the motion has stopped.
However I also want zm to carry on monitoring the two cameras I use frigate with. The problem is I can’t start frigate up while zm is running… the FPS for the cameras shows 100FPS and no live image is received… and also after a random number of days frigate seems to silently stop monitoring the cameras…
Given there’s no errors to go with any pointers on how I could resolve this? or for that matter is it just matter of fact frigate requires exclusive access to a camera?
That is why the mask was moved under motion. It only applies to motion and does not do any filtering for objects.
1 Like
Use https://your.public.hass.address.com/api/frigate/notifications/{{trigger.payload_json["after"]["id"]}}/{{trigger.payload_json["after"]["camera"]}}/snapshot.jpg. This will only be available once the event has ended.
1 Like
Frigate is aggressive about fetching the latest data from the camera, so its probably just saturating the bandwidth. Have you set the fps option in the config? Also, you may need to update the input parameters to be less aggressive. See the example in the docs for blue iris config.
1 Like
Hey Blake, I just updated the integration to 1.0 and am no longer able to connect to my Frigate container. Navigating to the container via the url http://192.168.1.51:5000 returns the “Frigate is alive and healthy” response, and I can see all is good in the container logs.
Any idea what’s going on? I believe it was working just fine prior to updating.
