Hi @mark, I think this question would be better in fresh topic since this topic is marked as solved (maybe @EliotBR could move it?), but anyways, here is the answer:
BlueOS is not yet capable of disabling automatic mavlink stream advertising (tracked here), however, I can offer two advanced ideas here:
-
Instead of dealing with mavlink advertising by yourself, you can make use of mavlink-camera-manager’s Redirect streams, which is a way to advertise streams to mavlink that weren’t managed by mavlink-camera-manager itself. We usually use this when we want to integrate an external IP camera or a custom pipeline.
-
You can also use the same mavlink-camera-manager’s Redirect streams to act as a placeholder to avoid having zero configured streams at the startup, which is the condition that triggers the automatic camera enumeration.
Soon we’ll be adding redirect streams management to our BlueOS UI (tracked here), but for now, you’d have to access the mavlink-camera-manager dev UI (http://blueos.local:6020) to create them:
Note that the configured endpoint for a Redirect Stream is exactly what mavlink-camera-manager will advertise, no IP translation or data processing will happen, meaning that localhost would be the device QGC is running on, not the raspberry.
Let me know if any of these options can be used in your case, otherwise, I could reply here when we implement the ability to disable the automatic mavlink stream advertising.
Thanks