Cloud replacement for vacuum robots enabling local-only operation
View the Project on GitHub Hypfer/Valetudo
Newcomer Guide Why Valetudo? Why not Valetudo? Getting Started Supported Robots Rooting Essentials Buying Supported Robots
Implementation Overview Capabilities Overview Upgrading Firmware Updates
Valetudo Companion (Android) Valetudo Tray Companion Valeronoi Lovelace Valetudo Map Card I Can't Believe It's Not Valetudo node-red-contrib-valetudo Fun & Games Other Noteworthy Projects
MQTT Home Assistant Node-RED openHAB
FAQ Style Guide Troubleshooting
Valetudo is the roman name for the greek goddess Hygieia, which is the goddess of health, cleanliness and hygiene.
Yes!
That’s the whole idea behind it.
In Valetudo, there are only two things that connect to the internet:
Additionally, some robot firmwares include connectivity checks that:
8.8.8.8
) <- You can block that but that’s up to you.Firmware ML/AI features such as obstacle avoidance based on AI image recognition will continue to function offline, as such things can’t be cloud based for latency-reasons alone.
The SoCs on the supported robots are more than fast enough to handle such workloads. No cloud required.
No.
Think about it. Why would we go through all this rooting trouble if there was an easier way?
Especially since that easier way is so trivial, everyone has already come up with it 20s after learning about Valetudo existing.
No, life isn’t that simple, sorry. Or not sorry, actually, because that is a good thing. IoT should be secure for the regular user.
It would be terrible if you could easily take over a whole fleet of expensive vacuum robots in peoples home networks just by messing with DNS.
For us as people who want to own our devices it’s bad, yes, but insecure IoT devices aren’t the solution to that.
They being hackable just by-accident happens to be a super inefficient band-aid “solution” with lots of collateral damage.
e.g. regarding End-User privacy, security, DDoS Botnets etc.
The proper solution is strong legislation enforcing product usage either without the cloud or with your own cloud in a controlled fashion right out of the box. The vendor cloud can still be an option, but it must not be the only way to use an IoT Device.
Sure! We’d be glad to look into your case. To help us help you, we only require you to buy and permanently donate 3 units of the robot in question to us. (2 for HW Hacking, 1 for SW Hacking)
Though we can’t promise to be successful, we strive to achieve a success rate of at least 3%.
As with any R&D project though, we unfortunately can’t offer any refunds if we fail to get the robot support.
We thank you for your understanding and are looking forward to doing business with you!
Because I don’t want the app to be a paid yearly subscription supporting only some small garage startups in Cupertino and not the actual project.
You might not be aware of this, but since there’s no sideloading and no alternative stores on iDevices, the only way to get your software on there is through the official distribution channel of the vendor which comes with a yearly 80€ fee.
Furthermore, development for iApps can only be done on a Mac which needs to be bought and also won’t last forever. Assuming a reasonable 5 years of lifetime for the hardware, picking the cheapest Mac mini and a 2-gen-behind base-spec iPhone, at the time of writing, I end up with this calculation for 5 years:
Sum: 1828€
This money needs to be earned somehow, and it needs to be earned yearly, which forces you to find some way of generating recurring revenue - something I do not want to do with this project.
Fine. If you insist, we can go along with that:
Excluding any compensation for my time spent on actually building and supporting that app, by dividing that number by 5, you end up with 365.50€. 365.50€ that would need to be donated or paid by users every year just so that I don’t lose money out of my own pocket on paying the cloud landlord for wanting to exist.
But it gets worse, because the platform also takes a 15% (previously 30%) fee on everything sold there, meaning that people would actually have to buy apps/subscriptions for 420.44€ every year; all of it ending up at the platform and nothing benefiting the actual project people would’ve wanted to support.
Imagine donating 10€ to a FOSS project you really liked and wanted to support only to then a little while later discover that you’ve actually been donating to billion-dollar big tech destroyers of worlds all along.
Now imagine 40+ people living through that every year for 5 years.
And after those 5 years, the App just vanishes from the storefront with no way of installing it anymore.
Sounds quite crushing, doesn’t it?
No! You don’t.
The app is just being used for robot discovery on your network and can be completely replaced by
OR
All the android one does is discover Valetudo instances and then open a browser.
You already have a browser on your iDevice.
…though, one that is frequently broken with no way for you to switch to a different browser, because on iDevices, every browser is Safari as required by the ToS of their digital storefront.
There is no Blink or Gecko. There’s only Apples special blend of WebKit including all its bugs and quirks.
But this is a different rant.
On Android, it’s different:
With effectively no barrier of entry, you can just start hacking something together without first having to worry about some kind of business plan ensuring recurring revenue. This allows for creation of tools that on other platforms would never exist because you just can’t (or don’t want to) monetize them.
While Google - as all big tech - is of course following the exact same playbook, slowly chipping away at all that, for now at least, it’s way less bad and thus the best and only thing we have. :(
Just for reference, I’m not interested in any special Apple sponsorships or donations of iHardware.
If you even think about doing that, you’ve completely missed the point of the previous wall of text.
It’s not about money. It’s about not enabling these business practices.
Further reading:
Cloud replacement for vacuum robots enabling local-only operation
View the Project on GitHub Hypfer/Valetudo
Newcomer Guide Why Valetudo? Why not Valetudo? Getting Started Supported Robots Rooting Essentials Buying Supported Robots
Implementation Overview Capabilities Overview Upgrading Firmware Updates
Valetudo Companion (Android) Valetudo Tray Companion Valeronoi Lovelace Valetudo Map Card I Can't Believe It's Not Valetudo node-red-contrib-valetudo Fun & Games Other Noteworthy Projects
MQTT Home Assistant Node-RED openHAB
FAQ Style Guide Troubleshooting