>>106530807
>How's the process and result?
The process is different depending on the robot. A lot of them require a breakout PCB. Which is supposedly easy to make. But I opted for a robot that's still insecure enough that I could connect to it via an exposed USB connector. Though it to took a bit of trial and error since connection was only possible after booting the robot as a startup script would disable the connector. But I got the access evnetually. After that it was rather easy.
>Does it feel janky or lacking?
I've never used the vendor app, so I can't say if it's lacking in comparison. I mean, the vendor supported multiple floors and Valetudo doesn't. But I'm living in a flat with only one floor. And for multiple floors you'd have to carry the robot up- and down the stairs anyway, which is impractical. But it's working just fine.
Keep in mind Valetudo is only a cloud replacement. The firmware is still mostly the same. So the mapping, pathfinding, and everything will still be original.
>How hard is it to reverse?
No idea. If you make a backup of the file system before any changes it should work? But if you don't it might not be possible since you will flash a slightly modified firmware.
>I definitely want to run it but I'm worried about permanently ruining or degrading an expensive appliance.
Yeah, I get that you might be apprehensive. I didn't get a high-end one. It cost around 200 €. But that's still a lot of money thrown out the window if you brick the robot. You should find resources somewhere which features (if avalable) Valetudo supports. Again, obstace avoidance and such should not be affected as it's part of the unchanged firmware.
>Also the main dev fucking hates Reddit so that's always a positive in my books
The main dev seems... difficult. I'll just not engage in their community. The latest release notes just reinforce my beliefs. (In it they even reacted to a singular random 4chan post where someone caimed Valetudo was a backdoor, kek.)