@hatmeh80 commented on GitHub (Oct 2, 2023):
may be the resolution ?
detect: width: 352 height: 288
@NickM-27 commented on GitHub (Oct 2, 2023):
No, that won't cause errors from the cameras
@hatmeh80 commented on GitHub (Oct 2, 2023):
mqtt: host: 192.168.100.237 user: mqttbroker password: rori2010
ffmpeg: hwaccel_args: preset-rpi-64-h264
detectors: …
@NickM-27 commented on GitHub (Oct 2, 2023):
no, then frigate wouldn't start. The issue is going to be something in the camera, being okay sending the main stream but not the low stream
@hatmeh80 commented on GitHub (Oct 2, 2023):
2023-10-02 13:21:32.162916175 [INFO] Starting Frigate... 2023-10-02 13:21:39.186325444 [2023-10-02 16:21:39] frigate.app INFO …
@NickM-27 commented on GitHub (Oct 2, 2023):
weird, I am not sure then why it is complaining on that stream but not the other one
@hatmeh80 commented on GitHub (Oct 2, 2023):
2023-10-02 13:10:41.547484838 [INFO] Starting Frigate... 2023-10-02 13:10:49.107385492 [2023-10-02 16:10:49] frigate.app INFO …
@hatmeh80 commented on GitHub (Oct 2, 2023):
if i don't define the go2rtc in the config , how would frigate know the path im referring to ?
@NickM-27 commented on GitHub (Oct 2, 2023):
because instead of using rtsp://127.0.0.1:8554/frontdoor_low you would just use `rtsp://admin:pass@192.168.100.49:554/user=admin_password=!_channel=1…
@hatmeh80 commented on GitHub (Oct 2, 2023):
did that but lost rtc as the below screenshot , do i have erros in the config i did ? My substream resolution is 352x288 May be indentation error…
@NickM-27 commented on GitHub (Oct 2, 2023):
I wasn't suggesting you delete go2rtc entirely, I was suggesting you just don't use go2rtc for the low stream
@hatmeh80 commented on GitHub (Oct 2, 2023):
ok got the cpu down to 12% but the UI shows no frames recieved, clicking on the camera loads it via webrtc . any idea why ? ![Screenshot 2023-10-02…