Replying to an earlier post

From what I gather, valetudo sits between the firmware and the cloud, co-opting cloud functionality and serving that from the vacuum. Since nothing is going to the cloud, only the information stored on the robot, or that you’ve stored yourself, can be used against you. So while your vacuum may have a microphone or camera, it shouldn’t be recording what you say or do anywhere. I have yet to start my valetudo journey and have barely started my robot vacuum journey precisely because of scenarios like this.

Replying to an earlier post

The code is open source. Like any open source software, unless it’s been vetted, you’re relying on trust. The premise is that the software is running on the vacuum, so there is no cloud or remote storage. So, just like anything else self-hosted, unless your network is compromised or you configure it to allow it, nothing external is accessing it. If you don’t trust it, vet it. Read the code or check your network logs.

Replying to @⁨VibeSurgeon@piefed.social⁩

Valetudo actively blocks the cloud connections. Also, only firmware versions specifically installed with Valetudo is supported (so no chance an update to the original device firmware happens, and does new things).

I think there’s a very low chance something escapes to the vendor cloud.

None the less, I personally run these on a separate VLAN without internet access.

Replying to @⁨VibeSurgeon@piefed.social⁩

It’s just DNS based, and iirc dont require any major effort other than patching the hosts file. Of course it is possible it is not enough, but I have high confidence in the authors after also having watched various talks at I.e DEFCON, that i would be surprised if they missed the firmware doing other nasty things.

Patching DNS is specifically possible to enable/disable on the firmware build tool: I.e builder.dontvacuum.me/_dreame_r2416.html and the source for that is here github.com/dgiese/…/modifys8image.sh#L169

Replying to an earlier post

Interesting.

This seems to be a model-specific quirk and moreso a side effect of getting Valetudo to work rather than an explicit goal - the same option does not appear in DustBuilder for my model (Roborock S5, still going strong after 941 hours of cleaning time).

I feel like I should check out this DEFCON talk though.

I learned something new today, thank you for that

en