Fix the Home Assistant warning "Update MariaDB to a supported LTS version" on MariaDB 13
Table of contents
- Key takeaways
- Why does Home Assistant say MariaDB 13 is not LTS?
- Who gets the warning?
- Why changing the tag to mariadb:12.3 is not enough
- How to move from MariaDB 13 to 12.3 with mariadb-dump
- How long the dump and the restore take
- Which MariaDB tag should you use so it does not happen again?
- FAQ
- Can I ignore the repair until 2027?
- Do I lose history or statistics when moving to 12.3?
- Does it affect me if I use MySQL instead of MariaDB?
- Conclusion
- Sources
Home Assistant 2026.10 warns that MariaDB 13.0 is not an LTS release and that the recorder stops working with it in 2027.3.0. It hits anyone running mariadb:latest in Docker. The fix is to dump the database with mariadb-dump, start mariadb:12.3 on an empty data directory and restore the dump; with a million states it took 11 seconds.
If Home Assistant shows the repair "Update MariaDB to a supported LTS version to continue using the recorder", your database is MariaDB 13.0, a release without long-term support (LTS), and the recorder stops using it in 2027.3.0. It hits anyone who had mariadb:latest in Docker, because that tag moved to 13.0.2. The fix is to dump the database, start mariadb:12.3 on an empty data directory and restore the dump. I reproduced it on 12 November 2026 with Home Assistant 2026.11.1 on Linux arm64. There is a Spanish version of this guide.
Key takeaways
- Since 2026.10, the recorder flags any MariaDB outside the LTS series 10.11, 11.4, 11.8 and 12.3 as unsupported.
- Today
mariadb:latestandmariadb:13point at 13.0.2, andmariadb:ltsat 12.3.3. - The MariaDB app for Home Assistant OS runs 11.8 since its version 4.0.0, so it is not affected.
- With a million states in
states(224 MiB), the dump took 1 second and the restore on 12.3.3 took 10.4 seconds. - Starting 12.3 on the 13 data worked in my test, but MariaDB does not support downgrading on the same data directory.
Why does Home Assistant say MariaDB 13 is not LTS?
It says so because the recorder checks the server version against a list of LTS series generated from endoflife.date. The list arrived with PR #179615[1], merged on 20 August 2026. In 2026.11.1 it holds 10.11, 11.4, 11.8 and 12.3 for MariaDB, and records 13.0 as the latest release that is not LTS.
The warning did not show in 2026.9 even if you were already on 13.0. The code accepts any series newer than the latest one it knows, and 13.0 only entered the list with PR #183037[2] on 24 September. Since 2026.10, the recorder raises this repair with warning severity:
Update MariaDB to a supported LTS version to continue using the recorder
This stops working in version 2027.3.0. Please address before upgrading.
Version 13.0.2 of MariaDB is not a supported long-term support (LTS)
release. [...] please upgrade to one of the supported LTS versions
(10.11, 11.4, 11.8, 12.3) and restart Home Assistant
13.0 is a rolling release: according to endoflife.date[3], its support ends on 31 December 2026, while 12.3 is supported until 12 June 2029. The review of MariaDB 13 in Docker covers what that release brings and the rolling schedule.
Who gets the warning?
It hits anyone whose recorder points at their own MariaDB on a series outside the list. In practice, that is a container install with the mariadb:latest or mariadb:13 tag:
| Install | MariaDB version | Warning? |
|---|---|---|
| Recorder on SQLite (default) | None | No |
| Home Assistant OS MariaDB app 4.0.0 | 11.8 | No |
Docker with mariadb:lts or mariadb:12.3 |
12.3.3 | No |
Docker with mariadb:latest or mariadb:13 |
13.0.2 | Yes |
| Unsupported series, such as 12.2 | 12.2 | Yes, same code path |
The Home Assistant install with Docker uses SQLite unless you set a db_url. If an automatic updater such as Watchtower watches your MariaDB, you may not remember when it moved to 13: the container says nothing when the series changes. To see which version you run, ask the server:
docker compose exec mariadb mariadb --version
In my lab it answered mariadb from 13.0.2-MariaDB. The warning also shows under Settings > Repairs.
Why changing the tag to mariadb:12.3 is not enough
Changing the image and reusing the same data directory is an in-place downgrade, and MariaDB does not support it. The MariaDB documentation[4] is blunt: "Downgrading is not officially supported, and MariaDB does not test in-place downgrades". It recommends a logical dump and restore.
I still tried it on a copy. 12.3.3 started on the 13.0.2 data with the message MariaDB upgrade not required, and Home Assistant ran with no errors and no repair. The system tables have the same 257 columns in both versions, which explains why it did not fail. But the mariadb_upgrade_info file still said 13.0.2, and nothing guarantees the next format difference will be as harmless.
There is also a case where it fails for sure. If you turned on 13's redo log archiving (innodb_log_archive), 12.3.3 refuses to start with File ./ib_logfile0 was not found, as I measured in the 13 review. A dump depends on none of that.
How to move from MariaDB 13 to 12.3 with mariadb-dump
The method I recommend is to dump only the Home Assistant database, create an empty MariaDB 12.3 and restore there. These are the steps I followed with a compose.yaml that mounts the data at ./mariadb and sets MARIADB_DATABASE, MARIADB_USER and MARIADB_PASSWORD, as in the guide to install MariaDB with Docker.
First stop Home Assistant, so it writes nothing after the dump, and dump the database with the root password the container already has:
docker compose stop homeassistant
docker compose exec -T mariadb sh -c 'exec mariadb-dump -uroot \
-p"$MARIADB_ROOT_PASSWORD" --single-transaction --routines \
--triggers --events --databases homeassistant' > ha-13.sql
The --databases option adds the CREATE DATABASE to the dump and leaves out the user tables, which the new container creates by itself. Then stop MariaDB, move the 13 directory aside and change the image:
docker compose stop mariadb
mv mariadb mariadb-13
sed -i 's/image: mariadb:13/image: mariadb:12.3/' compose.yaml
docker compose up -d mariadb
If your compose.yaml says mariadb:latest, change that tag instead. Because the directory is empty, the container creates the database and the user from the usual variables. Wait for the log to show MariaDB init process done and restore:
docker compose exec -T mariadb sh -c \
'exec mariadb -uroot -p"$MARIADB_ROOT_PASSWORD"' < ha-13.sql
docker compose up -d homeassistant
12.3.3 accepted the 13.0.2 dump untouched, including the first line /*M!999999\- enable the sandbox mode */ that the newer client adds. On start, Home Assistant did not raise the repair and the history was still there: the API returned 7184 points for one entity over the last three days. Keep mariadb-13 and ha-13.sql until you have checked everything works; rolling back means restoring the image and the directory.
How long the dump and the restore take
The restore sets the pace, because it rebuilds the states indexes. I measured it with a million synthetic rows in states, 224 MiB of data and indexes, on the same containers. The dump took up 132 MiB:
While Home Assistant is stopped it records nothing, so the history gets a gap as long as the whole procedure. To keep it short, prepare the compose.yaml and the commands before you stop the container.
Which MariaDB tag should you use so it does not happen again?
Use a specific LTS series tag, mariadb:12.3, not latest. The lts tag also works today, but it will change series when the next LTS ships, and a major series change in a self-updating container is exactly what caused this warning:
| Tag | Points at today | Changes series by itself |
|---|---|---|
mariadb:latest |
13.0.2 | Yes, with every rolling release |
mariadb:13 |
13.0.2 | Yes, to 13.1 and later |
mariadb:lts |
12.3.3 | Yes, with the next LTS |
mariadb:12.3 |
12.3.3 | No, only 12.3 patches |
Staying on 13 and moving to 13.1 is not a fix. With the current list, Home Assistant does not warn about a series it does not know yet. The repair comes back as soon as a Home Assistant release adds 13.1 to the list.
In issue #186992[5], opened on 17 October with 30 reactions, users ask to postpone the removal until 13.3 LTS ships. As of 12 November nobody from the team had replied.
FAQ
Can I ignore the repair until 2027?
You can click Ignore and the warning leaves the panel, but the deadline stays. The repair says it stops working in 2027.3.0. If you have not changed versions by then, do not upgrade Home Assistant to that release.
Do I lose history or statistics when moving to 12.3?
No, if you restore the full dump of the homeassistant database. In my test, the 1,000,016 states and recorder schema version 53 reached 12.3.3 intact. Long-term statistics live in tables of the same database, so they travel in the same dump.
Does it affect me if I use MySQL instead of MariaDB?
It can, through the same code. For MySQL, the Home Assistant 2026.11.1 list accepts the LTS series 8.4 and 9.7, and flags innovation releases up to 26.10 as not LTS. I have not tested it with MySQL.
Conclusion
The Home Assistant MariaDB LTS warning shows because mariadb:latest moved to 13.0, a rolling release supported until the end of 2026, and the recorder stops accepting it in 2027.3.0. Dump the database with mariadb-dump, start mariadb:12.3 on an empty directory and restore: with a million states it took 11 seconds. Do not reuse the 13 directory even if it starts, because MariaDB does not support downgrades. To check whether it affects you now, look at Settings > Repairs or run mariadb --version in your container.
Sources: [1] Home Assistant, issue #186992: Postpone removal of support for MariaDB short-term releases[5], [2] Home Assistant, PR #179615: Add repairs for upcoming bumps of minimum supported db engine versions[1], [3] Home Assistant, PR #183037: Update recorder database versions for MariaDB 13.0[2], [4] Home Assistant recorder documentation: MariaDB and MySQL[6], [5] MariaDB, downgrading between major versions[4], [6] endoflife.date: MariaDB[3], [7] Home Assistant MariaDB app changelog[7], [8] mariadb image tags on Docker Hub[8].