ESPHome 2026.11 Cuts RAM Use and Adds 30+ Components
ESPHome 2026.11.0 is out, and the November release is aimed squarely at the hardware most smart home tinkerers actually run. Released on November 18, the open-source firmware framework — the software that turns cheap ESP32 and ESP8266 boards into sensors, switches, lights and other Home Assistant-connected devices — spends most of this cycle shrinking its own footprint. Devices get more free memory, automations run as leaner code, and more than 30 new components widen what a single board can do.
ESPHome publishes a release like this every month, and November’s is a framework release: the kind that touches the plumbing underneath everything else rather than adding one headline device. For owners of older ESP8266 boards, which have lived on a tight RAM budget for years, that is good news. For everyone else, the headline is a faster, smaller build — plus a short list of breaking changes worth reading before hitting update.
A RAM diet for the ESP8266 — and every other chip
The biggest theme of 2026.11.0 is memory. ESPHome has moved another large sweep of constant data out of RAM and into flash memory: entity names, device classes, icons, log tags, sensor filter tables, light effect lists, climate presets, alarm codes and dozens of per-driver lookup tables now live in flash on every platform, and are only copied into RAM when a component actually uses them. On the ESP8266, where RAM has always been the scarcest resource, that frees up room previously spent on tables the device rarely touched.
The savings continue beyond the ESP8266. Scheduler timers no longer carry a per-component name string, the boolean flags for cover, fan, valve and lock traits are packed into single bytes, and several components have swapped growing heap vectors for fixed-size buffers. MQTT no longer stores subscription topics it can rebuild on demand, and a long list of components stop copying strings they only read. Individually these are small wins; together they add up to noticeably more headroom on boards that run a dozen sensors at once.
Automations now compile to C++ control flow
The other headline change sits under the hood of ESPHome’s automation engine. Until now, each step of an automation — an if, a choose, a while, a repeat, or a run of simple actions — needed its own action object at runtime. In 2026.11.0 the code generator compiles those steps straight into the generated function as plain C++ control flow.
On a test configuration with eight automations of three actions each, the change saves 1,632 bytes of RAM and 1,216 bytes of flash on the ESP8266, and 1,632 bytes of RAM and 1,628 bytes of flash on ESP32 builds using ESP-IDF. Lambda and script.execute chains no longer grow the stack as they run, either. For a typical home setup with a handful of automations per device, the savings are modest but real — and on a crowded ESP8266, every kilobyte counts.
More than 30 new components
The release adds over thirty new components, including support for the Daikin Madoka BLE controller, USB audio and keyboard, an RTSP server, a VNC client, BLE MIDI, HDMI-CEC, and the ESP32 ULP coprocessor, plus twelve new climate IR platforms and a batch of new sensors, radars and expanders.
The practical upshot is that a single ESP32 can now take on jobs that previously needed extra hardware or a separate project: streaming a camera feed over RTSP, exposing a remote display over VNC, or acting as a USB keyboard. The twelve new climate IR platforms extend ESPHome’s reach as a universal remote for air conditioners and heat pumps, a use case that has quietly become one of its most popular.
An experimental Thread border router
For Matter and Thread watchers, the most interesting line in the release notes is a small one: OpenThread on the ESP32 gains an experimental border router that bridges Thread to Wi-Fi. A Thread border router is the bridge that lets Thread’s low-power mesh network talk to the rest of the home network, and until now that job has mostly belonged to dedicated hubs from Apple, Google and Amazon, or to purpose-built hardware.
An ESP32 running ESPHome as a border router is still experimental, and ESPHome’s own notes flag that OpenThread builds now need ESP-IDF 5.5.5 or newer. But the direction is clear: the same inexpensive board that reads a temperature sensor could eventually also anchor a Thread mesh. Alongside it, the release adds Wi-Fi Easy Connect support on ESP32, caches the DHCP lease across reboots, and lets a device in access-point mode serve its web interface as a captive portal — small quality-of-life fixes for devices that live on flaky home Wi-Fi.
Native over-the-air updates get tougher, too: ESPHome OTA now falls back to UDP when the link is lossy, so firmware uploads finish on Wi-Fi that would previously have stalled the transfer.
Breaking changes to check before you update
As with any framework release, 2026.11.0 carries a short upgrade checklist, and a few items will bite if skipped.
- Sub-devices need a relation. Every entry under
esphome: devices:now needs arelation:field —viafor a separate physical device reached through this node, orchildfor a logical part of the node itself. - ESP-IDF 5.0 is out. The minimum ESP-IDF version rises to 5.1, so remove any pin to a 5.0.x framework version. LibreTiny moves to 1.14.0 and
esp_hostedto 3.1.0. - HTTP requests no longer block scripts.
http_requestactions inside scripts now run without pausing the script, so addmode: queuedormode: parallelwhere repeated runs must not be skipped. - Power meters on Beken chips may read half. A fix stops
hlw8012power meters with short pulses (such as the BL0937) from double-counting each pulse on BK72xx chips. If a plug calibrated on an older release reads half after updating, double thevoltage_dividerand the current calibration. - Internal entities are hidden from REST. The web server no longer exposes internal entities over its REST API; add
include_internal: trueunderweb_server:if you drive them by URL. - Large MQTT messages are dropped. Messages over 8 KB on ESP8266, 16 KB on LibreTiny or 32 KB on ESP32 are now dropped with a warning unless you raise the new
max_payload_sizeoption undermqtt:.
Most users running a typical configuration will not hit any of these, and the release notes say there is nothing else to check before updating beyond the checklist items. But anyone with sub-devices, Beken-based smart plugs, or REST-driven automations should read the list first.
What it means for your smart home
ESPHome rarely makes headlines the way a new speaker or camera does, but it is the firmware layer underneath a large slice of the DIY smart home — the sensors, buttons, blinds controllers and air quality monitors that feed Home Assistant. A release that gives those devices more memory, faster automations and new tricks like an RTSP server or a Thread border router extends the useful life of hardware people already own, including ESP8266 boards that are nearly a decade old.
That longevity is the point. While platform vendors push new hubs every year, ESPHome’s monthly releases keep old boards useful, and 2026.11.0 is a particularly good example: less RAM used, smaller builds, more components, and a Thread bridge on the horizon. If you run ESPHome devices, back up your configuration, skim the breaking changes above, and update — your boards will come back with room to spare.
Source: ESPHome 2026.11.0 release notes.