The solution being a huge monthly subscription. Or massive token rates if you’re a big customer

I’m playing Majora’s Mask using 2 Ship 2 Harkinian. It’s quite nice.

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.

I recommend trying out Sunshine/Moonlight for remote play in home. I’m using it to play games on the couch on my TV, streamed from my computer. It’s working very well so far, I’m quite impressed with the technology.

I’m not sure 5-10x bandwidth would necessarily improve on this situation for me, as there’s a high risk of network congestion becoming the bottleneck here. The latencies I’m getting (about 2-3ms I believe) coupled with the quality (1080@60fps, 22mbps) is more than sufficient for my purposes

Fair enough. I searched for pcap files in all the repositories for Hypfer on GitHub but found nothing - do they live somewhere else, or is this just GitHubs search being generally lacking?

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.

To be fair, their sales in Sweden have absolutely collapsed.

As sad as it may seem, Tesla did kind of win that fight in the end. All the union employees were bought out in the end, and the strike was called off. Tesla operates with impunity in Sweden.

Valetudo actively blocks the cloud connections.

Are you sure about that? It’d be a pretty big feature to implement, and surely it would be something that the Valetudo author would mention in the docs for the project.

I’m not talking about the code in Valetudo - I’m talking about the code that’s already running on the robot vacuum before installing Valetudo. It remains on the device after you install Valetudo.

Basically, any concerns about privacy stemming from the original software on the robot vacuum do not get eliminated by installing Valetudo

I’m not convinced this actually holds. To be able to use Valetudo at all, you at minimum do need to connect it to a wifi network which you are connected to as well on some kind of device. Unless you happen to be setting up some kind of firewalling on the robot vacuum, it is at that point free to start logging whatever information it deems appropriate.

Valetudo runs alongside the existing software on the robot vacuum though, does it not?