Home Assistant

Key features

• 1,000+ integrations with automatic discovery Connect more than 1,000 device brands with automatic local-network discovery, so adding a new light or sensor usually starts from a found device rather than a manual driver hunt.[1]

• Automation engine with triggers and conditions Combine triggers, conditions, and actions into routines such as evening lighting or wake-up sequences that execute locally even when the internet is down.[1]

• Customizable per-room dashboards Compose drag-and-drop dashboards per room, device type, person, or screen, so a wall tablet, a phone, and a desktop each show the controls that belong there.[1]

• Assist local voice assistant Use the built-in Assist voice pipeline, developed with the Open Voice Foundation, as an alternative to cloud speakers for households that want voice control without sending audio to a vendor.[1]

• Companion mobile apps with presence detection Run the free iOS and Android companion apps for remote dashboards, notifications, and presence detection, so arrival-based automations follow the household rather than a fixed schedule.[1]

• Add-on ecosystem with Node-RED and AdGuard Extend the hub with one-click add-ons for visual flow programming (Node-RED), network-wide ad blocking (AdGuard Home), media playback (Spotify Connect), and more.[1]

• Energy management and long-term statistics Track consumption over months with built-in energy dashboards and long-term statistics, which helps households find what drives their power bill.[1]

• Casting, NFC tags, and media control Cast audio and video to players around the house and trigger routines from NFC tags, so a tag by the door can run a leaving-home routine.[1]

Who will love it

• Privacy-minded households that want device states, automations, and voice commands processed inside their own network instead of a vendor cloud.[1][2]

• Tinkerers with mixed-brand collections spanning Zigbee, Z-Wave, Wi-Fi, and MQTT who want one hub plus Node-RED flows and YAML templating to unify them.[1]

• Households with unreliable internet, because automations execute on the local box so lighting, heating, and security routines keep running through an outage.[1][2]

Who should avoid it

• Anyone wanting an afternoon, no-maintenance setup: integration polish varies, manual YAML editing is sometimes needed, and advanced options assume Linux and networking skills.[1]

• Households fully invested in cloud routines with no spare time: migrating to self-hosted automation buys independence at the cost of weekends.[1][2]

• Renters or households that cannot place hardware: the system needs a box on the local network, and without somewhere to run it there is nothing to automate with.[1]

Alternatives and compatibility