Merge branch 'next' into feat/#3215_modbus_controller_courtesy_response

Author: jesserockz

changelog/2025.7.0.rst

@@ -460,6 +460,18 @@ Release 2025.7.4 - July 28
     - Fail with old lerp :esphomepr:`9914` by :ghuser:`HeMan`
 
 
+Release 2025.7.5 - August 5
+---------------------------
+
+.. collapse:: Show
+    :open:
+
+    - [lvgl] Bugfix for tileview :esphomepr:`9938` by :ghuser:`clydebarrow`
+    - [api] Fix OTA progress updates not being sent when main loop is blocked :esphomepr:`10049` by :ghuser:`bdraco`
+    - [font] Catch file load exception :esphomepr:`10058` by :ghuser:`clydebarrow`
+    - [i2s_audio] Use high-pass filter for dc offset correction :esphomepr:`10005` by :ghuser:`doobry`
+
+
 Full list of changes
 --------------------
 

components/display/mipi_spi.rst

@@ -56,6 +56,7 @@ Driver chips
     "GC9D01N", "240x240"
     "AXS15231", "320x240"
     "ST7735", "128x160"
+    "CO5300", "466x466"
     "CUSTOM", "Customisable"
 
 Boards with integrated displays
@@ -72,6 +73,7 @@ Boards with integrated displays
     "S3BOXLITE", "Espressif", "https://www.espressif.com/en/products/devkits/esp32-s3-box-lite"
     "WAVESHARE-4-TFT", "Waveshare", "https://www.waveshare.com/4inch-tft-touch-shield.htm"
     "PICO-RESTOUCH-LCD-3.5", "Waveshare", "https://www.waveshare.com/pico-restouch-lcd-3.5.htm"
+    "WAVESHARE-ESP32-S3-TOUCH-AMOLED-1.75", "Waveshare", "https://www.waveshare.com/esp32-s3-touch-amoled-1.75.htm"
     "WT32-SC01-PLUS", "Wireless-Tag", "https://www.wireless-tag.com/portfolio/wt32-sc01-plus/"
     "ESP32-2432S028", "Sunton", "https://www.espressif.com/en/products/devkits/esp32-2432s028"
     "JC3248W535", "Guition", "https://www.aliexpress.com/item/1005007566332450.html"

components/display/ssd1327.rst

@@ -11,7 +11,7 @@ Over I²C
 --------
 
 The ``ssd1327_i2c`` display platform allows you to use
-SSD1327 (`datasheet <https://www.generationrobots.com/media/Ecran_OLED_0_96/SSD1327_datasheet.pdf>`__,
+SSD1327 (`datasheet <https://www.waveshare.com/w/upload/a/ac/SSD1327-datasheet.pdf>`__,
 `Waveshare <https://www.waveshare.com/1.5inch-oled-module.htm>`__) displays with ESPHome. Note that this component is for
 displays that are connected via the :ref:`I²C Bus <i2c>`. If your SSD1327 is connected via the 4-Wire
 :ref:`SPI bus <spi>`, see :ref:`ssd1327-spi`.

components/esp32_ble.rst

@@ -23,6 +23,8 @@ can run.
     esp32_ble:
       io_capability: keyboard_only
       disable_bt_logs: true  # Default, saves flash
+      connection_timeout: 20s  # Default, matches client timeout
+      max_notifications: 12  # Default, increase if needed
 
 Configuration variables:
 ------------------------
@@ -48,6 +50,25 @@ Configuration variables:
 
     The ``disable_bt_logs`` option intelligently disables only the Bluetooth logging categories that are not required by your configuration. Each Bluetooth component registers the specific loggers it needs, and all unused loggers are automatically disabled during compilation. This includes loggers for Classic Bluetooth features (like RFCOMM, A2DP, HID) that are not used by ESPHome's BLE implementation.
 
+- **connection_timeout** (*Optional*, :ref:`config-time`): The maximum time to wait for a BLE connection to be established. Only available when using ESP-IDF framework. Defaults to ``20s``.
+
+  - Range: 10 to 180 seconds
+  - This timeout should align with the timeout used by your BLE client software to prevent connection slot waste
+
+.. note::
+
+    The ``connection_timeout`` option is particularly important when using ESPHome as a Bluetooth proxy. The default of 20 seconds matches the timeout used by aioesphomeapi and bleak-retry-connector. If a connection attempt times out on the client side but ESP-IDF continues trying to connect, the connection slot remains occupied and unavailable for new connections. Setting this to match your client timeout ensures connection slots are freed immediately when a connection fails.
+
+- **max_notifications** (*Optional*, integer): The maximum number of BLE characteristics that can have notifications enabled across all connections. Only available when using ESP-IDF framework. Defaults to ``12``.
+
+  - Range: 1 to 64
+  - This is a global limit shared across all BLE connections
+  - Increase if you see ``ESP_GATT_NO_RESOURCES`` (status=128) errors when enabling notifications
+
+.. note::
+
+    The ``max_notifications`` option controls the ``CONFIG_BT_GATTC_NOTIF_REG_MAX`` ESP-IDF setting. This limit is per GATT client interface, not per connection. If you're using ESPHome as a Bluetooth proxy with multiple devices that have many characteristics requiring notifications, you may need to increase this value. The error ``status=128`` in logs indicates you've hit this limit.
+
 ``ble.disable`` Action
 -----------------------
 

components/espnow.rst

@@ -33,8 +33,7 @@ Configuration variables:
 Automations:
 
 - **on_receive** (*Optional*, :ref:`Automation <automation>`): An automation to perform when data is received. See :ref:`espnow-on_receive`.
-- **on_unknown_peer** (*Optional*, :ref:`Automation <automation>`): An automation to perform when data is received from an unknown peer.
-  Cannot be used when ``auto_add_peer`` is set to ``true``. See :ref:`espnow-on_unknown_peer`.
+- **on_unknown_peer** (*Optional*, :ref:`Automation <automation>`): An automation to perform when data is received from an unknown peer. See :ref:`espnow-on_unknown_peer`.
 - **on_broadcast** (*Optional*, :ref:`Automation <automation>`): An automation to perform when a broadcast packet is received.
   See :ref:`espnow-on_broadcast`.
 
@@ -76,7 +75,7 @@ Configuration variables:
 ``on_unknown_peer``
 *******************
 
-This automation will be triggered when data is received from a peer that is not in the list of known peers.
+This automation will be triggered when data is received from a peer that is not in the list of known peers. This trigger gives you one possibility to decide if the unknown peer can be added or not.
 
 .. _espnow-on_broadcast:
 
@@ -118,14 +117,17 @@ Configuration variables:
 
 - **address** (**Required**, :ref:`templatable <config-templatable>`, MAC Address): The MAC address of the receiving device to send to.
 - **data** (**Required**, :ref:`templatable <config-templatable>`, string or list of bytes): The data to be sent.
-- **on_sent** (*Optional*, :ref:`Automation <automation>`): An automation to perform when the data is sent successfully.
 - **wait_for_sent** (*Optional*, boolean): The automation will wait for the data to be sent and for the ``on_sent`` or ``on_error``
   actions to be finished before continuing with the next action.
   Defaults to ``true``.
-- **on_error** (*Optional*, :ref:`Automation <automation>`): An automation to perform when the data could not be sent.
 - **continue_on_error** (*Optional*, boolean): If set to ``false``, the next action will not be triggered if the data could not be sent.
   Defaults to ``true``.
 
+Automations:
+
+- **on_sent** (*Optional*, :ref:`Automation <automation>`): An automation to perform when the data is sent successfully.
+- **on_error** (*Optional*, :ref:`Automation <automation>`): An automation to perform when the data could not be sent.
+
 
 .. _espnow-broadcast-action:
 
@@ -189,6 +191,24 @@ Configuration variables:
 
 - **address** (**Required**, MAC Address): The Peer address that needs to be removed from the list of allowed peers.
 
+.. _espnow-set_channel-action:
+
+``espnow.set_channel`` Action
+*****************************
+
+This is an :ref:`Action <config-action>` to change the channel that espnow is sending and receiving on.
+
+.. code-block:: yaml
+
+    on_...:
+      - espnow.set_channel:
+          channel: 1
+      - espnow.set_channel: 1
+
+Configuration variables:
+
+- **channel** (**Required**, int): This can be a value between ``0`` and ``15``. The maximum channel number depends on the country or region where you are using the device (for example, channels 1-11 are allowed in the US and most of Europe, 1-13 in many other countries, and 1-14 in Japan). For details, see the `Wi-Fi channel regulations by country <https://en.wikipedia.org/wiki/List_of_WLAN_channels>`__ or consult the `Espressif ESP-NOW documentation <https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-reference/network/esp_now.html>`__. ``0`` means that espnow will set the channel number itself (most of the time it would be ``1``).
+
 
 .. _espnow-peers:
 
@@ -204,6 +224,7 @@ will be an error when trying to send data to a peer.
 Setting ``auto_add_peer`` to ``true`` will allow the component to automatically add any incoming device as a peer, and will
 automatically add any peer that data is sent to.
 
+
 See Also
 --------
 

components/remote_transmitter.rst

@@ -1024,6 +1024,24 @@ Configuration variables:
 
     Toto remotes repeat all codes three times at a 36ms interval. This behavior will occur by default, but may be overridden by specifying ``repeat`` and ``wait time`` configuration variables.
 
+.. _remote_transmitter-digital_write:
+
+``remote_transmitter.digital_write`` **Action**
+***********************************************
+
+This :ref:`action <config-action>` sets the output value of the pin.
+
+.. code-block:: yaml
+
+    on_...:
+      - remote_transmitter.digital_write:
+          value: true
+
+Configuration variables:
+
+- **transmitter_id** (*Optional*, :ref:`config-id`): The remote transmitter to set the pin value on. Defaults to
+  the first one defined in the configuration.
+- **value** (**Required**, bool): The output value of the pin.
 
 .. _remote_transmitter-rc_switch-protocol:
 

components/sensor/ld2450.rst

@@ -285,6 +285,12 @@ Configuration variables:
 - **presence_timeout** (**Required**, int): The duration, in seconds, for which the
   :ref:`presence states<ld2450-binary-sensors>` will persist even after the detection is cleared. Default is ``5``
   seconds. All options from :ref:`Number <config-number>`.
+
+.. note::
+
+    The ``presence_timeout`` value applies *only* to the :ref:`presence binary sensor states<ld2450-binary-sensors>`.
+    It does **not** apply to any other sensor data, such as target count or target details.
+
 - **zone_N** (*Optional*): Configuration for the zone (N = 1 to 3), defined as a rectangular area in front of and
   relative to the sensor. A maximum of three zones can be configured: ``zone_1``, ``zone_2``, ``zone_3``. The zone
   coordinates consist of ``x1``, ``y1`` (near-left) to ``x2``, ``y2`` (far-right) and are specified in
@@ -475,7 +481,7 @@ Here is the complete example configuration for :doc:`ld2450`.
         bluetooth:
           name: "Bluetooth"
         multi_target:
-          name: Multi Target Tracking"
+          name: "Multi Target Tracking"
 
     select:
       - platform: ld2450

components/sensor/ms5611.rst

@@ -6,17 +6,17 @@ MS5611 Atmospheric Pressure Sensor
     :image: ms5611.jpg
     :keywords: MS5611
 
-The ``ms5611`` sensor platform allows you to use your MS5611 atmospheric pressure sensors
-(`hobbytronics`_) temperature and pressure sensors with ESPHome. The :ref:`I²C <i2c>` is
-required to be set up in your configuration for this sensor to work.
+The ``ms5611`` sensor platform allows you to use the MS5611 atmospheric pressure-and-temperature sensor with  
+ESPHome (see the `datasheet`_ for technical details). The :ref:`I²C <i2c>` is required to be set up in your  
+configuration for this sensor to work.
 
 .. figure:: images/ms5611-full.jpg
     :align: center
     :width: 50.0%
 
     MS5611 Atmospheric Pressure Sensor
 
-.. _hobbytronics: http://www.hobbytronics.co.uk/ms5611-altitude-sensor
+.. _datasheet: https://www.te.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Data+Sheet%7FMS5611-01BA03%7FB3%7Fpdf%7FEnglish%7FENG_DS_MS5611-01BA03_B3.pdf%7FCAT-BLPS0036
 
 .. figure:: images/ms5611-ui.png
     :align: center

components/sensor/sensor-filter-delta.rst

@@ -7,7 +7,7 @@ This difference can be calculated in two ways an absolute difference or a percen
 
 If a number is specified, it will be used as the absolute difference required.
 For example if the filter were configured with a value of 2 and the last value passed through was 10,
-only values greater than 12 or less than 8 would be passed through.
+only values greater than or equal to 12 or less than or equal to 8 would be passed through.
 
 .. code-block:: yaml
 
@@ -16,8 +16,9 @@ only values greater than 12 or less than 8 would be passed through.
 
 If a percentage is specified a percentage of the last value will be used as the required difference.
 For example if the filter were configured with a value of 20% and the last value passed through was 10,
-only values greater than 12 or less than 8 would be passed through.
-However, if the last value passed through was 100 only values greater than 120 or less than 80 would be passed through.
+only values greater than or equal to 12 or less than or equal to 8 would be passed through.
+However, if the last value passed through was 100 only values greater than or equal to 120 or less than or
+equal to 80 would be passed through.
 
 .. code-block:: yaml
 

components/stepper/index.rst

@@ -81,6 +81,20 @@ Configuration variables:
               number: GPIOXX
               inverted: true
 
+.. note::
+
+    TMC drivers are pin-compatible with the A4988, but instead of a ``SLEEP`` pin they expose an ``ENABLE`` pin.  
+    When using a TMC driver with the ``a4988`` platform you therefore need to invert the ``sleep_pin``:
+
+    .. code-block:: yaml
+
+        stepper:
+          - platform: a4988
+            # ...
+            sleep_pin:
+              number: GPIOXX
+              inverted: true
+
 ULN2003 Component
 -----------------