Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've been eyeing Valetudo for a while. I think it's a shame that it doesn't and (according to the author) never will support multiple maps. I don't want to have to buy a separate robot for each floor when I can easily carry it to the next floor when it's done.


Yeah the author is very set on his ways. I was thinking about contributing but he doesn't want any help. I read CONTRIBUTING.md and I kind of get it. Respect.


Mad respect indeed. I am not in the target audience for this project, but I just read through the contributing.md page. It is very well written, everything he says makes sense

If there's an issue that affects 3% of users doing something arcane which can be fixed by either a large chunk of code or just by not doing that arcane thing, the latter will be the preferred solution.


Yeah I really didn't mean it as criticism but rather as a reason why I'm in 2 minds about adopting it.


Some robots support restoring map snapshots. I wonder what's stopping people from using this as a multi floor implementation?


I use a fork [1] of Valetudo and it lets me do just this. I save one map per floor, then restore when carrying it between floors. One floor gets cleaned much more often, but so far I have preferred this over buying two robots.

[1] https://github.com/rand256/valetudo


Currently I can just get the robot from one floor to the next and press start. It takes a few seconds to find its bearings and switch maps, then goes on his merry way.

Having to restore a snapshot each time I move floors is a lot more friction.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: