Closed 007Nexus closed 2 years ago
Reolinks RTSP implementation is incredibly bad, it is often recommended to use their RTMP connection instead. Mine looks like this:
streams:
backyard_cam: ffmpeg:http://192.168.1.4/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=user&password=password
Reolinks RTSP implementation is incredibly bad, it is often recommended to use their RTMP connection instead. Mine looks like this:
streams: backyard_cam: ffmpeg:http://192.168.1.4/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=user&password=password
Thanks for the answer. But where does port 1935 come from? There is no such thing in the documentation. VLC does not play this link. This is not the first time I've seen this (reolink recommendations for Frigate), but it doesn't work for me. Perhaps this is for other cameras? The RTSP stream on my camera is pretty stable, btw. Log go2rtc: 16:41:51.042 DBG [streams] probe producer url=ffmpeg:http://192.168.3.22/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=XXXXX#video=mjpeg 16:41:51.043 DBG [exec] run url="exec:ffmpeg -hide_banner -fflags nobuffer -flags low_delay -i http://192.168.3.22/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=XXXXX -codec:v mjpeg -force_duplicated_matrix 1 -huffman 0 -pix_fmt yuvj420p -an -rtsp_transport tcp -f rtsp rtsp://localhost:8554/99cf4cd5f0ce3a85fe5526b817fd3fd4" http://192.168.3.22/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=XXXXX: Invalid data found when processing input
Log Frigate: [2022-10-20 19:26:12] ffmpeg.vorota.detect ERROR : http://192.168.3.22/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=XXXXX: Invalid data found when processing input [2022-10-20 19:26:12] frigate.video ERROR : vorota: Unable to read frames from ffmpeg process. [2022-10-20 19:26:12] frigate.video ERROR : vorota: ffmpeg process is not running. exit capture thread...
But where does port 1935 come from? There is no such thing in the documentation.
Port 1935 is the standard RTMP port, just like how 554 is the standard RTSP port
Log Frigate: [2022-10-20 19:26:12] ffmpeg.vorota.detect ERROR : http://192.168.3.22/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=XXXXX: Invalid data found when processing input [2022-10-20 19:26:12] frigate.video ERROR : vorota: Unable to read frames from ffmpeg process. [2022-10-20 19:26:12] frigate.video ERROR : vorota: ffmpeg process is not running. exit capture thread...
If you tried it in frigate, it looks like you didn't change your input_args which is of course required https://docs.frigate.video/configuration/camera_specific#reolink-410520-possibly-others
If you tried it in frigate, it looks like you didn't change your input_args which is of course required https://docs.frigate.video/configuration/camera_specific#reolink-410520-possibly-others
Thanks for the answer. Of course, I read the frigate documentation, and added input_args: -avoid_negative_ts
But this doesn't work for me. Above I gave part of the log.
VLC should open a video from a link?: http://192.168.3.22/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=XXXXX VLC won't open this link for me. My camera is Reolink-520A.
Interesting, maybe you have something disabled in the reolink cameras settings under Network Settings -> Advanced
We've had many users validate / use these settings with the 520a specifically and other reolink cams as well. I'm using it with 511WA personally
Interesting, maybe you have something disabled in the reolink cameras settings under
Network Settings -> Advanced
We've had many users validate / use these settings with the 520a specifically and other reolink cams as well. I'm using it with 511WA personally
I replaced in the settings only what is recommended here: https://docs.frigate.video/configuration/camera_specific/#reolink-410520-possibly-others
I can try to factory reset the camera, but it hangs high.
Oh, that looks different than my view, I wonder if you are not on the latest firmware for the camera.
(also recommend doing it in general, as it gives more options for setting the iframe interval and constant or variable frame rate)
Oh, that looks different than my view, I wonder if you are not on the latest firmware for the camera.
(also recommend doing it in general, as it gives more options for setting the iframe interval and constant or variable frame rate)
I'm trying to update the firmware, but:
RTP MJPEG https://www.rfc-editor.org/rfc/rfc2435#section-3.1.5 The maximum width is 2040 pixels. The maximum height is 2040 pixels.
I have added a fix for 2560x1920 and 2560x1440 https://github.com/AlexxIT/go2rtc/releases/tag/v0.1-beta.9
If anyone has a problem with other resolutions, write them here.
We've had many users validate / use these settings with the 520a specifically and other reolink cams as well.
I wrote to reolink support - they sent the firmware for my camera (for IPC_523128M5MP_V2, not IPC_523128M5MP). I updated the firmware, RTMP (go2rtc and frigate) started working normally. With the latest update go2rtc 0.1-beta.9, the conversion to MJPEG started working normally. Thank you very much!
can you please share it with us? Meanwhile i contacted support, still this update is not present on their website. I'm slowly changing all my reolink cameras with Dahua, much better hardware and software. And it's really frustrating with RTSP, i didn't find a way to get it working flawlessly... With Dahua, another story, all so fast and smooth!
can you please share it with us?
Sure! Firmware Reolink 520A
can you please share it with us?
Sure! Firmware Reolink 520A
Thanks, meanwhile i got from Reolink (i have RLC520A v2)
@AlexxIT said to mention any other problem resolutions.
I have added a fix for 2560x1920 and 2560x1440 https://github.com/AlexxIT/go2rtc/releases/tag/v0.1-beta.9 If anyone has a problem with other resolutions, write them here.
I have the misfortune of owning a Reolink 820A 4k IP cam. Its main stream supports 3840x2160, 2560x1440 and 2304x1296. I had it configured at the lowest of these resolutions (2304x1296) and couldn't get it to work in go2rtc (although it was working as a direct RTSP stream in Frigate). After finding this issue, I changed the resolution to 2560x1440 and everything worked. It would be great to also add a fix for 2304x1296 so it's not necessary to use a higher resolution stream.
Two new resolutions in release https://github.com/AlexxIT/go2rtc/releases/tag/v1.1.2
Hi! Beelink U59(n5105, 8/512, ip:192.168.3.12) Home assistant Supervised 2022.10 go2rtc 0.1-beta.8 Camera Reolink 520A. Browsers: Chrome, Brave, Yandex.
Log:
What I tried to do: The camera is on/off. The integration has been reloaded. Checked on the TP-link Tapo C200 camera - everything is fine.