Home Assistant Core 2026.10.3 was published on 23 October 2026 at 20:50 Warsaw time. The release notes list 32 pull requests. About a third are dependency bumps and build changes, and the rest fix single integrations. Nothing here changes how automations or the core work, but a few fixes matter if you use AVM FRITZ! thermostats, KNX, dynamic energy prices or Home Connect appliances.

FRITZ!SmartHome lock sensors were swapped

FRITZ!SmartHome devices expose two binary sensors: one for the button lock on the device itself and one for the lock set through the FRITZ!Box interface. The integration had their names the wrong way round, so the entity called "Button lock on device" actually showed the lock set in the UI, and the other way round. The report that led to the fix (#187059) came from a FRITZ!Smart Thermo 302. Pull request #187119 corrects the friendly names, and new installations get the right entity IDs. Existing entity IDs are left alone on purpose, because they may already be used in automations, scripts and dashboards. After the update, check which of the two sensors your automations really need, and rename the entity IDs by hand if you want them to match.

KNX no longer times out on a large telegram store

At start-up, Home Assistant cancels integrations that take too long to set up. The KNX integration keeps a history of bus telegrams in a database, and one user with a roughly 400 MB SQLite file saw KNX setup cancelled in the middle of a migration of that store. Since #186980, the bootstrap timeout is held off while the telegram store initializes.

Energy prices and appliances

  • EnergyZero: gas prices for the hours between midnight and 06:00 (Amsterdam time) were missing. The fix (#186917) moves to energyzero 5.1.1, which also removes duplicate price intervals. This matters for anyone who plans heating or charging around Dutch dynamic tariffs.
  • Home Connect: when refreshing the account token failed, the event listener stopped and Bosch, Siemens or Neff appliance entities froze until the integration was reloaded. Now the listener retries with a growing delay. If the account really needs to be signed in again, the integration reloads and its entities show as unavailable instead of keeping old values (#187207).
  • UniFi Access: one Face Unlock produced two access events, so blueprints sent two notifications for a single entry (#185160).
  • Proxmox VE: the update entity treated any updated package as a new Proxmox version, so a Ceph 19.2.6 update could show up as an upgrade from PVE 9.2.3. It now looks only at pve-manager (#184823).

Smaller fixes

  • Sensibo: the full_state action no longer modifies the shared coordinator data, which caused a KeyError: 'timestamp' (#187014).
  • SMTP: each connection gets a new SSL context instead of sharing one (#186812).
  • TP-Link Omada: missing update fields from the controller no longer break the integration (#185164).
  • Synology DSM: errors during button actions are handled (#186931).
  • EDL21: the bitstring library is held below version 5, which broke the pysml dependency (#186985).

The release also moves to Python 3.14.8 and frontend 20260930.5, with library updates for BleBox, Hive, NINA, Victron VRM, Opower and the Alexa Devices integration.