Upstream/esphome-docs
1
0
Fork 0
mirror of https://github.com/esphome/esphome-docs.git synced 2025-01-13 20:11:53 +01:00
Code Issues Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Jesse Hills 2022-04-14 13:48:27 +12:00
commit 4eb8b2af91
No known key found for this signature in database
GPG Key ID: BEAAE804EFD8E83A
5 changed files with 20 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
_static/custom.css
View File

@ -20,13 +20,12 @@ 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 {

15
components/button/index.rst
View File

@ -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 </components/binary_sensor/gpio>`.
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 <api-homeassistant_event_action>` instead.

6
components/sensor/ccs811.rst
View File

@ -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%

2
components/sensor/xiaomi_miscale.rst
View File

@ -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: |-

4
devices/esp8266.rst
View File

@ -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
------------