From 8f86f6b6ab749d83c1ade07a75027297c7d580c8 Mon Sep 17 00:00:00 2001 From: Vendo232 <44098230+Vendo232@users.noreply.github.com> Date: Tue, 12 Apr 2022 21:57:57 -0600 Subject: [PATCH 1/6] Update xiaomi_miscale.rst (#1995) --- components/sensor/xiaomi_miscale.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/sensor/xiaomi_miscale.rst b/components/sensor/xiaomi_miscale.rst index 7fa523872..277397ed8 100644 --- a/components/sensor/xiaomi_miscale.rst +++ b/components/sensor/xiaomi_miscale.rst @@ -73,7 +73,7 @@ You have to replace the numbers in the lambdas to determine your weight which is impedance: name: "Xiaomi Mi Scale Impedance" - id: impedance_xiaomi + id: impedance_miscale on_value: then: - lambda: |- From a7441684b91189dd8b69c25455beb9faa0719608 Mon Sep 17 00:00:00 2001 From: sumirati Date: Wed, 13 Apr 2022 06:04:13 +0200 Subject: [PATCH 2/6] Added note on WAK signal for CCS811 (#1998) --- components/sensor/ccs811.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/components/sensor/ccs811.rst b/components/sensor/ccs811.rst index 2ab3a2e43..9d9cdf615 100644 --- a/components/sensor/ccs811.rst +++ b/components/sensor/ccs811.rst @@ -8,6 +8,12 @@ CCS811 CO_2 and Volatile Organic Compound Sensor The ``ccs811`` sensor platform allows you to use CCS811 CO_2 and volatile organic compound sensors (`Adafruit`_) with ESPHome. +.. note:: + + Most CCS811 modules require the WAK pin to be pulled low to wake up the sensor, as outlined in the data sheets. + Outside low-power scenarios, connecting WAK to ground is the recommended configuration. For low power installations, + pulling WAK low should happen in software prior to taking the measures. + .. figure:: images/ccs811-full.jpg :align: center :width: 50.0% From d7150ffd99263f60554bcff07ad96e2e0b106ee4 Mon Sep 17 00:00:00 2001 From: Philip Allgaier Date: Wed, 13 Apr 2022 06:07:42 +0200 Subject: [PATCH 3/6] Add border-radius to images + dropshadow to tables (#1994) --- _static/custom.css | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_static/custom.css b/_static/custom.css index c9f761428..c11437ff5 100644 --- a/_static/custom.css +++ b/_static/custom.css @@ -20,17 +20,17 @@ div.sphinxsidebar { img.component-image { border: none; - vertical-align: middle; display: block; margin-left: auto; margin-right: auto; - width: 100%; height: 85px; object-fit: contain; + border-radius: 10px; } table.docutils { width: 100%; + box-shadow: 4px 4px 8px -4px #00000075; } .blink-tag { From 8e327313b4ea0d6a4a3910ed3e598775ecc8ce3a Mon Sep 17 00:00:00 2001 From: pbevilac <86719972+pbevilac@users.noreply.github.com> Date: Wed, 13 Apr 2022 06:09:18 +0200 Subject: [PATCH 4/6] added closing bracket, corrected bootloader baudrate to 74880 (#1996) --- devices/esp8266.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/devices/esp8266.rst b/devices/esp8266.rst index 6d846558b..0f922ebb2 100644 --- a/devices/esp8266.rst +++ b/devices/esp8266.rst @@ -113,7 +113,7 @@ This means effectively only the following pins can be used as general purpose GP ---------- ------------------------------ ------------------------------ ``GPIO15`` If LOW on boot Weak Pull Up ---------- ------------------------------ ------------------------------ -``GPIO16`` Has pull-down (but no pull-up Weak Pull Down +``GPIO16`` Has pull-down (but no pull-up) Weak Pull Down resistor ========== ============================== ============================== @@ -141,7 +141,7 @@ in the ``boot mode:`` line tells you what mode was selected ets Jan 8 2013,rst cause:4, boot mode:(3,6) The first lines when viewing the UART logs might have unrecognized characters. This is -because the ESP8266 bootloader uses a baudrate of 76800, whereas the program uses 115200. +because the effective baudrate of the ESP8266 bootloader is 74800, whereas the program uses 115200. Reset Causes ------------ From 4b0889f0c575ded768d37f5bf8df9687067dd65e Mon Sep 17 00:00:00 2001 From: Jesse Hills <3060199+jesserockz@users.noreply.github.com> Date: Wed, 13 Apr 2022 16:12:22 +1200 Subject: [PATCH 5/6] Revert table shadow added in #1994 (#2014) --- _static/custom.css | 1 - 1 file changed, 1 deletion(-) diff --git a/_static/custom.css b/_static/custom.css index c11437ff5..5df279829 100644 --- a/_static/custom.css +++ b/_static/custom.css @@ -30,7 +30,6 @@ img.component-image { table.docutils { width: 100%; - box-shadow: 4px 4px 8px -4px #00000075; } .blink-tag { From e051ae919c4bd1c1730372f332f6204a3fb4e3e3 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 13 Apr 2022 00:07:12 -0700 Subject: [PATCH 6/6] Help people that want to attach a button (#2015) --- components/button/index.rst | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/components/button/index.rst b/components/button/index.rst index 81d9d41b2..e8054733a 100644 --- a/components/button/index.rst +++ b/components/button/index.rst @@ -5,9 +5,14 @@ Button Component :description: Instructions for setting up button components in ESPHome. :image: folder-open.svg -ESPHome has support for components to create a button entity. A button entity is -basically a momentary switch with no state and can be triggered by either YAML or -the user/frontend. +.. note:: + + To attach a physical buttons to ESPHome, see + :doc:`GPIO Binary Sensor `. + +ESPHome has support for components to create button entities in Home Assistant. A button entity is +represented in ESPHome as a momentary switch with no state and can be triggered in Home Assistant +via the UI or automations. .. note:: @@ -96,8 +101,8 @@ Configuration variables: .. note:: - Buttons are designed to trigger an action on a device from Home Assistant, and have an unidirectional flow from - Home Assistant to ESPHome. If you press a button using this action, no button press event will be triggered in Home + Buttons are designed to trigger an action on a device from Home Assistant, and have an unidirectional flow from + Home Assistant to ESPHome. If you press a button using this action, no button press event will be triggered in Home Assistant. If you want to trigger an automation in Home Assistant, you should use a :ref:`Home Assistant event ` instead.