Merge branch 'current' into beta

.gitpod.yml

@@ -4,4 +4,4 @@ ports:
 
 tasks:
 - before: pip3 install -r requirements.txt
-  command: make webserver
+  command: make live-html

_static/custom.css

@@ -186,3 +186,7 @@ div.index-shields {
     margin-left: 32px;
   }
 }
+
+.breadcrumbs li {
+  display: inline;
+}

_templates/layout.html

@@ -27,6 +27,17 @@
   <meta name="viewport" content="width=device-width, initial-scale=0.9, maximum-scale=0.9">
 {% endblock %}
 
+{% block relbar_top %}
+  {% if parents|length > 0 %}
+  <ul class="breadcrumbs">
+    {%- for doc in parents %}
+      <li><a href="{{ doc.link|e }}">{{ doc.title }}</a> ➔</li>
+    {%- endfor %}
+      <li>{{title}}</li>
+  </ul>
+  {% endif %}
+{% endblock %}
+
 {% block footer %}
   <div id="upgrade-footer">
     A new version has been release since you last visited this page: {{ release }} 🎉

components/logger.rst

@@ -6,9 +6,10 @@ Logger Component
     :image: file-document-box.svg
 
 The logger component automatically logs all log messages through the
-serial port and through MQTT topics. By default, all logs with a
-severity higher than ``DEBUG`` will be shown. Decreasing the log level
-can help with the performance of the application and memory size.
+serial port and through MQTT topics (if there is an MQTT client in the
+configuration). By default, all logs with a severity higher than
+``DEBUG`` will be shown. Decreasing the log level can help with the
+performance of the application and memory size.
 
 .. code-block:: yaml
 
@@ -54,7 +55,9 @@ The logger component makes use of platform-specific hardware UARTs for serial lo
 By default, the logger will occupy ``UART0``. The ESP32 has three hardware UARTs, all of
 which can be used for both transmit and receive. The ESP8266 only has two hardware UARTs,
 one of which is transmit-only. The ESP8266 ``UART0`` can also be 'swapped' to TX/RX on the
-CTS/RTS pins, if you need to use GPIO1 and GPIO3 for something else.
+CTS/RTS pins, if you need to use GPIO1 and GPIO3 for something else. Note that the common
+NodeMCU boards have their USB-UART Adapters fixed to the default GPIOs used by ``UART0``,
+so if you use anything else you will not get log messages over the on-board USB.
 
 Possible Hardware UART configurations:
 

components/sensor/cse7766.rst

@@ -7,7 +7,7 @@ CSE7766 Power Sensor
     :keywords: cse7766, cse7759b, Sonoff Pow R2
 
 The ``cse7766`` sensor platform allows you to use your CSE7766 voltage/current and power sensors
-(`datasheet <http://dl.itead.cc/S31/CSE7766.pdf>`__) sensors with
+(`datasheet <https://itead.cc/wp-content/uploads/2022/05/CSE7766.pdf>`__) sensors with
 ESPHome. This sensor is commonly found in Sonoff POW R2. CSE7759B is similar to CSE7766
 and works with this integration.
 

components/sensor/ufire_ec.rst

@@ -7,10 +7,10 @@ uFire Isolated EC sensor
     :keywords: ufire ec sensor temperature esphome
 
 The ``ufire_ec`` sensor platform allows you to use your uFire Isolated EC sensor
-with ESPHome. The :ref:`I²C Bus <i2c>` is
-required to be set up in your configuration for this sensor to work.
-It required also to have an temperature sensor in the liquit tank; this can
-be on the same board or external sensor linked to the uFire EC configuration.
+with ESPHome. The :ref:`I²C Bus <i2c>` is required to be set up in your
+configuration for this sensor to work. It requires also to have a temperature
+sensor in the liquid tank; this can be on the same board or an external sensor
+linked to the uFire EC configuration.
 
 .. figure:: images/ufire_ec.png
     :align: center

components/sensor/xiaomi_ble.rst

@@ -92,7 +92,7 @@ Configuration example:
 LYWSDCGQ
 ********
 
-Hygro thermometer, round body, segment LCD, broadcasts temperature, humidity and battery level.
+Hygro thermometer, round body, segment LCD, broadcasts temperature, humidity and battery level. This device is also known as MJ_HT_V1. In HA's native Xiaomi BLE integration, the device info page shows it as "MJ_HT_V1 (LYWSDCGQ by Xiaomi)".
 
 .. figure:: images/xiaomi_lywsdcgq.jpg
     :align: center

devices/index.rst

@@ -1,4 +1,4 @@
-Cookbook
+Devices
 ========
 
 .. toctree::

guides/automations.rst

@@ -274,7 +274,7 @@ global variables can be used to store the state of a garage door.
       - id: my_global_string
         type: std::string
         restore_value: no  # Strings cannot be saved/restored
-        initial_value: '"hello world"'
+        initial_value: '"Global value is"'
 
    # In an automation
    on_press:
@@ -287,7 +287,7 @@ global variables can be used to store the state of a garage door.
              id(my_global_int) += 10;
            }
 
-           ESP_LOGD(TAG, "Global value is: %d", id(my_global_int));
+           ESP_LOGD(TAG, "%s: %d", id(my_global_string), id(my_global_int));
 
 Configuration variables: