ES-Alexander

> what is the current status of this PR ? Should we merge it ? @patrickelectric it wouldn't _hurt_ to merge it as-is, but I think it makes more sense...

Vehicle setup overview docs may need an updated screenshot.

1. From some digging after a discussion with @Williangalvani, I think [this](https://github.com/bluerobotics/BlueOS/blob/master/core/frontend/src/components/vehiclesetup/overview/OnboardSensors.vue#L250-L255) should just be an `if-else`, so the "not water sensor" doesn't get overwritten with the water sensor value...

#2560 fixes most of this, and ArduSub-4.5 (currently beta) fixes the sensor name issue (correctly displays MS5837 for the Bar30, and MS5611 for the internal/aerial one).

This is kind of handled by the disk usage indicator for running extensions, but it would be preferable if we could also display things like the space taken up by...

Adding to this that it would also be useful to show the size of extensions that have not yet been installed.

From some more looking at the logs and the code, it seems the Cerulean DVL has slightly malformed messages compared to what's being looked for, so it's currently just causing...

Where relevant, we could also consider adding resource usage indicators (e.g. to show CPU and memory usage of elements, and potentially also to show network bandwidth consumption of outputs).

This could also be used for modification of the standard gstreamer pipeline, which would be useful for cases like [this one](https://discuss.bluerobotics.com/t/activating-raspberry-pi-camera-module-3-in-blueos-via-docker-on-raspberry-pi-5/16423/9).

Since we have the "loading external service" animation thing now, maybe that could be used while the page is first loading?