LoginSign Up
← Back to all sparks
H

Home Assistant

INFRA · APIS
Velocity3.8

Open-source home automation platform for local control of smart devices

www.home-assistant.io ↗

Home Assistant is systematically removing the technical knowledge its own product used to require.

approachabilityautomationonboardingyaml-migrationsmart-homeopen-source
◆Current state
Home Assistant ships monthly, and the last five releases read as one campaign: strip out the prerequisites that made the product feel like infrastructure. 2026.7 made purpose-specific automation triggers the default for everyone, so you describe what your home should do instead of which entity changes state. 2026.8 went further and removed the :8123 port from new installations, moved web server configuration out of YAML into the interface, and deleted the words advanced and expert from roughly 43 places. The capability surface is not shrinking; the vocabulary required to reach it is.
◆Where it's heading
The pattern is consistent: take something that only worked if you already understood Home Assistant's internals, and re-express it in terms of the outcome the user wants. Triggers moved from entity-and-state to intent, the card picker moved from which card type to which thing in your home, and addressing moved from a memorized port to an ordinary web address. Each step ships with a migration that leaves existing installs untouched, which is how the project widens its audience without breaking the technical install base it already has. Integrations teaching the automation engine their own triggers is the piece with the most compounding left in it.
◆Prediction
Expect the next releases to keep converting Labs experiments into defaults and to move the remaining YAML-only configuration surfaces into the interface, following the pattern the web server settings just set.

◆Recent moves

  1. 28d ago

    Home Assistant drops the :8123 port for new installs

    ⚡ SPARK

    The clearest structural step in the approachability campaign: new Home Assistant OS installs answer on an ordinary web address, and web server settings move from YAML into the interface with a five-minute auto-rollback if the change locks you out. It also strips advanced and expert labelling from around 43 places across the app, docs, and companion apps.

    View source ↗
  2. 2mo ago

    Purpose-built automation triggers graduate from Labs to default

    ⚡ SPARK

    The automation arc that ran through 2026.4 and 2026.6 as a Labs experiment becomes the default here, which is what turns the approachability campaign from wording into architecture. Activity, still known to many users as the logbook, was also rebuilt into a day-grouped timeline.

    View source ↗
  3. 3mo ago

    Card picker suggests cards from what you want to show

    The same inversion as the automation work, applied to dashboards: the card picker asks which thing in your home you want to show rather than which card type you want, and previews the suggestions against your own data. New zone triggers and conditions moved Labs a step closer to the graduation that landed in 2026.7.

    View source ↗
  4. 3mo ago

    Public roadmap and rebuilt templating documentation

    Less a feature release than groundwork for the approachability campaign: the roadmap became public and open to comment, and the templating documentation was reworked by an expanded documentation team. Documentation is the part of approachability that never shows up as a headline feature, which is roughly where it sits in the release notes.

    View source ↗
  5. 5mo ago

    Infrared devices become first-class in Home Assistant

    Infrared support brings televisions and air conditioners with no network stack at all into Home Assistant as controllable devices, extending reach to hardware that predates the smart home entirely. The Labs triggers and conditions effort reached near feature-completeness here, two releases before it became the default.

    View source ↗