Merge branch 'next' into hosted_update

Author: swoboda1337

all_automations.json

@@ -287,6 +287,7 @@
     "remote_transmitter.transmit_dish",
     "remote_transmitter.transmit_dooya",
     "remote_transmitter.transmit_drayton",
+    "remote_transmitter.transmit_dyson",
     "remote_transmitter.transmit_haier",
     "remote_transmitter.transmit_jvc",
     "remote_transmitter.transmit_keeloq",

content/automations/_index.md

@@ -7,6 +7,8 @@ params:
     image: auto-fix.svg
 ---
 
+{{< anchor "automation" >}}
+
 Automations are a very powerful aspect of ESPHome; they allow you to easily perform actions given some condition(s).
 
 When you want your ESPHome device to respond to its environment, you use an automation. Here are some examples:

content/automations/actions.md

@@ -253,16 +253,18 @@ on_...:
   - repeat:
       count: 5
       then:
+        - lambda: ESP_LOGI("main", "Turning lights on for iteration [%d]", iteration);
         - light.turn_on: some_light
         - delay: 1s
+        - lambda: ESP_LOGI("main", "Turning lights off for iteration [%d]", iteration);
         - light.turn_off: some_light
         - delay: 10s
 ```
 
 #### Configuration variables
 
 - **count** (**Required**, int): The number of times the action should be repeated. The counter is available to
-  lambdas using the reserved word "iteration".
+  lambdas using the implicit script parameter `iteration`.
 
 - **then** (**Required**, [Action](#config-action)): The action to repeat.
 
@@ -460,7 +462,21 @@ on_...:
 
 - **condition** (**Required**, [condition](#config-condition)): The condition to check.
 
-{{< anchor "lambda_condition" >}}
+### `component.is_idle` Condition
+
+This condition checks if a given component is idle. A component is considered to be idle if it has completed
+setup, has not been marked as failed, and is not currently being called by the loop task. This is useful for
+synchronizing actions with the state of the component, for example, an e-paper display component that requires
+a significant amount of time to update the display panel.
+
+```yaml
+on_...:
+  then:
+    - if:
+        condition:
+          component.is_idle: some_component
+        # ...
+```
 
 ### `lambda` Condition
 

content/changelog/2025.10.0.md

@@ -381,6 +381,21 @@ continue working, but custom components and advanced setups may require updates.
 
 </details>
 
+## Release 2025.10.4 - November 4
+
+<details>
+<summary></summary>
+
+- [uart] Fix order of initialization calls [esphome#11510](https://github.com/esphome/esphome/pull/11510) by [@kbx81](https://github.com/kbx81)
+- Fix the LiberTiny bug with UART pin setup [esphome#11518](https://github.com/esphome/esphome/pull/11518) by [@asergunov](https://github.com/asergunov)
+- [mipi_rgb] Fix rotation with custom model [esphome#11585](https://github.com/esphome/esphome/pull/11585) by [@clydebarrow](https://github.com/clydebarrow) (new-feature)
+- [lvgl] Fix nested lambdas in automations unable to access parameters [esphome#11583](https://github.com/esphome/esphome/pull/11583) by [@bdraco](https://github.com/bdraco)
+- [image] Catch and report svg load errors [esphome#11619](https://github.com/esphome/esphome/pull/11619) by [@clydebarrow](https://github.com/clydebarrow)
+- [lvgl] Fix event for binary sensor [esphome#11636](https://github.com/esphome/esphome/pull/11636) by [@clydebarrow](https://github.com/clydebarrow)
+- [sdl] Fix keymappings [esphome#11635](https://github.com/esphome/esphome/pull/11635) by [@clydebarrow](https://github.com/clydebarrow)
+
+</details>
+
 ## Full list of changes
 
 ### New Features

content/components/_index.md

@@ -167,6 +167,7 @@ Create update entities simplifying management of OTA updates.
 "I²S Audio","components/i2s_audio","i2s_audio.svg",""
 "OpenTherm","components/opentherm","opentherm.png",""
 "SPI Bus","components/spi","spi.svg",""
+"TinyUSB","components/tinyusb","usb.svg","dark-invert"
 "UART","components/uart","uart.svg",""
 "USB Host","components/usb_host","usb.svg","dark-invert"
 "USB UART","components/usb_uart","usb.svg","dark-invert"

content/components/display/epaper_spi.md

@@ -15,28 +15,34 @@ better integration with ESPHome's async architecture.
 The communication method uses 4-wire [SPI](#spi), so you need to have an `spi:` section in your
 configuration.
 
+The driver supports a number of displays and there are also specific configurations for ESP32 boards with integrated displays.
+For those boards the predefined configuration will set the correct pins and dimensions for the display.
+
 ```yaml
 display:
   - platform: epaper_spi
-    cs_pin: GPIOXX
-    dc_pin: GPIOXX
-    busy_pin: GPIOXX
-    reset_pin: GPIOXX
-    model: 7.3in-spectra-e6
+    model: Seeed-reTerminal-E1002
     lambda: |-
       it.filled_circle(it.get_width() / 2, it.get_height() / 2, 50, Color::BLACK);
 ```
 
-## Configuration variables
+## Supported displays
 
-- **cs_pin** (**Required**, [Pin Schema](#config-pin_schema)): The CS pin.
-- **dc_pin** (**Required**, [Pin Schema](#config-pin_schema)): The DC pin.
-- **model** (**Required**): The model of the ePaper display. Currently supported:
+| Model name             | Manufacturer | Product Description                                        |
+|------------------------|--------------|------------------------------------------------------------|
+| Spectra-E6             | Eink         | <https://www.eink.com/brand/detail/Spectra6>               |
+| Seeed-reTerminal-E1002 | Seeed Studio | <https://www.seeedstudio.com/reTerminal-E1002-p-6533.html> |
+
+## Configuration variables
 
-  - `7.3in-spectra-e6` - 7.3" Spectra E6 6-color display (800×480 pixels)
+When using a model defining an integrated ESP32 display board most of the configuration such as the pins and dimensions will be set by default,
+but can be overridden if needed.
 
-- **busy_pin** (*Optional*, [Pin Schema](#config-pin_schema)): The BUSY pin. Defaults to not connected.
-- **reset_pin** (*Optional*, [Pin Schema](#config-pin_schema)): The RESET pin. Defaults to not connected.
+- **model** (**Required**): The model of the ePaper display. See the table above for options.
+- **cs_pin** (**Required**, [Pin Schema](#config-pin_schema)): The CS pin. Predefined for integrated boards.
+- **dc_pin** (**Required**, [Pin Schema](#config-pin_schema)): The DC pin. Predefined for integrated boards.
+- **busy_pin** (*Optional*, [Pin Schema](#config-pin_schema)): The BUSY pin, if used.
+- **reset_pin** (*Optional*, [Pin Schema](#config-pin_schema)): The RESET pin, if used.
   Make sure you pull this pin high (by connecting it to 3.3V with a resistor) if not connected to a GPIO pin.
 
 - **rotation** (*Optional*): Set the rotation of the display. Everything you draw in `lambda:` will be rotated

content/components/display/max7219digit.md

@@ -75,34 +75,24 @@ display:
 - **chip_lines_style** (*Optional*): How are the lines in Multiline Mode connected? Possible values are `zigzag` and `snake`. Defaults to `snake`
 - **flip_x** (*Optional*, boolean): Flip the horizontal axis on the screen. Defaults to `false`.
 
-{{< anchor "display-max7219digit_actions" >}}
-
 ## Actions
 
 The following actions are replicas of the LAMBDA functions shown in the next section.
 
-{{< anchor "display-max7219digit_actions_invert_on_off>" >}}
-
 ### `MAX7219.invert_on` & `MAX7219.invert_off` Action
 
 This action `MAX7219.invert_on` will invert the display. So background pixels are on and texts pixels are
 off. `MAX7219.invert_off` sets the display back to normal. The background pixels are only set at the next update, the pixels drawn in
 the various function like print, line, etc. are directly influenced by the invert command.
 
-{{< anchor "display-max7219digit_actions_turn_on_off" >}}
-
 ### `MAX7219.turn_on` & `MAX7219.turn_off` Action
 
 The display can be switched on and off "dynamically" with the actions `MAX7219.turn_on` & `MAX7219.turn_off`.
 
-{{< anchor "display-max7219digit_actions_reverse_off" >}}
-
 ## `MAX7219.reverse_on` & `MAX7219.reverse_off` Action
 
 With this actions you can reverse the display direction from left to right to right to left.
 
-{{< anchor "display-max7219digit_actions_intensity" >}}
-
 ## `MAX7219.intensity` Action
 
 The intensity of the screen can be set "dynamically" within the lambda code with the following command: it.intensity(`0` .. `15`  ).

content/components/display/mipi_rgb.md

@@ -66,7 +66,7 @@ display:
     id: my_display
 ```
 
-## Configuration variables
+## Configuration options
 
 - **rotation** (*Optional*): Rotate the display presentation in software. Choose one of `0°`, `90°`, `180°`, or `270°`.
   This option cannot be used with `transform`.
@@ -135,7 +135,8 @@ Displays needing a custom init sequence require an SPI bus to be configured, plu
 - **invert_colors** (*Optional*): Inverts the display colors, (white becomes black.) Defaults to false.
 - **color_order** (*Optional*): Should be one of `bgr` (default) or `rgb`.
 - **transform** (*Optional*): Transform the display presentation using hardware. All defaults are `false`.
-  This option cannot be used with `rotation`.
+  This option should not be used with `rotation`. For the `CUSTOM` model, use `transform: disabled`
+  if the display does not support it, which will prevent a `rotation` being translated to a hardware transform.
 
   - **mirror_x** (*Optional*, boolean): If true, mirror the x-axis.
   - **mirror_y** (*Optional*, boolean): If true, mirror the y-axis.

content/components/display/mipi_spi.md

@@ -29,7 +29,7 @@ boards and chips, but the driver is also designed to be customisable in YAML for
 ## Supported boards and driver chips
 
 The driver supports a number of display driver chips, and can be configured for custom displays. As well as support for
-driver chips, there are also specific configurations for several ESP32 boards with integrated displays. For tbose boards
+driver chips, there are also specific configurations for several ESP32 boards with integrated displays. For those boards
 the predefined configuration will set the correct pins and dimensions for the display.
 
 For custom displays, the driver can be configured with the correct pins and dimensions, and the driver chip can be
@@ -42,23 +42,23 @@ using an octal SPI bus, so references here to parallel and octal SPI are equival
 | ----------- | ------------------ |
 | RM690B0     | 320x240            |
 | ILI9341     | 320x240            |
-| ILI9481 | 320x480 |
-| ILI9486 | 320x480 |
-| ILI9488 | 320x480 |
-| ILI9488_A | 320x480 |
-| ST7796 | 320x480 |
-| ST7789V | 240x320 |
-| GC9A01A | 240x240 |
-| GC9D01N | 240x240 |
-| AXS15231 | 320x240 |
-| ST7735 | 128x160 |
-| CO5300 | 466x466 |
-| CUSTOM | Customisable |
+| ILI9481     | 320x480            |
+| ILI9486     | 320x480            |
+| ILI9488     | 320x480            |
+| ILI9488_A   | 320x480            |
+| ST7796      | 320x480            |
+| ST7789V     | 240x320            |
+| GC9A01A     | 240x240            |
+| GC9D01N     | 240x240            |
+| AXS15231    | 320x240            |
+| ST7735      | 128x160            |
+| CO5300      | 466x466            |
+| CUSTOM      | Customisable       |
 
 ### Boards with integrated displays
 
 | Model                                | Manufacturer | Product Description                                               |
-|--------------------------------------| ------------ | ----------------------------------------------------------------- |
+| ------------------------------------ | ------------ | ----------------------------------------------------------------- |
 | ADAFRUIT-S2-TFT-FEATHER              | Adafruit     | <https://www.adafruit.com/product/6312>                           |
 | ADAFRUIT-FUNHOUSE                    | Adafruit     | <https://www.adafruit.com/product/4985>                           |
 | M5CORE                               | M5Stack | <https://docs.m5stack.com/en/core/BASIC%20v2.6> |
@@ -74,7 +74,7 @@ using an octal SPI bus, so references here to parallel and octal SPI are equival
 | JC3636W518                           | Guition | <https://www.aliexpress.com/item/1005007890666293.html> |
 | JC3636W518V2                         | Guition | <https://www.aliexpress.com/item/1005007890666293.html> |
 | LANBON-L8                            | Lanbon | <https://www.lanbon.cn/product/lanbon-l8> |
-| T4-S3-AMOLED                         | Lilygo | <https://www.lilygo.cc/products/t4-s3> |
+| T4-S3                                | Lilygo | <https://www.lilygo.cc/products/t4-s3> |
 | T-EMBED                              | Lilygo | <https://www.lilygo.cc/products/t-embed> |
 | T-DISPLAY                            | Lilygo | <https://www.lilygo.cc/products/t-display> |
 | T-DISPLAY-S3                         | Lilygo | <https://www.lilygo.cc/products/t-display-s3> |
@@ -127,6 +127,8 @@ most of the configuration will be set by default, but can be overridden if neede
 - **invert_colors** (*Optional*, boolean): Specifies whether the display colors should be inverted. Options are `true` or `false`. Defaults to `false`.
 - **rotation** (*Optional*): Rotate the display presentation in software. Choose one of `0°`, `90°`, `180°`, or `270°`. If the driver chip supports hardware rotation for the given orientation this will be translated to the appropriate hardware command. If hardware rotation is not supported, the display will be rotated in software.
 - **transform** (*Optional*): If `rotation` is not sufficient, use this to transform the display. If this option is specified, then the `dimensions` option must also be provided. The value can either be the string `disabled` to disable hardware transform, or a dictionary. Options are:
+  This option should not be used with `rotation`. For the `CUSTOM` model, use `transform: disabled`
+  if the display does not support it, which will prevent a `rotation` being translated to a hardware transform.
 
   - **swap_xy** (**Required**, boolean): If true, exchange the x and y axes.
   - **mirror_x** (**Required**, boolean): If true, mirror the x axis.

content/components/esp32.md

@@ -148,6 +148,10 @@ esp32:
 - **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.
 
+- **loop_task_stack_size** (*Optional*, int): Loop task stack size in bytes. Increase if experiencing stack overflow
+  errors (e.g., with complex code or deep recursion). Higher values reduce heap availability. Valid range is 8192-32768
+  bytes. Defaults to 8192 bytes.
+
 **LWIP Optimization Options (ESP-IDF only):**
 
 The following options are available under the `advanced` section when using the ESP-IDF framework to optimize