Home Assistant is free, open-source software for centralized home automation and smart-home management. It runs on a local computer or server, connects devices from many manufacturers and protocols into one interface, and executes automation rules without depending on a manufacturer's cloud service. Its design emphasizes local control, user privacy and customization, and it is among the most widely used open-source projects of its kind.
History
The project began in 2013 as a personal experiment by the Dutch software engineer Paulus Schoutsen, who wrote a Python program to control Philips Hue lights. The first version was published on GitHub on 17 September 2013, and the project grew into a community effort as contributors joined. Schoutsen later founded Nabu Casa, a company that sells hardware and an optional subscription for remote access, with the aim of funding development without outside investors.
In April 2024 the source code and brand were transferred to the Open Home Foundation, a non-profit organization based in Switzerland. The transfer was intended to keep the software free and open-source and to protect it from being acquired or abandoned. The foundation also governs a number of related projects, including ESPHome, Z-Wave JS, Zigpy and the Open Home Matter Server. In October 2026 Nabu Casa's cloud service was renamed Home Assistant Link; the company states that most of its subscription profits go to the foundation.
Home Assistant is developed in Python for the backend and TypeScript for the web frontend. Releases follow a regular cycle, with versions named by year and month (for example 2026.9, released in September 2026).
Architecture and deployment
Home Assistant consists of a core that manages device states, an event system and automation engine; a web-based user interface; and a large library of integrations, which are plug-ins that communicate with specific devices or services. Users can control devices and build automations through a graphical editor or by writing configuration files in YAML.
The software can be installed in several ways. It runs in Docker containers and on general-purpose computers, and it is commonly installed as a dedicated operating system image on single-board computers such as the Raspberry Pi, on mini PCs, or on network-attached storage devices. The official "Home Assistant Green" and "Home Assistant Yellow" hardware are preconfigured options aimed at less technical users.
Integrations and protocols
A central feature is breadth of compatibility. Integrations cover lighting, thermostats, locks, cameras, sensors, energy meters, media players, appliances and online services. The integration count runs into the thousands, and many devices are supported through cloud APIs as well as local protocols.
Local protocols are especially important to the platform's design:
- Zigbee and Z-Wave are low-power mesh radio standards. Home Assistant typically uses a USB coordinator stick for each protocol, with integrations such as ZHA and Zigbee2MQTT for Zigbee and Z-Wave JS for Z-Wave. Zigbee has a larger and cheaper device catalog, while Z-Wave generally offers longer range and less interference on the 2.4 GHz band, at higher cost.
- Matter is an IP-based smart-home standard designed for interoperability across ecosystems. Home Assistant acts as a Matter controller, which allows it to commission (pair) and control Matter devices. It is not a Matter bridge, however, and cannot turn non-Matter devices into Matter devices. Thread, a mesh networking protocol used by many Matter devices, requires a compatible radio.
- MQTT, a lightweight messaging protocol, is widely used to connect custom hardware, such as microcontroller-based sensors built with ESP32 or ESP8266 boards.
Automation and interfaces
Automations are defined as triggers, conditions and actions. A trigger might be a sensor reaching a threshold or a scheduled time; actions might switch lights, adjust heating or send a notification. Scenes group device states, and scripts provide reusable sequences. Dashboards are configurable, and the companion mobile apps for iOS and Android provide notifications and location-based triggers.
Voice control is supported through local speech-recognition and text-to-speech components, and integrations allow the use of commercial assistants such as Amazon Alexa or Google Assistant. Some users connect large language models for natural-language control, although this requires additional configuration and hardware or external services.
Community and governance
Home Assistant is developed largely by volunteers and paid contributors on GitHub. Community forums, documentation and user-shared automations and integrations form a large part of its ecosystem. The official website states that the platform is used by over 2.7 million households, and the foundation reports that it is among the most actively contributed-to open-source projects on GitHub.
Privacy and local control
A defining principle is that core functions should continue when the internet is unavailable. Because automations run locally, lights, sensors and routines keep working during an outage, and data such as device history is stored on the user's own hardware by default. This contrasts with many commercial products, which rely on manufacturer servers and may stop working if a company discontinues a service.
Local operation does not eliminate privacy risks. Remote access to the system from outside the home network, third-party integrations and cloud-dependent devices each introduce exposure. Users are responsible for securing their networks, keeping software updated and choosing hardware with care. Optional cloud services, such as remote access and certain voice features, involve sending data to external providers.
Limitations and criticism
Home Assistant is more demanding than consumer smart-home apps. Initial setup, troubleshooting and maintenance often require technical knowledge, and configuration through YAML can be error-prone. Device support varies: some integrations are community-maintained, may lag behind firmware changes, or depend on reverse engineering. The fragmentation of protocols also means that a complete setup may require multiple radios and coordinators.
Some observers have questioned whether standards such as Matter will reduce the need for a central hub, while others argue that local control has long been achievable with existing protocols. Commercial competitors such as Apple Home, Google Home and Amazon Alexa offer simpler experiences, and open-source alternatives such as openHAB and Hubitat exist for users with different priorities.
Frequent updates, though beneficial for new features, can also break existing setups. Users are generally advised to back up their configuration before upgrading.
See also
- Internet of things
- Data privacy
- Cloud computing
- Automation
- Programming languages
References
- Home Assistanten.wikipedia.org
- Home Assistanthome-assistant.io
- Thinking Bigger: State of the Open Home 2024 - Home Assistanthome-assistant.io
- 2 million homes strong - State of the Open Home 2025 - Home Assistanthome-assistant.io
- Big Tech ruined the cloud, so we’re renaming ours - Home Assistanthome-assistant.io
- 10 years Home Assistantnewsletter.openhomefoundation.org
- Matter - Home Assistanthome-assistant.io
- Creating the Foundation for a New Home Assistant with Paulus Schoutsen - Last Week in AWS Podcastlastweekinaws.com
- 6 open source home automation toolsopensource.com
- Home Assistant: Open Source Self-Hosted Smart Home Automation - homeserver.pagehomeserver.page
- Zigbee vs Z-Wave for Home Assistant: Which to Choose? · SmartHomeSenseismarthomesensei.com
- Matter vs Zigbee vs Z-Wave vs WiFi - Smart Home Explorersmarthomeexplorer.com
- Home Assistant - Open Source Smart Home Automation · GitHubgithub.com