bug: Video Streams's Redirect source not working in 1.5.0-beta8?

[rmackay9]

Bug description

I can't seem to get the Video Streams in 1.5.0-beta8 to work. I'm unsure if I've messed up some configuration or if the latest beta has broken it but I'm sure I had it working about a month ago when I wrote this AP blog post (search for "Setup Cockpit Video Streaming")

Now the Video Manager always says "Not running" and the little thumbnail is not appearing

This also doesn't work on an RPI4 but the behaviour is different. What happens is I get a timeout message 1000ms when I try to setup the redirect source so I can never actually create it.

Steps to reproduce

Install BlueOS 1.5.0-beta8 on an RPI5 as described in this AP blog post
Connect a Siyi A8 to the RPI5 via Ethernet
Set the RPI5's IP address to 192.168.144.20
Open BlueOS's Video Streams:
- select, “ADD STREAM”
- Stream nickname: “Siyi A8”
- Select “RTSP” from drop-down on bottom left
- Stream endpoint: rtsp://192.168.144.25:8554/main.264
- Press Create
after a few seconds the live video thumbnail should be displayed (but it doesn't)

Primary pain point(s)

Unable to view live video from an IP camera in cockpit

Prerequisites

• I have checked to make sure that a similar request has not already been filed or fixed.

[patrickelectric]

can you confirm this @joaoantoniocardoso ?

[joaoantoniocardoso]

The last change related to Redirect was to add the thumbnails (mavlink-camera-manager t3.19.2), which arrived at BlueOS master from this PR from May, which corresponds to BlueOS 1.5.0-beta.2.

Another change that can relate is the change in the core version (from this PR on June 5), which updates GStreamer version from 1.24.8 to 1.26.2. This change arrived at BlueOS 1.5.0-beta.6.

My RTSP camera still work with Redirect on BlueOS 1.5.0-beta8:

---

@rmackay9 could you:

1. wait until the Errors: appear on the page and paste it here? Example:

2. test it with 1.5.0-beta.5 to see if that works?

Thanks

[rmackay9]

Hi @joaoantoniocardoso,

BlueOS 1.5.0-beta5 works but -beta8 does not. At least for me when using an XFRobot Z-1 Mini and BlueOS running on an RPI5. Below is what I see using -beta5

On -beta8 it never produces an error message. I left it for many minutes but no error appeared.

On an RPI4 running -beta8 with a different camera (the Siyi A8) it also doesn't work (at least the thumbnail isn't displayed) and no error message is shown

BTW, when testing with the RPI4 I see that a new page is visible called something like "RTSP Relay" but this doesn't appear on an RPI5. Maybe it hasn't been built for linux/arm64/v8? In any case, the RTSP Relay's "Web RTC Viewer" can display the video from the RPI4+Siyi A8

Thanks for your help!

[joaoantoniocardoso]

That's intriguing... In this case, I'll need the mavlink-camera-manager logs from when it's failing on beta.8.

Yeah, the "RTSP Relay" is from an extension, I'll check how it's receiving the video. And yes, it's probably not deployed for arm64 (yet).

Thanks

[rmackay9]

@joaoantoniocardoso,

And of course, now it starts working, at least partially

This is still an RPI5 running BlueOS-1.5.0-beta8 and the thumbnail is appearing now although I still can't make the video appear in cockpit. The VideoPlayer is just a black square. The only difference that I'm aware of is my precision landing extension which has been released now and is installed but not running. Previously though it wasn't even installed.

For what it's worth, here's the log https://www.dropbox.com/scl/fi/vcpgqbio9clilkx92fh3i/mavlink-camera-manager.2025-07-10-11.log?rlkey=m1443rdd3kwivy1f063sw18v2&dl=0

[joaoantoniocardoso]

Some observations from reading the logs:

• From 02:00 to 11:22, the MCM is struggling to have a stable connection to the camera via RTSP -- it is trying to connect to `rtsp://192.168.144.108", no port/path specified, which looks odd to me, but if it's getting frames for the thumbnail, it's probably correct.

• After 11:22, it was, apparently, able to establish a connection, but it seems to be stuttering 5 times per second.

• At 11:24 you've opened the video page and some thumbnails/snapshots are being generated, which surprisingly makes the stuttering stop for a minute or so.

• At 11:25 the stuttering returns, and some WebRTC client starts talking

• At 11:26 there's some WebRTC negotiation, but it fails to establish aa connection (WebRTCBin failed to negotiate under 10 seconds. Session will be killed immediatly to save resources). This usually happens when (1) the browser doesn't support the video format, or (2) the client is denying all offered routes (192.168.144.20, 192.168.87.37, 192.168.42.1, 10.147.17.60 for both UDP and TCP). Cockpit has a configuration for that on the Video Streams Configuration page.

Given that, I'd ask you to check whether you have your vehicle's ethernet interface IP allowed on the Cockpit allowed WebRTC remote IP addresses list.

Thanks

[rmackay9]

I think this issue is really all about bandwidth because I've gotten it working more reliably by reducing the XFRobot's rtsp stream resolution to 720p (was 1080p). It's still not reliable enough over LTE which means I think we need a way to reduce the resolution or frame rate on the RPI4/RPI5 but that's an enhancement request.

Thanks for the input on this, I'll close this now

New issue: #3482