Home Assistant Core 2026.10.3, released on 23 October 2026, fixes incorrect Proxmox VE update versions, duplicate UniFi Access events, missing Omada update entities and several integration failures. GitHub now marks it as the latest stable Core release. It is a maintenance update, not Home Assistant OS 18.4 or an ESPHome firmware release.
Quick summary
- The Proxmox VE update entity now takes its proposed version from the
pve-managerpackage instead of unrelated pending packages. - UniFi Access deduplicates matching door-access events received through two controller feeds within ten seconds.
- TP-Link Omada update entities can load when a controller, including reported OC300 cases, omits expected version fields.
- There are additional fixes for Synology DSM actions, SMTP TLS setup, KNX telegram-store migration and several device integrations.
Proxmox update reporting is more precise
The most important home-lab fix concerns the Proxmox VE integration. Its update entity previously examined pending packages from the Proxmox repository and could select the highest-looking version among them. That meant a Ceph package version could be presented as the proposed Proxmox VE version. A Debian-style package version could also fail Python’s version parsing and leave the entity unavailable.
Home Assistant now derives the proposed platform version specifically from pve-manager, while retaining the total count of available package updates. This changes what Home Assistant reports; it does not install or manage the Proxmox upgrade itself. Readers running Home Assistant as a virtual machine can also see our Proxmox USB passthrough guide.
UniFi Access and Omada controller fixes
UniFi Access controllers can expose the same door event through both their insights and logs feeds, only milliseconds apart. Before this patch, Home Assistant could put both copies on its event bus, producing duplicate history entries or running an automation twice. The integration now keeps a short cache and suppresses matching events received within ten seconds; events with different attributes remain distinct.
The Omada integration has a separate robustness fix. Some controller responses can omit currentVersion and related update fields. Those fields are now treated as optional and the integration uses fallbacks, allowing update entities to load rather than failing the whole path. Our UniFi and Omada comparison explains how the two controller ecosystems differ.
Synology, KNX and SMTP changes
For Synology DSM, failed button actions now surface as translated Home Assistant errors. This is better feedback, but it should not be read as a guarantee that a rejected NASAliExpress price command will succeed after updating.
KNX installations with a large telegram store should also behave better during startup. The integration now pauses its bootstrap timeout while the initial store migration runs, avoiding repeated cancellation by Home Assistant’s wider startup deadline. The SMTP integration creates its own SSL context, addressing TLS setup failures reported after 2026.10.0.
Other corrections restore EnergyZero gas prices before 06:00, separate the mixed-up FRITZ!SmartHome lock sensors, keep the Home Connect event listener alive after token-refresh errors and fix several smaller integration issues. These changes follow the broader 2026.10.2 maintenance release.
Availability and updating
Home Assistant’s GitHub repository lists 2026.10.3 as the latest stable Core release. Users can install it through their normal supported update route once it is offered to their installation. A current backup remains sensible before any Core update, especially where access-control or infrastructure automations are involved. The fixes are integration-specific, so installations that do not use the affected services may see little immediate change.
