Hello all…
I am struggling with 2 of my 5 cams…
I am getting instant picture on 3 cams and 2 of them dont want to or just after a while…
Is there a way to find out what is causing the stream delay/brake?
Here the frigate conf for go2rtc:
go2rtc:
streams:
rtsp_driveway_cam:
- rtsp://xxx:[email protected]/11 # <- stream which supports video & aac audio. This is only supported for rtsp streams, http must use ffmpeg
# - "fmpeg:rtsp_driveway_cam#video=h264"
# - "ffmpeg:rtsp_cam#audio=opus" # <- copy of the stream which transcodes audio to opus
rtsp_driveway_cam_sub:
- rtsp://xxx:[email protected]/12 # <- stream which supports video & aac audio. This is only supported for rtsp streams, http must use ffmpeg
# - "ffmpeg:rtsp_cam_sub#audio=opus" # <- copy of the stream which transcodes audio to opus
rtsp_backyard_cam:
- rtsp://xxx:[email protected]/11 # <- stream which supports video & aac audio. This is only supported for rtsp streams, http must use ffmpeg
# - "ffmpeg:rtsp_cam#audio=opus" # <- copy of the stream which transcodes audio to opus
rtsp_backyard_cam_sub:
- rtsp://xxx:[email protected]/12 # <- stream which supports video & aac audio. This is only supported for rtsp streams, http must use ffmpeg
# - "ffmpeg:rtsp_cam_sub#audio=opus" # <- copy of the stream which transcodes audio to opus
rtsp_porch_cam:
- rtsp://xxx:[email protected]/11 # <- stream which supports video & aac audio. This is only supported for rtsp streams, http must use ffmpeg
# - "ffmpeg:rtsp_cam#audio=opus" # <- copy of the stream which transcodes audio to opus
rtsp_porch_cam_sub:
- rtsp://xxx:[email protected]/12 # <- stream which supports video & aac audio. This is only supported for rtsp streams, http must use ffmpeg
# - "ffmpeg:rtsp_cam_sub#audio=opus" # <- copy of the stream which transcodes audio to opus
rtsp_chicken_cam:
- rtsp://xxx:[email protected]/11 # <- stream which supports video & aac audio. This is only supported for rtsp streams, http must use ffmpeg
# - "ffmpeg:rtsp_cam#audio=opus" # <- copy of the stream which transcodes audio to opus
rtsp_chicken_cam_sub:
- rtsp://xxx:[email protected]/12 # <- stream which supports video & aac audio. This is only supported for rtsp streams, http must use ffmpeg
# - "ffmpeg:rtsp_cam_sub#audio=opus" # <- copy of the stream which transcodes audio to opus
rtsp_coop_cam:
- rtsp://xxx:[email protected]/11 # <- stream which supports video & aac audio. This is only supported for rtsp streams, http must use ffmpeg
# - "ffmpeg:rtsp_cam#audio=opus" # <- copy of the stream which transcodes audio to opus
rtsp_coop_cam_sub:
- rtsp://xxx:[email protected]/12 # <- stream which supports video & aac audio. This is only supported for rtsp streams, http must use ffmpeg
# - "ffmpeg:rtsp_cam_sub#audio=opus" # <- copy of the stream which transcodes audio to opus
Coop and Porch cams are doing great…
Backyard, Driveway and Chicken having issues.
Cams are all same brand (SV3C) and work flawless in the 5 fps frigate view…
In the cards that are supposed to show them they all have the same code like this example:
start with looking into your network/wifi performance, and ofcause the device where you are trying to view the cams on
This above, and then you “miss” lot other factors which make it impossible to even trying to “guess” what you are doing and where/what your “issue” depends upon
So 1 TroubleShootingPath could be " turn of the 2 that " always ? " work, and see if that helps upon the 3 “problem-devices”
Do you have all 5 cams in same View(Dashboard) ? , imagine 5 (1080P) cams in same View over a “doubtful/uncertain/unknown” Wifi connection, thou this should most likely result in “random” issues
Ok, so ther is No differencies worth mention ?, like Cam-Model, Connection-type, AP-distance(if wifi) , same (2.4ghz) as all of your wifi-IP-Devices , Additional AP’s (extenders) , or are all cams wired to same switch in your Network topology, etc. etc. Questions are endless caused to the limited info you provide, assuming ofcause that you already have checked logs in HA, Router etc. etc.
Hello and thx for the quick reply.
Sorry for your frustration, but thats why asked for how to troubleshoot this all.
So the cams, driveway cam is hard wired and the rest are wifi. All 2.4 ghz and besides chicken all on same wifi router. But now that u are saying it, the 2 in question are either wifi connected or hardwired through the same second router. Which is acting as a repeater for the main network with different ssid but hard wired to the main switch and than router.
I will def give that thought a try and test if this second router might be a problem child. Bummer that i am at work and cant test right away. Besides that all cams are 1080 pixel and codec 264 and doing great in frigate 5 fps preview.
They are all on 1 dashboard but each cam has its own custom webrtc card for real time frames/view.
Will keep u posted later and maybe with the additional info u have another idea on top
Thx so far
Sooo, quick update. I undid the wire conection to one if the problem childs and joined it to the main wifi and it did not change a thing.
Will turn off the two good ones next to see if your bandwidth idea could actually be it.
Besides that i noticed that the go2rtc config on the dedicated webif for those bad webcams has way more entries than the good ones.
As soon i have a chance i will post examples
Another update, all but one problem Webcam are turned off and no difference.
Cabled or wified…
Turned off audio on all cams to redcue traffic and also no dice.
Switched in the custom webrtc card from all stream options to only mse but also no dice.
Open to ideas
As you are “an IT Guy”, i recommend you read below, and try to imagine what you would prefer seeing/hearing from people, try to troubleshoot their devices/network, in specific as you certainly don’t seems to have a “standard/basic” network
PS: Remove your second “Router” from your “Setup”. run cams on your local (1 network/1 Router) … it’s basic trouble shooting … Sorry, can’t hold your hand, or “push” your further, or give more " throw in the dark, guessing" suggestions.
Thou im still thinking , You got 3, which all seems fine ( yeah i know same Brands … VolksWagon also make Porsche ) , stick to the 3 , and use the other 2 for something, or start from scratch, to see if you have ANY chance to get the 2 “Others” to play along
Then use Frigate.Card in HA, Or is your “Frigate”, actually a standalone Installation ? …
I think this goes into wrong direction here.
I am not asking for holding hand, i am more interested in “are there log files that could give me an idea whats going wrong” or “are certain configs in go2rtc that can speed things up”.
I tried frigate card but i did not like the low frame rate and the swipe option for it wanst mine.
So i ruled out networks quirks and bandwith constraints.
Frigate is hass addon.
And yes i am an “it guy” but like with everything, learning curves are always steep in the beginning and if you dont know which levers to pull to get things done you ask for help
Edit; If you are lucky you might even be able to get “help” from your Router-logs/network-analyzer
And ofcause there is the search-function ( thou be prepared from the beginning, to deliver relevant infos, such as DEVICEs, HA- Setup, Network Setup etc … Hint the Docs linked above ,anyone with “doubts” should read