

Given that you are the author of the project, I do consider you the higher authority on what it can and cannot do.
But to me, there’s a slight distinction to be made here - Valetudo allows you to directly control the robot from a server running locally on the robot, giving you the option to not interact with a cloud service in order to remotely control the robot vacuum.
This doesn’t immediately imply that the robot is directly prevented from passing information to a cloud service - just that the cloud service does not have to be involved as a command proxy.
The larger feature I was thinking of was not only serving a local server to allow commands to come in directly, but also actively prevent any outgoing connections from the robot vacuum to its manufacturers cloud.
Again, you are the author - you know far better what Valetudo does and does not do, so your information weighs heavier here.
I guess I can also mention that I will be pleasantly surprised if my Chinese robot vacuum has actually been prevented from logging any information back home as a part of me having run Valetudo for the past years.
Longer trips in EVs require one small reframing, at least when compared to how we used to do longer trips before.
In longer trips with an ICE, we would have a meal before the trip, then drive until the destination, and have a meal when arriving.
With an EV, you should plan to have a meal on the road, and charge while you eat.
I’ve had a few experiences with this recently on a 300k trip we do fairly regularly. We do it in an older EV with comparatively poor range, but still we get away with making one stop to eat and charge.