Merge branch 'next' into jesserockz-2025-428

Author: bdraco

content/changelog/2025.9.0.md

@@ -27,6 +27,25 @@ developer tools while maintaining backward compatibility for most use cases.
 - **Improved sensor support** with enhanced BL0940 power monitoring capabilities
 - **Component improvements** including restructured Inkplate e-paper display support
 
+<!-- markdownlint-disable-next-line MD026 -->
+## 🎉 Welcome Jonathan to the Open Home Foundation Team!
+
+We're excited to announce that Jonathan ([@swoboda1337](https://github.com/swoboda1337)) has joined the
+Open Home Foundation as a **full-time developer on ESPHome**!
+
+Jonathan has been a long-standing and valued contributor, and now he'll be able to focus fully on building
+ESPHome — helping people create smart homes that are **private, sustainable, and built on open standards**.
+
+This milestone is made possible by the support of our community and the Open Home Foundation's mission to advance
+**open-source smart home technologies** while upholding the principles of **privacy, choice, and sustainability**.
+
+If you'd like to support continued development of ESPHome and other open home projects, consider:
+
+- **Supporting the Open Home Foundation** → [openhomefoundation.org](https://www.openhomefoundation.org/)
+- **Subscribing to Home Assistant Cloud** → [nabucasa.com](https://www.nabucasa.com/) to help fund open-source development
+
+🚀 Welcome to the team, Jonathan — we can't wait to see what you'll help build!
+
 ## MIPI RGB Display Support
 
 ESPHome 2025.9.0 introduces comprehensive support for MIPI RGB displays through the new
@@ -294,6 +313,35 @@ and advanced setups may require updates.
 - [thermostat] General clean-up, optimization, properly support "auto" mode [esphome#10561](https://github.com/esphome/esphome/pull/10561) by [@kbx81](https://github.com/kbx81)
 - [bl0940] extend configuration options of bl0940 device [esphome#8158](https://github.com/esphome/esphome/pull/8158) by [@dan-s-github](https://github.com/dan-s-github) (new-feature) (new-platform)
 - [inkplate] Rename component and fix grayscale [esphome#10200](https://github.com/esphome/esphome/pull/10200) by [@JosipKuci](https://github.com/JosipKuci) (breaking-change)
+- [thermostat] Rename timer enums to mitigate naming conflict [esphome#10666](https://github.com/esphome/esphome/pull/10666) by [@kbx81](https://github.com/kbx81)
+- Improve coverage for various core modules [esphome#10663](https://github.com/esphome/esphome/pull/10663) by [@bdraco](https://github.com/bdraco)
+- Update webserver local assets to 20250910-110003 [esphome#10668](https://github.com/esphome/esphome/pull/10668) by [@esphomebot](https://github.com/esphomebot)
+- [adc] Fix `FILTER_SOURCE_FILES` location [esphome#10673](https://github.com/esphome/esphome/pull/10673) by [@jesserockz](https://github.com/jesserockz)
+- Openthread Fix Factory Reset [esphome#9281](https://github.com/esphome/esphome/pull/9281) by [@rwrozelle](https://github.com/rwrozelle)
+- [core] Add millisecond precision to logging timestamps [esphome#10677](https://github.com/esphome/esphome/pull/10677) by [@bdraco](https://github.com/bdraco)
+- Add comprehensive tests for choose_upload_log_host to prevent regressions [esphome#10679](https://github.com/esphome/esphome/pull/10679) by [@bdraco](https://github.com/bdraco)
+- Add some more coverage for dashboard web_server [esphome#10682](https://github.com/esphome/esphome/pull/10682) by [@bdraco](https://github.com/bdraco)
+- [tests] Add upload_program and show_logs test coverage to prevent regressions [esphome#10684](https://github.com/esphome/esphome/pull/10684) by [@bdraco](https://github.com/bdraco)
+- Add additional coverage for util and writer [esphome#10683](https://github.com/esphome/esphome/pull/10683) by [@bdraco](https://github.com/bdraco)
+- Add additional dashboard and main tests [esphome#10688](https://github.com/esphome/esphome/pull/10688) by [@bdraco](https://github.com/bdraco)
+- [core] fix upload to device via MQTT IP lookup (e.g. when mDNS is disable) [esphome#10632](https://github.com/esphome/esphome/pull/10632) by [@Links2004](https://github.com/Links2004)
+- Add additional test coverage ahead of Path conversion [esphome#10700](https://github.com/esphome/esphome/pull/10700) by [@bdraco](https://github.com/bdraco)
+- [ethernet] Fix permanent component failure from undocumented ESP_FAIL in IPv6 setup [esphome#10708](https://github.com/esphome/esphome/pull/10708) by [@bdraco](https://github.com/bdraco)
+- [core] Optimize MAC address formatting to eliminate sprintf dependency [esphome#10713](https://github.com/esphome/esphome/pull/10713) by [@bdraco](https://github.com/bdraco)
+- [api] Revert unneeded GetTime bidirectional support added in #9790 [esphome#10702](https://github.com/esphome/esphome/pull/10702) by [@bdraco](https://github.com/bdraco)
+- [api] Optimize HelloResponse server_info to reduce memory usage [esphome#10701](https://github.com/esphome/esphome/pull/10701) by [@bdraco](https://github.com/bdraco)
+- [scheduler] Fix timing accumulation in scheduler causing incorrect execution measurements [esphome#10719](https://github.com/esphome/esphome/pull/10719) by [@bdraco](https://github.com/bdraco)
+- ina2xx should be total increasing for energy sensor [esphome#10711](https://github.com/esphome/esphome/pull/10711) by [@mikelawrence](https://github.com/mikelawrence)
+- [md5] Optimize MD5::get_hex() to eliminate sprintf dependency [esphome#10710](https://github.com/esphome/esphome/pull/10710) by [@bdraco](https://github.com/bdraco)
+- [wifi] Optimize WiFi MAC formatting to eliminate sprintf dependency [esphome#10715](https://github.com/esphome/esphome/pull/10715) by [@bdraco](https://github.com/bdraco)
+- [esp32_ble] Optimize BLE hex formatting to eliminate sprintf dependency [esphome#10714](https://github.com/esphome/esphome/pull/10714) by [@bdraco](https://github.com/bdraco)
+- [select] Use const references to avoid unnecessary vector copies [esphome#10741](https://github.com/esphome/esphome/pull/10741) by [@bdraco](https://github.com/bdraco)
+- [dashboard] Fix archive handler to properly delete build folders using correct path [esphome#10724](https://github.com/esphome/esphome/pull/10724) by [@bdraco](https://github.com/bdraco)
+- [ethernet] Conditionally compile PHY-specific code to reduce flash usage [esphome#10747](https://github.com/esphome/esphome/pull/10747) by [@bdraco](https://github.com/bdraco)
+- [mqtt] fix publish payload length when payload contains null characters [esphome#10744](https://github.com/esphome/esphome/pull/10744) by [@jokujossai](https://github.com/jokujossai)
+- [ade7880] fix channel a voltage registry [esphome#10750](https://github.com/esphome/esphome/pull/10750) by [@jokujossai](https://github.com/jokujossai)
+- [wizard] Fix KeyError when running wizard with empty OTA password [esphome#10753](https://github.com/esphome/esphome/pull/10753) by [@bdraco](https://github.com/bdraco)
+- [core] Fix clean build files to properly clear PlatformIO cache [esphome#10754](https://github.com/esphome/esphome/pull/10754) by [@bdraco](https://github.com/bdraco)
 
 </details>
 
@@ -324,6 +372,8 @@ and advanced setups may require updates.
 - Bump aioesphomeapi from 40.0.1 to 40.0.2 [esphome#10641](https://github.com/esphome/esphome/pull/10641) by [@dependabot[bot]](https://github.com/apps/dependabot)
 - Bump pytest-cov from 6.3.0 to 7.0.0 [esphome#10660](https://github.com/esphome/esphome/pull/10660) by [@dependabot[bot]](https://github.com/apps/dependabot)
 - Bump aioesphomeapi from 40.0.2 to 40.1.0 [esphome#10662](https://github.com/esphome/esphome/pull/10662) by [@dependabot[bot]](https://github.com/apps/dependabot)
+- Bump aioesphomeapi from 40.1.0 to 40.2.0 [esphome#10703](https://github.com/esphome/esphome/pull/10703) by [@dependabot[bot]](https://github.com/apps/dependabot)
+- Bump aioesphomeapi from 40.2.0 to 40.2.1 [esphome#10721](https://github.com/esphome/esphome/pull/10721) by [@dependabot[bot]](https://github.com/apps/dependabot)
 
 </details>
 

content/components/_index.md

@@ -1049,6 +1049,7 @@ ESPHome to cellular networks. **Does not encompass Wi-Fi.**
 "Status LED","components/status_led","led-on.svg","dark-invert"
 "Sun","components/sun","weather-sunny.svg","dark-invert"
 "Tuya MCU","components/tuya","tuya.png",""
+"Z-Wave Proxy","components/zwave_proxy","z-wave.svg",""
 {{< /imgtable >}}
 
 ## Cookbook

content/components/esp32.md

@@ -43,14 +43,18 @@ suitable for that variant. Both may be specified (for backwards compatibility) b
 - **partitions** (*Optional*, filename): The name of (optionally including the path to) the file containing the
   partitioning scheme to be used. When not specified, partitions are automatically generated based on `flash_size`.
 
-- **framework** (*Optional*): Options for the underlying framework used by ESPHome. See [Arduino framework](#esp32-arduino_framework)
-  and [ESP-IDF framework](#esp32-espidf_framework).
+- **framework** (*Optional*): Options for the underlying framework used by ESPHome. See [Framework](#esp32-framework).
 
-{{< anchor "esp32-arduino_framework" >}}
+{{< anchor "esp32-framework" >}}
 
-## Arduino framework
+## Framework
 
-This is the default framework for ESP32 chips at the moment.
+ESPHome supports two framework options for ESP32 chips:
+
+### Arduino Framework
+
+The Arduino framework is integrated as an ESP-IDF component. This provides Arduino API compatibility
+within the ESP-IDF build system. Arduino framework is available for ESP32 (classic), ESP32-C3, ESP32-S2, and ESP32-S3 variants.
 
 ```yaml
 # Example configuration entry
@@ -60,32 +64,11 @@ esp32:
     type: arduino
 ```
 
-### Configuration variables
-
-- **version** (*Optional*, string): The base framework version number to use, from
-  [ESP32 arduino releases](https://github.com/espressif/arduino-esp32/releases). Defaults to `recommended`.
-  Additional values are:
-
-  - `dev`  : Use the latest commit from <https://github.com/espressif/arduino-esp32>, note this may break at any time
-  - `latest`  : Use the latest *release* from <https://github.com/espressif/arduino-esp32/releases>, even if it hasn't
-    been recommended yet.
-
-  - `recommended`  : Use the recommended framework version.
-
-- **source** (*Optional*, string): The PlatformIO package or repository to use for framework. This can be used to use a
-  custom or patched version of the framework.
-
-- **platform_version** (*Optional*, string): The version of the
-  [pioarduino/espressif32](https://github.com/pioarduino/platform-espressif32/releases) package to use.
-
-- **advanced** (*Optional*, mapping): See [Advanced Configuration](#esp32-advanced_configuration) below.
-
-{{< anchor "esp32-espidf_framework" >}}
-
-## ESP-IDF framework
+### ESP-IDF Framework
 
-This is an alternative base framework for ESP32 chips; it is recommended for variants of the ESP32 like ESP32S2,
-ESP32S3, ESP32P4 and single-core ESP32 chips.
+ESP-IDF is Espressif's native development framework. It is required for ESP32-C2, ESP32-C5, ESP32-C6,
+ESP32-H2, and ESP32-P4 variants, as these are not supported by the Arduino framework. It is recommended for
+all ESP32 chips when possible. See the {{< docref "/guides/esp32_arduino_to_idf" "migration guide" >}} for help transitioning from Arduino.
 
 ```yaml
 # Example configuration entry
@@ -97,14 +80,15 @@ esp32:
 
 ### Configuration variables
 
+- **type** (*Optional*, string): The framework type, either `esp-idf` or `arduino`. Defaults to `arduino` for ESP32 (classic), ESP32-C3, ESP32-S2, and ESP32-S3. Defaults to `esp-idf` for ESP32-C2, ESP32-C5, ESP32-C6, ESP32-H2, and ESP32-P4 (Arduino is not supported on these variants)
+
 - **version** (*Optional*, string): The base framework version number to use, from
-  [ESP32 ESP-IDF releases](https://github.com/espressif/esp-idf/releases). Defaults to `recommended`.
+  [ESP32 ESP-IDF releases](https://github.com/espressif/esp-idf/releases) or
+  [ESP32 arduino releases](https://github.com/espressif/arduino-esp32/releases). Defaults to `recommended`.
   Additional values are:
 
-  - `dev`  : Use the latest commit from <https://github.com/espressif/esp-idf>, note this may break at any time
-  - `latest`  : Use the latest *release* from <https://github.com/espressif/esp-idf/releases>, even if it hasn't been
-    recommended yet.
-
+  - `dev`  : Use the latest commit, note this may break at any time
+  - `latest`  : Use the latest *release*, even if it hasn't been recommended yet.
   - `recommended`  : Use the recommended framework version.
 
 - **source** (*Optional*, string): The PlatformIO package or repository to use for the framework. This can be used to
@@ -154,9 +138,8 @@ esp32:
   address is not consistent with the burned-in CRC for that MAC address, resulting in an error like
   `Base MAC address from BLK0 of EFUSE CRC error`. **Valid only on original ESP32 with** `esp-idf` **framework.**
 
-- **enable_idf_experimental_features** (*Optional*, boolean): Can be set to `true` to enable experimental features in
-  the ESP-IDF framework. Not valid for the Arduino framework. Use of experimental features may cause instability or
-  other issues.
+- **enable_idf_experimental_features** (*Optional*, boolean): Can be set to `true` to enable experimental features. Use of
+  experimental features may cause instability or other issues.
 
 **LWIP Optimization Options (ESP-IDF only):**
 

content/components/images/z-wave.svg

@@ -104,17 +104,17 @@ hardware interfaces for logging. Many newer boards based on ESP32 variants (such
 are using the ESP's on-board USB hardware peripheral while boards based on older processors (such as
 the original ESP32 or ESP8266) continue to use USB-to-serial bridge ICs for communication.
 
-|          | Arduino   | ESP-IDF           |
-| -------- | --------- | ----------------- |
-| ESP8266  | `UART0`   | N/A               |
-| ESP32    | `UART0`   | `UART0`           |
-| ESP32-C3 | `USB_CDC` | `USB_SERIAL_JTAG` |
-| ESP32-C5 | `USB_CDC` | `USB_SERIAL_JTAG` |
-| ESP32-C6 | `USB_CDC` | `USB_SERIAL_JTAG` |
-| ESP32-P4 | `USB_CDC` | `USB_SERIAL_JTAG` |
-| ESP32-S2 | `USB_CDC` | `USB_CDC`         |
-| ESP32-S3 | `USB_CDC` | `USB_SERIAL_JTAG` |
-| RP2040 | `USB_CDC` | N/A |
+|          | Interface |
+| -------- | --------- |
+| ESP8266  | `UART0`   |
+| ESP32    | `UART0`   |
+| ESP32-C3 | `USB_SERIAL_JTAG` |
+| ESP32-C5 | `USB_SERIAL_JTAG` |
+| ESP32-C6 | `USB_SERIAL_JTAG` |
+| ESP32-P4 | `USB_SERIAL_JTAG` |
+| ESP32-S2 | `USB_CDC`         |
+| ESP32-S3 | `USB_SERIAL_JTAG` |
+| RP2040 | `USB_CDC` |
 
 {{< anchor "logger-log_levels" >}}
 

content/components/logger.md

@@ -17,7 +17,7 @@ It supports two different audio pipelines: announcement and media. Each audio pi
 
 On-device files built directly into the firmware are played without a network connection. Encode on-device files with the configured sample rate, 1 or 2 channels, and 16 bits per sample.
 
-This platform only works on ESP32 based chips using the [ESP-IDF framework](#esp32-espidf_framework).
+This platform only works on ESP32-based chips using the [ESP-IDF framework](#esp32-framework).
 
 {{< warning >}}
 Audio and voice components consume a significant amount of resources (RAM, CPU) on the device.

content/components/media_player/speaker.md

@@ -0,0 +1,95 @@
+---
+description: "Instructions for setting up the Z-Wave Proxy in ESPHome."
+title: "Z-Wave Proxy"
+params:
+  seo:
+    description: Instructions for setting up the Z-Wave Proxy in ESPHome.
+    image: z-wave.svg
+---
+
+The `zwave_proxy` component allows proxying of Z-Wave data frames between a
+[Z-Wave Modem SoC](https://www.silabs.com/wireless/z-wave/800-series-modem-soc) and
+[Z-Wave JS](https://zwave-js.github.io/zwave-js/) via ESPHome's {{< docref "/components/api" >}} over
+the {{< docref "/components/wifi" >}} or {{< docref "/components/ethernet" >}}. This allows for more flexibility when
+placing your Z-Wave hardware within your home.
+
+As the Z-Wave modem SoC communicates via a serial connection, you need to have a [UART](#uart) defined in your ESPHome
+device's configuration.
+
+In addition, the `zwave_proxy` expects to proxy messages via ESPHome's {{< docref "/components/api" >}}; this is also
+required in your configuration.
+
+{{< note >}}
+Number of connections
+
+While ESPHome supports multiple API connections/clients, only a single client may subscribe to and receive proxied
+Z-Wave data frames at any given time.
+
+{{< /note >}}
+
+## Configuration
+
+```yaml
+# Example configuration entry
+zwave_proxy:
+```
+
+- **id** (*Optional*, [ID](#config-id)): Manually specify the ID for the `zwave_proxy`.
+
+## Maximizing performance
+
+Low latency is key to achieving an optimal experience with Z-Wave (or any) wireless devices.
+
+It's important to understand that using the `zwave_proxy` *will* increase latency between your Z-Wave devices and
+Z-Wave JS -- this is simply the consequence of passing messages from one medium to another.
+
+Under near-ideal conditions:
+
+- With a direct serial connection to the Z-Wave modem SoC, latency may be as low as approximately 20 milliseconds (ms).
+- When introducing the Z-Wave proxy component, it's still possible to achieve low latency -- we've seen as low as 35
+  ms! However, in practice, it's more realistic to expect 50-60 ms, assuming decent RF conditions.
+
+In general, any duration less than 100 ms is quite acceptable in terms of latency; this value is generally a good
+target to keep in mind.
+
+## Maximizing reliability
+
+In addition to low latency, reliability is also critical to an optimal experience.
+
+**A wired Ethernet connection will provide the best reliability for the Z-Wave proxy.** Ethernet offers:
+
+- More stable and predictable latency
+- No connection drops or lag due to RF interference
+- Immunity to environmental conditions
+
+### Wi-Fi considerations
+
+Wi-Fi is impacted by:
+
+- Interference from other RF devices
+- Environmental conditions, such as:
+  - People/pets moving around a room
+  - Building construction materials
+  - Air density, quality, and even humidity
+
+These factors can periodically cause momentary signal instability. While Wi-Fi devices typically recover automatically,
+this comes at the expense of temporarily degraded performance (latency) and, in more extreme cases, brief loss of
+connectivity.
+
+If you choose to use Wi-Fi to bridge your Z-Wave modem to Z-Wave JS:
+
+- Confirm that there is a strong, stable Wi-Fi signal available in the location you'll place your Z-Wave proxy.
+- Do not attempt to place your Z-Wave proxy at or near the edge of the coverage area your Wi-Fi router/access point
+  provides. If in doubt, move it closer to your Wi-Fi router/access point.
+- If you find that your Z-Wave devices are not operating reliably, you might try:
+  - moving your Z-Wave proxy closer to your Wi-Fi router/access point.
+  - changing the Wi-Fi channel your Wi-Fi router/access point is using.
+  - getting a better Wi-Fi router/access point. In particular, many ISP-provided Wi-Fi routers are designed to be
+    cost-effective and are not optimized for performance.
+
+## See Also
+
+- {{< docref "/components/api" >}}
+- {{< docref "/components/ethernet" >}}
+- {{< docref "/components/wifi" >}}
+- {{< apiref "zwave_proxy/zwave_proxy.h" "zwave_proxy/zwave_proxy.h" >}}