Merge branch 'next' into heartbeat

Author: swoboda1337

content/changelog/2025.10.0.md

@@ -3,4 +3,4 @@ description: "Changelog"
 title: "Changelog"
 ---
 
-{{< redirect url="/changelog/2025.9.0.html" >}}
+{{< redirect url="/changelog/2025.10.0.html" >}}

content/changelog/_index.md

@@ -123,6 +123,7 @@ ESPHome-specific components or components supporting ESPHome device provisioning
 "ESP32 BLE Server","components/esp32_ble_server","bluetooth.svg","dark-invert"
 "Bluetooth Proxy","components/bluetooth_proxy","bluetooth.svg","dark-invert"
 "Improv via BLE","components/esp32_improv","improv.svg","dark-invert"
+"Nordic UART Service (NUS)","components/ble_nus","uart.svg",""
 {{< /imgtable >}}
 
 ## Management and Monitoring
@@ -388,6 +389,7 @@ Sensors are organized into categories; if a given sensor fits into more than one
 "HYT271","components/sensor/hyt271","hyt271.jpg","Temperature & Humidity",""
 "Inkbird IBS-TH1 Mini","components/sensor/inkbird_ibsth1_mini","inkbird_isbth1_mini.jpg","Temperature & Humidity",""
 "Internal Temperature","components/sensor/internal_temperature","thermometer.svg","Temperature","dark-invert"
+"LM75B","components/sensor/lm75b","lm75b.jpg","Temperature",""
 "LPS22","components/sensor/lps22","lps22.webp","Temperature & Barometric Pressure",""
 "MCP9808","components/sensor/mcp9808","mcp9808.jpg","Temperature",""
 "MH-Z19","components/sensor/mhz19","mhz19.jpg","CO₂ & Temperature",""
@@ -725,6 +727,7 @@ Often known as "tag" or "card" readers within the community.
 "MIPI DSI Displays","components/display/mipi_dsi","tab5.jpg"
 "MIPI RGB Displays","components/display/mipi_rgb","indicator.jpg"
 "MIPI SPI Displays","components/display/mipi_spi","t4-s3.jpg"
+"ePaper SPI Displays","components/display/epaper_spi","epaper.svg"
 "ILI9xxx","components/display/ili9xxx","ili9341.jpg"
 "ILI9341","components/display/ili9xxx","ili9341.svg"
 "ILI9342","components/display/ili9xxx","ili9342.svg"

content/changelog/images/changelog-2025.10.0.png

@@ -38,6 +38,7 @@ api:
   batch_delay: 50ms  # Reduce latency for real-time applications
   listen_backlog: 2  # Allow 2 pending connections in queue
   max_connections: 6  # Allow up to 6 simultaneous connections
+  max_send_queue: 10  # Maximum queued messages per connection before disconnect
   encryption:
     key: "YOUR_ENCRYPTION_KEY_HERE"
   reboot_timeout: 30min
@@ -56,6 +57,15 @@ api:
   > RAM available (ESP8266 typically has around 40KB of free RAM after boot, but this can drop to under 20KB once sensors and other components are configured; RP2040 uses LWIP raw sockets with similar constraints), so be careful not to set this value too high or it may cause out-of-memory crashes.
   > The defaults are set to balance memory usage with allowing multiple simultaneous connections.
 
+- **max_send_queue** (*Optional*, int): The maximum number of messages that can be queued for sending per connection before the connection is dropped. Must be between 1 and 64.
+  Defaults to `5` for ESP8266/RP2040, `8` for ESP32/BK72xx/RTL87xx/LN882x, `16` for host platform. This prevents memory exhaustion when a client is slow or network-stalled.
+  Each queued message uses approximately 8-12 bytes of overhead plus the message size.
+
+  > [!NOTE]
+  > When the send queue is full for a connection, the device will log an error and disconnect that client to prevent out-of-memory crashes.
+  > Slow clients, poor WiFi connections causing retries, or network congestion may trigger this. Increase this value if legitimate clients are being disconnected, but be mindful
+  > of memory constraints on embedded devices.
+
 - **encryption** (*Optional*): If present, encryption will be enabled for the API. Using encryption helps to secure the
   communication between the device running ESPHome and the connected client(s).
 
@@ -105,6 +115,10 @@ api:
 Before using any of the actions below, you'll need to tell Home Assistant to allow your device to
 perform actions.
 
+> [!NOTE]
+> Starting with ESPHome 2025.10.0, you can configure actions to receive and process responses from
+> Home Assistant using `capture_response`, `on_success`, and `on_error`. See [Action Response Handling](#action-response-handling) for details.
+
 Open the ESPHome integration page on your Home Assistant instance:
 
 [![Open your Home Assistant instance and show the ESPHome integration.](https://my.home-assistant.io/badges/integration.svg)](https://my.home-assistant.io/redirect/integration/?domain=esphome)
@@ -192,6 +206,20 @@ on_...:
 - **variables** (*Optional*, mapping): Optional variables that can be used in the `data_template`.
   Values are [lambdas](#config-lambda) and will be evaluated before sending the request.
 
+- **capture_response** (*Optional*, boolean): Enable capturing the response from the Home Assistant action call.
+  When enabled, `on_success` must be configured. Defaults to `false`.
+
+- **response_template** (*Optional*, [templatable](#config-templatable), string): Optional Jinja template to process
+  the action response data. This template is evaluated on the Home Assistant side with Home Assistant's templating engine.
+  Requires `capture_response: true`.
+
+- **on_success** (*Optional*, [Automation](#automation)): Optional automation to execute when the Home Assistant action
+  call succeeds. When `capture_response: true`, the response data is available as a `response` variable of type `JsonObjectConst`.
+  See [Action Response Handling](#action-response-handling).
+
+- **on_error** (*Optional*, [Automation](#automation)): Optional automation to execute when the Home Assistant action
+  call fails. See [Action Response Handling](#action-response-handling).
+
 Data structures are not possible, but you can create a script in Home Assistant and call with all
 the parameters in plain format.
 
@@ -225,6 +253,74 @@ on_...:
         blue: '71'
 ```
 
+#### Action Response Handling
+
+> [!NOTE]
+> Action response handling is available in ESPHome 2025.10.0 and later.
+
+You can configure actions to receive and process responses from Home Assistant. This enables bidirectional
+communication where ESPHome can not only call Home Assistant actions but also handle their responses.
+
+##### Basic Success/Error Handling
+
+Use `on_success` and `on_error` to respond to action completion:
+
+```yaml
+on_...:
+  - homeassistant.action:
+      action: light.toggle
+      data:
+        entity_id: light.demo_light
+      on_success:
+        - logger.log: "Toggled demo light"
+      on_error:
+        - logger.log: "Failed to toggle demo light"
+```
+
+##### Capturing Response Data
+
+To capture and process response data from actions, set `capture_response: true`. When enabled, `on_success` must be configured
+and the response data is available as a [`JsonObjectConst`](https://arduinojson.org/v7/api/jsonobjectconst/) variable named `response`.
+
+```yaml
+# Example: Get weather forecast and parse JSON response
+on_...:
+  - homeassistant.action:
+      action: weather.get_forecasts
+      data:
+        entity_id: weather.forecast_home
+        type: hourly
+      capture_response: true
+      on_success:
+        - lambda: |-
+            JsonObjectConst next_hour = response["response"]["weather.forecast_home"]["forecast"][0];
+            float next_temperature = next_hour["temperature"].as<float>();
+            ESP_LOGI("weather", "Temperature next hour: %.1f", next_temperature);
+```
+
+##### Using Response Templates
+
+Use `response_template` to extract and format data from complex responses using Home Assistant's Jinja templating engine.
+This requires `capture_response: true`.
+
+```yaml
+# Example: Extract temperature using a template
+on_...:
+  - homeassistant.action:
+      action: weather.get_forecasts
+      data:
+        entity_id: weather.forecast_home
+        type: hourly
+      capture_response: true
+      response_template: "{{ response['weather.forecast_home']['forecast'][0]['temperature'] }}"
+      on_success:
+        - lambda: |-
+            float temperature = response["response"].as<float>();
+            ESP_LOGI("weather", "Temperature next hour: %.1f", temperature);
+```
+
+When `response_template` is used, the processed result is available in `response["response"]`.
+
 {{< anchor "api-homeassistant_tag_scanned_action" >}}
 
 ### `homeassistant.tag_scanned` Action

content/components/_index.md

@@ -0,0 +1,39 @@
+---
+description: "Nordic UART Service (NUS)"
+title: "Nordic UART Service (NUS)"
+params:
+  seo:
+    description: BLE UART support using Nordic UART Service (NUS) for ESPHome logging and communication.
+    image: uart.svg
+---
+
+The BLE NUS component provides a Bluetooth Low Energy UART interface based on the Nordic UART Service.
+It can be used to stream logs or enable custom bidirectional communication with ESPHome.
+
+```yaml
+# Example configuration entry
+ble_nus:
+  type: logs
+```
+
+## Configuration variables
+
+- **type** (**Required**, string): Mode of operation. Must be set to ``logs`` to stream ESPHome logs over the BLE UART.
+
+## Usage
+
+To connect and view logs from the device over BLE:
+
+```bash
+esphome logs d.yaml --device BLE
+```
+
+Or connect to a specific BLE address:
+
+```bash
+esphome logs d.yaml --device 00:11:22:33:44:55
+```
+
+## See Also
+
+- Nordic UART Service <https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/libraries/bluetooth/services/nus.html>

content/components/api.md

@@ -54,7 +54,7 @@ bluetooth_proxy:
   Each configured slot consumes ~1KB of RAM, with a maximum of `9`. It is recommended not to exceed `5`
   connection slots to avoid memory issues. Defaults to `3`.
   The value must not exceed the total configured `max_connections`
-  for {{< docref "esp32_ble_tracker/" >}}.
+  for {{< docref "esp32_ble/" >}}.
 
 The Bluetooth proxy depends on {{< docref "esp32_ble_tracker/" >}} so make sure to add that to your configuration.
 

content/components/ble_nus.md

@@ -216,11 +216,12 @@ climate:
 
 ### `toshiba`
 
-- **model** (*Optional*, string): There are two valid models
+- **model** (*Optional*, string): There are four valid models:
 
   - `GENERIC`  : Temperature range is from 17 to 30 (default)
   - `RAC-PT1411HWRU-C`  : Temperature range is from 16 to 30; unit displays temperature in degrees Celsius
   - `RAC-PT1411HWRU-F`  : Temperature range is from 16 to 30; unit displays temperature in degrees Fahrenheit
+  - `RAS-2819T`  : Temperature range is from 18 to 30; supports two-packet IR protocol
 
 > [!NOTE]
 >
@@ -237,9 +238,22 @@ climate:
 >   internal temperature sensor; a value of 30 seconds seems to work well. See {{< docref "/components/sensor" >}}
 >   for more information.
 >
+> - The `RAS-2819T` model uses a two-packet IR protocol where most commands send a primary packet (containing
+>   temperature, mode, and fan speed) followed by a secondary packet (containing fan speed confirmation and
+>   mode-specific data). Single-packet commands are used for power-off and swing toggle operations.
+>
 > - This climate IR component is also known to work with Midea model MAP14HS1TBL and may work with other similar
 >   models, as well. (Midea acquired Toshiba's product line and re-branded it.)
 
+```yaml
+# Example configuration entry for RAS-2819T
+climate:
+  - platform: toshiba
+    name: "Toshiba AC"
+    model: RAS-2819T
+    sensor: room_temperature
+```
+
 {{< anchor "whirlpool" >}}
 
 ### `whirlpool`

content/components/bluetooth_proxy.md

@@ -161,8 +161,8 @@ Got all that? Great. Let's take a closer look at some configuration.
 The thermostat controller uses the sensor to determine whether it should heat or cool.
 
 - **sensor** (**Required**, [ID](#config-id)): The sensor that is used to measure the current temperature.
-- **humidity_sensor** (*Optional*, [ID](#config-id)): If specified, this sensor is used to measure the current humidity.
-  This is used for information only and does not influence temperature control.
+- **humidity_sensor** (*Optional*, [ID](#config-id)): The sensor that is used to measure the current humidity.
+  This may be used for humidity control; see [Humidity Control Actions](#humidity-control-actions).
 
 ### Heating and Cooling Actions
 
@@ -296,6 +296,20 @@ These should be used to control the fan only, if available.
 - **swing_both_action** (*Optional*, [Action](#config-action)): The action to call when the fan
   should oscillate in horizontal and vertical directions.
 
+### Humidity Control Actions
+
+These are triggered when the humidity control action is changed by the thermostat controller. It can trigger actions
+to activate humidification **or** dehumidification.
+
+- **humidity_control_dehumidify_action** (*Optional*, [Action](#config-action)): The action to call when
+  dehumidification is required.
+
+- **humidity_control_humidify_action** (*Optional*, [Action](#config-action)): The action to call when
+  humidification is required.
+
+- **humidity_control_off_action** (*Optional*, [Action](#config-action)): The action to call when
+  (de)humidification should stop. This action is **required** when either of the above actions are configured.
+
 ## Advanced Configuration/Behavior
 
 ### Set Point Options/Behavior
@@ -467,6 +481,9 @@ climate:
 
 ### Additional Actions/Behavior
 
+- **target_humidity_change_action** (*Optional*, [Action](#config-action)): The action to call when the
+  thermostat's target humidity is changed.
+
 - **target_temperature_change_action** (*Optional*, [Action](#config-action)): The action to call when the
   thermostat's target temperature(s) is/are changed.
 
@@ -544,6 +561,9 @@ the range of allowed temperature values in the thermostat component. See {{< doc
 - **heat_overrun** (*Optional*, float): The minimum temperature differential (heating beyond the set point)
   before calling the idle [action](#config-action). Defaults to 0.5 °C.
 
+- **humidity_hysteresis** (*Optional*, float): The maximum humidity differential (above/below the set point)
+  before calling the respective humidity control [action](#config-action). Defaults to 1%.
+
 > [!NOTE]
 >
 > - While this platform uses the term temperature everywhere, it can also be used to regulate other values.

content/components/climate/climate_ir.md

@@ -88,6 +88,17 @@ sensor:
 
 - **cpu_frequency** (*Optional*): Reports the CPU frequency in Hz. All options from [Sensor](#config-sensor).
 
+## Zephyr
+
+The component enables debugging features for ESPHome devices running on the Zephyr RTOS.
+It helps with low-level firmware debugging using **SWD (Serial Wire Debug)**. It enables:
+
+- **Thread Awareness in GDB**  
+Injects Zephyr thread metadata so that all active threads can be inspected via GDB when connected over SWD.
+
+- **Real-Time Logging over RTT**  
+Enables logging output over **SEGGER RTT** (Real Time Transfer), allowing non-intrusive debug logs through SWD.
+
 ## See Also
 
 - [Sensor Filters](#sensor-filters)