Loading...
E.G.

Home Assistant 2026.11 Upgrade: HACS to Marketplace

November 15, 2026
Table of Contents

On 10 November I upgraded my Home Assistant from 2026.9.4 straight to 2026.11.1 and skipped 2026.10. It runs as a Docker container with a pinned image tag. I had waited for the first bugfix release on purpose: 2026.11 replaces HACS with the built-in Marketplace, and I had no wish to find its first bugs on the instance that runs my house.

What I checked before switching

Because I skipped 2026.10, I read the release notes of both versions. The section on backward-incompatible changes had 22 entries for 2026.10 and 45 for 2026.11. None of them named an integration I use. A handful are general: usernames are now always normalised, state conditions that combine for with an attribute fail validation, the sign of a sun trigger offset now decides before or after, and entity names on dashboards are built from the device name. I searched my YAML for sun triggers with an offset, alert cards and that kind of state condition and found none.

Then I checked my configuration with the new version before switching the running container. I copied the config directory without the database and the backups to /tmp/hacheck, then ran the command below once with 2026.9.4 and once with 2026.11.1:

docker run --rm --network none -v /tmp/hacheck:/config \
  --entrypoint python3 ghcr.io/home-assistant/home-assistant:2026.11.1 \
  -m homeassistant --script check_config -c /config

Old and new image printed the same result. The only error was a media folder that the test container doesn't mount, and it showed up in both runs. Last step before switching: a fresh backup, 131 MB. I keep backups as described in my post on backups to S3-compatible storage. On the first start the KNX telegram history logged a database schema migration, so for a rollback I would have restored the backup first. I haven't tested whether the old image still runs against the migrated database.

The switch itself

The switch was one line in the compose file and a recreate, the same routine as in my Docker update workflow:

sed -i 's#home-assistant:2026.9.4#home-assistant:2026.11.1#' docker-compose.yml
docker compose up -d

The API answered at my first check, a few seconds after the container started. I compared all entity states before and after: 680 entities both times. After the restart, four detection sensors of my Tapo cameras and the new backup size sensor were unavailable. After every restart the Tapo sensors become available again with the first camera event, and the backup size sensor reports a value after the next backup.

What happened to HACS

I had HACS 2.0.5 installed, with two custom integrations from it: Midea AC LAN and Tapo Control. After the first start the hacs folder under custom_components was gone and so was the HACS entry in the sidebar. In its place there is a config entry called marketplace, found under Settings → Marketplace. No repair came up.

Both integrations are listed in the Marketplace as installed, with their update entities. The template integration_entities('marketplace') returns those two entities, and integration_entities('hacs') returns an empty list. The old update.hacs_update entity disappeared. The Marketplace stores its catalogue in the .storage folder, about 3 MB for 5,000 repositories.

One detail survived the migration that I hadn't expected. Version 2026.10.0 of Midea AC LAN, released on 23 October, was marked as skipped in HACS, and the Marketplace kept that skip. The update entity therefore showed no pending update although a newer version was listed.

The first update through the Marketplace

I used that skipped Midea update to try installation and restart through the Marketplace. I ran it from a script over the Home Assistant API, so I could keep the exact responses. The first attempt failed with this message:

Open the Marketplace and read the warning first, installing and updating work once it is accepted

The Marketplace stores for each user whether they accepted the warning, and after the migration from HACS I still had to accept it. After I accepted the warning, the install went through in about a second, and the Marketplace raised a repair saying a restart was required. After the restart Midea AC LAN ran on 2026.10.0 and both of its entities were available. What I describe in my HACS install guide about the Marketplace beyond this comes from the release notes and the documentation. I haven't added a new project through it yet.

What the log showed afterwards

Midea AC LAN still writes 29 deprecation warnings at start, about temperature properties of its climate and water heater entities. The update to 2026.10.0 didn't change that. A later Home Assistant release may stop supporting those properties, so I will check the integration before the next upgrade.

The old log file was 155 MB, mostly about 242,000 lines of TP-Link errors with status 403 for two devices, going back to 23 October. That had nothing to do with the upgrade. My old and new instance still run in parallel and both polled the same bulb and the same plug with the same account. As far as I can tell, every login of one instance ended the session of the other. I disabled the two devices on the new instance, and the errors stopped.

Frequently asked questions

Do I have to reinstall my HACS integrations?

On my instance, no. Both integrations were adopted on the first start and kept their update entities.

Can I go from 2026.9 straight to 2026.11?

I did. Read the backward-incompatible changes of both releases first, because a skipped release still applies its changes.

Does the Marketplace work with Home Assistant Container?

Yes, on my Docker install it was there after the first start with no extra step. I haven't tested Core in a Python virtual environment.

Related articles

Questions or additions?

Comments run on GitHub Discussions, so you need a GitHub account to write one.