Valetudo: Open-source cloud replacement for vacuum robots
valetudo.cloud
valetudo.cloud
Link to the guide: https://flodan.github.io/blog/articles/roborock-valetudo-mac...
Maybe it is helpful to someone
No, wait, uh--
The non-cloud is inconvenient, not because of not having cloud management, but due to the fact that it doesn't have any networking capabilities at all. I still keep it around and trigger manually. Its LIDAR died, but I just had to open and clean it to restore operation. One battery changed. Still going.
The other one, despite being cloud connected, can at least be managed by Home Assistant(although the initial integration is a pain). Which means I can do things like run it when there's no-one at home (or noone downstairs).
I also have a Braava. Which, despite connecting to iRobot's cloud, also has local control. It works even better than the D3.
They are all outclassed by newer robots. If I had the time I'd replace the onboard electronics entirely.
Maybe yet another device for Pine64 to consider, maybe.
https://github.com/awesome-vacuum/awesome-vacuum https://librervac.org/
Dyson make a (super expensive) vacuum one that actually vacuums, with a brush bar and everything. There are probably others now.
But in Fridays when I get home I give everything a once over with the plug in vac and the amount of dust and dirt it captures at first surprised me. The robo vac's suction just can't compete
But I still don't mind it as it makes keeping the floors in general cleaner easier - but if I had to do it again today I wouldn't buy the robo vac.
Our robot vac gets ran daily, and each day the bin is almost completely filled with dog hair. Then periodically we use the upright, and it still always manages to pull up lots of debris from the carpets.
So, to me, the house is actually cleaner, because there is no way I would vacuum every day.
And even if the suction isn't up to a regular one's standard, I'm still quite amazed by how much dust it gathers every time. And I don't have pets, and live in a relatively small apartment.
They never did. Even the best vacuum plugged into your standard 120v receptacle will have trouble removing all the crap that's accumulated in the average carpet. A small, battery powered vacuum can't either.
They do help in reducing the amount of stuff that accumulates in between hand vacuums. Back when I had carpets, because of my wife's allergies, I'd vacuum with the "old fashioned" vacuum every weekend. A Neato would run every day (and would have to be emptied every couple of days, it picked so much stuff). Then I'd actually _wash_ the carpets every month. Every single time, even with all that, the water would come out black. This helped, but ultimately we had to move. You can never really clean carpets.
If anyone in your family has allergies, get rid of carpets if you can. Just because they may not be displaying symptoms that are really obvious right now, doesn't mean they aren't having a constant allergic response.
I try to do the bottom floor every 3 months and the upper floor every 6 months. If I do it more frequently I start getting clean water out of the machine, especially in the upper floor.
That said, we don't use shoes inside our home. I think that makes a great difference.
---
The Apache-2.0 license is a very permissive license and a lot of work is being shared for free here, so I trust people to not take advantage of that and sell Valetudo; especially not as their own work. Please don’t disappoint me. Thank you.
---
If you want to build a community of contributors and deter freeloaders - that's exactly what GPL is for.
Apache-2.0 is designed to allow people to proprietarize Valetudo and use it in closed-source devices.
At the time, the idea behind that was that _maybe_ this would make the vendor pick it up and provide a cloud-free stock experience. In that case, it would've been fine-ish if they'd monetize the work as it would still be very much beneficial to everyone. That sentence in the docs is not directed at those. You can't reason with corporations.
Instead it's directed at that crafty kind of individual that would sell pre-rooted robots just because there's money to be made. Those people that purposefully refuse to share knowledge so that they can monetize it. I am aware that it won't stop them either, but at least there's an attempt I guess.
Given what I've learned in the process, I can't say for certain that I'd pick the Apache-2.0 license again but it is like that now. As far as I'm aware, re-licensing would require asking every single contributor for their consent. I'm not too fond of doing that tbh.
And you know what? They did it anyway. Several times people shipped our software, changed just enough that it wasn't blindingly obvious at a glance, but of course we figured it out and lots of lying ensued. There is no point whatsoever in trying to be nice wrt proprietary hardware, hardline all the way.
FYI the guy running the VLC project (Jean-Baptiste Kempf) once changed the license for it, 10 years after the project started, with tons of contributors to contact etc. Some patches had to be rewritten, but most authors just agreed. Took him years, but he totally did it, and VLC got the new license. I don't know if I'd recommend it, or have the stomach to do that myself, but the guy is a personal hero of mine because of it. You could be, too! :-)
> Those people that purposefully refuse to share knowledge so that they can monetize it
For both cases, again that's exactly what GPL is for.
> As far as I'm aware, re-licensing would require asking every single contributor for their consent
First, you can start contributing all new code under GPLv3 while keeping a copy of the Apache-2.0 license in the repo and a notice that inform users that large part of the codebase was contributed under Apache-2.
According to https://www.apache.org/licenses/LICENSE-2.0 redistribution paragraph and https://www.apache.org/licenses/GPL-compatibility.html
Secondly, you can also ask the few major contributors if they accept switching to GPL. Those who contributed tiny changes e.g. 1-line bugfixes in the past do not have enough contribution material to have a legally standing copyright claim.
Since when do individuals have an obligation to share knowledge for free?
Of course there may be other and actual valid reasons for why someone might not share all information. That's not what I'm talking about in the previous comment though.
But I would have loved to be able to simply buy one pre-rooted AND pay $50-$100 extra for it. I honestly think there is a market for "same robot as your neighbour, but not spying on you!" I'd buy two more for my parents.
But I'd want it to be clear about what they are doing. Like https://www.flashrouters.com/
* "Smart" homes
* Electric Vehicles
* "Power Walls"
And everything else tied to an internet connection
I went through them all and it seems the only one that's fully recommended is the Dreame Tech Z10 Pro. I actually bought it too the other day with the intention of installing this on it, so now waiting for delivery.
The rooting process seems relatively involved though, so we'll see how it goes.
[0] https://valetudo.cloud/pages/general/supported-robots.html#d...
> This was patched in many new firmwares. Do NOT update your robot via the Mi Home app if you want to root.
Which sounds ominous if you're buying the robot new today. How do you feel about posting back here, or emailing me, or whatever, after you give it a shot? That bot plus open source firmware looks absolutely ideal.
That doesn't mean that those robots aren't rootable though. We do have more rooting methods, however those aren't public currently. It is TBD how we will move on from here.
I'm still renting so I've not really bothered with any thermostat yet. I used to have a Nest Learning thermostat when I was living in a place where they allowed me to install it, but I gave that away when I moved.
Haven't bothered with thermostats since, and likely won't until I've moved into my own place, but I'm hoping to find a thermostat that can run without cloud or at least, with an OSS cloud replacement.
That said, once it worked, it's been working well since then! My only note is that you do need to make sure to keep the sensors clean or the map can "drift" and it'll stop understanding where it is. For me, to fix that, I had to reset the map before it would work reliably again.
I have a relatively new Roomba (one with the camera), and I hate it. Sure it can be more efficient than the old models without a camera, it insists on building an map of the house, which takes forever, constantly needs restarted because it literally can't find rooms, or just fails to update the maps, requiring you to start all over again. It doesn't even have those IR walls, that the old ones had.
IF there was a better mapping system, that would be helpful.
After like 10 years of trying these things, I've decided they're mostly a gimmick, but damn it, I want them to work.
Scrolling down
Building the firmware
I think the point they're making is that this isn't a full fledged vacuum robot firmware, it's basically the factory firmware patched with a Mi Home cloud emulator/replacement that runs as a daemon on the vacuum.
So while you build a firmware image, it's not a fully custom, from-scratch implementation of vacuum functionality, it's just the factory firmware image with the cloud parts replaced.
It's amazing stuff like this gets built, and even more amazing it is free.
You'll probably have to do the more involved shell replacement to get root and flash the firmware.
0: https://dontvacuum.me/robotinfo/detail_roborock.vacuum.a15_0...
The only thing I need to do regularly is to fill water tank in Braava and wash the moping pad, and every once a while replace the bag in Roomba self-emptying base.
One thing to note is that this requires fairly high-end models, at least in case of Roomba. I used some e-series model before and I wasn't happy. Now I have i7 series and it's a big difference (primarily in self-learning and navigation)
I own an L10 and am very happily running valetudo on it. Someone should make a business out of selling them pre-flashed with valetudo for a less technical audience…
Please don't. Attracting a less technical audience to the project would be immensely harmful to it. It is already quite difficult to deal with issues that technical people might have. You simply do not want everyone to use your open source project. There is also no point in doing so. Why would one want to make their own life harder?
From Why Valetudo[0]:
First of all, please do not try to convince people to use Valetudo.
We all know how terribly it usually turns out when people try to
convince their friends to use linux on their desktop. Using Valetudo
only makes sense if you understand its goals and feel like they are
important to you. Everything else will fail.
It is perfectly fine to continue using the cloud if you don’t really
care about its downsides. Do not flame people for doing that. You
can be a bit snarky about downtimes, lag and other cloud shenanigans
though :)
[0] https://valetudo.cloud/pages/general/why-valetudo.htmlTurns out Valetudo is the Roman name of the Greek goddess of cleanliness, Hygieia (which is where we get the word hygiene from)
Alternatively: https://sepulchritude.tumblr.com/post/152864353958/on-the-to...