DAdarkwater·Oct 26, 2021
We are probably talking about the same feature. What I meant was this kind of page https://github.com/home-assistant/core/issues/new/choose
In GitHub stale bot considered harmfulhome-assistant
core
Python2014–2026
home-assistant / core
core
:house_with_garden: Open source home automation that puts local control and privacy first.
45Distinct people
55Mentions
0Explicit recommenders
92.3KGitHub stars
What to know before exploring
What it is
:house_with_garden: Open source home automation that puts local control and privacy first.
GitHub
Where it is used
- Marine Assistant — Marine Assistant uses Home Assistant as the core software platform powering its aquarium controller. It relies on Home Assistant to provide the automation and update capabilities for the product. Source
- GrowRig — GrowRig uses Home Assistant as the foundation for its local-first grow monitoring and automation system. It builds its ecosystem on Home Assistant to power device integration and control. Source
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
- home-assistant/frontend · linked in 3 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:03:30 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 year55 dated mentions
Observed mentions: 2014-11-03 05:04:34 UTC to 2026-06-14 00:36:45 UTC.
* 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
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 7 | 2 | 5 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 7 | 1 | 6 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 4 | 1 | 3 |
What Hacker News says
10 sourcesHome-assistant/core: open-source home automation
1 points · Open discussionI was interested and also searched, here are the results:
https://github.com/home-assistant/core/issues?q=is%3Aissue+n...
https://community.home-assistant.io/search?q=nixos
I sampled a few of the closed issues and it cemented my decision to not use Home-Assistant for my Zigbee setup at home because of the recent behavior of frenck and other Home-Assistant top tier persons.
In “Please don't add any of my stuff to this project”You can’t have your cake and eat it too.
There are also a lot of contributors who might have an opinion about closing the license: https://github.com/home-assistant/core/graphs/contributors
In “Please don't add any of my stuff to this project”> a traditionally distro wouldn't even bother packaging any of this stuff or engage at all.
unfortunately the library author made a PR to Home Assistant, a program that is packaged in many distro; all those distro will add his package. see
https://github.com/home-assistant/core/pull/51645
In “Please don't add any of my stuff to this project”> You're entitled to nothing when authors write FOSS. They provide it as-is. Take it or leave it. No one is obligated to take support harassment.
the author of the lib literally pushed it to Home Assistant, so he gave it to a relatively famous project that is present in a lot of distro and Snapstore. Pushing to such project is a guarantee that your code will be repackaged.
He could say it was a misunderstanding and require to be remove from HA, but to go to a project that uses the project that you PR your code into? eh. We have licensing for this reason and I am quite sure if frenck had choose the correct license/limitation from the beginning, it would have never been accepted into HA and this whole problem would have been avoided
> Tons of FOSS projects do not support alternative distributions. In fact, implicitly, virtually no one doe
Read the rest
s. Most authors publish software with the expectation you'll use their distribution channels.
I don't think this is true, and the fact that already author's libs had been already packaged in Gentoo, Fedora and possibly more distro (and he said he will request to remove them) show how quickly alternative and well used channel can and will pick them up if not specified in your license. Especially if the project you are contributing is ALREADY packaged in different disto.
source: https://github.com/home-assistant/core/pull/51645
It looks like the bigger question here is this:
Is it the official policy of the home-assistant project that their software should not be packaged by NixOS?
frenck is the fourth most active contributor to home-assistant - and it uses quite a few libraries he has authored: https://github.com/home-assistant/core/graphs/contributors
If frenck is saying NixOS can't package his libraries, he's actually enforcing that NixOS cannot package home-assistant. Is this direction agreed by the other maintainers of that project?
In “Please don't add any of my stuff to this project”> It sounds like Home Assistant by default pulls the latest version of the package from PyPI at runtime and loads it dynamically.
Package versions are recorded in component manifests so it will not default to the latest version, someone has to make a code change and PR on homeassistant to update the version. And they are collected in a requirements file for every HA release[0]. So it should not be hard to automate that if needed whenever the HA Nix package gets updated to ensure the latest used version of ambee package is included.
[0] https://github.com/home-assistant/core/blob/dev/requirements...
In “Please don't add any of my stuff to this project”This is not true. Home-assistant does not pull the latest version of packages (for integrations) from pypi. They are tracked in manifest files: https://github.com/home-assistant/core/blob/ae28e4934f6d1cdb...
In “Please don't add any of my stuff to this project”What's worse is this frenk guy seems to be the reason his packages are being added to nixpkgs
He added the dependency himself https://github.com/home-assistant/core/pull/51645
Nobody gives a shit about frenk or his code directly here - they want to use Home Assistant. But now that frenk added his code as a dependency, he has the right to transitively make Home Assistant un-packagable on NixOS?
EDIT: On top of that, the way NixOS works is philosophically in-line with Home Assistant
> Open source home automation that puts local control and privacy first
Pinning every Python dependency instead of fetching HEAD is how you get local control and security!
In “Please don't add any of my stuff to this project”