[defanor]

There is also the "No multi-floor/multi-map support" point. Apparently it is treated less seriously than others there, and omitted here, but seemed particularly unfortunate to me: having per-floor dry cleaning robots seems wasteful, while in that text it is assumed that they should be fully autonomous (no manual transfer of those between floors), and likely with large and frequently used docking stations for wet cleaning.

(FWIW, I do not use multi-floor robots myself, only using an old random-walking Roomba in a single-floor setting, but considering getting another robotic cleaner for a two-floor house, where it does seem reasonable to manually move it between floors, as I would move any other cleaning tools.)

[lucb1e]

Yes, I didn't know what to make of it since it said that it's a legacy entry and that people only ever want it because it's listed on this page

Not sure what one needs a map for though, I know what my floors look like and the only thing I want from a future robot is that it drives around cables instead of suffocating on it

[ericpauley]

This was the example that really drove home all the other points for me. Not only is Valetudo opinionated software, but you'll be accused of having "fictional budget concerns" for wanting a very reasonable feature.

I occasionally take my Roborock upstairs on weekends for a vacuum. Turns out it will also do a basic mop run with the water in the tank. Takes me 5 minutes of setup/tear down to get an extra floor for no extra cost. It would take me more time to babysit the extra base cleaning task of a second mop, so this saves me time and money.

To me, this demonstrates that Valetudo is intended to be hobby pursuit of maximal automation/freedom at all costs, resulting in a system that has worse features and takes more work than the base software. I applaud the creator for being so clear in this mission to the point of explicitly encouraging me not to use it.