Merge branch 'next' into current

Author: NovakIrs

Doxygen

@@ -38,7 +38,7 @@ PROJECT_NAME           = "ESPHome"
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = 2025.5.0
+PROJECT_NUMBER         = 2025.6.0-dev
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a

Makefile

@@ -1,5 +1,5 @@
 ESPHOME_PATH = ../esphome
-ESPHOME_REF = 2025.5.2
+ESPHOME_REF = 2025.6.0b1
 PAGEFIND_VERSION=1.1.1
 PAGEFIND=pagefind
 NET_PAGEFIND=../pagefindbin/pagefind

_static/changelog-2025.6.0.png

@@ -1 +1 @@
-2025.5.2
+2025.7.0-dev

_static/version

@@ -2,7 +2,7 @@ Changelog
 =========
 
 .. redirect::
-    :url: /changelog/2025.5.0.html
+    :url: /changelog/2025.6.0.html
 
 .. toctree::
     :glob:

changelog/2025.6.0.rst

@@ -36,6 +36,7 @@ Configuration variables:
   - **input** (**Required**, string): The id of the binary sensor component
   - **bypass_armed_home** (*Optional*, boolean): This binary sensor will not trigger the alarm when in ``armed_home`` state.
   - **bypass_armed_night** (*Optional*, boolean): This binary sensor will not trigger the alarm when in ``armed_night`` state.
+  - **bypass_auto** (*Optional*, boolean): This binary sensor will be automatically bypassed if left on/open at the time of arming.
   - **trigger_mode** (*Optional*, string): Sets the trigger mode for this sensor. One of ``delayed``, ``instant``, or ``delayed_follower``. (``delayed`` is the default if not specified)
   - **chime** (*Optional*, boolean): When set ``true``, the chime callback will be called whenever the sensor goes from closed to open. (``false`` is the default if not specified)
 

changelog/index.rst

@@ -0,0 +1,142 @@
+ES8388
+======
+
+.. seo::
+    :description: Instructions for using ESPHome's es8388 audio DAC platform to play media from your devices and to configure microphone inputs.
+    :image: es8388.svg
+    :keywords: ES8388, Audio, DAC, I2S, ESP32
+
+The ``es8388`` component allows your ESPHome devices to use the es8388 low power audio codec (`datasheet <http://www.everest-semi.com/pdf/ES8388%20DS.pdf>`__)
+This allows the playback of audio through two channel high performance audio DAC output via the microcontroller from a range of sources via :doc:`/components/speaker/index` or
+:doc:`/components/media_player/index` .
+
+It also allows your ESPHome devices to use the ``es8388``  high performance two channel audio ADC.
+
+This allows attached microphones to be used as a microphone input via :doc:`/components/microphone/i2s_audio`.
+
+The :ref:`I²C bus <i2c>` is required in your configuration as this is used to communicate with the es8388.
+
+Audio DAC
+---------
+
+.. code-block:: yaml
+
+    # Example configuration entry
+    audio_dac:
+     - platform: es8388
+
+Configuration variables:
+************************
+- **address** (*Optional*, int): The I²C address of the driver. Defaults to ``0x10``.
+- **i2c_id** (*Optional*): The ID of the :ref:`I²C bus <i2c>` the ES8388 is connected to.
+- All other options from :ref:`Audio DAC <config-audio_dac>`.
+
+
+Select
+------
+
+The ``es8388`` select allows you to control the ``dac output`` and the ``adc input_mic`` of your :doc:`es8388`.
+
+.. code-block:: yaml
+
+    select:
+      - platform: es8388
+        es8388_id: es8388_parent
+        dac_output:
+          name: "DAC Output"
+        adc_input_mic:
+          name: "ADC Input MIC"
+
+Configuration variables:
+************************
+
+- **es8388_id** (*Optional*, :ref:`config-id`): Manually specify the ID for the :doc:`es8388` component.
+- **dac_output** (*Optional*): Control the DAC Audio output.
+
+  - ``LINE1`` (default)
+  - ``LINE2``
+  - ``BOTH``
+
+  All options from :ref:`Select <config-select>`.
+
+- **adc_input_mic** (*Optional*): Control the ADC Mic Input.
+
+  - ``LINE1`` (default)
+  - ``LINE2``
+  - ``DIFFERENCE``
+
+  All options from :ref:`Select <config-select>`.
+
+
+Automations
+-----------
+
+All :ref:`Audio DAC Automations <automations-audio_dac>` are supported by this platform.
+
+
+Configuration Examples
+----------------------
+
+**ESP32 Audio Kit**:
+
+.. code-block:: yaml
+
+    i2c:
+      sda: GPIO33
+      scl: GPIO32
+      frequency: 100kHz
+      id: bus_a
+
+    audio_dac:
+      - platform: es8388
+        id: es8388_dac
+
+    select:
+      - platform: es8388
+        es8388_id: es8388_dac
+        dac_output:
+          name: "DAC Output"
+        adc_input_mic:
+          name: "ADC Input MIC"
+
+    i2s_audio:
+      id: i2s_output
+      i2s_lrclk_pin: GPIO25
+      i2s_bclk_pin: GPIO27
+      i2s_mclk_pin: GPIO0
+
+    speaker:
+      - platform: i2s_audio
+        i2s_audio_id: i2s_output
+        sample_rate: 48000
+        id: speaker_id
+        i2s_dout_pin: GPIO26
+        bits_per_sample: 32bit
+        dac_type: external
+        channel: stereo
+        buffer_duration: 100ms
+        audio_dac: es8388_dac
+
+    microphone:
+      - platform: i2s_audio
+        i2s_din_pin: GPIO35
+        id: mic1
+        adc_type: external
+        pdm: false
+        sample_rate: 16000
+        bits_per_sample: 16bit
+
+    switch:
+      - platform: gpio
+        pin: GPIO21
+        id: mute_switch
+        name: "AMP Switch"
+        restore_mode: ALWAYS_ON
+
+See Also
+--------
+
+- :doc:`index`
+- :apiref:`es8388/es8388.h`
+- :apiref:`audio_dac/audio_dac.h`
+- :ghedit:`Edit`

components/alarm_control_panel/template.rst

@@ -68,8 +68,10 @@ Advanced options:
 - **disabled_by_default** (*Optional*, boolean): If true, then this entity should not be added to any client's frontend,
   (usually Home Assistant) without the user manually enabling it (via the Home Assistant UI).
   Defaults to ``false``.
-- **publish_initial_state** (*Optional*, boolean): If true, then the sensor will publish its initial state at boot or when
-  HA first connects, depending on the platform.  This means that any applicable triggers will be run. Defaults to ``false``.
+- **trigger_on_initial_state** (*Optional*, boolean): If true, any applicable triggers will be fired when the binary sensor
+  state changes from ``unknown`` to a valid state. This applies to the first valid state set, and any valid state set after
+  a ``binary_sensor.invalidate_state`` action has been excuted. The default is ``false``.
+  **publish_initial_state** (*Optional*, boolean): A deprecated equivalent to ``trigger_on_initial_state``.
 - **entity_category** (*Optional*, string): The category of the entity.
   See https://developers.home-assistant.io/docs/core/entity/#generic-properties
   for a list of available options.
@@ -79,6 +81,27 @@ Advanced options:
 
 .. _binary_sensor-filters:
 
+
+Actions
+-------
+
+.. _binary_sensor-invalidate_state-action:
+
+``binary_sensor.invalidate_state`` Action
+*****************************************
+
+This action will invalidate the current state of the sensor. It is most useful with the Template binary sensor.
+After the state is invalidated, it will be reported to Home Assistant as ``unknown``. Example:
+
+.. code-block:: yaml
+
+    on_...:
+      binary_sensor.invalidate_state: my_binary_sensor_id
+
+
+The state may also be invalidated by an API call in a lambda - see the API reference linked below.
+
+
 Binary Sensor Filters
 ---------------------
 
@@ -274,7 +297,8 @@ Configuration variables: See :ref:`Automation <automation>`.
 
 This automation will be triggered when a new state is received (and thus combines ``on_press``
 and ``on_release`` into one trigger). The new state will be given as the variable ``x`` as a boolean
-and can be used in :ref:`lambdas <config-lambda>`.
+and can be used in :ref:`lambdas <config-lambda>`. It will not be called when the state is invalidated; it will be called when
+the state initially becomes valid only if ``trigger_on_initial_state`` is true.
 
 .. code-block:: yaml
 
@@ -287,6 +311,31 @@ and can be used in :ref:`lambdas <config-lambda>`.
 
 Configuration variables: See :ref:`Automation <automation>`.
 
+.. _binary_sensor-on_state_change:
+
+``on_state_change``
+*******************
+
+An alternative to ``on_state`` that is also triggered when the binary sensor state is invalidated. It is passed two parameters, ``x`` as for ``on_change``
+will be the new value, and ``x_previous`` is the value immediately prior to the change. Both these parameters are of type ``optional<bool>`` so also indicate
+if the values were valid. Note that this is called on all state changes, including initial states.
+
+.. code-block:: yaml
+
+    binary_sensor:
+      - platform: gpio
+        # ...
+        on_state_change:
+          then:
+          - logger.log:
+              format: "Old state was %s"
+              args: ['x_previous.has_value() ? ONOFF(x_previous) : "Unknown"']
+          - logger.log:
+              format: "New state is %s"
+              args: ['x.has_value() ? ONOFF(x) : "Unknown"']
+
+Configuration variables: See :ref:`Automation <automation>`.
+
 .. _binary_sensor-on_click:
 
 ``on_click``

components/audio_dac/es8388.rst

@@ -43,7 +43,7 @@ ESP heap memory (free space, maximum free block size and fragmentation level) an
         cpu_frequency:
           name: "CPU Frequency"
 
-    # Logger must be at least debug (default)
+    # Logger must be configured
     logger:
       level: debug