Technical

Home Assistant

Home Assistant: an open source home automation platform that runs locally and unifies thousands of devices and services without relying on a manufacturer's cloud.

Maison miniature en verre translucide posée sur un socle noir, entourée d'un anneau lumineux fin reliant quatre petits objets en métal brossé posés sur des disques : une ampoule à filament, un bouton rotatif de thermostat, une prise murale et un petit haut-parleur, sur fond anthracite avec un reflet bordeaux au sol
Home Assistant — Image générée par IA (Qwen-Image 2.1, ComfyUI local)

Home Assistant is an open source home automation platform that runs in your home, on a box or a local server, and brings devices from hundreds of brands into a single interface: lighting, heating, appliances, cameras, meters, sensors. Stewarded since 2024 by the Open Home Foundation, a Swiss non-profit, it has become the most active open source project on GitHub by number of contributors. For a decision-maker, it is the most mature example of domestic digital infrastructure that depends on no manufacturer's cloud.

Technical definition

A platform, not an app

Home Assistant consists of a core (Core) that keeps track of the state of every device, a supervisor that manages the system and updates on Home Assistant OS, and add-ons that provide extra services: an MQTT broker, a Zigbee gateway with Zigbee2MQTT, a media player, a file editor, SSH access. All of it fits on a Home Assistant Green or a Raspberry Pi.

Integrations and entities

Each brand or protocol is supported by an integration. An integration exposes typed entities: a light, a thermostat, a temperature sensor, a switch, a to-do list. This shared model is what makes composition possible: an automation can react to a Zigbee sensor to control a Wi-Fi plug and notify a phone, without those three devices knowing about each other.

Automations, scripts and blueprints

Automations follow a trigger, conditions, actions pattern, editable graphically or in YAML. Scripts group reusable actions, and blueprints are parameterized automations shared by the community: you pick your devices from dropdowns and the rest is already written. I used a blueprint to sync a Bosch thermostat with its radiator.

Interfaces and APIs

The built-in dashboards cover everyday needs. To go further, Home Assistant exposes a REST API and a real-time WebSocket API, and serves static files: you can have it host your own web app, as I did with Maison, displayed in kiosk mode on a wall-mounted tablet.

Current challenges

The home as sovereign infrastructure

Every connected device sold with its own app imposes its cloud, its terms of use and its lifespan. Home Assistant flips that logic: the state of the house is held locally, automations survive the shutdown of a service, and remote access is a choice, not an obligation. At household scale, it is the same digital sovereignty question that companies face with hyperscalers.

A maturity that changes its category

With more than two million active households and thousands of contributors, the project is no longer reserved for tinkerers. Matter, the interoperability standard backed by the big players, is supported, and manufacturers now design their products with this compatibility in mind. The operating burden remains: monthly updates, devices that change behavior, community integrations to keep an eye on. A Home Assistant installation is maintained like a small information system.

A testing ground for agents

Because it exposes the full state of a house through a clean API, Home Assistant has become a natural playground for AI agents: an official MCP server lets an assistant read entities and call services. The governance question then arises at home just as it does at work: which actions can an agent trigger without approval, and which ones can it not.

Frequently Asked Questions

What is the difference between Home Assistant and Google Home, Alexa or Apple Home?

The big players' assistants are cloud services: your devices, your routines and often your data go through the manufacturer's servers, and the catalog of compatible devices is whatever the manufacturer accepts. Home Assistant runs in your home, on a small box or a server, and talks directly to your devices whenever they allow it (Zigbee, Z-Wave, Matter, local network). Everything local keeps working without the internet.

The two worlds are not mutually exclusive: Home Assistant can control Hue, Bosch or Sonos devices and expose its entities to Google or Apple. The difference is the point of control, which stays inside the house.

Do you need to know how to code to use Home Assistant?

Not for the essentials: installation, adding devices, automations and dashboards are all done in the graphical interface, and community-shared blueprints cover common cases. YAML is still useful for advanced cases, such as REST commands to an external service or template sensors.

In practice, the real skill required is not programming but an integrator's discipline: naming your devices, organizing your rooms, keeping secrets out of versioned files and testing your automations.

What hardware should you install Home Assistant on?

The simplest option is a dedicated box sold by the publisher, the Home Assistant Green, or a Raspberry Pi running Home Assistant OS, which manages the system, updates and add-ons (Zigbee2MQTT, Mosquitto, Music Assistant). A mini PC or a virtual machine suits heavier installations with cameras and long history.

Add a radio dongle for Zigbee or Thread if your devices use them, and plan regular backups: the box quickly becomes the central point of the house.

Is Home Assistant secure?

By default, everything stays on the local network. Remote access goes either through the paid Nabu Casa service, which funds the project and encrypts the connection, or through a VPN or reverse proxy you control. The main risk is exposing the box directly to the internet without protection.

Like any central system, it deserves the usual reflexes: HTTPS, named accounts, two-factor authentication, secrets kept out of repositories, and an audit of what each third-party integration can do.

Resources and Documentation