RTSP/RTMP proxy/server to offload the cameras #1623
Replies: 9 comments 21 replies
-
|
I'm planning to bake this into frigate directly in place of the existing RTMP restreaming implemented in nginx. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds like a great idea! Personally I have found the RTMP restreaming in nginx to be a bit clunky. |
Beta Was this translation helpful? Give feedback.
-
That would be a thing of beauty Blake. |
Beta Was this translation helpful? Give feedback.
-
|
THIS IS GREAT! |
Beta Was this translation helpful? Give feedback.
-
|
Tjabba Minglarn - Exactly. For me it serves:
Only Blue Iris and rtsp-server connects to the cams directly as of today. |
Beta Was this translation helpful? Give feedback.
-
|
Shouldn't there need to be some sort of security on the secondary rtsp(:8554) stream? Since you've already auth'd to the camera via simple-server tool, doesn't that make the camera streams completely visible to any IP on that network? |
Beta Was this translation helpful? Give feedback.
-
|
You can easily add that if you want, just a matter of some more conf to rtsp-server, please check the config for the options. |
Beta Was this translation helpful? Give feedback.
-
|
And in my case, no, ive got all my cams on an iot vlan. |
Beta Was this translation helpful? Give feedback.
-
|
Question... |
Beta Was this translation helpful? Give feedback.
-
Nope - on another machine. Ive noticed some issues when RTMP converts to RTSP via rtsp-simple-sever. As well as just redirecting RTMP to RTMP..... Havnt managed to figure out or tweak any configs. Ive only got one reolink running RTMP and I also tried it via rtsp-simple-server with so-so results :/ RTSP to RTSP works flawlessly. |
Beta Was this translation helpful? Give feedback.
-
|
@Minglarn Posted an issue on the RTMP stream issues... Please go in and make a comment and say "Me too" or something :) |
Beta Was this translation helpful? Give feedback.
-
|
I just tried it with my Reolink camera but I don't get the clear image. Do I need to make any changes ? |
Beta Was this translation helpful? Give feedback.
-
|
How do you add it back to HA ? HA Generic platform requires a still_image_url which rtsp-simple-server does not provide. |
Beta Was this translation helpful? Give feedback.
-
That is correct. Personally I still fetch the still image from the camera. |
Beta Was this translation helpful? Give feedback.
-
|
TLDR for anyone with reolink cams and stream stability issues, I highly recommend rtsp-simple-server as @tubalainen mentioned. #gamechanger! I have 5 Reolink cameras and have tried all manner of RTSP/RTMP/HTTP/neolink to integrate them into a frigate and maintain a "stable" connection. I was almost to the point of just throwing in the towel and replacing a few of my more critical cams with another brand, but rtsp-simple-server has changed the game for me. I run frigate on a separate RPi4 and have rtsp-simple-server running on a separate larger, more powerful host. I haven't moved rtsp-simple-server onto the frigate RPi4 yet as its currently using ~40% of one core on an intel 6132 CPU. I'm not sure yet if my RPI4 is going to be capable of running both frigate AND rtsp-simple-server with 10 streams (5640x480 detect streams, and 55MP record streams). My rtsp-simple server has been running now for 13 days without a restart, and frigate almost as long, as I only restarted it recently to upgrade to 0.91. So far, I haven't had a single detect or record stream get stuck to the point that I've had to restart either component, which I was doing every couple of days before. The rtsp-simple-server does restart streams from time to time, but frigate (and Home Assistant) seem to be able to handle the restart MUCH more gracefully than when frigate was talking directly to the cams. Looking forward to what @blakeblackshear has been mentioning around a more robust relay inside Frigate to hopefully eliminate the need for a separate rtsp-simple-server. |
Beta Was this translation helpful? Give feedback.
-
|
I run 4 RLC-410-5MP and 1 RLC-511W, all on the latest firmware available on the reolink download-center. Did you get a "preview" version of the firmware by working with support? I'd be happy to try a preview version with the newer firmware on one of my cams. Have you been able to try the rtsp based streams yet again? ModelRLC-511W ModelRLC-410-5MP |
Beta Was this translation helpful? Give feedback.
-
|
Sorry @rhatguy, forgot I'd offered to try RTSP! I ran it for 24 hours using Frigate's default FFmpeg args. On Frigate startup there were some green camera screens and broken frame errors in the logs, but after after ~10 seconds the streams connected and were stable. The recordings were only OK though with some freezing and a bit of studder. So perhaps some improvements in the 520A camera hardware and/or this firmware, but still not perfect. Instead of playing with FFmpeg I switched to RTMP streams using a previous config and...wow it's so much better! No issues on start-up and (more importantly) smoother recordings. My initial impressions are that, on this firmware, RTMP is as good Yes, Reolink Support sent me this firmware after I logged issues with the RTSP/RTMP streams. They've sent two; the second/current one on 1st Sept which, after checking in with them again last week, is still the latest they're giving out. To confess, I had upgraded but not tested this one, until now! (As I'd got HTTP paths to work well-enough in between.) Here's the 520A beta firmware they sent me - but it may void your warranty etc. and doubt it will work for other models. 0.9.1 RTMP config.yml detect:
width: 896
height: 672
fps: 5
ffmpeg:
hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
input_args: -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -rw_timeout 5000000 -f live_flv
output_args:
record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy # -an
motion:
mask:
- 265,650,265,625,630,625,630,650 # Camera timestamp, bottom centre
cameras:
Driveway:
ffmpeg:
inputs:
- path: rtmp:https://192.168.1.71/bcs/channel0_ext.bcs?channel=0&stream=2&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
roles:
- detect
- path: rtmp:https://192.168.1.71/bcs/channel0_main.bcs?channel=0&stream=0&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
roles:
- record |
Beta Was this translation helpful? Give feedback.
-
|
They have not offered me a beta version for my cams yet and keep saying they'll update in the next version, but no timeline on when that would be. The fact that they've given you a beta with a 2020 version does seem promising though as I believe there is a lot of commonality between their cams from what I've seen. It is interesting that if they were going to go through the trouble to upgrade they would go to 2020.08.12 instead of something newer. Perhaps they were already working on upgrading the library since before our requests. I get worried about things like the below, that were changed in the library AFTER 2020.08.12. 2021.05.17:
|
Beta Was this translation helpful? Give feedback.
-
|
Would you mind sharing your rtsp-simple-server configuration for the reolink cameras? |
Beta Was this translation helpful? Give feedback.
-
|
Reolink needs to fix their codec issues as they used to work fine in the past then it got bad in the last couple of years. I definitely make it a point to tell them anytime I can that people are not buying their gear due to this and I don't recommend them for custom stuff like BI or Frigate. Glad to see them working on things. As I do get it, swapping cameras can be expensive. |
Beta Was this translation helpful? Give feedback.
-
|
I know it's kind of OT, but after two weeks of switching between RTMP and HTTP streams on my 520A's with the 31 Aug beta firmware, both are great: stable streams and fluent recordings. So I'd encourage everyone with Reolink's to contact support to explain what you're seeing and ask if they are working on it - and hopefully they get the message and provide better firmware for all models! (Especially as they still sell them all) Frigate has crashed a few times with Python errors, but without anything to reference I don't know if this is a Frigate thing or a Reolink thing?? I'm still running 0.8.4. These are the relevant configs for reference- 0.8.4 HTTP config
ffmpeg:
hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
input_args: -avoid_negative_ts make_zero -fflags nobuffer+genpts+discardcorrupt -flags low_delay -strict experimental -analyzeduration 1000M -probesize 1000M -rw_timeout 5000000
cameras:
Driveway:
ffmpeg:
inputs:
- path: http:https://192.168.1.71/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
roles:
- detect
- path: http:https://192.168.1.71/flv?port=1935&app=bcs&stream=channel0_main.bcs&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
roles:
- clips
output_args:
clips: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy # -an
width: 896
height: 672
fps: 50.8.4 RTMP config
ffmpeg:
hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
input_args: -fflags nobuffer -flags low_delay -strict experimental -rw_timeout 5000000 -f live_flv
cameras:
Driveway:
ffmpeg:
inputs:
- path: rtmp:https://192.168.1.71/bcs/channel0_ext.bcs?channel=0&stream=2&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
roles:
- detect
- path: rtmp:https://192.168.1.71/bcs/channel0_main.bcs?channel=1&stream=0&user={FRIGATE_USER}&password={FRIGATE_PASSWORD}
roles:
- clips
output_args:
clips: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy # -an
width: 896
height: 672
fps: 5 |
Beta Was this translation helpful? Give feedback.
-
|
With the new 0.11-beta out i'm having huge issues with the rtsp-server... The RTMP streams is non working... |
Beta Was this translation helpful? Give feedback.
-
|
Yes issue confirmed in 0.11 beta 4 Frigate .11 beta 4 isn't able to consume on one or more of my RTSP camera streams from rtsp-simple-server proxy. also in Frigate .11 beta 4, RTMP streaming is partially broken as shown in RTSPtoWeb. I'm using deepch's container, some of the cameras are persistently throwing Rolled back to 0.10 and everything is fine, all cameras feeds load correctly from rtsp-simple-server, and RTMP streaming to RTSPtoWeb is perfect. Sticking with 0.10 for now |
Beta Was this translation helpful? Give feedback.
-
|
It's 2022 and I would like to say that go2rtc has replaced simple-rtsp-server for me, for good! |
Beta Was this translation helpful? Give feedback.
-
|
Me too, although I think it still has its beta tag as once a stream goes down for whatever reason it won't resolve until I restart the container manually |
Beta Was this translation helpful? Give feedback.
-
|
Hm... never happened to me. I think you should open an issue there if there is none already. |
Beta Was this translation helpful? Give feedback.
-
|
I'm going to I'm just collecting some logs. Seems similar issues have been filed and marked as a bug as well |
Beta Was this translation helpful? Give feedback.
-
This has been a blessing for me, my cameras started to act weird because I had too many active RTSP / RTMP clients connected to each camera (like more than 3-4 connections).
I just started using this tool to offload the cameras and it has been working wonders for frame drops and strange artefacts in general.
https://github.com/aler9/rtsp-simple-server
Here is my (simple) yaml config for the tool:
I use this docker creation string:
docker run -d --network=host --name="rtsp-server" -v /usr/share/dockers/rtsp-server/conf.yml:/rtsp-simple-server.yml aler9/rtsp-simple-serverThen from like frigate just use this RTSP URL (for cam1_ch1 in this example)
Hope it can help others :)
Beta Was this translation helpful? Give feedback.
All reactions