#Frigate and Unifi Protect
1 messages · Page 1 of 1 (latest)
I have done the config, as you can see they fill tell you how you can get the ffmpeg stream
“ffmpeg:cameraname#video=h264”
It doesn't work for me
what is your frigate config
I'm pretty sure unifi is already h264 so there is no need to do that
go2rtc:
streams:
g4_pro:
- rtspx://192.168.1.1:7441/NTuuEtctS9o7uuy5
- "ffmepg:g4_pro#video=h264"
g4_pro_packages:
- rtspx://192.168.1.1:7441/IaSqCAtwLVMRhat
webrtc:
candidates:
- 192.168.1.180:8555
- stun: 8555
cameras:
g4_doorbell:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/g4_pro?video=copy&audio=aac
roles:
- detect
- clips
g4_doorbell_packages:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/g4_pro_packages?video=copy&audio=aac
roles:
- detect
- clips
Indentation not formatted here
Is there a code block button here?
okay so the stream is called g4_pro and the camera is called g4_doorbell
these don't match
To be fair that is not important
of course it is important
it is literally the whole thing that is needed for the frigate integration to find the camera stream
You keep them with two different name for sake of sanity and mental health 😅
Check the url for the frigate stream
It is correct
You should know I am the one that implemented go2rtc into frigate and the frigate integration
the names of the go2rtc stream and frigate camera matching is REQUIRED
for the frigate integration to find the stream for the camera entity
That's awesome
I am with the right guy
So the path: input has the name from go2rtc
And in fact the whole thing works
the camera entity, and you wouldn't get the option for mse / webrtc stream in the frigate webUI
which you already said, you only have jsmpeg option
Sweet
Let me change that
Okay that was amazing. You were right and it did add the streams to the cameras
I still don't have the go2rtc dashboard tho
I don't know if this message means anything:
To access the go2rtc stream externally when utilizing the Frigate Add-On (for instance through VLC), you must first enable the RTSP Restream port. You can do this by visiting the Frigate Add-On configuration page within Home Assistant and revealing the hidden options under the "Show disabled ports" section.
if you want to access the go2rtc dashboard you need to enable port 1984 of the addon and use that
well you likely don't want the go2rtc dsahboard published to the outside
just need to enable the port on the addon so it can be accessed locally
I have one URL for inside/outside but I guess the router doesn't care 😅
Right
Thank you Nick. You gave me a solution and some stuff to work on
I think I published the 8555 port and maybe I shouldn’t have
Hey @sharp field, my main goal is to have a live low res feed to use in the actionable notifications (person detection on the front door).
What is the best settings I should use? And is it just another line in the frigate config or go2rtc as well?
so you want the low res feed to be used for live view?
Yes
in your config I only see one stream, is there a different url for the low res stream
you can just set the go2rtc config to use the low res stream, but then you'd want something else to connect to the high res stream for recordings https://docs.frigate.video/guides/getting_started#step-6-enable-recording-andor-snapshots
but the low res part I don't know, maybe @nocturne vigil knows
You just check off the low or mid quality rtsps stream from UniFi protect on that camera then do whatever with Go2rtc for restream
I use the middle for frigate object detection and high for dashboards
Cool