Frontend Architecture

The Home Assistant frontend is built using web components. This is a modern web technology allowing us to encapsulate templates, styling and logic into a single file and expose it as an HTML tag in the browser. These components are composable, allowing a very dynamic and powerful foundation of our application.


The Home Assistant frontend can be broken up in 4 parts:


File: src/entrypoints/core.js

This is a very tiny script which is the first thing that is loaded on the page. It is responsible for checking for authentication credentials and setting up the websocket connection with the backend.

The script allows us to start downloading the data while also downloading the rest of the UI in parallel.

App shell

File: src/entrypoints/app.js

This is everything that is required to render the sidebar and handle the routing.


Folder: src/panels/

Each page in Home Assistant is a panel. Components can register extra panels to be shown to the user. Examples of panels are "states", "map", "logbook" and "history".


Folder: src/dialogs

Certain information and data entry is presented to users in flows. Dialogs can be triggered on any page. The most common one is the entity more info dialog, which allows users to dig into an entity state, history and setting.s

Data Flow

The frontend leverages the Websocket API and the Rest API to interact with Home Assistant.

The data is made available as the hass property which is passed down to every component. The hass property contains the core state and has methods to call APIs.

Components can subscribe to information that is not available in the core state. Subscriptions run through the websocket API which keeps the data in sync with the backend.

We use a unidirectional data flow. When you make a change in the backend (like turning on a light), the hass object will be updated at the root of the application and will be made available to every component that needs it.


The frontend uses decentralized routing. Each component only knows enough about the routing to know how to handle the part it's responsible for. Further routing is passed down the component tree.

For example, the <home-assistant> main component will look at the first part of the url to decide which panel should be loaded. Each panel can have its own mapping between the url and what content to show.

Last updated on