HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Hypfer
Valetudo
JavaScript2019–2026
Hypfer / Valetudo

Valetudo

Cloud replacement for vacuum robots enabling local-only operation

24Distinct people
26Mentions
0Explicit recommenders
10KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Cloud replacement for vacuum robots enabling local-only operation

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year26 dated mentions

Observed mentions: 2019-08-06 06:44:45 UTC to 2026-08-03 11:49:48 UTC.

024682019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC110
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC505
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC321
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC312
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC312
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC211
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC808
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

What Hacker News says

26 sources
A few years back I wanted multifloor on my Valetudo (I had a weird single room which had a step into it) so I did my research and found a whole bunch of toxicity around this feature, mixed in with a bunch of information which mostly answered my questions (it wasn't supported, which of course I was fine with, because it's not my project and I was just grateful for being able to use it). I figured "oh, this would be useful to document", popped onto the Telegram and asked a few clarifying questions, saying I intended to contribute to the docs. First I was accused of not reading the docs (I had, they were confusing and incomplete), then I was accused of trying to sneak multi-floor into the product (..what), then I was accused of being a "well-off boomer who wanted him to do extra work because I wouldn't spring for a third vacuum" (I WASN'T AD
Read the rest
VOCATING FOR MULTI-FLOOR). So I backed off and watched for a bit, then landed up leaving. I have no desire to force change on the man (it's his garden after all); ultimately, GitHub was the wrong destination for his work. It's sort-of like he's opened a workshop in the middle of a bustling market and now he's barking at everyone for interupting him. Recently an error popped up in Home Assistant, so I hazarded a look at the issue tracker to find he'd closed an issue and banned a well-regarded Home Assistant community member for opening it: https://github.com/Hypfer/Valetudo/issues/2310
In Valetudo: Cloud replacement for vacuum robots enabling local-only operation
---- BEGIN EDIT What I meant between the lines is that there are a lot of entitled people everywhere, FOSS users are just an example of it, and one needs to be ready for them whenever setting up for a public-facing endeavor, be it an OSS project or a shop or whatever. Just not let that hit you with low defenses. I've been an OSS project maintainer myself, and realized that one must be ready to deal with people and their behaviors. If I could give an actionable tip to the author and all FOSS maintainers (or soon to be) is to add a README section "This project is a garden", and copy it from Valetudo: https://github.com/Hypfer/Valetudo?tab=readme-ov-file#valetu... ---- END EDIT The author complains about how many (probably entitled) users he started having to support, but deeply inside that was not a problem of being an Open Source maintaine
Read the rest
r as much as a problem of not being prepared to deal with the social side and the normal people's behavior. There's conflict everywhere. If you gave free umbrellas on the street and some of them were broken, for sure part of those people would turn around and request a good one, to which one needs to be prepared to have an answer, it can be "yeah sorry here you are" or "well it was free, be happy you got something at all"
In I've always wanted to be an open-source maintainer- now I regret it
Typo fix: I meant "apps you can'T block from doing this" of course. Addition: I also hate apps and gadgets using "clouds" for jobs which can perfectly be done locally. E.g. I want a vitals tracking device to record my heart and sleep data but I am not buying any because they send that data to their servers, I want them to only send it to my PC where I would do the data science myself (and/or to my smartphone to a purely local app). I would pay a lot (up to e.g. what a beefiest new MacBook costs) for such a device if it were purely local and well-made (wouldn't break soon). I also want a vacuum robot which would build and use my apartment map without sending it to any cloud but there are no such models no matter how much I am willing to pay (I know a solution[1] for vacuum robots - some can be hacked to run the server part on themselves bu
Read the rest
t I don't really have time for this). And there have recently been a leak of pictures made by vacuum robots which proves my paranoia is legitimate. Some genius has even invented a WC which analyzes your pee and stores your hormonal changes log in their cloud which is a great gift to conservative maniacs (I don't mean all conservatives are maniacs, some are awesome, there are many flavours of conservatism) which have just banned abortions and can now subpoena the company to find out you if you have secretly undergone an abortion in another state. Surely insurance companies and banks will also find a way to get your data and make your insurance and loans prohibitively expensive as soon as they find some clues you might have health risks. I am almost sure the problem of privacy negligence, every serious actor spying on people hoarding data, is going to become more and more serious up to a catastrophic point and hope it will get more and more attention soon. I used to be called a paranoid loon by fellow students for covering my laptop camera a decade ago, now almost everybody does this and my new laptops (HP EliteBook and ProBook) even came with built-in curtains on the cams. [1] https://github.com/Hypfer/Valetudo
In Dropbox telemetry can't be disabled
I can't believe I got a Telegram message (by a person unknown to me) trying to confront me about this a day later... Everyone, please calm down, our disagreement was merely about communication style! The presumed "abuse" was posting these 2 screenshots https://github.com/DeutscheKI/dreame-w10-valetudo-fork/blob/... https://github.com/DeutscheKI/dreame-w10-valetudo-fork/blob/... into this https://t.me/+uGuDHt0dNCVmODli telegram group with a polite but lengthy text about which UI changes were made between this fork https://github.com/DeutscheKI/dreame-w10-valetudo-fork and this master branch https://github.com/Hypfer/Valetudo/ and what the motivations for each UI decision were. That Telegram group has 1000+ users. But Hyper found it annoying that I @ tagged him in that message. That's it - no need for pitchforks :) Everyone, please calm dow
Read the rest
n, our disagreement was merely about communication style !!!!!one1111oneone!1!!11!one1!
In Valetudo – Free your vacuum cleaner from the cloud

Showing the 15 most recent of 26 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.