cameras:
# Required: name of the camera
back:
# Required: ffmpeg settings for the camera
ffmpeg:
# Required: A list of input streams for the camera. See documentation for more information.
inputs:
# Required: the path to the stream
- path: rtsp://viewer:{FRIGATE_RTSP_PASSWORD}@10.0.10.10:554/cam/realmonitor?channel=1&subtype=2
# Required: list of roles for this stream. valid values are: detect,record,clips,rtmp
roles:
- detect
- rtmp
# Optional: stream specific input args (default: inherit)
input_args:
also another case of ambiguity Iāve foundā¦ the install instructions for the new HA integration read " The best way to integrate with HomeAssistant is to use the official integration. When configuring the integration, you will be asked for the Host of your frigate instance"
I installed it via hass and I was not asked anything?!?!? not on the github page or the official docs can I find the specifics on how I configure the HA integration?!?!?
For clips, you are adding global clips options at the camera level. Some of those are global only options.
For your input_args, those either need to be indented one level up (they would apply to all inputs for the camera), or one level down (they would just apply to the one input). This is how they would be indented one level up.
HACS adds the integration so its available under Configuration > Integrations > Add like a normal integration. HACS does not setup the integration for you.
blakeblackshear Iāve actually been using HA for over a year now lol
Both your suggested fixes have workedā¦ many thanks for your help and sorry as it seems Iām having a bad day here, I should of spotted both those issues
1G to each container, I believe. Iām in the same boat as you with regards to familiarity with docker, and spent ages looking for a solution to the shm issue. I really donāt think that this can be the best way to do it, but it seems simple and works flawlessly (for me at least).
Perhaps someone could advise the best way to increase the shm-size for the Frigate add-on running on supervised HASSIO (in Debian/Ubuntu etc), and we could add it to the new docs site for others who are having trouble?
I love all the new additions to Frigate by the way - the new UI, docs, config changes etc. Itās super work by all involved!
I love this project to much just to let it goā¦
Im currently running ZoneMinder with zmevent notfication server.
As this āprojectā moves on I see the potential to drop ZM for Frigate.
A BIG THANKS to the authors/author for this wonderful project!
A questionā¦ Im still waiting for my coral to arrive and was thinking of reducing the overhead from my cams. As of today im running ZM (9 cams) and Frigate (4 cams).
I would like to use the url from ZM but have no luck as its mjpeg and starts with httpā¦
Have anyone had any success with the stream from ZM in Frigate? If so, please share your configā¦
I currently use Frigate behind Zoneminder (still on Frigate 0.7.3) as there are still some features that I prefer with the setup above what I can get with 0.8.0. Frigate will eventually mature (likely by 0.9.0) for me to be able to make the transition away from ZM completely.
But I use ZM camera (mjpeg) streams in Frigate easily since ffmpeg processes them without issue. Just use this as your input into Frigate:
https://<zm ip address>:8443/zm/cgi-bin/nph-zms?mode=jpeg&monitor=1&scale=50&maxfps=3
Obviously youāll need to adjust your IP address, monitor number, and optional scaling and max FPS. But that works pretty well for me.
The path to the jpg stream works in VLC but I cant seem to make it work in frigate.
Trowns tons of errors as these:
frigate.video INFO : frigate_pathway: ffmpeg process is not running. exiting capture thread...
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x55bff8575140] moov atom not found
/tmp/cache/frigate_pathway-20210127220819.mp4: Invalid data found when processing input
frigate.events INFO : bad file: frigate_pathway-20210127220819.mp4
frigate.video INFO : frigate_pathway: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
How have you configured FFMPEG settings in your setup?
Iād recommend starting with a simple config and building it out from there. Indentation matters, and itās easy to lose track of the correct indentation necessary for each part if your config is already pretty large.