Weekend Roundup Oct 19-25: ESPHome 2026.10.0, Matter 1.6.1, HA Patches

This week’s news is mostly maintenance, and it matters for anyone running ESPHome, Home Assistant or a Matter server. ESPHome 2026.10.0 shipped with several config changes that can break a working setup. Home Assistant 2026.10.3 and 2026.10.4 followed with fixes, and matter.js 0.18.0 brought Matter 1.6.1 support into the JavaScript stack. Here is what to check before you update.

ESPHome 2026.10.0: What Is Worth Knowing

ESPHome 2026.10.0 (released October 21, 2026) adds 20 new components and compressed over-the-air (OTA) updates that are about a third smaller on ESP32, RP2040, LibreTiny and host. Most users can update without changes, but four config areas can fail validation, so check them first.

The ESPHome 2026.10.0 announcement lists the new hardware coverage. The new components include Wi-Fi CSI motion sensing under the ESPectre name, a persistent Counter sensor, a Sensirion STCC4 CO2 sensor, and UART bridge, mux, TCP-UART and UART-TCP helpers. Check each component’s documentation for wiring and platform limits before you buy parts, because release notes do not replace datasheets.

ESP8266 Toolchain: Who Needs to Act Now

The native ESP8266 Arduino toolchain is now the default build. Working nodes need no change this weekend. Set toolchain: platformio under esp8266: to keep the old path, and migrate before 2027.4.0, the deadline the release notes give.

A practical split: keep one spare ESP8266 on the new default so warnings show up early, and leave production nodes on the escape hatch until you have tested them. Add the 2027.4.0 deadline to your winter maintenance list if you still run ESP8266 sensors, plugs or thermostats. ESP32, RP2040, LibreTiny and host users are not affected by the toolchain change, though they still get the compressed OTA benefit.

Four ESPHome Config Checks Before You Update

Four changes can break a working config: lights with initial_state:, the removed codec_support_enabled key, IR climate heat/cool flags, and Sendspin’s new encryption requirement. Review them line by line before you approve the update, because validation rejects some of them at compile time. Each has a specific YAML fix, listed in the table below.

Area	What changed in 2026.10.0	What to put in YAML
Lights with `initial_state:`	Now respected at boot	Confirm `initial_state:` plus `restore_mode` gives the power-on state you want
Speaker media players	`codec_support_enabled` removed; config fails validation if it stays	Remove it, and set pipeline `format:` to `NONE` for the old behaviour
IR climate	`supports_heat: false` or `supports_cool: false` no longer gets heat/cool auto by default	Add `supports_heat_cool: true` if you need the combined mode
Sendspin speakers	Every connection is now encrypted	Update Music Assistant to 2.10.7 or 2.11.0b4 or newer first

Lights deserve a slow check because boot behaviour is visible to the whole household. If a hallway or bedroom light uses initial_state:, verify it alongside restore_mode so a power blip does not leave an unintended default. For speakers, remove codec_support_enabled and set format: NONE only if you want the old behaviour.

The release notes list more validation failures than these four. Overlapping usb_uart entries are now rejected unless you split them with manufacturer and product filters. A sendspin switch needs type: enabled on each entry. On ESP8266, RP2040, LibreTiny, ESP32-C2 and ESP32-C61, a remote_receiver buffer_size: value should be multiplied by 4 to keep the same buffered pulse count. A homeassistant.action with more than 255 data or variable keys is rejected. Read the full upgrade checklist in the announcement before you approve the update.

Home Assistant 2026.10.3 and 2026.10.4: Apply the Latest Patch

Home Assistant 2026.10 was released October 7, 2026. Patch releases followed on October 10, 16, 23 and 24. The Home Assistant 2026.10 release notes list the fixes in each patch.

The 2026.10.3 patch (October 23) fixes Proxmox VE update version detection, duplicate access events in the UniFi Access integration, missing Omada controller update fields, and bumps the base image to 2026.10.0. If you run any of those integrations, this patch removes wrong update offers, doubled door events or incomplete controller data.

The 2026.10.4 patch (October 24) raises aiohttp client header limits to 64 KiB and bumps pylutron-caseta to 0.30.0. Our recommendation is to move to 2026.10.4 if you already run the 2026.10 series. Review the release notes, pick a quiet window, and confirm you can roll back through your normal backup workflow.

Home Assistant Cloud Becomes Home Assistant Link

Home Assistant Cloud is being renamed Home Assistant Link. Nabu Casa describes it in its renaming announcement as the same service under a clearer name. The change is planned for the 2026.12 release.

For subscribers, nothing changes in the service itself. You do not need to change remote access, voice or subscription settings because of the name alone. If you keep household documentation or onboarding notes, add a reminder to refresh screenshots after the December release.

matter.js 0.18.0 and Matter 1.6.1: When It Matters for Your Home

matter.js 0.18.0, released October 20, 2026, adds full Matter 1.6.1 software-cluster support and a new controller API. A 1.6.1 feature only helps when both your device and your platform support it, so check both before you buy. The matter.js 0.18.0 release also overhauls Groupcast and enables it by default, and each device endpoint is checked for its required clusters.

The Matter 1.6.1 update itself is a minor maintenance release. Per the matter-smarthome.de coverage, the Connectivity Standards Alliance published it in September 2026 with no new device types. It revises the Groupcast cluster so a controller can send one message to a group instead of one per device. It also updates the Chime device type so it can play preinstalled sounds such as a gong, and it refines access control and camera clusters.

The decision rule is simple. If either side lags, treat the feature as unavailable and do not buy hardware expecting it to unlock. The CSA’s Matter 1.6 newsroom post covers the earlier 1.6 release if you need the background.

OHF Matter Server 1.5.x: Startup, Logging and Aqara Fixes

The Open Home Foundation Matter Server shipped 1.5.4 (October 23) and 1.5.5 (October 24). They speed up startup and fix a stored-TTL problem, and 1.5.5 renames one Aqara LED strip cluster. Update the name in custom configs before you upgrade. The matterjs-server changelog is the primary record.

Version 1.5.4 speeds up node initialization at startup and adds a logger option for the ws-client, which is mostly for integrators and troubleshooting. Version 1.5.5 fixes nodes whose stored discovery TTL was damaged by an older server version, so they load again and no longer make nodes stored after them unavailable at startup. It also renames the custom cluster AqaraLedStripT2Cluster to AqaraLedStripCluster.

If you run custom Aqara LED strip configs, search your automations and custom cluster references for the old T2 name, then switch to AqaraLedStripCluster before you update.

The changelog also records version 1.5.0 (October 20) updating matter.js to 0.18.0, which adds Matter 1.6.1 support. The changelog does not say when Home Assistant’s Matter Server add-on will ship that build, so treat Matter 1.6.1 server support as confirmed in the code and unscheduled for your install.

Earlier Reports Worth Tracking

Two reported items are worth tracking, not acting on. IKEA’s Matter thermostat is reported to begin sales in January 2027, according to the Matter news ticker, which cites a German report. Aliro was named among Time’s 2026 best inventions. Neither is a buying trigger this week.

If you need heat control this winter, buy a current Matter thermostat on compatibility and wiring, not on a future listing. An IoT Business News report from October 13 describes LG and Apple co-developed devices with Matter over Thread on selected models. Apple’s own October 13 press release gives the Home Collection timing: products begin in December 2026, with select accessories in early 2027.

FAQ

Should I update to ESPHome 2026.10.0 this weekend? Yes, after you review the config checks: lights with initial_state:, the removed codec_support_enabled key, IR climate flags, and Sendspin encryption. If you cannot review your YAML now, wait until you can.

What ESP8266 deadline should I calendar? Plan to leave the old PlatformIO path before 2027.4.0. Until then, toolchain: platformio under esp8266: keeps the old behaviour while you test the native default on a spare board.

Which Home Assistant version should I run? Apply 2026.10.4. It follows 2026.10 (October 7) and the patches on October 10, 16 and 23. The 2026.10.3 notes list the Proxmox VE, UniFi Access and Omada fixes, and 2026.10.4 adds the aiohttp and pylutron-caseta changes.

When does Matter 1.6.1 change what I can do? Only when both your device and your platform support the feature you want, such as revised Groupcast, Chime sounds or camera and access-control refinements. matter.js 0.18.0 adds the 1.6.1 software support, but that alone does not turn on features in Home Assistant. Buy for features that ship today.

Do I need to act on the Aqara LED strip or Link renames? Only if you have custom Aqara LED strip clusters. Update AqaraLedStripT2Cluster references to AqaraLedStripCluster before you run matterjs-server 1.5.5 or later. For Home Assistant Link, no action is needed now.

The Bottom Line

Apply Home Assistant 2026.10.4 first, since it is the newest patch in the 2026.10 series. Then audit your ESPHome YAML against the four config checks and the extra validation items, update to ESPHome 2026.10.0, and test OTA on one node. Keep Matter 1.6.1 device features on your watch list until your devices and platform both support them, and put the ESP8266 migration before 2027.4.0 on your calendar.

How This Guide Was Built

This roundup is based on release notes, project changelogs and vendor announcements dated October 7 through October 24, 2026. We did not run these updates on hardware. We checked each version and date against the linked primary sources. Items that come only from a secondary report, such as the IKEA sales timing and the Matter 1.6.1 coverage from matter-smarthome.de, are labeled as reported.

HERO_IMAGE_PROMPT: Cozy smart home workbench with small ESP development boards, a thermostat and a glowing LED strip in soft evening light, no people, no text in image.

ToolBrain — tool reviews, LLM comparisons, and AI workflow guides

Cross-links automatically generated from SmartHome Field Guide.

← Back to guides