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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM 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

8 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

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.