ESPHome's November release is now in public testing, and the changelog is worth reading before you hit "update" on a fleet of nodes. Version 2026.11.0 is still a pre-release. The most recent build, 2026.11.0b3, was published on November 9, 2026, according to the b3 release page on GitHub, where it is marked as a pre-release. The changelog on the beta documentation site says plainly that this is a beta release and that details may change before stable. Everything below describes the beta, not a shipped stable build.

There are two kinds of news here. The headline additions are support for an OpenThread Border Router on ESP32, a menu widget for LVGL displays and a new packet interface component. The other kind is less fun: the cycle also removes a batch of options that had already been deprecated, and it rejects a pattern some users rely on, which is deferring actions inside certain component callbacks. External component authors who write addressable LED drivers get one more change of their own.

The status: third beta, no stable date

None of the sources gives a date for the stable 2026.11.0 release, so we won't guess one. The b3 notes are mostly fixes, the kind of work that normally fills the end of a beta cycle:

  • vl53l0x: the time-of-flight sensor component now recovers from a failed I2C read instead of stalling.
  • i2s_audio: a fix for the APLL clock source on ESP32-P4.
  • libretiny: millis(), micros() and delays now run on real time on the RTL8710B, and pin reads in interrupts no longer detach the interrupt on Realtek chips.
  • i2c: interrupts are masked after an error on the classic ESP32.
  • wifi: the IPv6 link-local address is created through lwIP on connect.

If you run LibreTiny-based RTL8710B modules or an ESP32-P4 audio build, the b3 fixes are the reason to test this beta on a bench device now rather than wait for stable.

New: ESP32 as an OpenThread Border Router

The biggest new feature in the changelog is listed under the [openthread] component: "Add ESP32 OpenThread Border Router support". ESPHome already has an openthread component, and this entry extends it to border router operation on ESP32. A border router is the device that connects a Thread mesh to an IP network. The changelog tags this entry as both a new feature and a breaking change, so read it carefully if you already use the openthread component.

The changelog entry, as we read it, doesn't specify which ESP32 variants are supported, whether a separate radio co-processor is needed, or what the required configuration looks like. Do not assume a particular chip combination works until the component documentation for the stable release says so. What we can confirm is that the feature is listed as new in 2026.11.0 and that it is still beta.

New: LVGL menu widget and a packet interface

On the display side, the [lvgl] component gains a menu widget. Anyone who has built a multi-level settings screen on a small touch panel out of buttons, pages and visibility toggles has wanted this. The changelog lists it as a new feature but gives no rendering or memory figures, so we have none to report.

The changelog also lists a new [packet_interface] component, tagged as a new component, new feature and new platform. The changelog line says only "Add packet interface component", so we can't say how it is exposed or whether it changes the existing udp component. Read the component documentation once 2026.11.0 reaches stable before building on it.

Breaking changes, component by component

This section is where the release will catch people out. The beta changelog lists the following breaking changes.

Deprecated options removed

  • [ethernet]: the deprecated clk_mode option is removed. Wired ESP32 boards whose configuration still uses it will likely fail validation until it is replaced with the current option. Check the Ethernet component documentation for the supported syntax.
  • [lvgl]: the deprecated update_on_release option is removed.
  • [nextion]: the deprecated dump_device_info option is removed.
  • [dlms_meter]: the deprecated provider option and the deprecated predefined sensor keys are removed. Smart-meter configurations that relied on a provider preset will need explicit sensor definitions.
  • [qspi_amoled]: the legacy renamed component stub is removed.

All of these were already deprecated, so if you ignored the warnings in your compile logs, this is the release where they are removed.

No more deferred actions in some callbacks

The changelog lists three entries: [mqtt] rejects deferring actions in on_json_message, [haier] rejects deferring actions in on_status_message, and [emontx] passes on_json/on_data data without copies and rejects deferring actions. A deferred action is one that doesn't finish at once and leaves the automation to resume later. In practice, an automation attached to one of these callbacks that waits or pauses partway through will likely no longer be accepted. Such automations may need restructuring, for example by moving the deferred work into a script the callback starts. The changelog doesn't give the reason for the change. Our reading is that these callbacks pass data that may not stay valid once the handler returns, which fits the emontx entry's "without copies" wording, but that is our inference, not the project's stated reason.

Remote receiver changes

Two [remote_base] entries are tagged as breaking. One decodes the full MagiQuest frame and checks its checksum, so MagiQuest receivers may report different output than before. The other fixes NEC command_repeats to send repeat frames, which affects transmit configurations that use that option. If you have IR automations that depend on either, retest them after upgrading.

For external component authors: AddressableLight and ESPColorAccessor

The ESPHome developer blog describes a C++ API change that applies to 2026.11.0 and later. Components that implement the AddressableLight interface must now provide an ESPColorAccessor instead of overriding AddressableLight::get_view_internal(). The post says this improves performance, prevents crashes and gives components more control over how LED strip data is stored and how color correction is applied. It describes the change as a developer breaking change for external components.

The blog says the user-facing API stays backwards-compatible, with one exception: ESPColorSettable::set(ESPHSVColor) and ESPRangeView::set(ESPHSVColor) are deprecated to remove ambiguity, and the existing set_hsv(ESPHSVColor) method should be used instead. This matters most to people who maintain custom LED strip drivers as external components, since a driver that overrides get_view_internal() will need porting. Lambdas that call set() with an HSV colour are the one user-facing pattern to check.

What It Means for Makers

Who it is for: Thread and Matter experimenters who want an ESP32 to act as a border router, and LVGL users building menu-driven touch interfaces. The breaking changes affect a wider group: owners of wired-Ethernet ESP32 boards with older configs, Nextion and DLMS smart-meter users, Haier HVAC and emonTx integrators, MQTT users with complex on_json_message automations, IR remote users, and maintainers of external addressable-light components.

What it replaces or enables: the border router support adds an ESP32 option to a role that Thread setups often fill with other hardware. The LVGL menu widget gives a built-in alternative to hand-built page-switching menus. On the breaking side, the release removes several previously deprecated options, and code that used the old get_view_internal() override must move to ESPColorAccessor.

Price and availability: the sources list no price. ESPHome 2026.11.0 is available only as a beta pre-release, most recently 2026.11.0b3 published on GitHub on November 9, 2026. There is no announced stable date, and the project warns that details may change before stable. The practical advice is to test the beta on one non-critical device, read the validation errors, fix your YAML, and wait for the stable tag before upgrading anything that controls heating, locks or other hardware you depend on.

Sources