Step 1 — Home Assistant files

The whole Home Assistant side is one archive, tab5_home_assistant.zip, attached to each release. Nothing to fill in: every value of your home is picked afterwards in Home Assistant, with the mouse (ADR-0024).

Two ways to put them in place: with HACS, which then updates them in one click at each release, or by hand, parts A to C below.

With HACS

From release 3.7.0, the files also come with a small integration, « Tab5 », that HACS installs (ADR-0035). HACS must already be installed. HACS offers full releases only: pre-releases (Beta channel) only if beta versions are switched on for this repository in HACS.

1. Add the packages: line of part B to configuration.yaml, if it is not there yet.
2. Open Tab5 in HACS: the link goes through My Home Assistant, which asks for your Home Assistant address the first time, then HACS offers to add the repository: Add (a box with a title only: reload the page, troubleshooting). Without the link: ⋮ (top right) → Custom repositories, repository https://github.com/Axellum/M5-Tab5-ESPHome-LVGL, type Integration, Add, then search for Tab5 in HACS and open it.
3. On the Tab5 page of HACS, Download.
4. Restart Home Assistant.
5. Settings → Devices & services → Add integration → Tab5. Leave « Then update the tablet » ticked to have the firmware of the same version installed after the files, at each release (updates).

The integration then puts the files in place by itself, without another restart. It worked if a notification « Tab5: Home Assistant files 3.x.y » says how many files were added, and the « Tab5 · » entities are there (see part C). Your own packages, templates and blueprints are never touched, and removing the integration leaves the files in place. Nothing else to do on this page: go to step 2, install the firmware.

Setup assistant (from 3.8, ADR-0052): once the files are in place, Settings → System → Repairs shows « Tab5: set up the tablet from your rooms ». It prepares the automation of step 6 from your Home Assistant areas: up to five rooms, the best equipped first, each with its lights, covers, switches, fans and media players (five at most), its temperature and humidity sensors and its climate. Then a Home page (TV, phone battery, a second temperature, climate, pots, weather: filled in only when your Home Assistant has a single answer) and a Calendars and people page (the « Tab5 · … » lists: a choice already made stays, a list still on « Aucun » gets a suggestion when a single entity fits, such as a calendar named « work »). Every page is filled in already: check it, change what you like, Submit. The last page sums it up; submitting writes the automation into automations.yaml (saved first in tab5_sauvegardes/automatisations/) and reloads the automations, then sets the lists that changed. An automation of the blueprint that already exists only changes if you tick « Replace the rooms and home inputs of the existing automation », and then only those (ADR-0053). If automations.yaml cannot be written safely (another include, a !secret in it), nothing is written and a notification gives the YAML to paste. Start it again any time: Settings → Devices & services → Tab5 → Configure, box « Start the setup assistant ». It needs your devices assigned to areas in Home Assistant; without any, it says so and changes nothing.

A. Download and unzip

Download tab5_home_assistant.zip from the latest release (Assets, at the bottom of the release) and unzip it into Home Assistant's config/ folder, the one holding configuration.yaml: Samba share, or the File editor or Studio Code Server add-on. It adds three folders:

Folder	What it holds
packages/	the automations and scripts that feed the screen, and the « Tab5 · » lists of step 5
custom_templates/	the dashboard of step 7, and the reader of some weather warnings
blueprints/automation/tab5/	the blueprint of step 6

Warning

The folders go straight into config/. Some tools unzip into a new folder named after the archive (tab5_home_assistant/). The three folders must sit directly in config/, next to configuration.yaml. A packages/ folder you already have keeps its files: the archive only adds its own.

A fourth folder, tab5_optionnel/, is not loaded: see a shutter that reports nothing.

B. One line in configuration.yaml

The only YAML you write (skip it if it is already there):

homeassistant:
  packages: !include_dir_named packages

If homeassistant: already exists, add only the packages: line under it, indented like the lines already there.

Optional, from 3.8: the alert raised when a push to the tablet fails to render (packages/tab5_health.yaml) also needs system_log: fire_event: true in configuration.yaml, then a restart. HACS cannot add it for you; without it, that one alert stays silent and everything else works.

C. Check, then restart

Developer tools → YAML → Check configuration, then restart Home Assistant (Settings → ⋮ → Restart Home Assistant).

It worked if Settings → Devices & services → Entities, searched for « Tab5 · », lists the « Tab5 · source des prévisions », « Tab5 · agenda de travail »… entities. You will set them at step 5, once the tablet is there.

A shutter that reports nothing

tab5_optionnel/volet_serre_tracking.yaml is only for a shutter that reports neither its position nor its travel (the author's Tuya motor): copy it into packages/, reload, and pick the shutter in « Tab5 · volet à course simulée ». It is not installed by default: the shutter picked in that list no longer gets the blueprint's commands but the package's script, which times its travel. Set that time in « Tab5 · course du volet » (seconds, 26 by default; from 3.8). Left on « Aucun », the package changes nothing. With HACS, copy it from config/custom_components/tab5/fichiers/tab5_optionnel/: once it is in packages/, the integration updates it with the others.

Where these files come from

The same files are in the repository (HomeAssistant_Config/packages/, custom_templates/, blueprints/, optionnel/); HomeAssistant_Config/README.md says what each package does. They are exactly what runs on the author's Home Assistant since 2026-09-26, with no per-home edit since 2026-09-28: there are no private versions, and nothing to merge into automations.yaml or scripts.yaml.

Already installed and updating? Updates.

Next: step 2, install the firmware.