Merge branch 'current' into next

changelog/2022.9.0.rst

@@ -36,6 +36,10 @@ A new Factory Reset switch and button has been added this release, allowing rese
 as counters, restored values, and more importantly, the wifi credentials of a device that has been set up
 using the captive portal such as pre-flashed devices you would have purchased.
 
+Release 2022.9.1 - September 22
+-------------------------------
+
+- Revert "fix spi timing issues" :esphomepr:`3838` by :ghuser:`jesserockz`
 
 Full list of changes
 --------------------

components/bluetooth_proxy.rst

@@ -5,7 +5,7 @@ Bluetooth Proxy
     :description: Instructions for setting up the Bluetooth Proxy in ESPHome.
     :image: bluetooth.svg
 
-Home Assistant can expand it's Bluetooth reach by communicating through
+Home Assistant can expand its Bluetooth reach by communicating through
 the Bluetooth proxy component in ESPHome. Place your ESPHome devices close to the
 Bluetooth devices that you want to interact with for the best
 experience.
@@ -41,4 +41,5 @@ See Also
 
 - :doc:`esp32_ble_tracker`
 - :apiref:`bluetooth_proxy/bluetooth_proxy.h`
+- BTHome `<https://bthome.io/>`__
 - :ghedit:`Edit`

components/climate/thermostat.rst

@@ -169,6 +169,45 @@ The thermostat controller uses the sensor to determine whether it should heat or
 
 - **sensor** (**Required**, :ref:`config-id`): The sensor that is used to measure the current temperature.
 
+Default Target Temperatures and Mode
+************************************
+
+These configuration items determine default values the thermostat controller should use when it starts.
+
+- **default_mode** (*Optional*, *Deprecated*, climate mode): The default climate mode the controller should
+  use if it is unable to restore it from memory. One of:
+
+  - ``off`` (default)
+  - ``heat_cool``
+  - ``cool``
+  - ``heat``
+  - ``dry``
+  - ``fan_only``
+  - ``auto``
+
+This value is used the first time your device starts after ESPHome is initially installed onto it. Add
+this option into your configuration if you want your thermostat component to start in a climate mode other
+than ``off``.  If this option is not configured, you'll need to manually change the climate mode later via
+the front end (Home Assistant), an ESPHome action, automation, or from within a lambda elsewhere in your
+device's configuration.
+
+- **default_target_temperature_low** (*Optional*, float): The default low target
+  temperature for the control algorithm. This can be dynamically set in the frontend later.
+- **default_target_temperature_high** (*Optional*, float): The default high target
+  temperature for the control algorithm. This can be dynamically set in the frontend later.
+
+**At least one of** ``default_target_temperature_low`` **and** ``default_target_temperature_high``
+**must be specified.**
+
+.. note::
+
+    **default_mode**, **default_target_temperature_low**, and **default_target_temperature_high** are
+    being removed in a future release. In the future you will need to migrate your configuration to using
+    a :ref:`preset <thermostat-preset>` which will allow for more flexibility and customisation
+
+Note that ``min_temperature`` and ``max_temperature`` from the base climate component are used to define
+the range of allowed temperature values in the thermostat component. See :doc:`/components/climate/index`.
+
 Heating and Cooling Actions
 ***************************
 
@@ -299,19 +338,19 @@ experience and automation.
 
 - **preset**: (*Optional*, list)
 
-  - **name** (*Required*, string): Name of the preset. If this is one of the *standard* presets (``eco``, ``away``, 
+  - **name** (*Required*, string): Name of the preset. If this is one of the *standard* presets (``eco``, ``away``,
     ``boost``, ``comfort``, ``home``, ``sleep``, or ``activity``) it is considered a *standard* preset. Any other
     string will make the preset a *custom* preset. *Standard* and *custom* presets are functionally equivalent,
     the only difference is that when switching the mode via :ref:`climate.control Action <climate-control_action>`
-    you will need to use the `preset` or `custom_preset` property as appropriate. The Home Assistant 
+    you will need to use the `preset` or `custom_preset` property as appropriate. The Home Assistant
     `climate.set_preset_mode` service treats them identically
-  - **default_target_temperature_low** (*Optional*, float): The default low target temperature when switching to 
+  - **default_target_temperature_low** (*Optional*, float): The default low target temperature when switching to
     this preset
   - **default_target_temperature_high** (*Optional*, float): The default high target temperature when switching
     to this preset.
   - **mode** (*Optional*, climate mode): The mode the thermostat should switch to when this preset is activated.
     If not specified, the thermostat's mode will remain unchanged when the preset is activated. One of:
-  
+
     - ``heat_cool``
     - ``cool``
     - ``heat``
@@ -334,7 +373,7 @@ experience and automation.
   - **swing_mode** (*Optional*, climate swing mode): The fan swing mode the thermostat should switch to when this
     preset is activated. If not specified, the thermostat's fan swing mode will remain unchanged when the preset
     is activated. One of:
-    
+
     - ``off``
     - ``both``
     - ``horizontal``
@@ -504,7 +543,7 @@ Hysteresis Values
 
     - While this platform uses the term temperature everywhere, it can also be used to regulate other values.
       For example, controlling humidity is also possible with this platform.
-    - ``min_temperature`` and ``max_temperature`` from the base climate component are used the define the range of 
+    - ``min_temperature`` and ``max_temperature`` from the base climate component are used the define the range of
       adjustability and the defaults will probably not make sense for control of things like humidity. See
       :doc:`/components/climate/index`.
 

components/cover/feedback.rst

@@ -198,7 +198,7 @@ Most options can be left untouched, but some modifications are needed:
           id: open_binary_sensor
           sensor_id: open_current_sensor
           threshold: 0.5
-          filter:
+          filters:
             - delayed_off: 0.8s
         - platform: analog_threshold
           id: open_obstacle_binary_sensor

components/cover/index.rst

@@ -200,7 +200,7 @@ Lambdas
 From :ref:`lambdas <config-lambda>`, you can access the current state of the cover (note that these
 fields are read-only, if you want to act on the cover, use the ``make_call()`` method as shown above).
 
-- ``position``: Retrieve the current position of the cover, as a value between ``0.0`` (open) and ``1.0`` (closed).
+- ``position``: Retrieve the current position of the cover, as a value between ``0.0`` (closed) and ``1.0`` (open).
 
     .. code-block:: cpp
 

components/cover/time_based.rst

@@ -64,6 +64,13 @@ Configuration variables:
     The stop button on the UI is always enabled even when the cover is stopped and each press
     on the button will cause the ``stop_action`` to be performed.
 
+.. note::
+
+    The state of the cover can be restored from flash after a node reboot, with 
+    ``esp8266_restore_from_flash: true`` option set. 
+    See :doc:`esp8266_restore_from_flash </components/esphome>` for details.
+
+
 
 See Also
 --------

components/display/tm1621.rst

@@ -80,7 +80,7 @@ Please see :ref:`display-printf` for a quick introduction into the ``printf`` fo
 Also we have five function to display or not some unites:
   - °C on the first line : ``display_celsius(bool)``
   - °F on the first line : ``display_fahrenheit(bool)``
-  - %HR on the second line : ``display_fahrenheit(bool)``
+  - %HR on the second line : ``display_humidity(bool)``
   - V on the first line and A on the second line : ``display_voltage(bool)``
   - kW/h on the first line and W on the second line : ``display_kwh(bool)``  
 

components/sensor/rotary_encoder.rst

@@ -23,7 +23,7 @@ a better understanding of these sensors.
     :align: center
     :width: 75.0%
 
-To use rotary encoders in ESPHome, first identify the two pins encoding th step value.
+To use rotary encoders in ESPHome, first identify the two pins encoding the step value.
 These are often called ``CLK`` and ``DT`` as in above image. Note if the values this sensor
 outputs go in the wrong direction, you can just swap these two pins.
 
@@ -57,7 +57,7 @@ Configuration variables:
   The second pin for determining the step value. Must not be a pin from an external I/O expander.
 - **name** (**Required**, string): The name of the rotary encoder sensor.
 - **pin_reset** (*Optional*, :ref:`Pin Schema <config-pin_schema>`):
-  An optional pin that resets the step value. This is useful with rotary encoders that have have a
+  An optional pin that resets the step value. This is useful with rotary encoders that have a
   third pin. Defaults to no reset pin.
 - **resolution** (*Optional*, string): The resolution of the sensor, this controls how many
   pulses are generated by one step:
@@ -72,7 +72,7 @@ Configuration variables:
 - **max_value** (*Optional*, int): The maximum value this rotary encoder will go to, turning
   the knob further will not increase the number. Defaults to no maximum.
 - **publish_initial_value** (*Optional*, boolean): Controls whether the value is published
-  upon start of ESPHome. By default the value is only published when it changes, causing an
+  upon start of ESPHome. By default, the value is only published when it changes, causing an
   "unknown" value at first. If you set this option to true, the value is published once after
   boot and when it changes. Defaults to ``false``.
 - **restore_mode** (*Optional*): Control how the Rotary Encoder attempts to restore state on bootup.

components/sensor/template.rst

@@ -37,7 +37,7 @@ Configuration variables:
   Lambda to be evaluated every update interval to get the new value of the sensor
 - **update_interval** (*Optional*, :ref:`config-time`): The interval to publish the value of the
   sensor, either the result of the lambda function or if no lambda function the last value
-  published using the publish action. Defaults to ``60s``.
+  published using the publish action. Set to ``never`` to disable updates. Defaults to ``60s``.
 - **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation.
 - All other options from :ref:`Sensor <config-sensor>`.
 

components/sensor/ufire_ec.rst

@@ -38,14 +38,12 @@ Configuration variables:
 - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas.
 - **temperature_sensor** (*Optional*, :ref:`config-id`): Set the ID of the temperature
   sensor. Only needed if the onboard temperature sensor is not used.
-- **ec** (*Optional*, :ref:`Sensor <config-sensor>`): Set the EC sensor configuration.
-- **temperature** (*Optional*, :ref:`Sensor <config-sensor>`): Set the onboard temperature sensor configuration.
-  Can't be used together with ``temperature_sensor``.
+- **ec** (*Optional*, :ref:`Sensor <config-sensor>`): Set the EC sensor configuration. All options from :ref:`Sensor <config-sensor>`.
+- **temperature** (*Optional*, :ref:`Sensor <config-sensor>`): Set the onboard temperature sensor configuration. All options from :ref:`Sensor <config-sensor>`.
 - **temperature_compensation** (*Optional*, float): Set the temperature compensation for the EC
   sensor. Defaults to ``21.0``.
 - **temperature_coefficient** (*Optional*, float): Set the temperature coefficient for the EC
   sensor. Defaults to ``0.019``.
-- All other options from :ref:`Sensor <config-sensor>`.
 
 .. _sensor-ufire_ec-calibrate_probe_action:
 
@@ -76,7 +74,7 @@ Configuration options:
 - **solution** (**Required**, float): Solution reference EC value.
 - **temperature** (**Required**, float): Solution current temperature.
 
-.. _sensor-ufire_ec-reset:
+.. _sensor-ufire_ec-reset_action:
 
 ``sensor.ufire_ec.reset`` Action
 --------------------------------

guides/supporters.rst

@@ -375,7 +375,6 @@ Contributors
 - `hreintke (@hreintke) <https://github.com/hreintke>`__
 - `Jan Hubík (@hubikj) <https://github.com/hubikj>`__
 - `Huub Eikens (@huubeikens) <https://github.com/huubeikens>`__
-- `Petr Urbánek (@HyperReap) <https://github.com/HyperReap>`__
 - `Arjan Filius (@iafilius) <https://github.com/iafilius>`__
 - `Adrián Panella (@ianchi) <https://github.com/ianchi>`__
 - `Ian Leeder (@ianleeder) <https://github.com/ianleeder>`__
@@ -560,6 +559,7 @@ Contributors
 - `Matteo Franceschini (@matteofranceschini) <https://github.com/matteofranceschini>`__
 - `Matthew Mazzanti (@matthewmazzanti) <https://github.com/matthewmazzanti>`__
 - `matthias882 (@matthias882) <https://github.com/matthias882>`__
+- `Matus Ivanecky (@maty535) <https://github.com/maty535>`__
 - `Maurice Schleußinger (@maurice-schleussinger) <https://github.com/maurice-schleussinger>`__
 - `Maximilian Gerhardt (@maxgerhardt) <https://github.com/maxgerhardt>`__
 - `mbo18 (@mbo18) <https://github.com/mbo18>`__
@@ -674,9 +674,7 @@ Contributors
 - `Peter Valkov (@peter-valkov) <https://github.com/peter-valkov>`__
 - `Peter Foreman (@peterforeman) <https://github.com/peterforeman>`__
 - `Peter Galantha (@peterg79) <https://github.com/peterg79>`__
-- `Peter Remøy Paulsen (@petrepa) <https://github.com/petrepa>`__
 - `Philippe FOUQUET (@Philippe12) <https://github.com/Philippe12>`__
-- `Philip Rosenberg-Watt (@PhilRW) <https://github.com/PhilRW>`__
 - `pieterbrink123 (@pieterbrink123) <https://github.com/pieterbrink123>`__
 - `Tommy van der Vorst (@pixelspark) <https://github.com/pixelspark>`__
 - `Peter Kuehne (@pkuehne) <https://github.com/pkuehne>`__
@@ -688,7 +686,6 @@ Contributors
 - `Iván Povedano (@pove) <https://github.com/pove>`__
 - `probonopd (@probonopd) <https://github.com/probonopd>`__
 - `Mike Lynch (@Prow7) <https://github.com/Prow7>`__
-- `Peter Stuifzand (@pstuifzand) <https://github.com/pstuifzand>`__
 - `Peter Tatrai (@ptatrai) <https://github.com/ptatrai>`__
 - `Patrick Toal (@ptoal) <https://github.com/ptoal>`__
 - `Leandro Puerari (@puerari) <https://github.com/puerari>`__
@@ -702,7 +699,6 @@ Contributors
 - `Johannes Rebling (@r0oland) <https://github.com/r0oland>`__
 - `Richard Kuhnt (@r15ch13) <https://github.com/r15ch13>`__
 - `Richard Miles (@r89m) <https://github.com/r89m>`__
-- `Pär Stålberg (@rabbadab) <https://github.com/rabbadab>`__
 - `Aaron Zhang (@rabbit-aaron) <https://github.com/rabbit-aaron>`__
 - `RadekHvizdos (@RadekHvizdos) <https://github.com/RadekHvizdos>`__
 - `Florian Ragwitz (@rafl) <https://github.com/rafl>`__
@@ -899,4 +895,4 @@ Contributors
 - `Zack Barett (@zsarnett) <https://github.com/zsarnett>`__
 - `Christian Zufferey (@zuzu59) <https://github.com/zuzu59>`__
 
-*This page was last updated September 21, 2022.*
+*This page was last updated September 22, 2022.*