Home Assistant 2026.11.2 upgrade: 48 fixes, no breaking changes
Summary
2026.11.2 is a bug-fix release with 48 entries. Many are dependency bumps for single integrations. Fixes you may care about:
- MQTT: fixes a reload loop caused by a duplicate unique ID on a disabled entity, and an unsubscribe callback problem after the MQTT entry reloads. It also ignores a self-referencing
via_device. - webOS TV: fixes the TV going unavailable when it resets the connection, and hides the volume-set control when the TV says it is unsupported.
- Axis: fixes basic auth for cameras and stream cleanup on unload.
- Reolink: fixes playback for NVRs and Hubs.
- FRITZ!: fixes FRITZ!OS version parsing and diagnostics for older repeaters.
- Hue: fixes a migration failure for multi-channel Zigbee devices.
- Security and privacy: the Solar-Log password and Alexa Devices account identifiers are now redacted in diagnostics.
aioftpwas upgraded to 0.28.3 (marked “security” in the notes), and configuration values are no longer logged inempty_config_schema. - Frontend is updated to 20261028.6.
Breaking changes and deprecations
The release notes list none. One behaviour change to be aware of: input_text.set_value now rejects values that violate the entity’s pattern, so automations that set non-matching values will start to fail.
Tested in our lab
Tested in our lab: a Docker upgrade of a fresh, empty instance from 2026.11.1 to 2026.11.2. This covers the container upgrade path only. We did not set up any integrations, so none of the individual fixes above were tested.
- Installed 2026.11.1 with the official container image, host networking and a
/configvolume. - Completed the first onboarding step (created a user) on 2026.11.1.
- Stopped and removed the container, then started 2026.11.2 on the same
/configvolume. - The web API answered, the version reported 2026.11.2, and the onboarding API still showed the user step as done. The user was still in
.storage/auth. - The log search for “error” or “warn” returned only one line, a harmless
s6-rc-compilewarning about an empty directory. We did not capture the 2026.11.1 logs, so we can’t say whether that line is new.
Lab log
$ docker run -d --name homeassistant --restart=unless-stopped -v /opt/ha/config:/config -v /etc/localtime:/etc/localtime:ro --network=host ghcr.io/home-assistant/home-assistant:2026.11.1
$ docker exec homeassistant python3 -c "import homeassistant.const as c;print(c.__version__)"
2026.11.1
$ docker stop homeassistant
homeassistant
$ docker rm homeassistant
homeassistant
$ docker run -d --name homeassistant --restart=unless-stopped -v /opt/ha/config:/config -v /etc/localtime:/etc/localtime:ro --network=host ghcr.io/home-assistant/home-assistant:2026.11.2
$ curl -s http://localhost:8123/api/onboarding
[{"step":"user","done":true},{"step":"core_config","done":false},{"step":"analytics","done":false},{"step":"integration","done":false}]
$ docker exec homeassistant python3 -c "import homeassistant.const as c;print(c.__version__)"
2026.11.2
$ docker ps --format "{{.Image}} {{.Status}}"
ghcr.io/home-assistant/home-assistant:2026.11.2 Up 9 seconds
$ docker logs homeassistant 2>&1 | grep -iE "error|warn" | head -20
s6-rc-compile: warning: source /etc/s6-overlay/s6-rc.d is empty
Reported by others
We did not look for user reports for this release. Everything in the Summary comes from the release notes.
Verdict
Upgrade when convenient, especially if you use MQTT, webOS TV, Axis, Reolink or FRITZ!. The notes list no breaking changes, and the container upgrade from 2026.11.1 worked in our lab. Take a backup first as usual. If you set input_text values from automations, check that they match the entity’s pattern. Our test did not cover your integrations or a populated configuration.