Merge branch 'current' into next

.github/workflows/lint.yml

@@ -21,7 +21,7 @@ jobs:
     steps:
     - uses: actions/checkout@v4.1.0
     - name: Set up Python 3.8
-      uses: actions/setup-python@v4
+      uses: actions/setup-python@v5
       with:
         python-version: 3.8
     - name: Install dependencies

changelog/2023.11.0.rst

@@ -106,6 +106,12 @@ Release 2023.11.5 - November 28
 - Add 'voice_assistant.connected' condition :esphomepr:`5845` by :ghuser:`jesserockz`
 
 
+Release 2023.11.6 - November 28
+-------------------------------
+
+- Fix write_speaker without speaker in config :esphomepr:`5847` by :ghuser:`jesserockz`
+
+
 Full list of changes
 --------------------
 

components/light/spi_led_strip.rst

@@ -8,8 +8,8 @@ SPI LED Strip Light
 The ``spi_led_strip`` light platform drives one or more SPI interfaced RGB LEDs. These LEDs are often used in strips, where
 each LED is individually addressable. This component requires an SPI interface to be configured.
 
-This component has been tested with APA102 LEDs and should also work with HD107 and SK9822 type LEDs, or any others
-with a similar interface - SPI, 8 bits per colour and BGR ordering.
+This component has been tested with APA102 LEDs and the P9813 LED driver. It should also work with HD107 and SK9822 type 
+LEDs, or any others with a similar interface - SPI, 8 bits per colour and BGR ordering.
 
 .. figure:: images/apa102.jpg
     :align: center

components/remote_transmitter.rst

@@ -343,6 +343,8 @@ This :ref:`action <config-action>` sends an NEC infrared remote code to a remote
     In version 2021.12, the order of transferring bits was corrected from MSB to LSB in accordance with the NEC standard.
     Therefore, if the configuration file has come from an earlier version of ESPhome, it is necessary to reverse the order of the address and command bits when moving to 2021.12 or above.
     For example, address: 0x84ED, command: 0x13EC becomes 0xB721 and 0x37C8 respectively.
+    Additionally, ESPHome does not automatically generate parity bits or pad values to 2 bytes.
+    So, in order to send command 0x0, you need to use 0xFF00 (0x00 being the command and 0xFF being the logical inverse).
 
 .. code-block:: yaml
 
@@ -354,8 +356,8 @@ This :ref:`action <config-action>` sends an NEC infrared remote code to a remote
 
 Configuration variables:
 
-- **address** (**Required**, int): The address to send, see dumper output for more details.
-- **command** (**Required**, int): The NEC command to send.
+- **address** (**Required**, int): The 16-bit address to send, see dumper output for more details.
+- **command** (**Required**, int): The 16-bit NEC command to send.
 - **command_repeats** (*Optional*, int): The number of times the command bytes are sent in one transmission. Defaults to `1`.
 - All other options from :ref:`remote_transmitter-transmit_action`.
 

components/sensor/airthings_ble.rst

@@ -53,6 +53,7 @@ Configuration example:
 
     sensor:
       - platform: airthings_wave_plus
+        name: wave_plus
         ble_client_id: airthings01
         update_interval: 5min # default
         battery_update_interval: 24h # default

components/sensor/dsmr.rst

@@ -419,6 +419,9 @@ or a transistor-based circuit are not feasible options. Here's an example circui
 
 .. figure:: images/dsmr-request-pin-circuit-example.png
 
+When using a type of MCU that provides 5V on the GPIO outputs instead of 3.3V, then use a 330 Ohm
+resistor instead of the 200 Ohm resistor.
+
 .. _sensor-dsmr-improving_reader_results:
 
 Improving reader results

components/sensor/index.rst

@@ -570,7 +570,7 @@ However, if the last value passed through was 100 only values greater than 120 o
 ``or``
 ******
 
-Pass forward a value with the first child filter that returns. Above example
+Pass forward a value with the first child filter that returns. Below example
 will only pass forward values that are *either* at least 1s old or are if the absolute
 difference is at least 5.0.
 

components/sensor/teleinfo.rst

@@ -10,7 +10,7 @@ Component/Hub
 -------------
 
 The ``teleinfo`` component allows you to retrieve data from a
-French electrical counter using Teleinformation (`datasheet <https://www.enedis.fr/sites/default/files/Enedis-NOI-CPT_54E.pdf>`__). It works with Linky electrical
+French electrical counter using Teleinformation (`datasheet <https://www.enedis.fr/media/2035/download>`__). It works with Linky electrical
 counter but also legacy EDF electrical counter.
 
 .. figure:: images/teleinfo-full.jpg

components/time/sntp.rst

@@ -7,6 +7,11 @@ SNTP Time Source
     time:
       - platform: sntp
         id: sntp_time
+        timezone: Europe/Sofia
+        servers:  
+         - 0.pool.ntp.org
+         - 1.pool.ntp.org
+         - 2.pool.ntp.org
 
 
 Configuration variables

guides/configuration-types.rst

@@ -344,7 +344,8 @@ Another way to modularize and reuse your configuration is to use packages. This
 you to put common pieces of configuration in separate files and keep only unique pieces of your
 config in the main yaml file. All definitions from packages will be merged with your main
 config in non-destructive way so you could always override some bits and pieces of package
-configuration.
+configuration. Substitutions in your main config will override substitutions with the same
+name in a package.
 
 Dictionaries are merged key-by-key. Lists of components are merged by component
 ID if specified. Other lists are merged by concatenation. All other config

guides/contributing.rst

@@ -373,6 +373,10 @@ a fork of the repository that you can modify and create git branches on.
     git clone https://github.com/<YOUR_GITHUB_USERNAME>/<REPO_NAME>.git
     # For example: git clone https://github.com/OttoWinter/esphome.git
 
+    # To continue you now need to enter the directory you created above
+    cd <REPO_NAME>
+    # For example: cd esphome
+
     # Add "upstream" remote
     git remote add upstream https://github.com/esphome/<REPO_NAME>.git
     # For example: git remote add upstream https://github.com/esphome/esphome.git

guides/diy.rst

@@ -91,6 +91,7 @@ Custom Components & Code
 - `ZclMqttBridge custom component <https://github.com/HyperReap/zcl_mqtt_bridge>`__ by :ghuser:`HyperReap`
 - `Custom esp32 media player and notifier <https://www.printables.com/model/327708-esphome-nodemcu-esp32-media-player>`__ by :ghuser:`rananna`
 - `Blauberg recuperator S22 controller replacement <https://github.com/Benas09/Blauberg_S22>`__ by :ghuser:`Benas09`
+- `Rheem Econet Water Heater and Furnace Controller <https://github.com/esphome-econet/esphome-econet>`__ by `ESPHome-econet <https://github.com/esphome-econet>`__
 
 Sample Configurations
 ---------------------

guides/migrate_sonoff_tasmota.rst

@@ -8,6 +8,11 @@ Migrating from Tasmota
 Migrating from previous Tasmota setups is very easy. You just need to have
 ESPHome create a binary for you and then upload that in the Tasmota web interface.
 
+Incompatible versions
+---------------------
+WARNING! Migrating via OTA on ESP32, from Tasmota v12 (with boot partition) and up is currently not possible! Trying it could soft-brick your device!
+
+
 Getting the Binary
 ------------------
 

projects/installer.html

@@ -543,7 +543,7 @@
     </li>
     <li>
       The YAML configuration is on
-      <a href="https://github.com/esphome/bluetooth-proxies/">GitHub</a>
+      <a href="https://github.com/esphome/firmware/tree/main/bluetooth-proxy">GitHub</a>
     </li>
   </ul>
 </div>