HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
home-assistant
core
Python2014–2026
home-assistant / core

core

:house_with_garden: Open source home automation that puts local control and privacy first.

Security & PrivacyHardware & EmbeddedRobotics & IoTAutomation & Workflows
Explore on GitHubRead Hacker News discussions
45Distinct people
55Mentions
0Explicit recommenders
92.3KGitHub stars
REPOSITORY AT A GLANCE

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

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 year55 dated mentions

Observed mentions: 2014-11-03 05:04:34 UTC to 2026-06-14 00:36:45 UTC.

02468102014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 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
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC110
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC817
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC725
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1019
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 UTC606
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC312
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC716
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC413

What Hacker News says

55 sources
nijave·Jun 10, 2026
Do you have examples of issues? OCI is tarball of dependencies that doesn't fight with the OS userland. Why do you need to write code to insulate Python in containers? At the simplest level, you can add the flags to the container runtime (network host, host ipc, host process namespace) to turn off all the namespacing besides filesystem and the Python container runs just like a non containerized process. An extreme example https://github.com/home-assistant/docker-base (Debian, Ubuntu, Alpine base images with Python for arm64 and amd64) & https://github.com/home-assistant/core/blob/dev/Dockerfile (Python app built on those with >1000 deps) And even there most of the custom code is just running a ton of combinations of inputs against docker build. The OCI container gets rid of "wide range of scenarios" for you standardizing the runtime envir
Read the rest
onment
In Are you expected to run five Python type-checkers now?
denismi·Jul 21, 2025
> The latest Daikin indoor units have a built-in WiFi module which only allows control through their cloud infrastructure. Which ones? My Alira X from a couple of years ago is currently talking directly to Home Assistant over WiFi. For a year or so I've been unable to update firmware without losing the functionality, but it looks like the community has a fix pending verification: https://github.com/home-assistant/core/issues/99251 I have another old unit that I'll have to replace eventually, and ideally it could be Daikin and would work natively without involving external hardware.
In ESP32-Faikin: ESP32 based module to control Daikin aircon units
kristofferR·Feb 14, 2025
It's like the recent Samsung phones, functionality fees are waived until 2026. No word about the price yet. [1] Samsung should be avoided like the plague anyway, I've never seen such a malicious and hostile company! On Dec 13 they silently announced that they were gonna break Samsung APIs on Dec 30 [2]. Yeah, they gave devs the "You gotta spend your holidays fixing our mess, otherwise your app will break". Due to that Samsung is still broken in Home Assistant and other API integrations. [3] [1] https://youtu.be/a4NJNdHqs_I?t=418 [2] https://community.smartthings.com/t/changes-to-personal-acce... [3] https://github.com/home-assistant/core/issues/133623
In Zed now predicts your next edit with Zeta, our new open model
farawayea·Jan 25, 2025
https://github.com/home-assistant/core/blob/dev/requirements... lists all the direct dependencies installed in the container. It's enough for just a single direct or indirect dependency to be compromised to have a botnet or turn it into something used for surveillance against the users. Preventing it from exfiltrating data by isolating it from the network with Internet access is the only option if you want to run it. This requires local only devices. Accessing it through the web UI or through the mobile app will still load icons from https://brands.home-assistant.io. The details are in this ticket https://github.com/home-assistant/frontend/issues/18549
In How I Use Home Assistant in 2025
farawayea·Jan 25, 2025
I've been using Home Assistant for about three years. I was very glad it exists. I wanted to make the most out of it. It has numerous problems and regressions are very frequent. The disappointment lies in it not being as it's described and in the fact that its development process doesn't appear to improve, nor does its overall quality appear to improve. It still gains new features in spite of all of these issues. Home Assistant's dashboards and UI have regressions in every single release. Many such regressions aren't fixed quickly or remain that way permanently. Github issues get closed by the bot. New features ship in every release without fixing these bugs. This gave me the impression that the developers employed by Nabu Casa have very little time to focus on bugs and that there's no pre-release QA. The graphs and their history had plen
Read the rest
ty of bugs in the 2025.1 release. Are there plans to improve the development process to improve quality? Home Assistant is described on its home page as "Open source home automation that puts local control and privacy first.". A Home Assistant OS download is useless offline and without the Nabu Casa infrastructure. A download of a Home Assistant OS image obtained today would be completely useless in 5 years for now. These are completely useless if Nabu Casa's infrastructure goes away for any reason. Do you have plans to address this? Another point related to Home Assistant being local and making privacy a priority, Home Assistant downloads all icons from [1]. The GitHub issue [2] has been open for a while without any involvement from the developers. The Home Assistant container image doesn't include all the assets required for it to provide a Home Assistant deployment in a container. Is this something you plan to address or should it be handled in a fork of Home Assistant meant to be run completely locally? Home Assistant bundles numerous dependencies [3]. The Home Assistant container bundles and has all of these available. Are there any plans to let users disable all cloud only integrations? What's done to assess the security of these numerous packages? This matters because people allow Home Assistant to access their indoor cameras, door locks and other potentially sensitive devices. Some malicious code run from one compromised dependency's __init__.py could have serious consequences. Home Assistant is a Python monolith. Adding something as simple as a shell command to my configuration requires a restart of Home Assistant. Are there any plans to split this up or to improve the architecture to not have such issues anymore? The energy dashboard is extremely limited. Are there plans to make this more flexible? Why are you forcing people to use encryption since 2025.1? I was including these backups in my encrypted backups anyway. The voice functionality for Home Assistant and voice PE require a cloud service or a local machine with a GPU for good performance. Are there any plans to address this to provide higher performance local voice control? The old Rhasspy (the version released before Nabu Casa hired its developer) seemed to work a lot better with defined sentences and was faster. I've seen Home Assistant become faster over the last three years. My YAML had to be updated a few times. New features have been introduced to the dashboards. Old issues and limitations are still there. The dashboards gain new features while the number of bugs and regressions also increases. The custom resources for custom cards don't always load in the mobile app. The UI still loads all the icons from the Nabu Casa icons site [1]. Home Assistant frequently stops updating my location (home vs away) and requires deletion of the device from HA to get it to work again. Entities don't update in the dashboard sometimes. Home Assistant is described as being an open source project which has been donated or moved to the Open Home Foundation. Why does it still require a CLA to be signed, just like corporate open source projects? Setting up Home Assistant for someone who's non-technical is a terrible idea. This is an even bigger issue if they want it set up and left alone without updates/maintenance. The mobile app would probably stop working properly with this installation or they'd break it at some point by installing updates. I'll wait for a bit longer while I prepare to migrate away from Home Assistant and Home Assistant OS. I'm considering a setup which uses Home Assistant core to trigger automations and to display a dashboard. All the automations and device integrations would be done with other tools. This would reduce exposure to Home Assistant's regressions and avoid Home Assistant OS's limitations. [1] the Nabu Casa run icons site - https://brands.home-assistant.io [2] https://github.com/home-assistant/frontend/issues/18549 [3] Home Assistant Python requirements https://github.com/home-assistant/core/blob/dev/requirements...
In How I Use Home Assistant in 2025
dhx·Nov 13, 2024
This account was spamming Python repositories with the same type of low value obvious backdoor spam.[1] Full list of attempted pull requests (all deleted seemingly by GitHub): 1 https://www.github.com/KurtBestor/Hitomi-Downloader/pull/7638 2 https://www.github.com/home-assistant/core/pull/130423 3 https://www.github.com/celery/celery/pull/9407 4 https://www.github.com/chriskiehl/Gooey/pull/921 5 https://www.github.com/crewAIInc/crewAI/pull/1582 6 https://www.github.com/cumulo-autumn/StreamDiffusion/pull/177 7 https://www.github.com/AUTOMATIC1111/stable-diffusion-webui/pull/16646 8 https://www.github.com/Aider-AI/aider/pull/2343 9 https://www.github.com/aboul3la/Sublist3r/pull/383 10 https://www.github.com/plotly/dash/pull/3073 11 https://www.github.com/soimort/you-get/pull/3034 12 https://www.github.com/streamlink/
Read the rest
streamlink/pull/6290 13 https://www.github.com/jumpserver/jumpserver/pull/14440 14 https://www.github.com/junyanz/pytorch-CycleGAN-and-pix2pix/pull/1684 15 https://www.github.com/kornia/kornia/pull/3069 16 https://www.github.com/langflow-ai/langflow/pull/4520 17 https://www.github.com/exo-explore/exo/pull/432 18 https://www.github.com/PostHog/posthog/pull/26144 19 https://www.github.com/PrefectHQ/prefect/pull/15987 20 https://www.github.com/pydantic/pydantic/pull/10822 21 https://www.github.com/pyg-team/pytorch_geometric/pull/9777 22 https://www.github.com/qutebrowser/qutebrowser/pull/8379 23 https://www.github.com/tornadoweb/tornado/pull/3441 24 https://www.github.com/ungoogled-software/ungoogled-chromium/pull/3092 25 https://www.github.com/locustio/locust/pull/2980 26 https://www.github.com/matterport/Mask_RCNN/pull/3057 27 https://www.github.com/Stability-AI/generative-models/pull/425 28 https://www.github.com/yt-dlp/yt-dlp/pull/11520 [1] https://play.clickhouse.com/play?user=play#U0VMRUNUICogRlJPT...
In Backdoor attempt on Exolabs GitHub repo through an innocent looking PR
wutwutwat·Nov 14, 2023
Home assistant does headless bt presence detection in ~200 lines of python I think the author had a painful experience because they wanted to do embedded and had to interface at a much lower level, where it's a long ago solved problem in higher level languages. Considering the tracker ended up in their door next to their computer, they could have stuck with the rpi that ran python and been fine https://github.com/home-assistant/core/blob/dev/homeassistan... https://www.home-assistant.io/integrations/bluetooth_tracker...
In Building an occupancy sensor with a $5 ESP32 and a serverless DB

Showing the 15 most recent of 55 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.