What has changed in Home Assistant 2026.11.1?
The release notes list around 60 changes. Roughly half are library bumps for integrations such as UniFi, Broadlink, ZHA, KNX, Overkiz and Android TV Remote. The rest are genuine fixes, and the ones most likely to touch a UK household are below. The full list is on the GitHub release page.
| Integration | What was fixed |
|---|---|
| HomeKit | Camera motion events now reach HomeKit |
| Shelly | Sleeping RPC devices restored after a restart gain their new entities on wake; an RPC cover no longer fails to close at position 0 |
| SimpliSafe | Sensors are marked unavailable when they are reported offline |
| MQTT | Payload encoding is validated and unknown encodings are handled on receive |
| VeSync | Missing fan modes restored |
| myUplink | Energy log sensors that had been removed are restored |
| Samsung TV | First power check after setup uses the PowerState value |
| NUT | Alarm sensor updates work again (relevant to UPS monitoring) |
| ONVIF | Event webhooks use a random ID |
| Marketplace | Rate-limit connection errors log without a traceback; the README is refetched after install or uninstall |
Other fixes cover La Marzocco (it now prefers the cloud model over Bluetooth and delays a settings refresh after a firmware update), Midea (devices close when Home Assistant stops, and a duplicate probe after key validation is skipped), ESPHome (a serial proxy URL fix and a climate defrosting action mapping), Tomorrow.io (the integration now starts polling after setup), Agent DVR, SolarEdge, Kostal Plenticore, WeatherFlow Cloud and TP-Link Omada.
Why does this matter for Home Assistant users?
If you use any integration in the table above, update. If you do not, the release changes nothing visible, so there is no rush beyond the usual advice to keep a current build. It follows the big feature drop in Home Assistant 2026.11, which brought the built-in Marketplace and the new entity naming scheme.
A few fixes are worth a closer look:
- Shelly owners: the cover fix matters if you run Shelly relays on blinds, garage doors or gates. A cover that fails to close at position 0 is exactly the kind of fault that goes unnoticed until it is cold or raining.
- Anyone using MQTT: the payload validation change makes the integration cope with unexpected encodings instead of choking on them. If you publish from custom scripts or older devices, it is worth watching your logs after updating. Our MQTT guide explains the basics.
- Security-system users: SimpliSafe sensors now show as unavailable when they are reported offline, which is more honest than showing a stale state. See our SimpliSafe UK review if you are weighing the system up.
- Energy and heat-pump users: myUplink energy log sensors return after being removed earlier, so any dashboards or statistics that relied on them should start filling again. This is a restore of earlier behaviour, not a new feature.
Should you update now or wait?
Update, but take a backup first. Patch releases are small and targeted, yet any update can interact badly with a specific setup. Home Assistant 2026.11 added local backups to a USB drive, and our USB backup guide shows how to set that up. If you need the basics, read how to back up and restore Home Assistant.
The usual process applies. In Settings, check the available updates, create a backup when prompted, and install. Afterwards, glance at the logs for new errors from integrations you rely on. If you are on a cautious schedule, there is no harm in waiting for 2026.11.2 if one is announced. We have not seen one at the time of writing, and we cannot say when it will arrive.
What does this release not fix?
The notes describe individual integration fixes. They do not describe any change to Matter, Zigbee or Thread behaviour beyond a ZHA library bump, and they do not claim to resolve every open bug in 2026.11. If you hit a problem that is not listed, check the Home Assistant issue tracker and community forum before assuming the patch covers it. We have not independently tested each fix on hardware, so the descriptions above come from the project's own release notes.
