From 03807510dc54d3f732ebd67dc76c531c4b27b8df Mon Sep 17 00:00:00 2001 From: Alex Boyd Date: Thu, 25 Apr 2024 05:23:40 -0600 Subject: [PATCH 01/11] Fix Docker build (#3798) --- Dockerfile | 1 + guides/contributing.rst | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/Dockerfile b/Dockerfile index cd58e282f..a99ffa478 100644 --- a/Dockerfile +++ b/Dockerfile @@ -14,6 +14,7 @@ RUN useradd -ms /bin/bash esphome USER esphome WORKDIR /workspaces/esphome-docs +ENV PATH="${PATH}:/home/esphome/.local/bin" COPY requirements.txt ./ RUN pip3 install --no-cache-dir --no-binary :all: -r requirements.txt diff --git a/guides/contributing.rst b/guides/contributing.rst index e1b37be32..fc38f75b1 100644 --- a/guides/contributing.rst +++ b/guides/contributing.rst @@ -98,7 +98,7 @@ Build .. code-block:: bash - docker run --rm -v "${PWD}/":/data/esphomedocs -p 8000:8000 -it ghcr.io/esphome/esphome-docs + docker run --rm -v "${PWD}/":/workspaces/esphome-docs -p 8000:8000 -it ghcr.io/esphome/esphome-docs With ``PWD`` referring to the root of the ``esphome-docs`` git repository. Then go to ``:8000`` in your browser. From 051ed8736d20d16141002971de855a4b1088f357 Mon Sep 17 00:00:00 2001 From: Alex Boyd Date: Fri, 26 Apr 2024 05:52:15 -0600 Subject: [PATCH 02/11] Redo the homeassistant service call API setup instructions (#3631) Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com> --- _static/custom.css | 5 +++++ components/api.rst | 37 +++++++++++++++++++++++++++++++------ 2 files changed, 36 insertions(+), 6 deletions(-) diff --git a/_static/custom.css b/_static/custom.css index 451d5cb4b..182ffa4ab 100644 --- a/_static/custom.css +++ b/_static/custom.css @@ -240,6 +240,11 @@ a:hover code { background: none; } +/* don't underline links that contain an image and nothing else */ +a:has(> img:only-child) { + border-bottom: none; +} + div.body p, div.body dd, div.body li, div.body blockquote { hyphens: none; } diff --git a/components/api.rst b/components/api.rst index cb1a48116..a6386a845 100644 --- a/components/api.rst +++ b/components/api.rst @@ -75,20 +75,35 @@ Configuration variables: .. _api-actions: -.. note:: - - Before a newly added ESPHome device can interact with the Home Assistant API it needs to be allowed to communicate - with it. This setting can be found in the ESPHome integration (NOT in the Add-On) by clicking "CONFIGURE" for - that device and enabling the "Allow device to make service calls" option. - Actions ------- +Before using any of the actions below, you'll need to tell Home Assistant to allow your device to +make service calls. + +Open the ESPHome integration page on your Home Assistant instance: + +.. raw:: html + + Open your Home Assistant instance and show an integration. + +Then: + +#. Fnd your device in the device list +#. Click the "configure" button next to it +#. Check the "Allow the device to make Home Assistant service calls" box +#. Then click "submit". + .. _api-homeassistant_event_action: ``homeassistant.event`` Action ****************************** +.. note:: + + Be sure to :ref:`follow the instructions above ` to tell Home Assistant to allow + your device to make service calls. + When using the native API with Home Assistant, you can create events in the Home Assistant event bus straight from ESPHome :ref:`Automations `. @@ -117,6 +132,11 @@ Configuration variables: ``homeassistant.service`` Action ******************************** +.. note:: + + Be sure to :ref:`follow the instructions above ` to tell Home Assistant to allow + your device to make service calls. + When using the native API with Home Assistant, you can create Home Assistant service calls straight from ESPHome :ref:`Automations `. @@ -189,6 +209,11 @@ Then, in ESPHome: ``homeassistant.tag_scanned`` Action ************************************ +.. note:: + + Be sure to :ref:`follow the instructions above ` to tell Home Assistant to allow + your device to make service calls. + When using the native API with Home Assistant, you can push tag_scanned to Home Assistant straight from ESPHome :ref:`Automations `. From 7a11619a8b462d84ae2730786d3094b3805f3194 Mon Sep 17 00:00:00 2001 From: Jesse Hills <3060199+jesserockz@users.noreply.github.com> Date: Tue, 30 Apr 2024 15:47:41 +1200 Subject: [PATCH 03/11] Bump version to 2024.4.2 --- Doxygen | 2 +- Makefile | 2 +- _static/version | 2 +- conf.py | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Doxygen b/Doxygen index 3179fed5c..149e4876c 100644 --- a/Doxygen +++ b/Doxygen @@ -38,7 +38,7 @@ PROJECT_NAME = "ESPHome" # could be handy for archiving the generated documentation or if some version # control system is used. -PROJECT_NUMBER = 2024.4.1 +PROJECT_NUMBER = 2024.4.2 # Using the PROJECT_BRIEF tag one can provide an optional one line description # for a project that appears at the top of each page and should give viewer a diff --git a/Makefile b/Makefile index fd31de088..5251aa29e 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ ESPHOME_PATH = ../esphome -ESPHOME_REF = 2024.4.1 +ESPHOME_REF = 2024.4.2 .PHONY: html html-strict cleanhtml deploy help live-html Makefile netlify netlify-api api netlify-dependencies svg2png copy-svg2png minify diff --git a/_static/version b/_static/version index f38c6ceaf..af96240eb 100644 --- a/_static/version +++ b/_static/version @@ -1 +1 @@ -2024.4.1 \ No newline at end of file +2024.4.2 \ No newline at end of file diff --git a/conf.py b/conf.py index 66d1ff697..469f336c3 100644 --- a/conf.py +++ b/conf.py @@ -69,7 +69,7 @@ author = "ESPHome" # The short X.Y version. version = "2024.4" # The full version, including alpha/beta/rc tags. -release = "2024.4.1" +release = "2024.4.2" # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. From fe89003adfbb70144dac64c04ba32312be4a98db Mon Sep 17 00:00:00 2001 From: Jesse Hills <3060199+jesserockz@users.noreply.github.com> Date: Tue, 30 Apr 2024 15:49:32 +1200 Subject: [PATCH 04/11] Update changelog for 2024.4.2 --- changelog/2024.4.0.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/changelog/2024.4.0.rst b/changelog/2024.4.0.rst index 89284d8cb..ed0b3af4c 100644 --- a/changelog/2024.4.0.rst +++ b/changelog/2024.4.0.rst @@ -50,6 +50,15 @@ Release 2024.4.1 - April 23 - Fix or filter :esphomepr:`6574` by :ghuser:`swoboda1337` +Release 2024.4.2 - April 30 +--------------------------- + +- Fix SHT3xd fails sometimes in 2024.4.0 :esphomepr:`6592` by :ghuser:`mrtoy-me` +- allow defaults with no include vars :esphomepr:`6613` by :ghuser:`ssieb` +- Revert #6458 :esphomepr:`6650` by :ghuser:`tronikos` +- [i2s_audio.microphone] Fixing adc bug :esphomepr:`6654` by :ghuser:`jesserockz` + + Full list of changes -------------------- From 9955fcb151b59c0895f6df18a3d3a16b2a102954 Mon Sep 17 00:00:00 2001 From: Jesse Hills <3060199+jesserockz@users.noreply.github.com> Date: Tue, 30 Apr 2024 15:50:06 +1200 Subject: [PATCH 05/11] Update supporters for 2024.4.2 --- guides/supporters.rst | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/guides/supporters.rst b/guides/supporters.rst index 9b6111b73..1c9098e51 100644 --- a/guides/supporters.rst +++ b/guides/supporters.rst @@ -122,6 +122,7 @@ Contributors - `arunderwood (@arunderwood) `__ - `Arya (@Arya11111) `__ - `aschmitz (@aschmitz) `__ +- `Anton Sergunov (@asergunov) `__ - `Borys Pierov (@ashald) `__ - `Ash McKenzie (@ashmckenzie) `__ - `ashp8i (@ashp8i) `__ @@ -259,6 +260,7 @@ Contributors - `cg089 (@cg089) `__ - `Audric Schiltknecht (@chemicalstorm) `__ - `Charles Johnson (@ChemicalXandco) `__ +- `chiahsing (@chiahsing) `__ - `chris-jennings (@chris-jennings) `__ - `Chris (@chrismaki) `__ - `Christoph Wagner (@Christoph-Wagner) `__ @@ -319,6 +321,7 @@ Contributors - `Daniel Bjørnbakk (@danibjor) `__ - `Daniel Baulig (@DanielBaulig) `__ - `danielionutmuresan (@danielionutmuresan) `__ +- `Daniel Kent (@danielkent-net) `__ - `Daniel Kucera (@danielkucera) `__ - `Daniel O'Connor (@DanielO) `__ - `Daniel Rheinbay (@danielrheinbay) `__ @@ -350,7 +353,6 @@ Contributors - `Davy Landman (@DavyLandman) `__ - `Dawid Cieszyński (@dawidcieszynski) `__ - `Darren Tucker (@daztucker) `__ -- `Donovan Baarda (@dbaarda) `__ - `David Buezas (@dbuezas) `__ - `dckiller51 (@dckiller51) `__ - `Daniel Correa Lobato (@dclobato) `__ @@ -392,7 +394,6 @@ Contributors - `Dan Mannock (@dmannock) `__ - `Dmitriy Lopatko (@dmitriy5181) `__ - `Tristan Rowley (@doctea) `__ -- `DrZoid (@docteurzoidberg) `__ - `DominikBitzer (@DominikBitzer) `__ - `Dominik (@DomiStyle) `__ - `Don Burch (@donburch888) `__ @@ -452,8 +453,8 @@ Contributors - `Elkropac (@Elkropac) `__ - `Elliot Wood (@elliot-wood) `__ - `Eduard Llull (@ellull) `__ +- `Joakim Plate (@elupus) `__ - `Andrew Elwell (@Elwell) `__ -- `EmbeddedDevver (@EmbeddedDevver) `__ - `EmmanuelLM (@EmmanuelLM) `__ - `Emory Dunn (@emorydunn) `__ - `Eric van Blokland (@Emrvb) `__ @@ -727,7 +728,6 @@ Contributors - `AngeloGioacchino Del Regno (@kholk) `__ - `Kilowatt (@Kilowatt-W) `__ - `Kip (@kipwittchen) `__ -- `Ed (@kixtarter) `__ - `Klaas Schoute (@klaasnicolaas) `__ - `Klarstein (@Klarstein) `__ - `Marcus Klein (@kleini) `__ @@ -752,7 +752,6 @@ Contributors - `Ludovic BOUÉ (@lboue) `__ - `lcavalli (@lcavalli) `__ - `Craig Fletcher (@leakypixel) `__ -- `Dominik Wagenknecht (@LeDominik) `__ - `Benny de Leeuw (@leeuwte) `__ - `Thayne (@Legot) `__ - `Leonardo La Rocca (@leoli51) `__ @@ -1023,6 +1022,7 @@ Contributors - `Jan Pluskal (@pluskal) `__ - `DK (@poldim) `__ - `poloswiss (@poloswiss) `__ +- `polyfloyd (@polyfloyd) `__ - `Pontus Oldberg (@PontusO) `__ - `poptix (@poptix) `__ - `Peter Provost (@PProvost) `__ @@ -1159,6 +1159,7 @@ Contributors - `Niklas Wagner (@Skaronator) `__ - `Brian Slesinsky (@skybrian) `__ - `Jordan W. Cobb (@skykingjwc) `__ +- `slimeinacloak (@slimeinacloak) `__ - `Sebastian Lövdahl (@slovdahl) `__ - `smischny (@smischny) `__ - `John Mueller (@softplus) `__ @@ -1345,9 +1346,10 @@ Contributors - `Brynley McDonald (@ZephireNZ) `__ - `Stefan Goethals (@zipkid) `__ - `zivillian (@zivillian) `__ +- `zry98 (@zry98) `__ - `Zack Barett (@zsarnett) `__ - `Zsolt Zsiros (@ZsZs73) `__ - `Christian Zufferey (@zuzu59) `__ - `Zynth-dev (@Zynth-dev) `__ -*This page was last updated April 23, 2024.* +*This page was last updated April 30, 2024.* From 5266732e8873f20dea64c4a7d53e1c2da4cfd992 Mon Sep 17 00:00:00 2001 From: Carsten Grohmann Date: Sat, 4 May 2024 12:27:48 +0200 Subject: [PATCH 06/11] Order of esphome parameters corrected (#3813) --- guides/getting_started_command_line.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/getting_started_command_line.rst b/guides/getting_started_command_line.rst index 3f088e99f..21617f353 100644 --- a/guides/getting_started_command_line.rst +++ b/guides/getting_started_command_line.rst @@ -191,7 +191,7 @@ for docker you need to supply an additional parameter: .. code-block:: bash - esphome livingroom.yaml run + esphome run livingroom.yaml # On docker docker run --rm -v "${PWD}":/config -it ghcr.io/esphome/esphome run livingroom.yaml From cb230f57d484d45dd55c8c50a217bd0350020635 Mon Sep 17 00:00:00 2001 From: Carsten Grohmann Date: Sun, 5 May 2024 18:07:49 +0200 Subject: [PATCH 07/11] Order of esphome parameters corrected II (#3816) --- components/mqtt.rst | 2 +- guides/migrate_espeasy.rst | 2 +- guides/migrate_espurna.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/components/mqtt.rst b/components/mqtt.rst index a62bdd94d..154a492bd 100644 --- a/components/mqtt.rst +++ b/components/mqtt.rst @@ -266,7 +266,7 @@ then run the ``mqtt-fingerprint`` script of ESPHome to get the certificate: .. code-block:: bash - esphome livingroom.yaml mqtt-fingerprint + esphome mqtt-fingerprint livingroom.yaml > SHA1 Fingerprint: a502ff13999f8b398ef1834f1123650b3236fc07 > Copy above string into mqtt.ssl_fingerprints section of livingroom.yaml diff --git a/guides/migrate_espeasy.rst b/guides/migrate_espeasy.rst index b0f954d63..1524da252 100644 --- a/guides/migrate_espeasy.rst +++ b/guides/migrate_espeasy.rst @@ -19,7 +19,7 @@ file. Then, generate and download the binary: .. figure:: images/download_binary.png -- **Using the command line**: run ``esphome livingroom.yaml compile`` (replacing +- **Using the command line**: run ``esphome compile livingroom.yaml`` (replacing ``livingroom.yaml`` with your configuration file of course) and navigate to the ``/.pioenvs//`` folder. There you will find a ``firmware.bin`` file, this is the binary you will upload. diff --git a/guides/migrate_espurna.rst b/guides/migrate_espurna.rst index 09505a24e..ef7dc8f12 100644 --- a/guides/migrate_espurna.rst +++ b/guides/migrate_espurna.rst @@ -20,7 +20,7 @@ file. Then, generate and download the binary: .. figure:: images/download_binary.png -- **Using the command line**: run ``esphome livingroom.yaml compile`` (replacing +- **Using the command line**: run ``esphome compile livingroom.yaml`` (replacing ``livingroom.yaml`` with your configuration file of course) and navigate to the ``/.pioenvs//`` folder. There you will find a ``firmware.bin`` file, this is the binary you will upload. From 567fa6a76a7d76cfc3caab527b041c83dd00d15f Mon Sep 17 00:00:00 2001 From: IreuN Date: Tue, 7 May 2024 03:04:42 +0200 Subject: [PATCH 08/11] Update bme680_bsec licence url (#3818) --- components/sensor/bme680_bsec.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/sensor/bme680_bsec.rst b/components/sensor/bme680_bsec.rst index a182b1ec1..2b3e0780b 100644 --- a/components/sensor/bme680_bsec.rst +++ b/components/sensor/bme680_bsec.rst @@ -30,7 +30,7 @@ The :ref:`I²C ` is required to be set up in your configuration for this se BME680 Temperature, Pressure, Humidity & Gas Sensor. -.. _BSEC license agreement: https://www.bosch-sensortec.com/media/boschsensortec/downloads/bsec/2017-07-17_clickthrough_license_terms_environmentalib_sw_clean.pdf +.. _BSEC license agreement: https://www.bosch-sensortec.com/media/boschsensortec/downloads/software/bme688_development_software/2023_04/license_terms_bme688_bme680_bsec.pdf .. _Adafruit: https://www.adafruit.com/product/3660 From 435ac134882f53840e0f37a1efbc4efe24114137 Mon Sep 17 00:00:00 2001 From: joukepouke-personal <73423163+joukepouke-personal@users.noreply.github.com> Date: Tue, 7 May 2024 03:07:27 +0200 Subject: [PATCH 09/11] Update getting_started_command_line.rst (#3814) * Update getting_started_command_line.rst * add space --- guides/getting_started_command_line.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/getting_started_command_line.rst b/guides/getting_started_command_line.rst index 21617f353..5746fad08 100644 --- a/guides/getting_started_command_line.rst +++ b/guides/getting_started_command_line.rst @@ -224,8 +224,8 @@ To start the ESPHome dashboard, simply start ESPHome with the following command .. code-block:: bash # Install dashboard dependencies - pip install tornado esptool - esphome dashboard config/ + pip install tornado esptool\ + esphome dashboard config # On Docker, host networking mode is required for online status indicators docker run --rm --net=host -v "${PWD}":/config -it ghcr.io/esphome/esphome From ca96dd49e192c40b37e4829cdf56c3eaef7d8bcc Mon Sep 17 00:00:00 2001 From: Keith Burzinski Date: Tue, 7 May 2024 00:16:56 -0500 Subject: [PATCH 10/11] Change "integration" -> "component", minor copy fixes (#3790) --- components/binary_sensor/custom.rst | 28 +++--- components/climate/custom.rst | 26 ++++-- components/copy.rst | 8 +- components/cover/custom.rst | 29 +++--- components/cover/tuya.rst | 2 +- components/demo.rst | 12 +-- components/dfplayer.rst | 5 +- components/display/index.rst | 2 +- components/display/lcd_display.rst | 8 +- components/display/max7219.rst | 4 +- components/display/max7219digit.rst | 4 +- components/display/waveshare_epaper.rst | 2 +- .../display_menu/graphical_display_menu.rst | 2 +- components/display_menu/index.rst | 6 +- components/display_menu/lcd_menu.rst | 2 +- components/fingerprint_grow.rst | 2 +- components/gps.rst | 4 +- components/light/custom.rst | 26 ++++-- components/light/neopixelbus.rst | 2 +- components/micronova.rst | 2 +- components/mqtt.rst | 5 +- components/output/ac_dimmer.rst | 7 +- components/output/custom.rst | 22 +++-- components/output/sigma_delta_output.rst | 2 +- components/sensor/ads1115.rst | 2 +- components/sensor/airthings_ble.rst | 3 +- components/sensor/as3935.rst | 2 +- components/sensor/bl0940.rst | 4 +- components/sensor/bl0942.rst | 4 +- components/sensor/ccs811.rst | 2 +- components/sensor/cse7766.rst | 2 +- components/sensor/custom.rst | 25 +++-- components/sensor/dsmr.rst | 2 +- components/sensor/growatt_solar.rst | 2 +- components/sensor/havells_solar.rst | 2 +- components/sensor/hlw8012.rst | 8 +- components/sensor/inkbird_ibsth1_mini.rst | 2 +- components/sensor/mcp3204.rst | 7 +- components/sensor/mmc5983.rst | 3 +- components/sensor/mopeka_pro_check.rst | 2 +- components/sensor/mopeka_std_check.rst | 2 +- components/sensor/mqtt_subscribe.rst | 2 +- components/sensor/pulse_meter.rst | 2 +- components/sensor/pzem004t.rst | 2 +- components/sensor/pzemac.rst | 2 +- components/sensor/pzemdc.rst | 2 +- components/sensor/ruuvitag.rst | 2 +- components/sensor/sdm_meter.rst | 2 +- components/sensor/selec_meter.rst | 2 +- components/sensor/smt100.rst | 6 +- components/servo.rst | 2 +- components/switch/custom.rst | 26 ++++-- components/text_sensor/custom.rst | 28 +++--- components/text_sensor/mqtt_subscribe.rst | 2 +- components/tm1651.rst | 6 +- custom/custom_component.rst | 27 ++++-- custom/i2c.rst | 20 ++-- custom/spi.rst | 20 ++-- custom/uart.rst | 20 ++-- guides/contributing.rst | 28 +++--- guides/faq.rst | 93 +++++++++++++------ 61 files changed, 343 insertions(+), 237 deletions(-) diff --git a/components/binary_sensor/custom.rst b/components/binary_sensor/custom.rst index d2ee55fdc..f983584cb 100644 --- a/components/binary_sensor/custom.rst +++ b/components/binary_sensor/custom.rst @@ -1,22 +1,28 @@ Custom Binary Sensor ==================== +.. seo:: + :description: Instructions for setting up Custom C++ binary sensors with ESPHome. + :image: language-cpp.svg + :keywords: C++, Custom + .. warning:: - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. -This integration can be used to create custom binary sensors in ESPHome -using the C++ (Arduino) API. +.. warning:: -Please first read :doc:`/components/sensor/custom` guide, -the same principles apply here and binary sensors are very similar -to sensors internally. + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. + +This component can be used to create custom binary sensors in ESPHome using the C++ (Arduino) API. + +Please first read :doc:`/components/sensor/custom` guide, the same principles apply here and binary +sensors are very similar to sensors internally. The example below is an example of a custom binary sensor; this custom sensor is essentially the same as the gpio binary sensor. diff --git a/components/climate/custom.rst b/components/climate/custom.rst index e4d86f19e..1544fa9f1 100644 --- a/components/climate/custom.rst +++ b/components/climate/custom.rst @@ -1,21 +1,27 @@ Custom Climate ============== +.. seo:: + :description: Instructions for setting up Custom C++ climate components with ESPHome. + :image: language-cpp.svg + :keywords: C++, Custom + .. warning:: - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. -This integration can be used to create custom climate devices in ESPHome -using the C++ (Arduino) API. +.. warning:: -Please first read :doc:`/components/sensor/custom` guide, -the same principles apply here. + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. + +This component can be used to create custom climate devices in ESPHome using the C++ (Arduino) API. + +Please first read :doc:`/components/sensor/custom` guide, the same principles apply here. The example below is an example of a custom climate device - all climate devices must override two methods (:apiclass:`Climate `): diff --git a/components/copy.rst b/components/copy.rst index 93f21c6d4..5cc7191c8 100644 --- a/components/copy.rst +++ b/components/copy.rst @@ -1,11 +1,11 @@ -Copy Integration -================ +Copy Component +============== .. seo:: - :description: Instructions for setting up the copy integration in ESPHome + :description: Instructions for setting up the copy component in ESPHome :image: content-copy.svg -The ``copy`` integration can be used to copy an existing component (like a sensor, switch, etc.) +The ``copy`` component can be used to copy an existing component (like a sensor, switch, etc.) and create a duplicate mirroring the source's state and forwarding actions such as turning on to the source. For each of the supported platforms, the configuration consists of the required configuration diff --git a/components/cover/custom.rst b/components/cover/custom.rst index 4b49dbc5c..c623a54f9 100644 --- a/components/cover/custom.rst +++ b/components/cover/custom.rst @@ -1,24 +1,29 @@ Custom Cover ============ +.. seo:: + :description: Instructions for setting up Custom C++ covers with ESPHome. + :image: language-cpp.svg + :keywords: C++, Custom + .. warning:: - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. -This integration can be used to create custom covers in ESPHome -using the C++ (Arduino) API. +.. warning:: -Please first read :doc:`/components/sensor/custom` guide, -the same principles apply here. + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. -The example below is an example of a custom cover - all covers must override -two methods: +This component can be used to create custom covers in ESPHome using the C++ (Arduino) API. + +Please first read :doc:`/components/sensor/custom` guide, the same principles apply here. + +The example below is an example of a custom cover - all covers must override two methods: - ``get_traits``: This should return a :apiclass:`CoverTraits ` object representing the capabilities of the cover. diff --git a/components/cover/tuya.rst b/components/cover/tuya.rst index 2293cdd63..917b87545 100644 --- a/components/cover/tuya.rst +++ b/components/cover/tuya.rst @@ -45,7 +45,7 @@ Configuration variables: Supported devices ----------------- -Tuya cover devices known to be supported by this integration: +Tuya cover devices known to be supported by this component: - Tuya ``M515EGWT`` (motor for bead chain roller blinds) diff --git a/components/demo.rst b/components/demo.rst index faccce99f..65eef4b51 100644 --- a/components/demo.rst +++ b/components/demo.rst @@ -1,12 +1,12 @@ -Demo Integration -================ +Demo Component +============== .. seo:: - :description: Instructions for setting up the demo integration in ESPHome + :description: Instructions for setting up the demo component in ESPHome :image: description.svg -The ``demo`` integration can be used for testing to generate sample instances of many -different integrations (sensors, lights, ...) +The ``demo`` component can be used for testing to generate sample instances of many +different components (sensors, lights, ...) .. figure:: images/demo-ui.png :align: center @@ -20,7 +20,7 @@ different integrations (sensors, lights, ...) Configuration variables: ------------------------ -This integration has no configuration variables +This component has no configuration variables See Also -------- diff --git a/components/dfplayer.rst b/components/dfplayer.rst index 9b2f5e655..fadc1c232 100644 --- a/components/dfplayer.rst +++ b/components/dfplayer.rst @@ -2,7 +2,7 @@ DF-Player mini ============== .. seo:: - :description: Instructions for setting up DF Player Mini integration in ESPHome. + :description: Instructions for setting up DF Player Mini component in ESPHome. :image: dfplayer.svg The ``dfplayer`` (`datasheet `__), component @@ -14,8 +14,7 @@ allows you to play sound and music stored in an SD card or USB flash drive. DF-Player mini Module. -For this integration to work you need to have set up a :ref:`UART bus ` -in your configuration. +For this component to work you need to have set up a :ref:`UART bus ` in your configuration. Overview -------- diff --git a/components/display/index.rst b/components/display/index.rst index d6f443eba..c9b39e072 100644 --- a/components/display/index.rst +++ b/components/display/index.rst @@ -2,7 +2,7 @@ Display Component ================= .. seo:: - :description: Instructions for setting up the display integration. + :description: Instructions for setting up the display component. :image: folder-open.svg The ``display`` component houses ESPHome's powerful rendering and display diff --git a/components/display/lcd_display.rst b/components/display/lcd_display.rst index 005de6c4c..530b13b23 100644 --- a/components/display/lcd_display.rst +++ b/components/display/lcd_display.rst @@ -2,12 +2,12 @@ Character-Based LCD Display =========================== .. seo:: - :description: Instructions for setting up character-based HD44780 LCD displays. + :description: Instructions for setting up character-based HD44780 LCDs. :image: lcd.jpg -The ``lcd_pcf8574`` and ``lcd_gpio`` display components allow you to use HD44780-compatible, character-based LCD displays -with ESPHome. This integration is only for LCD displays that display individual characters on a screen -(usually 8-40 columns and 2-4 rows), and not for LCD displays that can control each pixel individually. +The ``lcd_pcf8574`` and ``lcd_gpio`` display components allow you to use HD44780-compatible, character-based LCDs +with ESPHome. This component is only for LCDs that display individual characters on a screen +(usually 8-40 columns and 2-4 rows), and not for LCDs that can control each pixel individually. .. figure:: images/lcd-hello_world.jpg :align: center diff --git a/components/display/max7219.rst b/components/display/max7219.rst index ad1b1c6c5..11e069f1c 100644 --- a/components/display/max7219.rst +++ b/components/display/max7219.rst @@ -8,7 +8,7 @@ MAX7219 7-Segment Display The ``max7219`` display platform allows you to use MAX7219 7-segment display drivers ( `datasheet `__, `hobbycomponents `__) -with ESPHome. Please note that this integration is *only* for 7-segment display, not matrix configurations. +with ESPHome. Please note that this component is *only* for 7-segment display, not matrix configurations. .. figure:: images/max7219-full.jpg :align: center @@ -16,7 +16,7 @@ with ESPHome. Please note that this integration is *only* for 7-segment display, MAX7219 7-Segment Display. -As the communication with the MAX7219 is done using SPI for this integration, you need +As the communication with the MAX7219 is done using SPI for this component, you need to have an :ref:`SPI bus ` in your configuration with both the **mosi_pin** set (miso_pin is not required). Connect VCC to 3.3V (the manufacturer recommends 4+ V, but 3.3V seems to work fine), DIN to your ``mosi_pin`` and CS to your set ``cs_pin`` and finally GND to GND. diff --git a/components/display/max7219digit.rst b/components/display/max7219digit.rst index 2c7923c43..650ef878e 100644 --- a/components/display/max7219digit.rst +++ b/components/display/max7219digit.rst @@ -5,7 +5,7 @@ MAX7219 Digit Display :description: Instructions for setting up MAX7219 Digit displays. :image: max7219digit.jpg -The ``max7219`` display platform allows you to use MAX7219 digit with ESPHome. Please note that this integration +The ``max7219`` display platform allows you to use MAX7219 digit with ESPHome. Please note that this component is *only* for the digit "matrix" display, for the 7 segment display see :doc:`max7219`. .. figure:: images/max7219digit.png @@ -14,7 +14,7 @@ is *only* for the digit "matrix" display, for the 7 segment display see :doc:`ma MAX7219 Digit Display. -As the communication with the MAX7219 Digit is done using SPI for this integration, you need +As the communication with the MAX7219 Digit is done using SPI for this component, you need to have an :ref:`SPI bus ` in your configuration with both the **mosi_pin** set (miso_pin is not required). Connect VCC to 3.3V (the manufacturer recommends 4+ V, but 3.3V seems to work fine), DIN to your ``mosi_pin`` and CS to your set ``cs_pin`` and finally GND to GND. diff --git a/components/display/waveshare_epaper.rst b/components/display/waveshare_epaper.rst index 44a194a81..ca58e9fd2 100644 --- a/components/display/waveshare_epaper.rst +++ b/components/display/waveshare_epaper.rst @@ -23,7 +23,7 @@ single-color E-Ink displays are implemented and of those only a few modules. Waveshare E-Paper 2.9 Inch E-Paper Display. -The communication ESPHome has chosen to use for this integration is 4-wire :ref:`SPI `, as it's the most stable +The communication ESPHome has chosen to use for this component is 4-wire :ref:`SPI `, as it's the most stable and high-speed. So you need to make sure your board is set to the 4-wire SPI mode and have an ``spi:`` section in your configuration. diff --git a/components/display_menu/graphical_display_menu.rst b/components/display_menu/graphical_display_menu.rst index 751769d8f..9949b8b4e 100644 --- a/components/display_menu/graphical_display_menu.rst +++ b/components/display_menu/graphical_display_menu.rst @@ -19,7 +19,7 @@ ESPHome node, without the requirement of a network connection. Overview -------- -The integration implements the :ref:`Display Menu ` integration providing +The component implements the :ref:`Display Menu ` component providing a hierarchical menu primarily intended to be controlled either by a rotary encoder with a button or a five-button joystick controller. diff --git a/components/display_menu/index.rst b/components/display_menu/index.rst index 752c2ae94..9a38ecbf8 100644 --- a/components/display_menu/index.rst +++ b/components/display_menu/index.rst @@ -7,7 +7,7 @@ Display Menu .. _display_menu: -The integration provides a menu primarily intended to be controlled either by a rotary encoder +The component provides a menu primarily intended to be controlled either by a rotary encoder with a button or a five-button joystick controller. It allows to navigate a hierarchy of items and submenus with the ability to change the values and execute commands. The menu can be activated and deactivated on demand, allowing alternating between using the screen for @@ -17,8 +17,8 @@ Overview -------- This document describes the configuration and automations common for the components implementing -this integration. At the moment the character based LCD displays are supported using -the :ref:`lcd_menu ` integration and an instance of this is used in the configuration +this component. At the moment the character based LCD displays are supported using +the :ref:`lcd_menu ` component and an instance of this is used in the configuration examples. diff --git a/components/display_menu/lcd_menu.rst b/components/display_menu/lcd_menu.rst index 676c6d474..9645ece37 100644 --- a/components/display_menu/lcd_menu.rst +++ b/components/display_menu/lcd_menu.rst @@ -19,7 +19,7 @@ ESPHome node, without the requirement of a network connection. Overview -------- -The integration implements the :ref:`Display Menu ` integration providing +The component implements the :ref:`Display Menu ` component providing a hierarchical menu primarily intended to be controlled either by a rotary encoder with a button or a five-button joystick controller. diff --git a/components/fingerprint_grow.rst b/components/fingerprint_grow.rst index c36a2e2c1..56435d509 100644 --- a/components/fingerprint_grow.rst +++ b/components/fingerprint_grow.rst @@ -2,7 +2,7 @@ Grow Fingerprint Reader ======================= .. seo:: - :description: Instructions for setting up Grow Fingerprint Reader integration in ESPHome. + :description: Instructions for setting up Grow Fingerprint Reader component in ESPHome. :image: fingerprint.svg The ``fingerprint_grow`` component allows you to use your R307, R503, R503-RGB, ZFM-20, ... fingerprint sensors with ESPHome. diff --git a/components/gps.rst b/components/gps.rst index a391a2c46..0f6834a71 100644 --- a/components/gps.rst +++ b/components/gps.rst @@ -2,7 +2,7 @@ GPS Component ============= .. seo:: - :description: Instructions for setting up GPS integration in ESPHome. + :description: Instructions for setting up GPS component in ESPHome. :image: crosshairs-gps.svg The ``gps`` component allows you to connect GPS modules to your ESPHome project. @@ -16,7 +16,7 @@ Any GPS module that uses the standardized NMEA communication protocol will work. .. _Adafruit: https://www.adafruit.com/product/746 -For this integration to work you need to have set up a :ref:`UART bus ` +For this component to work you need to have set up a :ref:`UART bus ` in your configuration - only the RX pin should be necessary. .. code-block:: yaml diff --git a/components/light/custom.rst b/components/light/custom.rst index 03353f6f1..0ebf96564 100644 --- a/components/light/custom.rst +++ b/components/light/custom.rst @@ -1,21 +1,27 @@ Custom Light Output =================== +.. seo:: + :description: Instructions for setting up Custom C++ lights with ESPHome. + :image: language-cpp.svg + :keywords: C++, Custom + .. warning:: - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. -This integration can be used to create custom lights in ESPHome -using the C++ (Arduino) API. +.. warning:: -Please first read :doc:`/components/sensor/custom` guide, -the same principles apply here. + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. + +This component can be used to create custom lights in ESPHome using the C++ (Arduino) API. + +Please first read :doc:`/components/sensor/custom` guide, the same principles apply here. All internal stuff (like effects, transitions etc) is handled by the light core and cannot be overridden. Light outputs are only responsible for displaying some state diff --git a/components/light/neopixelbus.rst b/components/light/neopixelbus.rst index 271af0c6e..701fa7337 100644 --- a/components/light/neopixelbus.rst +++ b/components/light/neopixelbus.rst @@ -18,7 +18,7 @@ in ESPHome for individually addressable lights like NeoPixel or WS2812. It is very similar to the :doc:`fastled` platform. In fact, most addressable lights are supported through both light platforms. The difference is that they use different libraries: while the fastled platform uses -the `FastLED `__ library, this integration uses +the `FastLED `__ library, this component uses the `NeoPixelBus `__ library internally. .. code-block:: yaml diff --git a/components/micronova.rst b/components/micronova.rst index 8ccda83bd..f350588c2 100644 --- a/components/micronova.rst +++ b/components/micronova.rst @@ -18,7 +18,7 @@ The :ref:`UART ` must be configured with a baud rate 1200, 8 data bits, 2 Also, switching your stove on or off can behave different on the various MicroNova flavours. - Use this integration at your own risk. + Use this component at your own risk. Connecting your stove --------------------- diff --git a/components/mqtt.rst b/components/mqtt.rst index 154a492bd..c255d8ef2 100644 --- a/components/mqtt.rst +++ b/components/mqtt.rst @@ -184,13 +184,12 @@ Home Assistant generates entity names for all discovered devices based on entity entity name (e.g. ``sensor.uptime``). Numeric suffixes are appended to entity names when multiple devices use the same name for a sensor, making it harder to distinguish between similar sensors on different devices. Home Assistant 2021.12 allows MQTT devices to change -this behaviour by specifying ``object_id`` discovery attribute which replaces the sensor +this behaviour by specifying the ``object_id`` discovery attribute which replaces the sensor name part of the generated entity name. Setting ``discovery_object_id_generator: device_name`` -in ESPHome MQTT integration configuration will cause Home Assistant to include device name +in the ESPHome MQTT component configuration will cause Home Assistant to include device name in the generated entity names (e.g. ``sensor.uptime`` becomes ``sensor._uptime``), making it easier to distinguish the entities in various entity lists. - .. _mqtt-defaults: Defaults diff --git a/components/output/ac_dimmer.rst b/components/output/ac_dimmer.rst index b70474852..1a7c2b1a3 100644 --- a/components/output/ac_dimmer.rst +++ b/components/output/ac_dimmer.rst @@ -2,7 +2,7 @@ AC Dimmer Component =================== .. seo:: - :description: Instructions for setting up AC Dimmer integration in ESPHome. + :description: Instructions for setting up AC Dimmer component in ESPHome. :image: ac_dimmer.svg .. warning:: @@ -16,9 +16,8 @@ AC Dimmer Component The ``ac_dimmer`` component allows you to connect a dimmable light or other load which supports phase control dimming to your ESPHome project. -There are several already made boards which are compatible with this integration, -for example the `RobotDyn dimmer -`__. +There are several already made boards which are compatible with this component, such as the +`RobotDyn dimmer `__. .. figure:: images/robotdyn_dimmer.jpg :align: center diff --git a/components/output/custom.rst b/components/output/custom.rst index 501d46725..ad37e1bf0 100644 --- a/components/output/custom.rst +++ b/components/output/custom.rst @@ -1,17 +1,25 @@ Custom Output ============= +.. seo:: + :description: Instructions for setting up Custom C++ outputs with ESPHome. + :image: language-cpp.svg + :keywords: C++, Custom + .. warning:: - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. -This integration can be used to create custom binary and float :doc:`outputs ` +.. warning:: + + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. + +This component can be used to create custom binary and float :doc:`outputs ` in ESPHome using the C++ (Arduino) API. Please first read :doc:`/components/sensor/custom` guide, the same principles apply here. diff --git a/components/output/sigma_delta_output.rst b/components/output/sigma_delta_output.rst index 9884f00b9..1201f981c 100644 --- a/components/output/sigma_delta_output.rst +++ b/components/output/sigma_delta_output.rst @@ -1,7 +1,7 @@ Sigma-Delta Output ================== -This integration uses `sigma-delta modulation `__ +This component uses `sigma-delta modulation `__ to output a floating-point value on a binary output. Unlike with :doc:`/components/output/slow_pwm`, it is possible to update the output value with each update cycle, not just at the end of a longer period. diff --git a/components/sensor/ads1115.rst b/components/sensor/ads1115.rst index cc1640bcc..3e2eb83c4 100644 --- a/components/sensor/ads1115.rst +++ b/components/sensor/ads1115.rst @@ -36,7 +36,7 @@ Configuration variables: - **address** (**Required**, int): The i²c address of the sensor. See :ref:`I²C Addresses ` for more information. - **continuous_mode** (*Optional*, boolean): Set if the ADS1115 should continuously measure voltages or - only measure them when an update is called. Please enable this for the :doc:`ct_clamp` integration. + only measure them when an update is called. Please enable this for the :doc:`ct_clamp` component. Defaults to ``off``. - **id** (*Optional*, :ref:`config-id`): Manually specify the ID for this ADS1115 Hub. Use this if you want to use multiple ADS1115 hubs at once. diff --git a/components/sensor/airthings_ble.rst b/components/sensor/airthings_ble.rst index c29f966b4..e6fad15e7 100644 --- a/components/sensor/airthings_ble.rst +++ b/components/sensor/airthings_ble.rst @@ -135,8 +135,7 @@ Battery Level Reporting *********************** If you wish to have the 'percentage of battery life remaining' -reported as a sensor, you can make use of the :ref:`copy-sensor` -integration. +reported as a sensor, you can make use of the :ref:`copy-sensor` component. The examples below are based on standard alkaline-chemistry batteries; if you use other types of batteries you may need to adjust the diff --git a/components/sensor/as3935.rst b/components/sensor/as3935.rst index 7bc0aa4f0..d38520faa 100644 --- a/components/sensor/as3935.rst +++ b/components/sensor/as3935.rst @@ -19,7 +19,7 @@ Component/Hub The AS3935 can be configured to use either the SPI **or** I²C protocol for data communication. First choose which communication method you want to use for the sensor, set the SI pin for the appropriate -level and set up the ESPHome integration for the chosen communication method. +level and set up the ESPHome component for the chosen communication method. Module Pins ----------- diff --git a/components/sensor/bl0940.rst b/components/sensor/bl0940.rst index 9ee4eed3d..6053fddf1 100644 --- a/components/sensor/bl0940.rst +++ b/components/sensor/bl0940.rst @@ -1,5 +1,5 @@ Belling BL0940 Energy Monitor -================================== +============================= .. seo:: :description: Instructions for setting up BL0940 power monitors. @@ -16,7 +16,7 @@ Belling BL0940 Energy Monitor The ``bl0940`` sensor platform allows you to use BL0940 energy monitors sensors with ESPHome. These are used in some Tuya-devices (e.g. the power metering BW-SHP10) -The communication with this integration is done over a :ref:`UART bus `. +The communication with this component is done via a :ref:`UART `. You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 4800 with 1 stop bit. diff --git a/components/sensor/bl0942.rst b/components/sensor/bl0942.rst index 47220333c..b2757725e 100644 --- a/components/sensor/bl0942.rst +++ b/components/sensor/bl0942.rst @@ -1,5 +1,5 @@ Belling BL0942 Energy Monitor -================================== +============================= .. seo:: :description: Instructions for setting up BL0942 power monitors. @@ -9,7 +9,7 @@ Belling BL0942 Energy Monitor The ``bl0942`` sensor platform allows you to use BL0942 energy monitors sensors with ESPHome. These are used in some Tuya-devices (e.g. Aubess Tuya WiFi Mini Smart Switch With Energy Monitor) -The communication with this integration is done over a :ref:`UART bus `. +The communication with this component is done via a :ref:`UART `. You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 4800 with 1 stop bit. diff --git a/components/sensor/ccs811.rst b/components/sensor/ccs811.rst index 831d95ea8..95b4bde42 100644 --- a/components/sensor/ccs811.rst +++ b/components/sensor/ccs811.rst @@ -23,7 +23,7 @@ The ``ccs811`` sensor platform allows you to use CCS811 eCO_2 and volatile organ .. _Adafruit: https://www.adafruit.com/product/3566 The communication with this sensor is done via :ref:`I²C Bus `, so you need to have -an ``i2c:`` section in your config for this integration to work. +an ``i2c:`` section in your config for this component to work. .. code-block:: yaml diff --git a/components/sensor/cse7766.rst b/components/sensor/cse7766.rst index dcf6acd73..5b820555d 100644 --- a/components/sensor/cse7766.rst +++ b/components/sensor/cse7766.rst @@ -9,7 +9,7 @@ CSE7766 Power Sensor The ``cse7766`` sensor platform allows you to use your CSE7766 voltage/current and power sensors (`datasheet `__) sensors with ESPHome. This sensor is commonly found in Sonoff POW R2. CSE7759B is similar to CSE7766 -and works with this integration. +and works with this component. .. note:: diff --git a/components/sensor/custom.rst b/components/sensor/custom.rst index 76caada78..ad52cbeb5 100644 --- a/components/sensor/custom.rst +++ b/components/sensor/custom.rst @@ -1,16 +1,6 @@ Custom Sensor Component ======================= -.. warning:: - - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. - - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. - .. seo:: :description: Instructions for setting up Custom C++ sensors with ESPHome. :image: language-cpp.svg @@ -18,11 +8,18 @@ Custom Sensor Component .. warning:: - While I do try to keep the ESPHome configuration options as stable as possible - and back-port them, the ESPHome API is less stable. If something in the APIs needs - to be changed in order for something else to work, I will do so. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. -So, you just set up ESPHome for your ESP32/ESP8266, but sadly ESPHome is missing a sensor integration + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. + +.. warning:: + + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. + +So, you just set up ESPHome for your ESP32/ESP8266, but sadly ESPHome is missing a sensor component you'd really like to have 😕. It's pretty much impossible to support every single sensor, as there are simply too many. That's why ESPHome has a really simple API for you to create your own **custom sensors** 🎉 diff --git a/components/sensor/dsmr.rst b/components/sensor/dsmr.rst index 0f664b0e7..0181270e0 100644 --- a/components/sensor/dsmr.rst +++ b/components/sensor/dsmr.rst @@ -11,7 +11,7 @@ Component/Hub The DSMR component connects to Dutch Smart Meters which comply to DSMR (Dutch Smart Meter Requirements), also known as ‘Slimme meter’ or ‘P1 port’. -This integration supports plain non encrypted telegrams and also encrypted as used in Luxembourg. +This component supports plain non encrypted telegrams and also encrypted as used in Luxembourg. In case your equipment has encryption you must get a 32 character long encryption key from your energy company. This component is passive, it does not transmit any data to your equipment, the equipment always transmits diff --git a/components/sensor/growatt_solar.rst b/components/sensor/growatt_solar.rst index b44244688..5aefa3623 100644 --- a/components/sensor/growatt_solar.rst +++ b/components/sensor/growatt_solar.rst @@ -14,7 +14,7 @@ The ``Growatt Inverter`` sensor platform allows you to use growatt inverter data Growatt Logo -The communication with this integration is done over a :ref:`UART bus ` using :ref:`Modbus `. +The communication with this component is done over a :ref:`UART bus ` using :ref:`Modbus `. You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 9600. diff --git a/components/sensor/havells_solar.rst b/components/sensor/havells_solar.rst index 5338e6f5e..dec07ff51 100644 --- a/components/sensor/havells_solar.rst +++ b/components/sensor/havells_solar.rst @@ -16,7 +16,7 @@ with ESPHome. Havells On Grid Solar Inverter. -The communication with this integration is done over a :ref:`UART bus ` using :ref:`Modbus `. +The communication with this component is done via a :ref:`UART ` using :ref:`Modbus `. You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 9600. diff --git a/components/sensor/hlw8012.rst b/components/sensor/hlw8012.rst index eb1dcf0f7..4a635e7f7 100644 --- a/components/sensor/hlw8012.rst +++ b/components/sensor/hlw8012.rst @@ -9,12 +9,14 @@ HLW8012 Power Sensor The ``hlw8012`` sensor platform allows you to use your HLW8012 voltage/current and power sensors (`datasheet `__) sensors with ESPHome. This sensor is commonly found in Sonoff POWs. CSE7759 and BL0937 are similar to HLW8012 -and work with this integration. Beware that CSE7759B is different and should be used -with the :doc:`CSE7766 ` integration. +and work with this component. Beware that CSE7759B is different and should be used with the +:doc:`CSE7766 ` component. .. note:: - SAFETY HAZARD: Some devices such as Sonoff POWs/Shelly/etc, have the digital GND connected directly to mains voltage so **the GPIOs become LIVE during normal operation**. Our advice is to mark these boards to prevent any use of the dangerous digital pins. + SAFETY HAZARD: Some devices such as Sonoff POWs/Shelly/etc, have the digital GND connected directly to mains + voltage so **the GPIOs become LIVE during normal operation**. Our advice is to mark these boards to prevent + any use of the dangerous digital pins. This sensor has two data outputs which both encode values using the frequency of a modulated signal: CF and CF1. CF's frequency is proportional to the (active) power measured and CF1 is proportional to the current/voltage. Using diff --git a/components/sensor/inkbird_ibsth1_mini.rst b/components/sensor/inkbird_ibsth1_mini.rst index 4b641aab5..530fc4e5a 100644 --- a/components/sensor/inkbird_ibsth1_mini.rst +++ b/components/sensor/inkbird_ibsth1_mini.rst @@ -107,7 +107,7 @@ entry like in the configuration example at the top. .. note:: - The ESPHome Inkbird IBS-TH1/TH2 integration listens passively to packets the device sends by itself. + The ESPHome Inkbird IBS-TH1/TH2 component listens passively to packets the device sends by itself. ESPHome therefore has no impact on the battery life of the device. See Also diff --git a/components/sensor/mcp3204.rst b/components/sensor/mcp3204.rst index b8239a977..117b9359f 100644 --- a/components/sensor/mcp3204.rst +++ b/components/sensor/mcp3204.rst @@ -6,10 +6,9 @@ MCP3204 & MCP3208 12-Bit A/D Converters :keywords: MCP3204 MCP3208 :image: mcp3204.jpg -The Microchip Technology Inc. MCP3204 & MCP3208 -devices are successive approximation 12-bit Analog-to-Digital (A/D) converters with on-board sample and -hold circuitry. This integration is common for both device types. -configure both devices as MCP3204 and observe the maximum number of channels as per variant used. +The Microchip Technology Inc. MCP3204 & MCP3208 devices are successive approximation 12-bit Analog-to-Digital (A/D) +converters with on-board sample and hold circuitry. This component is common for both device types. +Configure both devices as MCP3204 and observe the maximum number of channels as per variant used. .. figure:: images/mcp3204.jpg :align: center diff --git a/components/sensor/mmc5983.rst b/components/sensor/mmc5983.rst index c29a5b37a..b061354d0 100644 --- a/components/sensor/mmc5983.rst +++ b/components/sensor/mmc5983.rst @@ -8,8 +8,7 @@ MMC5983 Magnetometer :image: mmc5983.jpg :keywords: MMC5983 -The ``mmc5983`` integration allows you to use your MMC5983 triple-axis magnetometer -(`datasheet`_, `SparkFun`_) with ESPHome. +The ``mmc5983`` component allows you to use your MMC5983 triple-axis magnetometer (`datasheet`_, `SparkFun`_) with ESPHome. The :ref:`I²C Bus ` is required to be set up for this sensor to work. The device supports 400kHz operation, so you may specify up to ``frequency: 400kHz`` in your ``i2c`` configuration. diff --git a/components/sensor/mopeka_pro_check.rst b/components/sensor/mopeka_pro_check.rst index d5b8b8406..ec003a832 100644 --- a/components/sensor/mopeka_pro_check.rst +++ b/components/sensor/mopeka_pro_check.rst @@ -144,7 +144,7 @@ Then just copy the address (``D3:75:F2:DC:16:91``) into a new .. note:: - The ESPHome Mopeka Pro Check BLE integration listens passively to packets the Mopeka/Lippert device sends by itself. + The ESPHome Mopeka Pro Check BLE component listens passively to packets the Mopeka/Lippert device sends by itself. ESPHome therefore has no impact on the battery life of the device. See Also diff --git a/components/sensor/mopeka_std_check.rst b/components/sensor/mopeka_std_check.rst index 43911030e..e9f7f6f6d 100644 --- a/components/sensor/mopeka_std_check.rst +++ b/components/sensor/mopeka_std_check.rst @@ -138,7 +138,7 @@ Then just copy the address (``D3:75:F2:DC:16:91``) into a new .. note:: - The ESPHome Mopeka Standard Check BLE integration listens passively to packets the Mopeka device sends by itself. + The ESPHome Mopeka Standard Check BLE component listens passively to packets the Mopeka device sends by itself. ESPHome therefore has no impact on the battery life of the device. See Also diff --git a/components/sensor/mqtt_subscribe.rst b/components/sensor/mqtt_subscribe.rst index c004949fb..ae8e723e0 100644 --- a/components/sensor/mqtt_subscribe.rst +++ b/components/sensor/mqtt_subscribe.rst @@ -10,7 +10,7 @@ The ``mqtt_subscribe`` sensor platform allows you to get external data into ESPH The sensor will subscribe to messages on the given MQTT topic and parse each message into a floating point number. -Please note this integration only works with MQTT topics that have numeric data! Each time +Please note this component only works with MQTT topics that have numeric data! Each time a message that is not a number is published a warning will be shown. Please use the MQTT subscribe text sensor for importing arbitrary text into the ESPHome ecosystem. diff --git a/components/sensor/pulse_meter.rst b/components/sensor/pulse_meter.rst index 102a20163..5941c377b 100644 --- a/components/sensor/pulse_meter.rst +++ b/components/sensor/pulse_meter.rst @@ -6,7 +6,7 @@ Pulse Meter Sensor :image: pulse.svg The pulse meter sensor allows you to count the number and frequency of pulses on any pin. It is intended to be a drop-in replacement -for the :doc:`pulse counter integration `. +for the :doc:`pulse counter component `. Rather than counting pulses over a fixed time interval, the pulse meter sensor measures the time between pulses. The precise manner in which this is done depends on the ``internal_filter_mode`` option. This leads to a higher resolution, especially for low pulse rates, as the pulse counter sensor is limited by the number of pulses within a time interval. Here's a comparison of the two sensors. The pulse meter is the smoother line. Both are set to an update interval of 10 seconds (using the ``update_interval`` and the ``throttle_average`` option respectively): diff --git a/components/sensor/pzem004t.rst b/components/sensor/pzem004t.rst index 2e339e37a..b35d2c6ae 100644 --- a/components/sensor/pzem004t.rst +++ b/components/sensor/pzem004t.rst @@ -24,7 +24,7 @@ ESPHome. The PZEM-004, however, is still working (and selling) with this protocol and does not use modbus. For using the newer V3 variant of this sensor please see :doc:`pzemac `. -The communication with this integration is done over a :ref:`UART bus `. +The communication with this component is done via a :ref:`UART `. You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 9600. diff --git a/components/sensor/pzemac.rst b/components/sensor/pzemac.rst index cebb686a1..cd3ee42dc 100644 --- a/components/sensor/pzemac.rst +++ b/components/sensor/pzemac.rst @@ -37,7 +37,7 @@ for more information. This page refers to version V3 of the PZEM004T. For using the older V1 variant of this sensor please see :doc:`pzem004t `. -The communication with this integration is done over a :ref:`UART bus ` using :ref:`Modbus `. +The communication with this component is done via a :ref:`UART ` using :ref:`Modbus `. You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 9600. diff --git a/components/sensor/pzemdc.rst b/components/sensor/pzemdc.rst index 6a7d29091..c2a9edc0e 100644 --- a/components/sensor/pzemdc.rst +++ b/components/sensor/pzemdc.rst @@ -15,7 +15,7 @@ Peacefair PZEM-00X DC Energy Monitor The ``pzemdc`` sensor platform allows you to use various DC Peacefair PZEM energy monitors with ESPHome. The supported models are: PZEM-003, PZEM-014, PZEM-016 and PZEM-017. -The communication with this integration is done over a :ref:`UART bus `. +The communication with this component is via a :ref:`UART `. You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 9600. diff --git a/components/sensor/ruuvitag.rst b/components/sensor/ruuvitag.rst index 92a3ae9d7..b38f80740 100644 --- a/components/sensor/ruuvitag.rst +++ b/components/sensor/ruuvitag.rst @@ -176,7 +176,7 @@ Then just copy the address (``FF:56:D3:2F:7D:E8``) into a new .. note:: - The ESPHome Ruuvi BLE integration listens passively to packets the RuuviTag device sends by itself. + The ESPHome Ruuvi BLE component listens passively to packets the RuuviTag device sends by itself. ESPHome therefore has no impact on the battery life of the device. See Also diff --git a/components/sensor/sdm_meter.rst b/components/sensor/sdm_meter.rst index 44067ca03..fa3192694 100644 --- a/components/sensor/sdm_meter.rst +++ b/components/sensor/sdm_meter.rst @@ -16,7 +16,7 @@ with ESPHome. SDM230M Energy Monitor. -The communication with this integration is done over a :ref:`UART bus ` using the :ref:`Modbus protocol ` +The communication with this component is done via a :ref:`UART ` using the :ref:`Modbus protocol ` over RS485 wiring. You will need an RS485 to UART converter for communication. You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 9600bps. diff --git a/components/sensor/selec_meter.rst b/components/sensor/selec_meter.rst index 392583905..fb268dffa 100644 --- a/components/sensor/selec_meter.rst +++ b/components/sensor/selec_meter.rst @@ -16,7 +16,7 @@ with ESPHome. Selec EM2M Energy Monitor. -The communication with this integration is done over a :ref:`UART bus ` using :ref:`Modbus `. +The communication with this component is done via a :ref:`UART ` using :ref:`Modbus `. You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 9600. diff --git a/components/sensor/smt100.rst b/components/sensor/smt100.rst index 93e7567fc..cfabbd757 100644 --- a/components/sensor/smt100.rst +++ b/components/sensor/smt100.rst @@ -1,5 +1,5 @@ SMT100 Soil Moisture Sensor -================================ +=========================== .. seo:: :description: Instructions for setting up SMT100 soil moisture and temperature sensor @@ -14,7 +14,9 @@ The SMT100 sensor platform allows you to use the SMT100 soil moisture and temper :width: 50.0% -The communication with this integration is done over a UART bus using a simple ASCII protocol. You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 9600. +The communication with this component is done via a :ref:`UART ` using a simple ASCII protocol. You must +therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set to some pins on your +board and the baud rate set to 9600. .. code-block:: yaml diff --git a/components/servo.rst b/components/servo.rst index 89939fba4..271a78d95 100644 --- a/components/servo.rst +++ b/components/servo.rst @@ -9,7 +9,7 @@ The ``servo`` component allows you to use servo motors with ESPHome. Servos are motor controllers that contain all the electronics necessary for driving the motor and provide a simple PWM interface to control the motor. -This integration works with both continuous-rotation and absolute servos and has a similar +This component works with both continuous-rotation and absolute servos and has a similar interface to the Arduino Servo library. First, create an :ref:`output component ` (here ``esp8266_pwm``) for the pin the diff --git a/components/switch/custom.rst b/components/switch/custom.rst index 1f9344980..5e0823171 100644 --- a/components/switch/custom.rst +++ b/components/switch/custom.rst @@ -1,21 +1,27 @@ Custom Switch ============= +.. seo:: + :description: Instructions for setting up Custom C++ switches with ESPHome. + :image: language-cpp.svg + :keywords: C++, Custom + .. warning:: - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. -This integration can be used to create custom switches in ESPHome -using the C++ (Arduino) API. +.. warning:: -Please first read :doc:`/components/sensor/custom` guide, -the same principles apply here. + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. + +This component can be used to create custom switches in ESPHome using the C++ (Arduino) API. + +Please first read :doc:`/components/sensor/custom` guide, the same principles apply here. The example below is an example of a custom switch; this custom switch is essentially the same as the gpio switch implementation. diff --git a/components/text_sensor/custom.rst b/components/text_sensor/custom.rst index e43e31f7d..f0606e19d 100644 --- a/components/text_sensor/custom.rst +++ b/components/text_sensor/custom.rst @@ -1,22 +1,28 @@ Custom Text Sensor ================== +.. seo:: + :description: Instructions for setting up Custom C++ text sensors with ESPHome. + :image: language-cpp.svg + :keywords: C++, Custom + .. warning:: - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. -This integration can be used to create custom text sensors in ESPHome -using the C++ (Arduino) API. +.. warning:: -Please first read :doc:`/components/sensor/custom` guide, -the same principles apply here and text sensors are very similar -to sensors internally. + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. + +This component can be used to create custom text sensors in ESPHome using the C++ (Arduino) API. + +Please first read :doc:`/components/sensor/custom` guide, the same principles apply here and text +sensors are very similar to sensors internally. The example below is an example of a custom text sensor which constantly publishes the message "Hello World!". diff --git a/components/text_sensor/mqtt_subscribe.rst b/components/text_sensor/mqtt_subscribe.rst index 306955c70..17a6d5966 100644 --- a/components/text_sensor/mqtt_subscribe.rst +++ b/components/text_sensor/mqtt_subscribe.rst @@ -31,7 +31,7 @@ Configuration variables: Example Usage for Displays -------------------------- -This integration is especially useful for displays, to show external data on the display. +This component is especially useful for displays, to show external data on the display. Please note you have to use the ``.c_str()`` method on the ``.state`` object together with the ``%s`` format to use it in ``printf`` expressions. diff --git a/components/tm1651.rst b/components/tm1651.rst index adc334661..8ace6218d 100644 --- a/components/tm1651.rst +++ b/components/tm1651.rst @@ -10,9 +10,9 @@ TM1651 Battery Display Battery Display --------------- -The ``tm1651`` display platform allows you to use battery display units based on TM1651 chip, like -`this one `__ -with ESPHome. Currently integration supports level and brightness setting. All updates can be made via lambda expressions. +The ``tm1651`` display platform allows you to use battery display units based on the TM1651 chip such as +`this one `__ with ESPHome. This component supports the level +and brightness settings. All updates can be made via lambda expressions. .. figure:: images/tm1651-battery-display.jpg :align: center diff --git a/custom/custom_component.rst b/custom/custom_component.rst index 5544f3aac..72e23baf9 100644 --- a/custom/custom_component.rst +++ b/custom/custom_component.rst @@ -1,20 +1,29 @@ Generic Custom Component ======================== +.. seo:: + :description: Instructions for setting up Custom C++ components with ESPHome. + :image: language-cpp.svg + :keywords: C++, Custom + .. warning:: - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. -This integration can be used to create generic custom components in ESPHome -using the C++ (Arduino) API. This integration should be used in cases where +.. warning:: + + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. + + +This component can be used to create generic custom components in ESPHome +using the C++ (Arduino) API. This component should be used in cases where none of ESPHome's abstraction layers (for example the "sensor", "binary sensor", -"switch", etc concepts) work well for your integration. +"switch", etc concepts) work well for your component. Please first read :doc:`/components/sensor/custom` guide, the same principles apply here. diff --git a/custom/i2c.rst b/custom/i2c.rst index 7b556a9ba..87940b8be 100644 --- a/custom/i2c.rst +++ b/custom/i2c.rst @@ -1,15 +1,23 @@ Custom I²C Device ================= +.. seo:: + :description: Instructions for setting up Custom C++ I2C devices with ESPHome. + :image: language-cpp.svg + :keywords: C++, Custom + .. warning:: - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. + +.. warning:: + + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. Lots of devices communicate using the I²C protocol. If you want to integrate a device into ESPHome that uses this protocol you can pretty much use almost diff --git a/custom/spi.rst b/custom/spi.rst index 1653a282c..6407d1d58 100644 --- a/custom/spi.rst +++ b/custom/spi.rst @@ -1,15 +1,23 @@ Custom SPI Device ================= +.. seo:: + :description: Instructions for setting up Custom C++ SPI devices with ESPHome. + :image: language-cpp.svg + :keywords: C++, Custom + .. warning:: - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. + +.. warning:: + + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. Lots of devices communicate using the SPI protocol. If you want to integrate a device into ESPHome that uses this protocol you can pretty much use almost diff --git a/custom/uart.rst b/custom/uart.rst index 57c52bcf0..40b71b668 100644 --- a/custom/uart.rst +++ b/custom/uart.rst @@ -1,15 +1,23 @@ Custom UART Device ================== +.. seo:: + :description: Instructions for setting up Custom C++ UART devices with ESPHome. + :image: language-cpp.svg + :keywords: C++, Custom + .. warning:: - Custom components are deprecated, not recommended for new configurations - and will be removed from ESPHome in a future release. - Please look at creating a real ESPHome component and "importing" it into your - configuration with :doc:`/components/external_components`. + Custom components are deprecated, not recommended for new configurations and will be removed from ESPHome in a + future release. Please look at creating a real ESPHome component and "importing" it into your configuration with + :doc:`/components/external_components`. - You can find some basic documentation on creating your own components - at :ref:`contributing_to_esphome`. + You can find some basic documentation on creating your own components at :ref:`contributing_to_esphome`. + +.. warning:: + + While we try to keep the ESPHome YAML configuration options as stable as possible, the ESPHome API is less + stable. If something in the APIs needs to be changed in order for something else to work, we will do so. Lots of devices communicate using the UART protocol. If you want to integrate a device into ESPHome that uses this protocol you can pretty much use almost diff --git a/guides/contributing.rst b/guides/contributing.rst index fc38f75b1..97a8a7791 100644 --- a/guides/contributing.rst +++ b/guides/contributing.rst @@ -485,7 +485,7 @@ Let's leave what's written in those files for (2.), but for now you should also whenever a component is loaded, all the C++ source files in the folder of the component are automatically copied into the generated PlatformIO project. So you just need to add the C++ source files in the folder and the ESPHome core will copy them with no additional code required -by the integration developer. +by the component developer. .. note:: @@ -520,7 +520,7 @@ called ``CONFIG_SCHEMA``. An example of such a schema is shown below: This variable is automatically loaded by the ESPHome core and validated against. The underlying system ESPHome uses for this is `voluptuous `__. Going into how to validate is out of scope for this guide, but the best way to learn is to look -at examples of how similar integrations validate user input. +at examples of how similar components validate user input. A few point on validation: @@ -537,7 +537,7 @@ After the user input has been successfully validated, the last step of the Pytho is called: Code generation. As you may know, ESPHome converts the user's configuration into C++ code (you can see the generated -code under ``/src/main.cpp``). Each integration must define its own ``to_code`` method +code under ``/src/main.cpp``). Each component must define its own ``to_code`` method that converts the user input to C++ code. This method is also automatically loaded and invoked by the ESPHome core. An example of @@ -555,10 +555,10 @@ such a method can be seen below: Again, going into all the details of ESPHome code generation would be out-of-scope. However, ESPHome's code generation is 99% syntactic sugar - and again it's probably best to study other -integrations and just copy what they do. +components and just copy what they do. There's one important concept for the ``to_code`` method: coroutines with ``yield``. -First the problem that leads to coroutines: In ESPHome, integrations can declare (via ``cg.Pvariable``) and access variables +First the problem that leads to coroutines: In ESPHome, components can declare (via ``cg.Pvariable``) and access variables (``cg.get_variable()``) - but sometimes when one part of the code base requests a variable it has not been declared yet because the code for the component creating the variable has not run yet. @@ -575,14 +575,14 @@ If you do not call "add" a piece of code explicitly, it will not be added to the ********** Okay, the Python part of the codebase is now complete - now let's talk about the C++ part of -creating a new integration. +creating a new component. -The two major parts of any integration roughly are: +The two major parts of any component roughly are: - Setup Phase - Run Phase -When you create a new integration, your new component will inherit from :apiclass:`Component`. +When you create a new component, your new component will inherit from :apiclass:`Component`. That class has a special ``setup()`` method that will be called once to set up the component - at the time the ``setup()`` method is called, all the setters generated by the Python codebase have already run and the all fields are set for your class. @@ -590,7 +590,7 @@ have already run and the all fields are set for your class. The ``setup()`` method should set up the communication interface for the component and check if communication works (if not, it should call ``mark_failed()``). -Again, look at examples of other integrations to learn more. +Again, look at examples of other components to learn more. The next thing that will be called with your component is ``loop()`` (or ``update()`` for a :apiclass:`PollingComponent`). In these methods you should retrieve the latest data from the @@ -621,11 +621,11 @@ loader. These are: - ``AUTO_LOAD``: Automatically load a component if the user hasn't added it manually. - ``MULTI_CONF``: Mark this component to accept an array of configurations. If this is an integer instead of a boolean, validation will only permit the given number of entries. -- ``CONFLICTS_WITH``: Mark a list of components as conflicting with this integration. If the user +- ``CONFLICTS_WITH``: Mark a list of components as conflicting with this component. If the user has one of them in the config, a validation error will be generated. -- ``ESP_PLATFORMS``: Provide a list of allowed ESP types this integration works with. -- ``CODEOWNERS``: GitHub usernames or team names of people that are responsible for this integration. +- ``ESP_PLATFORMS``: Provide a list of allowed ESP types this component works with. +- ``CODEOWNERS``: GitHub usernames or team names of people that are responsible for this component. You should add at least your GitHub username here, as well as anyone who helped you to write code that is being included. @@ -663,8 +663,8 @@ Standard for the esphome-core codebase: like ``Wire`` there's a problem because then the component may not modular (i.e. not possible to create two instances of a component on one ESP) -- Integrations **must** use the provided abstractions like ``Sensor``, ``Switch`` etc. - Integration should specifically **not** directly access other components like for example +- Components **must** use the provided abstractions like ``sensor``, ``switch`` etc. + Components should specifically **not** directly access other components like for example publish to MQTT topics. - Implementations for new devices should contain reference links for the datasheet and other sample diff --git a/guides/faq.rst b/guides/faq.rst index 61bc3a12b..a7b9abe9c 100644 --- a/guides/faq.rst +++ b/guides/faq.rst @@ -73,12 +73,14 @@ Tips for using ESPHome .. |include| replace:: ``!include`` .. _include: https://www.home-assistant.io/docs/configuration/splitting_configuration/ -I can't get flashing over USB to work. --------------------------------------- +I can't get flashing over USB to work +------------------------------------- .. _esphome-esptool: -ESPHome depends on the operating system the tool is running on to recognize the ESP. This can sometimes fail. Common causes are that you may not have the drivers installed (see :ref:`here `) or you are trying to upload from a Docker container and did not mount the ESP device into your container using ``--device=/dev/ttyUSB0``. +ESPHome depends on the operating system the tool is running on to recognize the ESP. This can sometimes fail. Common +causes are that you may not have the drivers installed (see :ref:`here `) or you are trying to +upload from a Docker container and did not mount the ESP device into your container using ``--device=/dev/ttyUSB0``. First, you need to get the firmware file to flash. For the Home Assistant add-on based installs you can use the ``Manual download`` method of the Dashboard (click ``Install`` in the overflow icon with the three dots @@ -90,10 +92,18 @@ Second, you need to put the ESP in :ref:`programming mode ` Third, to flash a firmware file downloaded from Home Assistant add-on Dashboard, you can use: -- `ESPHome Web `__ web-based installer, which requires a browser that supports WebSerial, like Google Chrome or Microsoft Edge. Connect the board to your computer, make sure it's detected as a :ref:`serial port `, and press **Connect**. Give the requested permission in the browser and in the popup box that appears, select the serial device which connects to your ESP. Then press **Install**, and browse for the binary file you downloaded from the Dashboard in the step above. Note that the file will be processed locally, it won't be uploaded to any cloud service. -- *esptool* `from the GitHub repository `__, package from your distro or install it yourself with ``pip install esptool`` (in case of Linux). +- `ESPHome Web `__ web-based installer, which requires a browser that supports WebSerial, like + Google Chrome or Microsoft Edge. Connect the board to your computer, make sure it's detected as a + :ref:`serial port `, and press **Connect**. Give the requested permission in the browser and in + the pop-up box that appears, select the serial device which connects to your ESP. Then press **Install**, and browse + for the binary file you downloaded from the Dashboard in the step above. Note that the file will be processed + locally, it won't be uploaded to any cloud service. +- *esptool* `from the GitHub repository `__, package from your distro or + install it yourself with ``pip install esptool`` (in case of Linux). -Before using ``esptool``, make sure you know which serial port your programming adapter is connected to. In Linux use the ``dmesg`` command afer you plug the device into the USB port to see the name of the newly detected serial port. In Windows check the Device Manager to see if a new serial port appears when you plug it in and note the COM number. +Before using ``esptool``, make sure you know which serial port your programming adapter is connected to. In Linux use +the ``dmesg`` command afer you plug the device into the USB port to see the name of the newly detected serial port. +In Windows check the Device Manager to see if a new serial port appears when you plug it in and note the COM number. Erase flash: @@ -109,15 +119,19 @@ Program flash with your firmware binary: .. note:: - If you're just seeing ``Connecting....____....`` on the screen and the flashing fails, check for these: + If you're just seeing ``Connecting....____....`` on the screen and flashing fails: - - the device name of the port has changed while you were re-plugging it too fast (eg. changed from ``/dev/ttyUSB0`` to ``/dev/ttyUSB1``). - - double check the UART wires are connected correctly if flashing using an external programmer (RX of programmer to TX of the ESP and vice-versa). + - verify that the device name of the port has not changed while you were re-plugging it too fast (eg. changed + from ``/dev/ttyUSB0`` to ``/dev/ttyUSB1``). + - double check the UART wires are connected correctly if flashing using an external programmer (RX of programmer to + TX of the ESP and vice-versa). - for some devices you need to keep ``GPIO0`` and ``GND`` connected at least until flashing has begun. - for some devices you need to power-cycle in programming mode after erasing flash, they don't auto-reset. - - it also might be a sign that ESP is defect or cannot be programmed. + - it also might be a sign that ESP is defective, damaged or otherwise cannot be programmed. - If you're in an RF noisy environment or your UART wires are a bit long, flashing can fail during transfer. Don't worry, an ESP won't brick just because of that. Put it again in programming mode and flash with a reduced baudrate for safer transfers: + If you're in an RF noisy environment or your UART wires are a bit long, flashing can fail during transfer. Don't + worry, an ESP won't brick just because of that. Put it again in programming mode and flash with a reduced baudrate + for safer transfers: ``esptool.py --port /dev/ttyUSB0 --baud 460800 write_flash 0x0 your_node_firmware.bin`` @@ -277,7 +291,7 @@ Some steps that can help with the issue: of the networking code. For this reason, we advise using a lower log level for production purposes. - Related to this, seems to be the number of clients that are simultaneously connected to the native - API server on the device. These might for example be Home Assistant (via the ESPHome integration) and + API server on the device. These might for example be Home Assistant (via the ESPHome component) and the log viewer on the web dashboard. In production, you will likely only have a single connection from Home Assistant, making this less of an issue. But beware that attaching a log viewer might have impact. @@ -367,14 +381,16 @@ And a docker compose file looks like this: .. _docker-reference-notes: .. note:: - By default ESPHome uses mDNS to show online/offline state in the dashboard view. So for that feature to work you need to enable host networking mode. + By default ESPHome uses mDNS to show online/offline state in the dashboard view. So for that feature to work you + need to enable host networking mode. On MacOS the networking mode ("-net=host" option) doesn't work as expected. You have to use another way to launch the dashboard with a port mapping option and use alternative to mDNS to have the online/offline stat (see below) mDNS might not work if your Home Assistant server and your ESPHome nodes are on different subnets. - If your router supports Avahi (eg. OpenWRT or pfSense), you are able to get mDNS working over different subnets following the steps below: + If your router supports Avahi (eg. OpenWRT or pfSense), you are able to get mDNS working over different subnets + following the steps below: 1. Enable Avahi on both subnets (install Avahi modules on OpenWRT or pfSense). 2. Enable UDP traffic from ESPHome node's subnet to 224.0.0.251/32 on port 5353. @@ -387,15 +403,22 @@ And a docker compose file looks like this: .. _faq-notes_on_disabling_mdns: Notes on disabling mDNS ------------------------------------------------------------------------------- -Some of ESPHome's functionalities rely on mDNS, so naturally :doc:`disabling ` it will cause these features to stop working. -Generally speaking, disabling mDNS without setting a :ref:`static IP address ` (or a static DHCP lease) is bound to cause problems. This is due to the fact that mDNS is used to find the IP address of each ESPHome nodes. +----------------------- +Some of ESPHome's functionalities rely on mDNS, so naturally :doc:`disabling ` it will cause these +features to stop working. +Generally speaking, disabling mDNS without setting a :ref:`static IP address ` (or a static DHCP lease) +is bound to cause problems. This is due to the fact that mDNS is used to find the IP address of each ESPHome nodes. - You will not be able to use the node's hostname to ping, find it's IP address or connect to it. -- Automatic discovery in Home Assistant when using :doc:`native API ` relies on mDNS broadcast messages to detect presence of new ESPHome nodes. If you need to use the native API with mDNS disabled, then you will have to use a static IP address and manually add the ESPHome integration with the fixed IP address. +- Automatic discovery in Home Assistant when using :doc:`native API ` relies on mDNS broadcast + messages to detect presence of new ESPHome nodes. If you need to use the native API with mDNS disabled, then you will + have to use a static IP address and manually add the ESPHome component with the fixed IP address. -- Online status detection in ESPHome's dashboard by default uses mDNS, so disabling mDNS will cause the ESPHome dashboard to show the status of the nodes created without mDNS support to be always offline. Currently, this does not affect any functionality, however if you want to see the online/offline status you could configure ESPHome to ping each node instead. See the :ref:`notes in the Docker Reference section ` for more information. +- Online status detection in ESPHome's dashboard by default uses mDNS, so disabling mDNS will cause the ESPHome + dashboard to show the status of the nodes created without mDNS support to be always offline. Currently, this does not + affect any functionality, however if you want to see the online/offline status you could configure ESPHome to ping + each node instead. See the :ref:`notes in the Docker Reference section ` for more information. Can Configuration Files Be Recovered From The Device? ----------------------------------------------------- @@ -411,25 +434,37 @@ Always back up all your files! Why shouldn't I use underscores in my device name? -------------------------------------------------- -The top level ``name:`` field in your .yaml file defines the node name(/hostname) on the local network. According to `RFC1912 `_, underscore characters (``_``) in hostnames are not valid. In reality some local DNS/DHCP setups will be ok with underscores and some will not. If connecting via a static IP address, there will probably be no issues. In some cases, initial setup using an underscore works, but later the connection might fail when Home Assistant restarts or if you change router hardware. Recommendation: use hyphen (``-``) instead of underscore if you can. +The top level ``name:`` field in your .yaml file defines the node name(/hostname) on the local network. According to +`RFC1912 `_, underscore characters (``_``) in hostnames are not valid. +In reality some local DNS/DHCP setups will be ok with underscores and some will not. If connecting via a static IP +address, there will probably be no issues. In some cases, initial setup using an underscore works, but later the +connection might fail when Home Assistant restarts or if you change router hardware. +Recommendation: use hyphen (``-``) instead of underscore if you can. -Important: follow these `instructions `_ to use the ``use_address`` parameter when renaming a live device, as the connection to an existing device will only work with the old name until the name change is complete. +Important: follow these `instructions `_ to use the +``use_address`` parameter when renaming a live device, as the connection to an existing device will only +work with the old name until the name change is complete. .. _strapping-warnings: Why am I getting a warning about strapping pins? --------------------------------------------------- +------------------------------------------------ -The ESP chips have special "strapping pins" that are read during the bootup procedure and determine how it boots up. They define whether the ESP boots into a special "flashing mode" or normal boot and a couple of other internal settings. +The ESP chips have special "strapping pins" that are read during the bootup procedure and determine how it boots up. +They define whether the ESP boots into a special "flashing mode" or normal boot and a couple of other internal settings. If an external pullup/down changes the configured voltage levels boot failures or hard to diagnose issues can happen. -While the use of them in software is not a problem, if there's something attached to the pins (particularly if they're not floating during the bootup) you may run into problems. -It's recommended to avoid them unless you have a pressing need to use them and you have reviewed the expected boot voltage levels of these pins from the ESP datasheet. +While the use of them in software is not a problem, if there's something attached to the pins (particularly if they're +not floating during the bootup) you may run into problems. +It's recommended to avoid them unless you have a pressing need to use them and you have reviewed the expected boot +voltage levels of these pins from the ESP datasheet. -Some development boards connect GPIO 0 to a button, often labeled "boot". Holding this button while the ESP is turning on will cause it to go into bootloader mode. Once the ESP is fully booted up, this button can be used as a normal input safely. +Some development boards connect GPIO 0 to a button, often labeled "boot". Holding this button while the ESP is +turning on will cause it to go into bootloader mode. Once the ESP is fully booted up, this button can be used +as a normal input safely. -Strapping pins should be safe to use as outputs if they are *only* connected to other devices that have hi-impedance inputs -with no pull-up or pull-down resistors. Note that I2C clock and data lines *do* have pull-up resistors and are not -safe on strapping pins. +Strapping pins should be safe to use as outputs if they are *only* connected to other devices that have hi-impedance +inputs with no pull-up or pull-down resistors. Note that I2C clock and data lines *do* have pull-up resistors and are +not safe on strapping pins. If you are absolutely sure that your use of strapping pins is safe, and want to suppress the warning, you can add ``ignore_strapping_warning: true`` to the relevant pin configurations. From 88e315e0e4b102996f2f2604f0ff9c6272ff514a Mon Sep 17 00:00:00 2001 From: Jesse Hills <3060199+jesserockz@users.noreply.github.com> Date: Tue, 7 May 2024 17:40:12 +1200 Subject: [PATCH 11/11] Many example yaml tidy-ups (#3821) * Many example yaml tidy-ups * Update components/sensor/hlw8012.rst --------- Co-authored-by: Keith Burzinski --- components/alarm_control_panel/template.rst | 14 +- components/at581x.rst | 17 +- components/binary_sensor/cap1188.rst | 2 +- components/binary_sensor/esp32_touch.rst | 10 +- components/binary_sensor/haier.rst | 12 +- components/binary_sensor/hydreon_rgxx.rst | 6 - components/binary_sensor/rc522.rst | 2 +- components/button/output.rst | 2 +- components/button/uart.rst | 4 - components/canbus.rst | 68 ++--- components/climate/climate_ir.rst | 16 +- components/climate/haier.rst | 9 +- components/climate/midea.rst | 11 - components/dfplayer.rst | 21 +- components/display/addressable_light.rst | 18 +- components/display/ili9xxx.rst | 16 +- components/display/lcd_display.rst | 36 +-- components/display/nextion.rst | 30 +-- components/display/qspi_amoled.rst | 12 +- components/display/st7789v.rst | 14 +- components/display/tm1621.rst | 10 +- components/display/tm1638.rst | 20 +- components/esp32_camera.rst | 16 +- components/ethernet.rst | 16 +- components/exposure_notifications.rst | 2 +- components/fan/binary.rst | 11 +- components/fan/hbridge.rst | 8 - components/fingerprint_grow.rst | 59 ++-- components/gps.rst | 3 - components/i2c.rst | 12 +- components/i2s_audio.rst | 4 +- components/light/binary.rst | 4 - components/light/esp32_rmt_led_strip.rst | 2 +- components/light/fastled.rst | 6 +- components/light/hbridge.rst | 13 +- components/light/monochromatic.rst | 5 - components/light/neopixelbus.rst | 6 +- components/light/rgb.rst | 9 +- components/light/rgbw.rst | 3 +- components/light/rgbww.rst | 3 +- components/light/rp2040_pio_led_strip.rst | 2 +- components/light/spi_led_strip.rst | 7 +- components/light/status_led.rst | 4 +- components/lightwaverf.rst | 15 +- components/lock/output.rst | 2 +- components/matrix_keypad.rst | 16 +- components/max6956.rst | 55 ++-- components/mcp23Sxx.rst | 4 +- components/media_player/i2s_audio.rst | 6 +- components/microphone/i2s_audio.rst | 8 +- components/modbus_controller.rst | 64 ++--- components/output/ac_dimmer.rst | 4 +- components/output/bp1658cj.rst | 4 +- components/output/bp5758d.rst | 4 +- components/output/esp8266_pwm.rst | 2 +- components/output/gpio.rst | 2 +- components/output/ledc.rst | 55 ++-- components/output/my9231.rst | 14 +- components/output/pca9685.rst | 8 +- components/output/sigma_delta_output.rst | 10 +- components/output/slow_pwm.rst | 2 +- components/output/sm16716.rst | 28 +- components/output/sm2135.rst | 33 +-- components/output/sm2235.rst | 4 +- components/output/sm2335.rst | 4 +- components/output/template.rst | 8 +- components/output/tlc5947.rst | 24 +- components/output/tlc5971.rst | 20 +- components/output/x9c.rst | 8 +- components/pipsolar.rst | 10 +- components/pn7150.rst | 10 +- components/pn7160.rst | 20 +- components/power_supply.rst | 2 +- components/remote_receiver.rst | 9 +- components/remote_transmitter.rst | 23 +- components/rtttl.rst | 4 +- components/sensor/adc.rst | 2 +- components/sensor/adc128s102.rst | 22 +- components/sensor/ade7880.rst | 14 +- components/sensor/ade7953.rst | 42 +-- components/sensor/ads1118.rst | 12 +- components/sensor/as3935.rst | 60 ++--- components/sensor/as5600.rst | 18 +- components/sensor/atm90e26.rst | 12 +- components/sensor/atm90e32.rst | 10 +- components/sensor/binary_sensor_map.rst | 24 +- components/sensor/bl0939.rst | 12 - components/sensor/bme280.rst | 16 +- components/sensor/cs5460a.rst | 7 +- components/sensor/cse7761.rst | 11 - components/sensor/dallas.rst | 20 +- components/sensor/daly_bms.rst | 285 ++++++++------------ components/sensor/growatt_solar.rst | 23 +- components/sensor/haier.rst | 13 - components/sensor/havells_solar.rst | 13 +- components/sensor/hlw8012.rst | 26 +- components/sensor/honeywellabp.rst | 17 +- components/sensor/hrxl_maxsonar_wr.rst | 17 +- components/sensor/hydreon_rgxx.rst | 44 +-- components/sensor/kuntze.rst | 6 - components/sensor/max31856.rst | 13 +- components/sensor/mcp3204.rst | 35 ++- components/sensor/mhz19.rst | 21 +- components/sensor/pmsx003.rst | 6 - components/sensor/pulse_counter.rst | 6 +- components/sensor/pulse_meter.rst | 6 +- components/sensor/t6615.rst | 13 +- components/sensor/teleinfo.rst | 67 +++-- components/sensor/tx20.rst | 17 +- components/sensor/vl53l0x.rst | 6 +- components/servo.rst | 4 +- components/sim800l.rst | 2 +- components/sml.rst | 63 ++--- components/sn74hc165.rst | 34 +-- components/sn74hc595.rst | 13 +- components/speaker/i2s_audio.rst | 4 +- components/spi.rst | 36 +-- components/sprinkler.rst | 50 ++-- components/status_led.rst | 6 +- components/stepper/index.rst | 18 +- components/switch/gpio.rst | 12 +- components/switch/output.rst | 2 +- components/switch/uart.rst | 4 - components/text_sensor/wl_134.rst | 7 +- components/tm1651.rst | 4 +- components/touchscreen/cst226.rst | 2 +- components/touchscreen/cst816.rst | 4 +- components/touchscreen/ektf2232.rst | 4 +- components/touchscreen/ft63x6.rst | 28 +- components/touchscreen/gt911.rst | 2 +- components/touchscreen/index.rst | 4 +- components/touchscreen/tt21100.rst | 4 +- components/touchscreen/xpt2046.rst | 4 +- components/tuya.rst | 10 +- components/uart.rst | 8 +- components/vbus.rst | 10 +- components/wiegand.rst | 24 +- cookbook/display_time_temp_oled.rst | 8 +- cookbook/garage-door.rst | 4 +- cookbook/infostrip.rst | 14 +- cookbook/lambda_magic.rst | 38 +-- custom/uart.rst | 4 +- guides/automations.rst | 16 +- guides/configuration-types.rst | 20 +- guides/contributing.rst | 4 +- guides/faq.rst | 12 +- guides/getting_started_command_line.rst | 6 +- guides/getting_started_hassio.rst | 2 +- 148 files changed, 895 insertions(+), 1539 deletions(-) diff --git a/components/alarm_control_panel/template.rst b/components/alarm_control_panel/template.rst index 91796ff95..35f80ad5c 100644 --- a/components/alarm_control_panel/template.rst +++ b/components/alarm_control_panel/template.rst @@ -27,8 +27,8 @@ Configuration variables: - **codes** (*Optional*, list of string): A list of codes for disarming the alarm, if *requires_code_to_arm* set to true then for arming the alarm too. - **requires_code_to_arm** (*Optional*, boolean): Code required for arming the alarm, *codes* must be provided. - **arming_away_time** (*Optional*, :ref:`config-time`): The exit delay before the alarm is armed to away mode. Defaults to ``0s``. -- **arming_home_time** (*Optional*, :ref:`config-time`): The exit delay before the alarm is armed to home mode. -- **arming_night_time** (*Optional*, :ref:`config-time`): The exit delay before the alarm is armed to night mode. +- **arming_home_time** (*Optional*, :ref:`config-time`): The exit delay before the alarm is armed to home mode. +- **arming_night_time** (*Optional*, :ref:`config-time`): The exit delay before the alarm is armed to night mode. - **pending_time** (*Optional*, :ref:`config-time`): The entry delay before the alarm is triggered. Defaults to ``0s``. - **trigger_time** (*Optional*, :ref:`config-time`): The time after a triggered alarm before resetting to previous state if the sensors are cleared/off. Defaults to ``0s``. - **binary_sensors** (*Optional*, *list*): A list of binary sensors the panel should use. Each consists of: @@ -169,7 +169,7 @@ Example: name: Zone 1 device_class: door pin: - number: D1 + number: GPIOXX mode: INPUT_PULLUP inverted: True - platform: gpio @@ -177,7 +177,7 @@ Example: name: Zone 2 device_class: door pin: - number: D2 + number: GPIOXX mode: INPUT_PULLUP inverted: True - platform: gpio @@ -185,7 +185,7 @@ Example: name: Zone 3 device_class: motion pin: - number: D3 + number: GPIOXX mode: INPUT_PULLUP inverted: True - platform: gpio @@ -193,7 +193,7 @@ Example: name: Zone 4 device_class: door pin: - number: D4 + number: GPIOXX mode: INPUT_PULLUP inverted: True - platform: homeassistant @@ -206,7 +206,7 @@ Example: id: siren name: Siren icon: mdi:alarm-bell - pin: D7 + pin: GPIOXX See Also diff --git a/components/at581x.rst b/components/at581x.rst index 06b33c213..9513112a2 100644 --- a/components/at581x.rst +++ b/components/at581x.rst @@ -32,17 +32,6 @@ a :doc:`/components/i2c` component (and its requisite GPIO pins) is required in id: "Radar" i2c_id: bus_a - binary_sensor: - - platform: gpio - pin: GPIO21 - name: "Radar motion" - - switch: - # Switch to turn on/off RF emission - - platform: at581x - at581x_id: "Radar" - name: "Enable Radar" - .. _at581x-component: Component/Hub @@ -87,7 +76,7 @@ The state of the radar detection is available via its GPIO pin. It's required to binary_sensor: - platform: gpio name: "Human in front" - pin: GPIO21 + pin: GPIOXX Configuration variables: ************************ @@ -127,8 +116,8 @@ Actions .. warning:: - The hardware frontend reset option is only required to reset the frontend in case it is struck, before sending the - new configuration. However, a frontend reset is always performed after changing the settings. + The hardware frontend reset option is only required to reset the frontend in case it is struck, before sending the + new configuration. However, a frontend reset is always performed after changing the settings. The radar has several settings which can be changed. These settings are not saved in non-volatile memory and need to be set on each boot. diff --git a/components/binary_sensor/cap1188.rst b/components/binary_sensor/cap1188.rst index 0cc7a5113..016720311 100644 --- a/components/binary_sensor/cap1188.rst +++ b/components/binary_sensor/cap1188.rst @@ -30,7 +30,7 @@ required to be set up in your configuration for this sensor to work. cap1188: id: cap1188_component address: 0x29 - reset_pin: 14 + reset_pin: GPIOXX touch_threshold: 0x40 allow_multiple_touches: true diff --git a/components/binary_sensor/esp32_touch.rst b/components/binary_sensor/esp32_touch.rst index 5b9363fc2..7c6bc25f3 100644 --- a/components/binary_sensor/esp32_touch.rst +++ b/components/binary_sensor/esp32_touch.rst @@ -130,8 +130,8 @@ an ``OFF`` state. binary_sensor: - platform: esp32_touch - name: "ESP32 Touch Pad GPIO27" - pin: GPIO27 + name: "ESP32 Touch Pad" + pin: GPIOXX threshold: 1000 Configuration variables: @@ -164,7 +164,7 @@ If access to the raw values is required, a template sensor can be created that p binary_sensor: - platform: esp32_touch id: esp32_touch_pad - pin: GPIO4 + pin: GPIOXX threshold: 0 sensor: @@ -174,8 +174,8 @@ If access to the raw values is required, a template sensor can be created that p return id(esp32_touch_pad).get_value(); update_interval: 3s -One example of use is a wide area pressure sensor that integrates a number of smaller sensors in an area. Make two strips -of aluminium foil that sandwich paper, and connect one wire to a touch pin and the other to ground. Set up several sensors +One example of use is a wide area pressure sensor that integrates a number of smaller sensors in an area. Make two strips +of aluminium foil that sandwich paper, and connect one wire to a touch pin and the other to ground. Set up several sensors under a flexible object like a plastic mat, add the raw values, and apply a threshold. .. _esp32-touch-pad-pins: diff --git a/components/binary_sensor/haier.rst b/components/binary_sensor/haier.rst index 29e5445f5..69a581bde 100644 --- a/components/binary_sensor/haier.rst +++ b/components/binary_sensor/haier.rst @@ -17,17 +17,17 @@ Additional sensors for Haier Climate device. **These sensors are supported only # Example configuration entry uart: baud_rate: 9600 - tx_pin: 17 - rx_pin: 16 + tx_pin: GPIOXX + rx_pin: GPIOXX id: ac_port - + climate: - platform: haier id: haier_ac protocol: hOn name: Haier AC uart_id: ac_port - + binary_sensor: - platform: haier haier_id: haier_ac @@ -56,9 +56,9 @@ Configuration variables: All options from :ref:`Binary Sensor `. - **indoor_electric_heating_status** (*Optional*): A binary sensor that indicates electrical heating system activity. All options from :ref:`Binary Sensor `. -- **indoor_fan_status** (*Optional*): A binary sensor that indicates indoor fan activity. +- **indoor_fan_status** (*Optional*): A binary sensor that indicates indoor fan activity. All options from :ref:`Binary Sensor `. -- **outdoor_fan_status** (*Optional*): A binary sensor that indicates outdoor fan activity. +- **outdoor_fan_status** (*Optional*): A binary sensor that indicates outdoor fan activity. All options from :ref:`Binary Sensor `. See Also diff --git a/components/binary_sensor/hydreon_rgxx.rst b/components/binary_sensor/hydreon_rgxx.rst index 844b9a0ca..47a5b7dba 100644 --- a/components/binary_sensor/hydreon_rgxx.rst +++ b/components/binary_sensor/hydreon_rgxx.rst @@ -12,12 +12,6 @@ For this sensor to work, a :doc:`/components/sensor/hydreon_rgxx` must be set up .. code-block:: yaml # Example RG-9 entry - - uart: - rx_pin: GPIO16 - tx_pin: GPIO17 - baud_rate: 9600 - sensor: - platform: hydreon_rgxx model: "RG_9" diff --git a/components/binary_sensor/rc522.rst b/components/binary_sensor/rc522.rst index 48e60e643..1c89732b1 100644 --- a/components/binary_sensor/rc522.rst +++ b/components/binary_sensor/rc522.rst @@ -42,7 +42,7 @@ you can then create individual binary sensors that track if an NFC/RFID tag is c spi: rc522_spi: - cs_pin: GPIO15 + cs_pin: GPIOXX binary_sensor: - platform: rc522 diff --git a/components/button/output.rst b/components/button/output.rst index 9e83019a1..d037730fc 100644 --- a/components/button/output.rst +++ b/components/button/output.rst @@ -17,7 +17,7 @@ momentarily set a GPIO pin using a button. # Example configuration entry output: - platform: gpio - pin: 25 + pin: GPIOXX id: output1 button: diff --git a/components/button/uart.rst b/components/button/uart.rst index 5799e5b8d..565e42af2 100644 --- a/components/button/uart.rst +++ b/components/button/uart.rst @@ -11,10 +11,6 @@ The ``uart`` button platform allows you to send a pre-defined sequence of bytes .. code-block:: yaml # Example configuration entry - uart: - baud_rate: 9600 - tx_pin: D0 - button: - platform: uart name: "UART String Output" diff --git a/components/canbus.rst b/components/canbus.rst index 8656ab0e4..8c562f626 100644 --- a/components/canbus.rst +++ b/components/canbus.rst @@ -69,7 +69,7 @@ Configuration variables: - ``12K5BPS`` - Support by ``esp32_can`` depends on ESP32 variant - ``16KBPS`` - Support by ``esp32_can`` depends on ESP32 variant - ``20KBPS`` - Support by ``esp32_can`` depends on ESP32 variant - - ``25KBPS`` + - ``25KBPS`` - ``31K25BPS`` - Not supported by ``esp32_can`` - ``33KBPS`` - Not supported by ``esp32_can`` - ``40KBPS`` - Not supported by ``esp32_can`` @@ -197,8 +197,8 @@ You only need to specify the RX and TX pins. Any GPIO will work. # Example configuration entry canbus: - platform: esp32_can - tx_pin: GPIO5 - rx_pin: GPIO4 + tx_pin: GPIOXX + rx_pin: GPIOXX can_id: 4 bit_rate: 50kbps on_frame: @@ -209,28 +209,28 @@ You only need to specify the RX and TX pins. Any GPIO will work. The table lists the specific bit rates supported by the component for ESP32 variants: =================== ======= ========== ========== ========== ========== ========== - bit_rate ESP32 ESP32-S2 ESP32-S3 ESP32-C3 ESP32-C6 ESP32-H2 + bit_rate ESP32 ESP32-S2 ESP32-S3 ESP32-C3 ESP32-C6 ESP32-H2 =================== ======= ========== ========== ========== ========== ========== - 1KBPS x x x x x - 5KBPS x x x x x - 10KBPS x x x x x - 12K5BPS x x x x x - 16KBPS x x x x x - 20KBPS x x x x x - 25KBPS x x x x x x - 31K25BPS - 33KBPS - 40KBPS - 50KBPS x x x x x x - 80KBPS - 83K38BPS - 95KBPS - 100KBPS x x x x x x - 125KBPS (Default) x x x x x x - 250KBPS x x x x x x - 500KBPS x x x x x x - 800KBPS x x x x x x - 1000KBPS x x x x x x + 1KBPS x x x x x + 5KBPS x x x x x + 10KBPS x x x x x + 12K5BPS x x x x x + 16KBPS x x x x x + 20KBPS x x x x x + 25KBPS x x x x x x + 31K25BPS + 33KBPS + 40KBPS + 50KBPS x x x x x x + 80KBPS + 83K38BPS + 95KBPS + 100KBPS x x x x x x + 125KBPS (Default) x x x x x x + 250KBPS x x x x x x + 500KBPS x x x x x x + 800KBPS x x x x x x + 1000KBPS x x x x x x =================== ======= ========== ========== ========== ========== ========== @@ -273,7 +273,7 @@ For wiring up the MSP2515 please refer to the section below. # Example configuration entry canbus: - platform: mcp2515 - cs_pin: D5 + cs_pin: GPIOXX can_id: 4 bit_rate: 50kbps on_frame: @@ -359,7 +359,7 @@ Standard IDs and Extended IDs can coexist on the same segment. - platform: mcp2515 id: my_mcp2515 spi_id: McpSpi - cs_pin: GPIO14 + cs_pin: GPIOXX can_id: 0x1fff use_extended_id: true bit_rate: 125kbps @@ -385,9 +385,9 @@ Button is connected on a can node which sends an A message on ID 0x100 with payl spi: id: McpSpi - clk_pin: GPIO16 - mosi_pin: GPIO5 - miso_pin: GPIO4 + clk_pin: GPIOXX + mosi_pin: GPIOXX + miso_pin: GPIOXX binary_sensor: - platform: template @@ -398,7 +398,7 @@ Button is connected on a can node which sends an A message on ID 0x100 with payl - platform: mcp2515 id: my_mcp2515 spi_id: McpSpi - cs_pin: GPIO14 + cs_pin: GPIOXX can_id: 4 bit_rate: 125kbps on_frame: @@ -430,15 +430,15 @@ Buttons are connected on the CAN-Node and also the motor is connected via CAN. spi: id: McpSpi - clk_pin: GPIO16 - mosi_pin: GPIO5 - miso_pin: GPIO4 + clk_pin: GPIOXX + mosi_pin: GPIOXX + miso_pin: GPIOXX canbus: - platform: mcp2515 id: my_mcp2515 spi_id: McpSpi - cs_pin: GPIO14 + cs_pin: GPIOXX can_id: 4 bit_rate: 125kbps on_frame: diff --git a/components/climate/climate_ir.rst b/components/climate/climate_ir.rst index 249f181a4..9cb410abc 100644 --- a/components/climate/climate_ir.rst +++ b/components/climate/climate_ir.rst @@ -76,7 +76,7 @@ controller unit. # Example configuration entry remote_transmitter: - pin: GPIO32 + pin: GPIOXX carrier_duty_percent: 50% climate: @@ -156,7 +156,7 @@ IR receiver. remote_receiver: id: rcvr pin: - number: GPIO14 + number: GPIOXX inverted: true mode: input: true @@ -283,8 +283,8 @@ Configuration variables: - **set_fan_mode** (*Optional*, string): Select the fan modes desired or that are supported on your remote. Defaults to ``3levels`` - - Options are: ``3levels`` , ``4levels``, ``quiet_4levels``. - + - Options are: ``3levels`` , ``4levels``, ``quiet_4levels``. + - ``3levels``; Low [fan speed 1], Medium [2], High [3] - ``4levels``; Low [1], Middle [2], Medium [3], High [4] - ``quiet_4levels``; Low [1], Middle [2], Medium [3], High [4], Quiet [5] @@ -292,10 +292,10 @@ Configuration variables: - **supports_dry** (*Optional*, boolean): Enables setting dry mode for this unit. Defaults to ``false``. - **supports_fan_only** (*Optional*, boolean): Enables setting fan only mode for this unit. Confirm that mode is supported on your remote. Defaults to ``false``. -- **horizontal_default** (*Optional*, string): What to default to when the AC unit's horizontal direction is *not* set to swing. Defaults to ``middle``. +- **horizontal_default** (*Optional*, string): What to default to when the AC unit's horizontal direction is *not* set to swing. Defaults to ``middle``. - Options are: ``left``, ``middle-left``, ``middle``, ``middle-right``, ``right``, ``auto`` -- **vertical_default** (*Optional*, string): What to default to when the AC unit's vertical direction is *not* set to swing. Defaults to ``middle``. +- **vertical_default** (*Optional*, string): What to default to when the AC unit's vertical direction is *not* set to swing. Defaults to ``middle``. - Options are: ``down``, ``middle-down``, ``middle``, ``middle-up``, ``up``, ``auto`` @@ -423,8 +423,8 @@ Configuration variables: ``zhlt01`` Climate --------------------- -ZH/LT-01 is a remote control that is used with many locally branded split airconditioners. -Supported brands include: +ZH/LT-01 is a remote control that is used with many locally branded split airconditioners. +Supported brands include: - Eurom - Chigo diff --git a/components/climate/haier.rst b/components/climate/haier.rst index caf04d18e..843ecfa0b 100644 --- a/components/climate/haier.rst +++ b/components/climate/haier.rst @@ -58,18 +58,11 @@ This component requires a :ref:`uart` to be setup. .. code-block:: yaml # Example configuration entry - - uart: - baud_rate: 9600 - tx_pin: 17 - rx_pin: 16 - id: ac_port - climate: - platform: haier id: haier_ac protocol: hOn - name: Haier AC + name: Haier AC uart_id: ac_port wifi_signal: true beeper: true diff --git a/components/climate/midea.rst b/components/climate/midea.rst index fc560077e..cec59359c 100644 --- a/components/climate/midea.rst +++ b/components/climate/midea.rst @@ -25,17 +25,6 @@ The ``midea`` component creates a Midea air conditioner climate device. .. code-block:: yaml # Example configuration entry - - # Disable logging over UART (required) - logger: - baud_rate: 0 - - # UART settings for Midea dongle (required) - uart: - tx_pin: 1 # hardware dependant - rx_pin: 3 # hardware dependant - baud_rate: 9600 - # Main settings climate: - platform: midea diff --git a/components/dfplayer.rst b/components/dfplayer.rst index fadc1c232..672cc4615 100644 --- a/components/dfplayer.rst +++ b/components/dfplayer.rst @@ -30,16 +30,7 @@ will be required. .. code-block:: yaml # Example configuration entry - uart: - tx_pin: GPIO2 - rx_pin: GPIO5 - baud_rate: 9600 - - # Declare DFPlayer mini module dfplayer: - on_finished_playback: - then: - logger.log: 'Somebody press play!' Configuration variables: ------------------------ @@ -113,11 +104,11 @@ Configuration options: ``dfplayer.play_mp3`` Action ---------------------------- -Plays a track inside the folder ``mp3``. Files inside the folder must be numbered from 1 +Plays a track inside the folder ``mp3``. Files inside the folder must be numbered from 1 to 9999, like ``0001.mp3``, ``0002.mp3``, ... etc. -The folder name needs to be ``mp3``, placed under the SD card root directory, and the -mp3 file name needs to be 4 digits, for example, "0001.mp3", placed under the mp3 folder. -If you want, you can add additional text after the number in the filename, for example, +The folder name needs to be ``mp3``, placed under the SD card root directory, and the +mp3 file name needs to be 4 digits, for example, "0001.mp3", placed under the mp3 folder. +If you want, you can add additional text after the number in the filename, for example, ``0001hello.mp3``, but must always be referenced by number only in yaml. .. code-block:: bash @@ -344,8 +335,8 @@ Sample code .. code-block:: yaml uart: - tx_pin: GPIO2 - rx_pin: GPIO5 + tx_pin: GPIOXX + rx_pin: GPIOXX baud_rate: 9600 dfplayer: diff --git a/components/display/addressable_light.rst b/components/display/addressable_light.rst index 44c125b7e..8f9e39481 100644 --- a/components/display/addressable_light.rst +++ b/components/display/addressable_light.rst @@ -19,18 +19,6 @@ The display requires that an :apiclass:`AddressableLight `): A lambda that returns the integer address of the LED - given the supplied the ``x`` and ``y`` pixel coordinate. By default, a left-to-right direct pixel mapper is used. + given the supplied the ``x`` and ``y`` pixel coordinate. By default, a left-to-right direct pixel mapper is used. - **lambda** (*Optional*, :ref:`lambda `): The lambda to use for rendering the content on the display. ``it`` will be an instance of :apiclass:`DisplayBuffer `. - See :ref:`display-engine` for more information. + See :ref:`display-engine` for more information. - **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. @@ -73,7 +61,7 @@ Configuration variables: When enabled (the default, but also via ``it.set_enabled(true)``), any effect currently running on the addressable light will be disabled. When disabled (``it.set_enabled(false)``), the last configured effect will be restored. - + While the display is enabled, it is still possible to control the parent addressable light component in some limited capacity. Changing the brightness will still work, but changing the color will have no affect. It is not adivsable to enable any effects (ex: rainbow, color wipe, etc) while the display is enabled, as this will cause a diff --git a/components/display/ili9xxx.rst b/components/display/ili9xxx.rst index f734b2a13..7bd3ddecc 100644 --- a/components/display/ili9xxx.rst +++ b/components/display/ili9xxx.rst @@ -55,8 +55,8 @@ beyond the basic SPI connections, and a reasonable amount of RAM, it is not well display: - platform: ili9xxx model: ili9341 - dc_pin: 27 - reset_pin: 33 + dc_pin: GPIOXX + reset_pin: GPIOXX lambda: |- it.fill(COLOR_BLACK); it.print(0, 0, id(my_font), id(my_red), TextAlign::TOP_LEFT, "Hello World!"); @@ -180,13 +180,13 @@ To configure a dimmable backlight: # Define a PWM output on the ESP32 output: - platform: ledc - pin: 32 - id: gpio_32_backlight_pwm + pin: GPIOXX + id: backlight_pwm # Define a monochromatic, dimmable light for the backlight light: - platform: monochromatic - output: gpio_32_backlight_pwm + output: backlight_pwm name: "Display Backlight" id: back_light restore_mode: ALWAYS_ON @@ -204,8 +204,8 @@ To configure an image adaptive color pallet to show greater than 8 bit color dep display: - platform: ili9xxx model: ili9341 - dc_pin: 4 - reset_pin: 22 + dc_pin: GPIOXX + reset_pin: GPIOXX rotation: 90 id: tft_ha color_palette: IMAGE_ADAPTIVE @@ -234,7 +234,7 @@ This config rotates the display into landscape mode using the driver chip. mirror_y: true color_order: bgr data_rate: 80MHz - cs_pin: 10 + cs_pin: GPIOXX dc_pin: GPIO13 reset_pin: GPIO9 diff --git a/components/display/lcd_display.rst b/components/display/lcd_display.rst index 530b13b23..c1bbf04e3 100644 --- a/components/display/lcd_display.rst +++ b/components/display/lcd_display.rst @@ -6,7 +6,7 @@ Character-Based LCD Display :image: lcd.jpg The ``lcd_pcf8574`` and ``lcd_gpio`` display components allow you to use HD44780-compatible, character-based LCDs -with ESPHome. This component is only for LCDs that display individual characters on a screen +with ESPHome. This component is only for LCDs that display individual characters on a screen (usually 8-40 columns and 2-4 rows), and not for LCDs that can control each pixel individually. .. figure:: images/lcd-hello_world.jpg @@ -15,12 +15,12 @@ with ESPHome. This component is only for LCDs that display individual characters .. note:: - Multiple versions of the display exist, supporting different character sets: - + Multiple versions of the display exist, supporting different character sets: + - HD44780UA00 English-Japanese which includes katakana characters, some Greek letters and mathematical symbols - HD44780UA02 English-European which includes Greek, Cyrillic and Western European characters (with some diacritics) - HD44780UBxx custom, manufacturer-specific character sets - + It is also possible to add eight user-defined characters. .. _lcd-pcf8574: @@ -28,7 +28,7 @@ with ESPHome. This component is only for LCDs that display individual characters lcd_pcf8574 Component --------------------- -``lcd_pcf8574`` is for LCD displays with a PCF8574 GPIO expander module connected to all the data pins. This has the +``lcd_pcf8574`` is for LCD displays with a PCF8574 GPIO expander module connected to all the data pins. This has the benefit that you only need to connect two data wires to the ESP instead of the six or ten as with the :ref:`lcd-gpio`. The communication happens via :ref:`I²C Bus `, you need to have an ``i2c:`` section in your configuration. @@ -65,7 +65,7 @@ Configuration variables: .. note:: - If you're not seeing anything on the display, try turning the contrast potentiometer around on the + If you're not seeing anything on the display, try turning the contrast potentiometer around on the PCF8574 board. .. _lcd-gpio: @@ -74,7 +74,7 @@ lcd_gpio Component ------------------ The ``lcd_gpio`` version of this component addresses the screen directly and does not employ a GPIO expander module. -Each of the data pins of the LCD needs a dedicated GPIO pin on the ESP. Connecting the screen this way offers +Each of the data pins of the LCD needs a dedicated GPIO pin on the ESP. Connecting the screen this way offers faster refresh, especially in conjunction with an :ref:`LCD Menu `. .. figure:: images/lcd_gpio.svg @@ -90,12 +90,12 @@ faster refresh, especially in conjunction with an :ref:`LCD Menu `. - platform: lcd_gpio dimensions: 20x4 data_pins: - - GPIO32 - - GPIO33 - - GPIO5 - - GPIO17 - enable_pin: D4 - rs_pin: D5 + - GPIOXX + - GPIOXX + - GPIOXX + - GPIOXX + enable_pin: GPIOXX + rs_pin: GPIOXX lambda: |- it.print("Hello World!"); @@ -105,8 +105,8 @@ Configuration variables: - **dimensions** (**Required**, string): The dimensions of the display with ``COLUMNSxROWS``. If you're not sure, power the display on, turn contrast high up and just count them. - **data_pins** (**Required**, list of :ref:`pins `): A list of the data pins you - have hooked up to the LCD. The list can either be 4 items long (operating in 4-bit mode with - either the first 4 data pins connected or the last 4 data pins connected), or 8 items long (when you have + have hooked up to the LCD. The list can either be 4 items long (operating in 4-bit mode with + either the first 4 data pins connected or the last 4 data pins connected), or 8 items long (when you have connected all 8 data pins). - **enable_pin** (**Required**, :ref:`pin `): The pin you have ``E`` (``06``) hooked up to. - **rs_pin** (**Required**, :ref:`pin `): The pin you have ``RS`` (``04``) hooked up to. @@ -118,7 +118,7 @@ Configuration variables: .. note:: - If you're not seeing anything on the display, make sure you apply ``3.3V`` to the ``VEE`` (``03``) contrast control + If you're not seeing anything on the display, make sure you apply ``3.3V`` to the ``VEE`` (``03``) contrast control pin of the board. You can use a potentiometer to make it adjustable. @@ -177,7 +177,7 @@ The LCD display has the possibility to define up to eight user defined character ``0`` to ``7`` and mirrored at ``8`` to ``15`` (i.e. ``\x08`` can be used instead of the ``\0`` that can be problematic in strings). Each character has eight lines of five bits, with the first line on the top and the most significant bit on the left, meaning that ``0b10000`` followed by six zeros and a ``0b00001`` -defines a dot at the upper left and lower right of the character. +defines a dot at the upper left and lower right of the character. .. code-block:: yaml @@ -221,7 +221,7 @@ Keep in mind that the display lambda runs for every ``update_interval``, so if t it cannot be overridden from other parts. With the ``lcd_gpio``, the backlight is lit by applying ``Vcc`` to the ``BLA`` (``15``) pin and connect ``BLK`` (``16``) -pin to ``GND``. The backlight can draw more power than the microcontroller output pins can supply, so it is advisable +pin to ``GND``. The backlight can draw more power than the microcontroller output pins can supply, so it is advisable to use a transistor as a switch to control the power for the backlight pins. Below an example for a typical use-case where the backlight is turned on when a motion sensor activates and diff --git a/components/display/nextion.rst b/components/display/nextion.rst index 95c29a89e..09d8a85f9 100644 --- a/components/display/nextion.rst +++ b/components/display/nextion.rst @@ -18,15 +18,15 @@ with ESPHome. As the communication with the Nextion LCD display is done using UART, you need to have an :ref:`UART bus ` in your configuration with ``rx_pin`` both the ``tx_pin`` set to the respective pins on the display. The Nextion uses a baud rate of 9600 by default. It may be configured to use a faster speed by adding (for -example) +example) .. code-block:: c++ baud=115200 // Sets the baud rate to 115200 bkcmd=0 // Tells the Nextion to not send responses on commands. This is the current default but can be set just in case - - + + to the ``program.s`` source file (in the Nextion Editor) before the ``page`` line. This permits faster communication with the Nextion display and it is highly recommended when using :ref:`uart-hardware_uarts`. Without a hardware uart make sure to set the baud rate to 9600. @@ -36,17 +36,9 @@ The below example configures a UART for the Nextion display to use .. code-block:: yaml # Example configuration entry - uart: - id: uart_2 - rx_pin: GPIO16 - tx_pin: GPIO17 - baud_rate: 115200 - - display: - platform: nextion id: nextion1 - uart_id: uart_2 lambda: |- it.set_component_value("gauge", 50); it.set_component_text("textview", "Hello World!"); @@ -73,7 +65,7 @@ Configuration variables: - **on_wake** (*Optional*, :ref:`Action `): An action to be performed when the Nextion wakes up. See :ref:`Nextion Automation `. - **on_page** (*Optional*, :ref:`Action `): An action to be performed after a page change. See :ref:`Nextion Automation `. - **on_touch** (*Optional*, :ref:`Action `): An action to be performed after a touch event (press or release). See :ref:`Nextion Automation `. - + .. _display-nextion_lambda: Rendering Lambda @@ -113,7 +105,7 @@ Lambda Calls ************ Several methods are available for use within :ref:`lambdas `; these permit advanced functionality beyond simple -display updates. See the full :apiref:`nextion/nextion.h` for more info. +display updates. See the full :apiref:`nextion/nextion.h` for more info. .. _nextion_upload_tft: @@ -126,7 +118,7 @@ The developer tools in Home Assistant can be used to trigger the update. The bel services: - service: update_nextion then: - - lambda: 'id(nextion1)->upload_tft();' + - lambda: 'id(nextion1)->upload_tft();' .. _nextion_update_all_components: @@ -178,7 +170,7 @@ The developer tools in Home Assistant can be used to trigger the update. The bel .. _nextion_queue_types: - Queue Types: + Queue Types: - SENSOR 0 - BINARY_SENSOR 1 - SWITCH 2 @@ -291,7 +283,7 @@ The following arguments will be available: Uploading A TFT File -------------------- This will download the file from the tft_url and will transfer it over the UART to the Nextion. -Once completed both the ESP and Nextion will reboot. During the upload process esphome will be +Once completed both the ESP and Nextion will reboot. During the upload process esphome will be unresponsive and no logging will take place. This uses the same protocol as the Nextion editor and only updates the changes of the TFT file. If HTTPS/SSL is enabled it will be about 1kB/sec. @@ -304,7 +296,7 @@ To host the TFT file you can use Home Assistant itself or any other web server. Home Assistant ************** -To host the TFT file from Home Assistant, create a www directory if it doesn't exist in your config +To host the TFT file from Home Assistant, create a www directory if it doesn't exist in your config directory. You can create a subdirectory for those files as well. For example if the file is located @@ -321,8 +313,8 @@ The below NGINX example configuration will serve files out of the /var/www/nexti .. code-block:: nginx server { - listen 80; - access_log /var/log/nginx/nextion_access.log; + listen 80; + access_log /var/log/nginx/nextion_access.log; error_log /var/log/nginx/nextion_error.log; root /var/www/nextion; } diff --git a/components/display/qspi_amoled.rst b/components/display/qspi_amoled.rst index 54e277b82..5d65d8b46 100644 --- a/components/display/qspi_amoled.rst +++ b/components/display/qspi_amoled.rst @@ -50,9 +50,9 @@ ESP-IDF. PSRAM is a requirement due to the size of the display buffer. A :ref:`q color_order: rgb invert_colors: false brightness: 255 - cs_pin: 11 - reset_pin: 13 - enable_pin: 9 + cs_pin: GPIOXX + reset_pin: GPIOXX + enable_pin: GPIOXX Configuration variables: @@ -150,17 +150,17 @@ Lilygo T-Display S3 AMOLED - 7 - 48 - 5 - + i2c: sda: 3 scl: 2 - + touchscreen: - platform: cst816 id: my_touchscreen interrupt_pin: number: 21 - + display: - platform: qspi_amoled model: RM67162 diff --git a/components/display/st7789v.rst b/components/display/st7789v.rst index 1395d5d01..e56924b6c 100644 --- a/components/display/st7789v.rst +++ b/components/display/st7789v.rst @@ -40,17 +40,13 @@ to an ESP module. .. code-block:: yaml # Example minimal configuration entry - spi: - clk_pin: GPIO18 - mosi_pin: GPIO19 - display: - platform: st7789v model: TTGO TDisplay 135x240 - backlight_pin: GPIO4 - cs_pin: GPIO5 - dc_pin: GPIO16 - reset_pin: GPIO23 + backlight_pin: GPIOXX + cs_pin: GPIOXX + dc_pin: GPIOXX + reset_pin: GPIOXX lambda: |- it.print(0, 0, id(font), "Hello World!"); @@ -191,7 +187,7 @@ Items marked RQ are hardware dependent but required and not preset. Items marked - 22 - 23 - 4 - - + - - 18 - 19 * - Custom diff --git a/components/display/tm1621.rst b/components/display/tm1621.rst index 169ff2e95..e1619a965 100644 --- a/components/display/tm1621.rst +++ b/components/display/tm1621.rst @@ -22,10 +22,10 @@ The LCD have four signal, ``cs`` for chip select, ``data`` for data signal, ``re display: platform: tm1621 id: tm1621_display - cs_pin: GPIO17 - data_pin: GPIO5 - read_pin: GPIO23 - write_pin: GPIO18 + cs_pin: GPIOXX + data_pin: GPIOXX + read_pin: GPIOXX + write_pin: GPIOXX lambda: |- it.printf(0, "%.1f", id(my_sensor1).state); it.display_celsius(true); @@ -82,7 +82,7 @@ Also we have five function to display or not some unites: - °F on the first 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)`` + - kW/h on the first line and W on the second line : ``display_kwh(bool)`` See Also -------- diff --git a/components/display/tm1638.rst b/components/display/tm1638.rst index 742f1ccbd..025d1ab99 100644 --- a/components/display/tm1638.rst +++ b/components/display/tm1638.rst @@ -23,9 +23,9 @@ The module can be powered with 5v DC. To display the colon punctuation use the display: platform: tm1638 id: tm1638_display - stb_pin: 5 - clk_pin: 18 - dio_pin: 23 + stb_pin: GPIOXX + clk_pin: GPIOXX + dio_pin: GPIOXX intensity: 5 update_interval: 5s lambda: |- @@ -113,9 +113,9 @@ The following example creates a typical digital clock with the ``:`` colon flash display: platform: tm1638 - clk_pin: 18 - dio_pin: 23 - stb_pin: 5 + clk_pin: GPIOXX + dio_pin: GPIOXX + stb_pin: GPIOXX update_interval: 500ms lambda: |- static int i = 0; @@ -132,16 +132,16 @@ The TM1638 7 Segment Display Keypad & LED Module has 8 LED lights across the top .. code-block:: yaml - switch: + switch: - platform: tm1638 id: TM1638Led1 led: 0 - + output: - platform: tm1638 id: TM1638Led2 led: 1 - + Buttons @@ -163,7 +163,7 @@ The TM1638 7 Segment Display Keypad & LED Module has 8 buttons across the top or on_release: then: - switch.turn_off: TM1638Led1 - + - platform: tm1638 name: "TM1638 Button 2" id: TM1638Button2 diff --git a/components/esp32_camera.rst b/components/esp32_camera.rst index 0981c25fc..0de4c1ffd 100644 --- a/components/esp32_camera.rst +++ b/components/esp32_camera.rst @@ -14,16 +14,16 @@ directly integrate into Home Assistant through the native API. esp32_camera: name: My Camera external_clock: - pin: GPIO27 + pin: GPIOXX frequency: 20MHz i2c_pins: - sda: GPIO25 - scl: GPIO23 - data_pins: [GPIO17, GPIO35, GPIO34, GPIO5, GPIO39, GPIO18, GPIO36, GPIO19] - vsync_pin: GPIO22 - href_pin: GPIO26 - pixel_clock_pin: GPIO21 - reset_pin: GPIO15 + sda: GPIOXX + scl: GPIOXX + data_pins: [GPIOXX, GPIOXX, GPIOXX, GPIOXX, GPIOXX, GPIOXX, GPIOXX, GPIOXX] + vsync_pin: GPIOXX + href_pin: GPIOXX + pixel_clock_pin: GPIOXX + reset_pin: GPIOXX resolution: 640x480 jpeg_quality: 10 diff --git a/components/ethernet.rst b/components/ethernet.rst index 80fa7dd0b..b10165883 100644 --- a/components/ethernet.rst +++ b/components/ethernet.rst @@ -17,8 +17,8 @@ This component and the Wi-Fi component may **not** be used simultaneously, even # Example configuration entry for RMII chips ethernet: type: LAN8720 - mdc_pin: GPIO23 - mdio_pin: GPIO18 + mdc_pin: GPIOXX + mdio_pin: GPIOXX clk_mode: GPIO0_IN phy_addr: 0 @@ -33,12 +33,12 @@ This component and the Wi-Fi component may **not** be used simultaneously, even # Example configuration entry for SPI chips ethernet: type: W5500 - clk_pin: GPIO19 - mosi_pin: GPIO21 - miso_pin: GPIO23 - cs_pin: GPIO18 - interrupt_pin: GPIO36 - reset_pin: GPIO22 + clk_pin: GPIOXX + mosi_pin: GPIOXX + miso_pin: GPIOXX + cs_pin: GPIOXX + interrupt_pin: GPIOXX + reset_pin: GPIOXX Configuration variables: ------------------------ diff --git a/components/exposure_notifications.rst b/components/exposure_notifications.rst index 75f323de3..1007cf55f 100644 --- a/components/exposure_notifications.rst +++ b/components/exposure_notifications.rst @@ -52,7 +52,7 @@ minute, the indicator will be on. switch: - platform: gpio - pin: GPIO22 + pin: GPIOXX id: led script: diff --git a/components/fan/binary.rst b/components/fan/binary.rst index eefad56e1..c7328c5e7 100644 --- a/components/fan/binary.rst +++ b/components/fan/binary.rst @@ -14,18 +14,13 @@ The ``binary`` fan platform lets you represent any binary :ref:`output` as a fan .. code-block:: yaml # Example configuration entry - output: - - id: fan_output - platform: gpio - pin: GPIO16 - fan: - platform: binary output: fan_output name: "Living Room Fan" - - - + + + Configuration variables: ------------------------ diff --git a/components/fan/hbridge.rst b/components/fan/hbridge.rst index 4ed716697..7e4295f8c 100644 --- a/components/fan/hbridge.rst +++ b/components/fan/hbridge.rst @@ -23,14 +23,6 @@ The ``hbridge`` fan platform allows you to use a compatible *h-bridge* (L298N, D .. code-block:: yaml # Example configuration entry - output: - - platform: ... - id: motor_forward_pin - pin: GPIO5 - - platform: ... - id: motor_reverse_pin - pin: GPIO4 - fan: - platform: hbridge id: my_fan diff --git a/components/fingerprint_grow.rst b/components/fingerprint_grow.rst index 56435d509..cdba66074 100644 --- a/components/fingerprint_grow.rst +++ b/components/fingerprint_grow.rst @@ -30,16 +30,10 @@ If available on your reader model, it's recommended to connect 3.3VT (touch indu .. code-block:: yaml # Example configuration entry - uart: - rx_pin: GPIO13 - tx_pin: GPIO15 - baud_rate: 57600 - - # Declare Grow Fingerprint Reader fingerprint_grow: - sensing_pin: GPIO12 + sensing_pin: GPIOXX sensor_power_pin: - number: GPIO18 + number: GPIOXX inverted: true idle_period_to_sleep: 5s @@ -93,46 +87,27 @@ Configuration variables: - **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - All other options from :ref:`Binary Sensor `. -Optional Sensor Configuration: Sensor ------ - **fingerprint_count**: The number of enrolled fingerprints stored on the reader. - - - **name** (**Required**, string): The name for the sensor. - - **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. - **last_finger_id**: The last matched enrolled fingerprint as set by :ref:`fingerprint_grow-on_finger_scan_matched`. - - - **name** (**Required**, string): The name for the sensor. - - **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. - **last_confidence**: The last matched confidence as set by :ref:`fingerprint_grow-on_finger_scan_matched`. - - - **name** (**Required**, string): The name for the sensor. - - **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. - **status**: The integer representation of the internal status register of the reader. - - - **name** (**Required**, string): The name for the sensor. - - **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. - **capacity**: The fingerprint storage capacity of the reader. - - - **name** (**Required**, string): The name for the sensor. - - **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. - **security_level**: The integer representation of the currently configured security level of the reader. Higher security levels reduce the false acceptance rate (FAR) at the expense of increasing the false rejection rate (FRR). Range is 1 (lowest) to 5 (highest). - - - **name** (**Required**, string): The name for the sensor. - - **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. .. _fingerprint_grow-sleep_mode: @@ -150,14 +125,14 @@ This is a wiring example for the R503 and below you can find the respective conf .. code-block:: yaml uart: - rx_pin: GPIO16 - tx_pin: GPIO17 + rx_pin: GPIOXX + tx_pin: GPIOXX baud_rate: 57600 - + fingerprint_grow: - sensing_pin: GPIO4 + sensing_pin: GPIOXX sensor_power_pin: - number: GPIO18 + number: GPIOXX inverted: true idle_period_to_sleep: 5s @@ -191,7 +166,7 @@ The ``new_password:`` configuration option is meant to be compiled, flashed to t ``on_finger_scan_start`` Trigger ------------------------------------ -With this configuration option, you can trigger an automation when a finger is detected touching the sensor. Very useful to indicate to the user via AuraLed that the sensor has detected the finger touch and will perform the scan. This trigger will **only** activate if your fingerprint sensor is configured with the ``sensing_pin`` option. +With this configuration option, you can trigger an automation when a finger is detected touching the sensor. Very useful to indicate to the user via AuraLed that the sensor has detected the finger touch and will perform the scan. This trigger will **only** activate if your fingerprint sensor is configured with the ``sensing_pin`` option. .. code-block:: yaml @@ -513,12 +488,12 @@ Sample code .. code-block:: yaml uart: - rx_pin: GPIO13 - tx_pin: GPIO15 + rx_pin: GPIOXX + tx_pin: GPIOXX baud_rate: 57600 fingerprint_grow: - sensing_pin: GPIO12 + sensing_pin: GPIOXX on_finger_scan_invalid: - homeassistant.event: event: esphome.test_node_finger_scan_invalid diff --git a/components/gps.rst b/components/gps.rst index 0f6834a71..94a4efbc0 100644 --- a/components/gps.rst +++ b/components/gps.rst @@ -22,9 +22,6 @@ in your configuration - only the RX pin should be necessary. .. code-block:: yaml # Example configuration entry - uart: - rx_pin: D7 - baud_rate: 9600 # Declare GPS module gps: diff --git a/components/i2c.rst b/components/i2c.rst index 48176e248..a4fe7a4df 100644 --- a/components/i2c.rst +++ b/components/i2c.rst @@ -20,8 +20,8 @@ connecting the wires from each device back to the two I²C pins on the ESP. # Example configuration entry for ESP32 i2c: - sda: 21 - scl: 22 + sda: GPIOXX + scl: GPIOXX scan: true id: bus_a @@ -51,12 +51,12 @@ Configuration variables: # Example configuration entry i2c: - id: bus_a - sda: 13 - scl: 16 + sda: GPIOXX + scl: GPIOXX scan: true - id: bus_b - sda: 14 - scl: 15 + sda: GPIOXX + scl: GPIOXX scan: true # Sensors should be specified as follows - platform: bme680 diff --git a/components/i2s_audio.rst b/components/i2s_audio.rst index 3eb07a8f6..424fc5b1d 100644 --- a/components/i2s_audio.rst +++ b/components/i2s_audio.rst @@ -14,8 +14,8 @@ This component only works on ESP32 based chips. # Example configuration entry i2s_audio: - i2s_lrclk_pin: GPIO33 - i2s_bclk_pin: GPIO19 + i2s_lrclk_pin: GPIOXX + i2s_bclk_pin: GPIOXX Configuration variables: ------------------------ diff --git a/components/light/binary.rst b/components/light/binary.rst index 43e1ee7bc..4a3bf44e5 100644 --- a/components/light/binary.rst +++ b/components/light/binary.rst @@ -20,10 +20,6 @@ The ``binary`` light platform creates a simple ON/OFF-only light from a name: "Desk Lamp" output: light_output - output: - - id: light_output - platform: gpio - pin: GPIO16 Configuration variables: ------------------------ diff --git a/components/light/esp32_rmt_led_strip.rst b/components/light/esp32_rmt_led_strip.rst index 8c4a67c2e..cb1914244 100644 --- a/components/light/esp32_rmt_led_strip.rst +++ b/components/light/esp32_rmt_led_strip.rst @@ -12,7 +12,7 @@ This is a component using the ESP32 RMT peripheral to drive most addressable LED light: - platform: esp32_rmt_led_strip rgb_order: GRB - pin: GPIO13 + pin: GPIOXX num_leds: 30 rmt_channel: 0 chipset: ws2812 diff --git a/components/light/fastled.rst b/components/light/fastled.rst index 41c61a060..f1799fca0 100644 --- a/components/light/fastled.rst +++ b/components/light/fastled.rst @@ -47,7 +47,7 @@ Clockless FastLED lights differ from the light: - platform: fastled_clockless chipset: WS2811 - pin: GPIO23 + pin: GPIOXX num_leds: 60 rgb_order: BRG name: "FastLED WS2811 Light" @@ -126,8 +126,8 @@ whereas the clockless lights only need a single pin. light: - platform: fastled_spi chipset: WS2801 - data_pin: GPIO23 - clock_pin: GPIO22 + data_pin: GPIOXX + clock_pin: GPIOXX num_leds: 60 rgb_order: BRG name: "FastLED SPI Light" diff --git a/components/light/hbridge.rst b/components/light/hbridge.rst index 6dcd095d6..07b8c23cc 100644 --- a/components/light/hbridge.rst +++ b/components/light/hbridge.rst @@ -12,23 +12,12 @@ The ``hbridge`` light platform creates a dual color brightness controlled light :align: center :width: 40.0% -H-bridge lights are very common for Christmas lighting and they use 2 wires for a bunch of LEDs. +H-bridge lights are very common for Christmas lighting and they use 2 wires for a bunch of LEDs. The pins are switched alternatively to allow two sets of lights to operate. .. code-block:: yaml # Example configuration entry - - # Specify the two pins of the h-bridge as PWM pins - output: - - platform: esp8266_pwm - id: pina - pin: GPIO12 - - platform: esp8266_pwm - id: pinb - pin: GPIO14 - - # Create a light using the hbridge light: - platform: hbridge id: mainlight diff --git a/components/light/monochromatic.rst b/components/light/monochromatic.rst index 2b86555d2..c24a9787a 100644 --- a/components/light/monochromatic.rst +++ b/components/light/monochromatic.rst @@ -26,11 +26,6 @@ The ``monochromatic`` light platform creates a simple brightness-only light from name: "Kitchen Lights" output: output_component1 - # Example output entry - output: - - platform: esp8266_pwm - id: output_component1 - pin: D1 Configuration variables: ------------------------ diff --git a/components/light/neopixelbus.rst b/components/light/neopixelbus.rst index 701fa7337..852978677 100644 --- a/components/light/neopixelbus.rst +++ b/components/light/neopixelbus.rst @@ -28,7 +28,7 @@ the `NeoPixelBus `__ library internally. - platform: neopixelbus type: GRB variant: WS2811 - pin: GPIO23 + pin: GPIOXX num_leds: 60 name: "NeoPixel Light" @@ -129,7 +129,7 @@ settings vary by method: - **esp8266_uart**: An alternative method for ESP8266s that uses the UART peripheral to send data. Available on pin GPIO1 for bus 0, and GPIO2 for bus 1. Additional options: - - **bus** (*Optional*, int): The UART bus to use. If 0, the logger ``baud_rate`` option must + - **bus** (*Optional*, int): The UART bus to use. If 0, the logger ``baud_rate`` option must be set to 0 and logs over USB/serial won't work. - **async** (*Optional*, boolean): Use an asynchronous transfer. Defaults to ``false``. If enabled, the logger must be disabled even if bus 1 is used. @@ -154,7 +154,7 @@ The following method is available only for two-wire chips (specify ``data_pin`` - **bus** (*Optional*, string): On ESP32s the SPI bus to be used can be selected. One of ``vspi`` and ``hspi``. - **speed** (*Optional*, int): The frequency to send data with. Defaults to ``10MHz``. One of ``40MHz``, ``20MHz``, ``10MHz``, ``5MHz``, ``2MHz``, ``1MHz``, ``500KHz``. - + On ESP8266 only GPIO13 can be used for ``data_pin`` and only GPIO14 can be used for ``clock_pin``. The ``method`` key also accepts a short-hand syntax consisting of a single value for historic reasons. Usage of diff --git a/components/light/rgb.rst b/components/light/rgb.rst index 61bb69936..2c1f4f837 100644 --- a/components/light/rgb.rst +++ b/components/light/rgb.rst @@ -28,12 +28,6 @@ The ``rgb`` light platform creates an RGB light from 3 :ref:`float output compon green: output_component2 blue: output_component3 - # Example output entry - output: - - platform: esp8266_pwm - id: output_component1 - pin: D1 - # Repeat for green and blue output Color Correction ---------------- @@ -54,9 +48,8 @@ perceived intensity of different colors will generally vary. This can be done by # Example output entry output: - - platform: esp8266_pwm + - platform: ... id: output_component1 - pin: D1 max_power: 80% # Repeat for green and blue output diff --git a/components/light/rgbw.rst b/components/light/rgbw.rst index 3383f8ff5..ca089b07d 100644 --- a/components/light/rgbw.rst +++ b/components/light/rgbw.rst @@ -38,9 +38,8 @@ perceived intensity of different colors will generally vary. This can be done by # Example output entry output: - - platform: esp8266_pwm + - platform: ... id: output_component1 - pin: D1 max_power: 80% .. note:: diff --git a/components/light/rgbww.rst b/components/light/rgbww.rst index f40f2dfca..426e45f1b 100644 --- a/components/light/rgbww.rst +++ b/components/light/rgbww.rst @@ -44,9 +44,8 @@ perceived intensity of different colors will generally vary. This can be done by # Example output entry output: - - platform: esp8266_pwm + - platform: ... id: output_component1 - pin: D1 max_power: 80% .. note:: diff --git a/components/light/rp2040_pio_led_strip.rst b/components/light/rp2040_pio_led_strip.rst index d012329e3..ceeda5cfa 100644 --- a/components/light/rp2040_pio_led_strip.rst +++ b/components/light/rp2040_pio_led_strip.rst @@ -13,7 +13,7 @@ This is a component using the RP2040 PIO peripheral to drive most addressable LE - platform: rp2040_pio_led_strip name: led_strip id: led_strip - pin: GPIO13 + pin: GPIOXX num_leds: 10 pio: 0 rgb_order: GRB diff --git a/components/light/spi_led_strip.rst b/components/light/spi_led_strip.rst index d6cb4a75d..31b226e09 100644 --- a/components/light/spi_led_strip.rst +++ b/components/light/spi_led_strip.rst @@ -8,7 +8,7 @@ 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 the P9813 LED driver. It should also work with HD107 and SK9822 type +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 @@ -18,14 +18,9 @@ LEDs, or any others with a similar interface - SPI, 8 bits per colour and BGR or .. code-block:: yaml # Example configuration entry - spi: - mosi_pin: GPIO3 - clk_pin: GPIO9 - light: - platform: spi_led_strip num_leds: 30 - color_correct: [80%, 60%, 100%] id: rgb_led name: "RGB LED Strip" data_rate: 1MHz diff --git a/components/light/status_led.rst b/components/light/status_led.rst index 99d1fa52f..69b315b5f 100644 --- a/components/light/status_led.rst +++ b/components/light/status_led.rst @@ -22,7 +22,7 @@ When the device is in OK state, the LED will be restored to the state of the ``b light: - platform: status_led name: "Switch state" - pin: GPIO2 + pin: GPIOXX .. note:: @@ -50,7 +50,7 @@ Configuration variables: .. code-block:: yaml pin: - number: GPIO2 + number: GPIOXX inverted: true diff --git a/components/lightwaverf.rst b/components/lightwaverf.rst index 78bcac9e5..1026b677f 100644 --- a/components/lightwaverf.rst +++ b/components/lightwaverf.rst @@ -22,19 +22,8 @@ Using an inexpensive RF transmitter and receiver you can control your devices vi # Specify the two pins to connect the receiver and transmitter lightwaverf: - read_pin: 13 - write_pin: 14 - - # Create a switch to trigger a light - switch: - - platform: template - name: "Turn off sofa" - id: light_off_ceiling_sofa - turn_on_action: - lightwaverf.send_raw: - code: [0x04, 0x00, 0x00, 0x00, 0x0f, 0x03, 0x0d, 0x09, 0x08, 0x08] - name: "Sofa" - repeat: 1 + read_pin: GPIOXX + write_pin: GPIOXX Note: To gather the RAW codes from the remote, setup the ``read_pin`` and observe in the logs the printing of the codes. diff --git a/components/lock/output.rst b/components/lock/output.rst index 282763eb7..ef07f4518 100644 --- a/components/lock/output.rst +++ b/components/lock/output.rst @@ -16,7 +16,7 @@ The ``output`` lock platform allows you to use any output component as a lock. # Example configuration entry output: - platform: gpio - pin: 25 + pin: GPIOXX id: 'generic_out' lock: - platform: output diff --git a/components/matrix_keypad.rst b/components/matrix_keypad.rst index 2820df56f..bf9703223 100644 --- a/components/matrix_keypad.rst +++ b/components/matrix_keypad.rst @@ -23,15 +23,15 @@ Component matrix_keypad: id: mykeypad rows: - - pin: 21 - - pin: 19 - - pin: 18 - - pin: 5 + - pin: GPIOXX + - pin: GPIOXX + - pin: GPIOXX + - pin: GPIOXX columns: - - pin: 17 - - pin: 16 - - pin: 4 - - pin: 15 + - pin: GPIOXX + - pin: GPIOXX + - pin: GPIOXX + - pin: GPIOXX keys: "123A456B789C*0#D" has_diodes: false diff --git a/components/max6956.rst b/components/max6956.rst index 7e2871908..9ef10f5a1 100644 --- a/components/max6956.rst +++ b/components/max6956.rst @@ -13,7 +13,7 @@ The ``max6956`` exists in 2 versions 20 or 28 ports, depending on the packaging. Once configured, you can use any of the 20 or 28 pins for your projects. Within ESPHome they emulate a real internal GPIO pin and can therefore be used with many of ESPHome's components such as the GPIO binary sensor or GPIO switch. Interrupt-on-change for inputs is not possible. -Pins can also be individualy configured as led driver and used with Light components. Current value can be set globaly or for each pin, through 16 possible levels. Driving RGB +Pins can also be individualy configured as led driver and used with Light components. Current value can be set globaly or for each pin, through 16 possible levels. Driving RGB led requires 3 pins. Any option accepting a :ref:`Pin Schema ` can theoretically be used. @@ -48,7 +48,7 @@ Configuration variables: - **brightness_global** (*Optional*): Set the value of the current to be sink by all pins configured as led driver. Defaults to ``0`` - **brightness_mode** (*Optional*): Define if the current to be sink will be confgured globaly or per pin configured as led driver. - Defaults to ``global`` + Defaults to ``global`` Binary Sensor Example @@ -58,19 +58,7 @@ Binary Sensor Example .. code-block:: yaml - # Example configuration : pin as input with pullup - i2c: - id: bus_a - sda: GPIO13 - scl: GPIO16 - scan: false - - max6956: - - id: max6956_1 - address: 0x40 - i2c_id: bus_a - - # Individual input + # Example configuration binary_sensor: - platform: gpio name: "MaxIn Pin 4" @@ -78,7 +66,7 @@ Binary Sensor Example pin: max6956: max6956_1 number: 4 - mode: + mode: input: true pullup: true inverted: False @@ -91,18 +79,7 @@ Switch Example .. code-block:: yaml - # Example configuration : pin as output - i2c: - id: bus_a - sda: GPIO13 - scl: GPIO16 - - max6956: - - id: max6956_1 - address: 0x40 - i2c_id: bus_a - - # Individual output + # Example configuration switch: - platform: gpio name: "MaxIn Pin 8" @@ -110,9 +87,9 @@ Switch Example pin: max6956: max6956_1 number: 8 - mode: + mode: output: true - inverted: False + inverted: False Led driver Example @@ -126,8 +103,8 @@ Led driver Example # Example configuration : pin as led driver, current globaly i2c: id: bus_a - sda: GPIO13 - scl: GPIO16 + sda: GPIOXX + scl: GPIOXX switch: - platform: template @@ -153,7 +130,7 @@ Led driver Example - max6956.set_brightness_global: id: max6956_1 brightness_global: !lambda return x; - + max6956: - id: max6956_1 address: 0x40 @@ -166,7 +143,7 @@ Led driver Example - platform: max6956 pin: 4 id: maxOut_pin4 - + #led binded to output light: - platform: monochromatic @@ -178,8 +155,8 @@ Led driver Example # Example configuration : pin as led driver, current managed individualy (RBG led) i2c: id: bus_a - sda: GPIO13 - scl: GPIO16 + sda: GPIOXX + scl: GPIOXX max6956: - id: max6956_1 @@ -229,7 +206,7 @@ Led driver Example - output.set_level: id: maxOut_pin4 level: !lambda return x/100; - + - platform: template name: "Number Green" id: number_LedGreen @@ -256,7 +233,7 @@ Led driver Example on_value: - output.set_level: id: maxOut_pin6 - level: !lambda return x/100; + level: !lambda return x/100; output: - platform: max6956 pin: 4 @@ -275,7 +252,7 @@ Led driver Example gamma_correct: 1 red: maxOut_pin4 green: maxOut_pin5 - blue: maxOut_pin6 + blue: maxOut_pin6 diff --git a/components/mcp23Sxx.rst b/components/mcp23Sxx.rst index c058eaf65..af26d0876 100644 --- a/components/mcp23Sxx.rst +++ b/components/mcp23Sxx.rst @@ -26,7 +26,7 @@ The MCP23S08 component (`datasheet `): The GPIO pin to use to mute the media player. - **mode** (*Optional*, string): The mode of the I²S bus. Can be ``mono`` or ``stereo``. Defaults to ``mono``. - **i2s_audio_id** (*Optional*, :ref:`config-id`): The ID of the :ref:`I²S Audio ` you wish to use for this media player. -- **i2s_comm_fmt** (*Optional*, string): I2S communication format. By default MSB format is used (AC101, PCM5102A). - Set to ``lsb`` if using an external DAC that uses Japanese (Least Significant Bit Justified) format (like PT8211). +- **i2s_comm_fmt** (*Optional*, string): I2S communication format. By default MSB format is used (AC101, PCM5102A). + Set to ``lsb`` if using an external DAC that uses Japanese (Least Significant Bit Justified) format (like PT8211). Can be ``msb`` or ``lsb``. Defaults to ``msb``. For best results, keep the wires as short as possible. diff --git a/components/microphone/i2s_audio.rst b/components/microphone/i2s_audio.rst index 468a0e1db..7e84843f9 100644 --- a/components/microphone/i2s_audio.rst +++ b/components/microphone/i2s_audio.rst @@ -24,12 +24,12 @@ This platform only works on ESP32 based chips. - platform: i2s_audio id: external_mic adc_type: external - i2s_din_pin: GPIO23 + i2s_din_pin: GPIOXX - platform: i2s_audio id: adc_mic adc_type: internal - adc_pin: GPIO35 + adc_pin: GPIOXX Configuration variables: @@ -80,7 +80,7 @@ M5Stack Atom Echo microphone: - platform: i2s_audio adc_type: external - i2s_din_pin: GPIO23 + i2s_din_pin: GPIOXX pdm: true RaspiAudio Muse Luxe @@ -90,7 +90,7 @@ RaspiAudio Muse Luxe microphone: - platform: i2s_audio - i2s_din_pin: GPIO35 + i2s_din_pin: GPIOXX adc_type: external pdm: false diff --git a/components/modbus_controller.rst b/components/modbus_controller.rst index c21b0a13e..00fcfd135 100644 --- a/components/modbus_controller.rst +++ b/components/modbus_controller.rst @@ -78,7 +78,7 @@ Technically there is no difference between the "inline" and the standard definit ... modbus: - flow_control_pin: 5 + flow_control_pin: GPIOXX id: modbus1 modbus_controller: @@ -129,43 +129,43 @@ Bitmasks Some devices use decimal values in read registers to show multiple binary states occupying only one register address. To decode them, you can use bitmasks according to the table below. The decimal value corresponding to a bit is always double of the previous one in the row. Multiple bits can be represented in a single register by making a sum of all the values corresponding to the bits. -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | Alarm bit | Description | DEC value | HEX value | -+============+==================+===========+===========+ ++============+==================+===========+===========+ | bit 0 | Binary Sensor 0 | 1 | 1 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 1 | Binary Sensor 1 | 2 | 2 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 2 | Binary Sensor 2 | 4 | 4 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 3 | Binary Sensor 3 | 8 | 8 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 4 | Binary Sensor 4 | 16 | 10 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 5 | Binary Sensor 5 | 32 | 20 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 6 | Binary Sensor 6 | 64 | 40 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 7 | Binary Sensor 7 | 128 | 80 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 8 | Binary Sensor 8 | 256 | 100 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 9 | Binary Sensor 9 | 512 | 200 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 10 | Binary Sensor 10 | 1024 | 400 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 11 | Binary Sensor 11 | 2048 | 800 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 12 | Binary Sensor 12 | 4096 | 1000 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 13 | Binary Sensor 13 | 8192 | 2000 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 14 | Binary Sensor 14 | 16384 | 4000 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ | bit 15 | Binary Sensor 15 | 32768 | 8000 | -+------------+------------------+-----------+-----------+ ++------------+------------------+-----------+-----------+ -In the example below, register ``15``, holds several binary values. It stores the decimal value ``12288``, which is the sum of ``4096`` + ``8192``, meaning the corresponding bits ``12`` and ``13`` are ``1``, the other bits are ``0``. +In the example below, register ``15``, holds several binary values. It stores the decimal value ``12288``, which is the sum of ``4096`` + ``8192``, meaning the corresponding bits ``12`` and ``13`` are ``1``, the other bits are ``0``. To gather some of these bits as binary sensors in ESPHome, use ``bitmask``: @@ -513,7 +513,7 @@ The response is mapped to the sensor based on ``register_count`` and offset in b The code synchronizes the localtime of MCU to the epever controller The time is set by writing 12 bytes to register 0x9013. Then battery charge settings are sent. - + .. code-block:: yaml esphome: @@ -565,7 +565,7 @@ The response is mapped to the sensor based on ``register_count`` and offset in b 0x04BA, // 900d Low Volt. Disconnect Volt. 11.8 0x04BA // 900E Discharging Limit Voltage 11.8 }; - + // Boost and equalization periods std::vector battery_settings2 = { 0x0000, // 906B Equalize Duration (min.) 0 @@ -574,7 +574,7 @@ The response is mapped to the sensor based on ``register_count`` and offset in b esphome::modbus_controller::ModbusCommandItem set_battery1_command = esphome::modbus_controller::ModbusCommandItem::create_write_multiple_command(controller, 0x9000, battery_settings1.size() , battery_settings1); - + esphome::modbus_controller::ModbusCommandItem set_battery2_command = esphome::modbus_controller::ModbusCommandItem::create_write_multiple_command(controller, 0x906B, battery_settings3.size(), battery_settings2); @@ -583,19 +583,19 @@ The response is mapped to the sensor based on ``register_count`` and offset in b delay(200) ; controller->queue_command(set_battery2_command); ESP_LOGI("ModbusLambda", "EPSOLAR Battery set"); - + uart: id: mod_bus - tx_pin: 19 - rx_pin: 18 + tx_pin: GPIOXX + rx_pin: GPIOXX baud_rate: 115200 stop_bits: 1 - + modbus: - #flow_control_pin: 23 + #flow_control_pin: GPIOXX send_wait_time: 200ms id: mod_bus_epever - + modbus_controller: - id: epever ## the Modbus device addr @@ -604,7 +604,7 @@ The response is mapped to the sensor based on ``register_count`` and offset in b command_throttle: 0ms setup_priority: -10 update_interval: ${updates} - + sensor: - platform: modbus_controller modbus_controller_id: epever @@ -617,7 +617,7 @@ The response is mapped to the sensor based on ``register_count`` and offset in b accuracy_decimals: 1 filters: - multiply: 0.01 - + - platform: modbus_controller modbus_controller_id: epever id: array_rated_current @@ -629,7 +629,7 @@ The response is mapped to the sensor based on ``register_count`` and offset in b accuracy_decimals: 2 filters: - multiply: 0.01 - + - platform: modbus_controller modbus_controller_id: epever id: array_rated_power diff --git a/components/output/ac_dimmer.rst b/components/output/ac_dimmer.rst index 1a7c2b1a3..0fd7ea664 100644 --- a/components/output/ac_dimmer.rst +++ b/components/output/ac_dimmer.rst @@ -33,9 +33,9 @@ There are several already made boards which are compatible with this component, output: - platform: ac_dimmer id: dimmer1 - gate_pin: D7 + gate_pin: GPIOXX zero_cross_pin: - number: D6 + number: GPIOXX mode: input: true inverted: yes diff --git a/components/output/bp1658cj.rst b/components/output/bp1658cj.rst index 84aeb2136..2743b77ba 100644 --- a/components/output/bp1658cj.rst +++ b/components/output/bp1658cj.rst @@ -24,8 +24,8 @@ It is used in some smart light bulbs: # Example configuration entry bp1658cj: - data_pin: GPIO6 - clock_pin: GPIO7 + data_pin: GPIOXX + clock_pin: GPIOXX max_power_color_channels: 4 # Valid values 0-15 max_power_white_channels: 6 # Valid values 0-15 diff --git a/components/output/bp5758d.rst b/components/output/bp5758d.rst index ffbcc2340..adde2757b 100644 --- a/components/output/bp5758d.rst +++ b/components/output/bp5758d.rst @@ -24,8 +24,8 @@ It is used in some smart light bulbs: # Example configuration entry bp5758d: - data_pin: GPIO3 - clock_pin: GPIO5 + data_pin: GPIOXX + clock_pin: GPIOXX Configuration variables: diff --git a/components/output/esp8266_pwm.rst b/components/output/esp8266_pwm.rst index e55a2dd43..ba2c572f7 100644 --- a/components/output/esp8266_pwm.rst +++ b/components/output/esp8266_pwm.rst @@ -15,7 +15,7 @@ like the one on the ESP32 (see :doc:`ledc`) are preferred. # Example configuration entry output: - platform: esp8266_pwm - pin: D1 + pin: GPIOXX frequency: 1000 Hz id: pwm_output diff --git a/components/output/gpio.rst b/components/output/gpio.rst index de9547819..26fdf0db9 100644 --- a/components/output/gpio.rst +++ b/components/output/gpio.rst @@ -14,7 +14,7 @@ will not show up in Home Assistant. See :doc:`/components/switch/gpio`. # Example configuration entry output: - platform: gpio - pin: D1 + pin: GPIOXX id: gpio_d1 Configuration variables: diff --git a/components/output/ledc.rst b/components/output/ledc.rst index 305b84350..a2e25b185 100644 --- a/components/output/ledc.rst +++ b/components/output/ledc.rst @@ -12,6 +12,32 @@ of the ESP32 as an output component. The frequency range of LEDC is from 10Hz to 40MHz - however, higher frequencies require a smaller bit depth which means the output is not that accurate for frequencies above ~300kHz. + +Configuration variables: +------------------------ + +- **pin** (**Required**, :ref:`config-pin`): The pin to use LEDC on. Can only be GPIO0-GPIO33. +- **id** (**Required**, :ref:`config-id`): The id to use for this output component. +- **frequency** (*Optional*, float): At which frequency to run the LEDC + channel’s timer. Defaults to 1000Hz. +- All other options from :ref:`Output `. + +Advanced options: + +- **channel** (*Optional*, int): Manually set the `LEDC + channel `__ + to use. Two adjacent channels share the same timer. Defaults to an automatic selection. + +Note: When configuring custom frequencies for two or more outputs, ensure that you manually specify +channel 0, 2, 4, 6 for each output. This will prevent issues that arise from automatic selection, +which chooses adjacent channels with shared timers. See +`Issue #3114 `__ for more details. + +- **phase_angle** (*Optional*, float): Set a phase angle to the other channel of this timer. + Range 0-360°, defaults to 0° + +Note: this variable is only available for the esp-idf framework + Example Usage For a Light ************************* @@ -20,8 +46,8 @@ Example Usage For a Light # Example configuration entry output: - platform: ledc - pin: GPIO19 - id: gpio_19 + pin: GPIOXX + id: gpio_ # Example usage in a light light: @@ -63,31 +89,6 @@ Example Usage For a Piezo Buzzer id: buzzer level: "50%" -Configuration variables: ------------------------- - -- **pin** (**Required**, :ref:`config-pin`): The pin to use LEDC on. Can only be GPIO0-GPIO33. -- **id** (**Required**, :ref:`config-id`): The id to use for this output component. -- **frequency** (*Optional*, float): At which frequency to run the LEDC - channel’s timer. Defaults to 1000Hz. -- All other options from :ref:`Output `. - -Advanced options: - -- **channel** (*Optional*, int): Manually set the `LEDC - channel `__ - to use. Two adjacent channels share the same timer. Defaults to an automatic selection. - -Note: When configuring custom frequencies for two or more outputs, ensure that you manually specify -channel 0, 2, 4, 6 for each output. This will prevent issues that arise from automatic selection, -which chooses adjacent channels with shared timers. See -`Issue #3114 `__ for more details. - -- **phase_angle** (*Optional*, float): Set a phase angle to the other channel of this timer. - Range 0-360°, defaults to 0° - -Note: this variable is only available for the esp-idf framework - Recommended frequencies ----------------------- diff --git a/components/output/my9231.rst b/components/output/my9231.rst index db062f5b6..c195b46dd 100644 --- a/components/output/my9231.rst +++ b/components/output/my9231.rst @@ -31,14 +31,9 @@ global ``my9231`` hub and give it an id, and then define the # Example configuration entry my9231: - - data_pin: GPIO12 - clock_pin: GPIO14 + - data_pin: GPIOXX + clock_pin: GPIOXX - # Individual outputs - output: - - platform: my9231 - id: 'my9231_output1' - channel: 0 Configuration variables: ************************ @@ -68,11 +63,6 @@ The MY931/MY9291 output component exposes a MY931/MY9291 channel of a global .. code-block:: yaml - # Example configuration entry - my9231: - - data_pin: GPIO12 - clock_pin: GPIO14 - # Individual outputs output: - platform: my9231 diff --git a/components/output/pca9685.rst b/components/output/pca9685.rst index 42772ecbf..00e9b6293 100644 --- a/components/output/pca9685.rst +++ b/components/output/pca9685.rst @@ -44,7 +44,7 @@ global ``pca9685`` hub and give it an id, and then define the output: # generate PWM from ESP32 ledc - platform: ledc - pin: 25 + pin: GPIOXX id: extclk min_power: 1 frequency: 40MHz @@ -118,10 +118,10 @@ This output can be used for different PWM functions. E.g. output for light, fan - platform: pca9685 channel: 0 id: pwm01 - + light: - - platform: monochromatic - name: 'main light' + - platform: monochromatic + name: 'main light' output: pwm01 See Also diff --git a/components/output/sigma_delta_output.rst b/components/output/sigma_delta_output.rst index 1201f981c..55b69a8a2 100644 --- a/components/output/sigma_delta_output.rst +++ b/components/output/sigma_delta_output.rst @@ -14,13 +14,13 @@ it is possible to update the output value with each update cycle, not just at th For example, if you choose to toggle the output at most once every 1 second and decide on a PWM period of 10 seconds, for reasonably frequent updates, with :doc:`/components/output/slow_pwm` there are only 10 possible levels, and for higher precision a longer update interval is needed, -restricting the update rate. +restricting the update rate. A *sigma-delta* output is updated during each cycle, thus a higher precision can be achieved, without being constrained by a calculation timeframe (=period). So instead of having to define a ``period`` where the width of the pulse determines the output level, here you -choose an ``update_interval`` which acts like a clock signal from where the pulse density determines the output level. +choose an ``update_interval`` which acts like a clock signal from where the pulse density determines the output level. This component can be used as a drop-in replacement for :doc:`/components/output/slow_pwm` by changing the ``platform`` to ``sigma_delta_output`` and changing ``period`` to ``update_interval`` (you usually want to set the *sigma-delta*'s @@ -35,7 +35,7 @@ This component can be used as a drop-in replacement for :doc:`/components/output id: sd_heater_output # Output to a pin - pin: 15 + pin: GPIOXX # Use the same output, but through automations turn_on_action: @@ -44,9 +44,9 @@ This component can be used as a drop-in replacement for :doc:`/components/output turn_off_action: then: - output.turn_off: heater_relay - + - platform: gpio - pin: 15 + pin: GPIOXX id: heater_relay Configuration variables: diff --git a/components/output/slow_pwm.rst b/components/output/slow_pwm.rst index 34d6c8aa7..bef7ae0ec 100644 --- a/components/output/slow_pwm.rst +++ b/components/output/slow_pwm.rst @@ -22,7 +22,7 @@ heating element through a relay where a fast PWM update cycle would not be appro # Example configuration entry output: - platform: slow_pwm - pin: D1 + pin: GPIOXX id: my_slow_pwm period: 15s diff --git a/components/output/sm16716.rst b/components/output/sm16716.rst index e5fc31826..d8e8bd856 100644 --- a/components/output/sm16716.rst +++ b/components/output/sm16716.rst @@ -28,22 +28,11 @@ global ``sm16716`` hub and give it an id, and then define the # Example configuration entry sm16716: - data_pin: GPIO14 - clock_pin: GPIO4 + data_pin: GPIOXX + clock_pin: GPIOXX num_channels: 3 num_chips: 1 - # Individual outputs - output: - - platform: sm16716 - id: output_red - channel: 0 - - platform: sm16716 - id: output_green - channel: 1 - - platform: sm16716 - id: output_blue - channel: 2 Configuration variables: ************************ @@ -69,13 +58,6 @@ The SM16716 output component exposes a SM16716 channel of a global .. code-block:: yaml - # Example configuration entry - sm16716: - data_pin: GPIO14 - clock_pin: GPIO4 - num_channels: 3 - num_chips: 1 - # Individual outputs output: - platform: sm16716 @@ -174,7 +156,7 @@ A complete configuration for a Feit Electric A19 looks like: The white LEDs are much brighter than the color LEDs and will fully overpower the set color when the white level is set even a little bit high. You will need to set the white level to 0 in order to get usable colors from this bulb. - + Alternative Costco Feit A19 RGBCT bulb configuration: .. code-block:: yaml @@ -224,8 +206,8 @@ Alternative Costco Feit A19 RGBCT bulb configuration: power_supply: - id: rgb_power pin: GPIO13 - - + + See Also -------- diff --git a/components/output/sm2135.rst b/components/output/sm2135.rst index 2ff9a1488..df6b064d2 100644 --- a/components/output/sm2135.rst +++ b/components/output/sm2135.rst @@ -27,31 +27,9 @@ global ``sm2135`` hub and give it an id, and then define the # Example configuration entry sm2135: - data_pin: GPIO12 - clock_pin: GPIO14 + data_pin: GPIOXX + clock_pin: GPIOXX - # Individual outputs - output: - - platform: sm2135 - id: output_red - channel: 0 - max_power: 0.8 - - platform: sm2135 - id: output_green - channel: 1 - max_power: 0.8 - - platform: sm2135 - id: output_blue - channel: 2 - max_power: 0.8 - - platform: sm2135 - id: output_white - channel: 3 - max_power: 0.8 - - platform: sm2135 - id: output_warmwhite - channel: 4 - max_power: 0.8 Configuration variables: ************************ @@ -62,7 +40,7 @@ Configuration variables: - **id** (*Optional*, :ref:`config-id`): The id to use for this ``sm2135`` component. Use this if you have multiple SM2135 chains connected at the same time. -- **cw_current** (*Optional*, current): The current used for the white channel. +- **cw_current** (*Optional*, current): The current used for the white channel. Defaults to ``10mA``. Can be one of ``10mA``, ``15mA``, ``20mA``, ``25mA``, ``30mA``, ``35mA``, ``40mA``, ``45mA``, ``50mA``, ``55mA``, ``60mA``. - **rgb_current** (*Optional*, current): The current used for the RGB channel. @@ -82,11 +60,6 @@ The SM2135 output component exposes a SM2135 channel of a global .. code-block:: yaml - # Example configuration entry - sm2135: - data_pin: GPIO12 - clock_pin: GPIO14 - # Individual outputs output: - platform: sm2135 diff --git a/components/output/sm2235.rst b/components/output/sm2235.rst index 71cbb7c30..e3008a032 100644 --- a/components/output/sm2235.rst +++ b/components/output/sm2235.rst @@ -21,8 +21,8 @@ global ``sm2235`` hub and give it an id, and then define the # Example configuration entry sm2235: - data_pin: GPIO4 - clock_pin: GPIO5 + data_pin: GPIOXX + clock_pin: GPIOXX max_power_color_channels: 9 max_power_white_channels: 9 diff --git a/components/output/sm2335.rst b/components/output/sm2335.rst index 011df7bc9..9ed107cbe 100644 --- a/components/output/sm2335.rst +++ b/components/output/sm2335.rst @@ -24,8 +24,8 @@ global ``sm2335`` hub and give it an id, and then define the # Example configuration entry sm2335: - data_pin: GPIO4 - clock_pin: GPIO5 + data_pin: GPIOXX + clock_pin: GPIOXX max_power_color_channels: 9 max_power_white_channels: 9 diff --git a/components/output/template.rst b/components/output/template.rst index 267c47cca..b479bcff7 100644 --- a/components/output/template.rst +++ b/components/output/template.rst @@ -22,14 +22,10 @@ The ``template`` output component can be used to create templated binary and flo id: output2 level: !lambda return state; - - platform: esp8266_pwm + - platform: ... id: output1 - pin: GPIO12 - inverted: true - - platform: esp8266_pwm + - platform: ... id: output2 - pin: GPIO14 - inverted: true diff --git a/components/output/tlc5947.rst b/components/output/tlc5947.rst index 57b84345d..0a880d44e 100644 --- a/components/output/tlc5947.rst +++ b/components/output/tlc5947.rst @@ -27,21 +27,9 @@ global ``tlc5947`` hub and give it an id, and then define the # Example configuration entry tlc5947: - data_pin: GPIO12 - clock_pin: GPIO14 - lat_pin: GPIO15 - - # Individual outputs - output: - - platform: tlc5947 - id: output_red - channel: 0 - - platform: tlc5947 - id: output_green - channel: 1 - - platform: tlc5947 - id: output_blue - channel: 2 + data_pin: GPIOXX + clock_pin: GPIOXX + lat_pin: GPIOXX Configuration variables: ************************ @@ -66,12 +54,6 @@ The tlc5947 output component exposes a tlc5947 channel of a global .. code-block:: yaml - # Example configuration entry - tlc5947: - data_pin: GPIO12 - clock_pin: GPIO14 - lat_pin: GPIO15 - # Individual outputs output: - platform: tlc5947 diff --git a/components/output/tlc5971.rst b/components/output/tlc5971.rst index 0a371c761..5701b3627 100644 --- a/components/output/tlc5971.rst +++ b/components/output/tlc5971.rst @@ -27,20 +27,9 @@ global ``tlc5971`` hub and give it an id, and then define the # Example configuration entry tlc5971: - data_pin: GPIO12 - clock_pin: GPIO14 + data_pin: GPIOXX + clock_pin: GPIOXX - # Individual outputs - output: - - platform: tlc5971 - id: output_red - channel: 0 - - platform: tlc5971 - id: output_green - channel: 1 - - platform: tlc5971 - id: output_blue - channel: 2 Configuration variables: ************************ @@ -63,11 +52,6 @@ The tlc5971 output component exposes a tlc5971 channel of a global .. code-block:: yaml - # Example configuration entry - tlc5971: - data_pin: GPIO12 - clock_pin: GPIO14 - # Individual outputs output: - platform: tlc5971 diff --git a/components/output/x9c.rst b/components/output/x9c.rst index ce7732d91..4a1ffebc8 100644 --- a/components/output/x9c.rst +++ b/components/output/x9c.rst @@ -15,7 +15,7 @@ The ``x9c`` output platform allows you to add an output that controls a `X9C dig The X9C family of digital potentiometers are available in different resistance values. -==================== ===================== +==================== ===================== ``X9C102`` ``1kΩ`` -------------------- --------------------- ``X9C103`` ``10kΩ`` @@ -33,9 +33,9 @@ All chips are controlled by a three wire interface and feature 100 possible wipe output: - platform: x9c id: x9c_pot - cs_pin: GPIO25 - inc_pin: GPIO27 - ud_pin: GPIO26 + cs_pin: GPIOXX + inc_pin: GPIOXX + ud_pin: GPIOXX initial_value: 0.5 Configuration variables: diff --git a/components/pipsolar.rst b/components/pipsolar.rst index d7f20ca46..5597ec1da 100644 --- a/components/pipsolar.rst +++ b/components/pipsolar.rst @@ -37,16 +37,8 @@ There is a buffer to buffer up to 10 commands. .. code-block:: yaml # Example configuration entry - uart: - - id: uart_bus - tx_pin: GPIO18 - rx_pin: GPIO19 - # most devices use 2400 as baud_rate - baud_rate: 2400 - pipsolar: - - uart_id: uart_bus - id: inverter0 + - id: inverter0 Configuration variables: ~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/components/pn7150.rst b/components/pn7150.rst index b76e6e2df..498f713ac 100644 --- a/components/pn7150.rst +++ b/components/pn7150.rst @@ -30,10 +30,10 @@ In addition, the :doc:`binary_sensor/nfc` platform may be used to quickly and ea .. code-block:: yaml pn7150_i2c: - dwl_req_pin: 17 - irq_pin: 35 - ven_pin: 16 - wkup_req_pin: 21 + dwl_req_pin: GPIOXX + irq_pin: GPIOXX + ven_pin: GPIOXX + wkup_req_pin: GPIOXX emulation_message: https://www.home-assistant.io/tag/pulse_ce tag_ttl: 1000ms @@ -348,7 +348,7 @@ NDEF Writing The examples below illustrate how NDEF messages may be written to cards/tags via the PN7150. Note that a :doc:`button ` is a great mechanism to use to trigger these actions. -The first example will write a simple, fixed NDEF message to a tag. +The first example will write a simple, fixed NDEF message to a tag. .. code-block:: yaml diff --git a/components/pn7160.rst b/components/pn7160.rst index f359a7b5d..dd8d6b5ca 100644 --- a/components/pn7160.rst +++ b/components/pn7160.rst @@ -42,11 +42,11 @@ The ``pn7160_spi`` component allows you to use :ref:`SPI-equipped ` PN7160 .. code-block:: yaml pn7160_spi: - cs_pin: 15 - dwl_req_pin: 17 - irq_pin: 35 - ven_pin: 16 - wkup_req_pin: 21 + cs_pin: GPIOXX + dwl_req_pin: GPIOXX + irq_pin: GPIOXX + ven_pin: GPIOXX + wkup_req_pin: GPIOXX emulation_message: https://www.home-assistant.io/tag/pulse_ce tag_ttl: 1000ms @@ -87,10 +87,10 @@ The ``pn7160_i2c`` component allows you to use :ref:`I²C-equipped ` PN7160 .. code-block:: yaml pn7160_i2c: - dwl_req_pin: 17 - irq_pin: 35 - ven_pin: 16 - wkup_req_pin: 21 + dwl_req_pin: GPIOXX + irq_pin: GPIOXX + ven_pin: GPIOXX + wkup_req_pin: GPIOXX emulation_message: https://www.home-assistant.io/tag/pulse_ce tag_ttl: 1000ms @@ -406,7 +406,7 @@ NDEF Writing The examples below illustrate how NDEF messages may be written to cards/tags via the PN7160. Note that a :doc:`button ` is a great mechanism to use to trigger these actions. -The first example will write a simple, fixed NDEF message to a tag. +The first example will write a simple, fixed NDEF message to a tag. .. code-block:: yaml diff --git a/components/power_supply.rst b/components/power_supply.rst index f4e69c574..bdd734a8a 100644 --- a/components/power_supply.rst +++ b/components/power_supply.rst @@ -21,7 +21,7 @@ after the last output has been disabled. # Example configuration entry power_supply: - id: 'power_supply1' - pin: 13 + pin: GPIOXX Configuration variables: ------------------------ diff --git a/components/remote_receiver.rst b/components/remote_receiver.rst index d3eb1f6f5..b6bbac710 100644 --- a/components/remote_receiver.rst +++ b/components/remote_receiver.rst @@ -20,7 +20,7 @@ which will trigger when they hear their own configured signal. # Example configuration entry remote_receiver: - pin: GPIO32 + pin: GPIOXX dump: all Configuration variables: @@ -206,10 +206,6 @@ then immediately OFF. .. code-block:: yaml # Example configuration entry - remote_receiver: - pin: GPIO32 - dump: all - binary_sensor: - platform: remote_receiver name: "Panasonic Remote Input" @@ -439,7 +435,7 @@ Remote code selection (exactly one of these has to be included): remote_receiver: pin: - number: D4 + number: GPIOXX inverted: true mode: input: true @@ -475,4 +471,3 @@ See Also - `IRRemoteESP8266 `__ by `Mark Szabo-Simon `__ - :apiref:`remote/remote_receiver.h` - :ghedit:`Edit` - diff --git a/components/remote_transmitter.rst b/components/remote_transmitter.rst index 5d34b30b3..6f18cfb75 100644 --- a/components/remote_transmitter.rst +++ b/components/remote_transmitter.rst @@ -24,18 +24,9 @@ remote signals. # Example configuration entry remote_transmitter: - pin: GPIO32 + pin: GPIOXX carrier_duty_percent: 50% - # Individual switches - switch: - - platform: template - name: "Panasonic TV Off" - turn_on_action: - remote_transmitter.transmit_panasonic: - address: 0x4004 - command: 0x100BCBD - Configuration variables: ------------------------ @@ -293,7 +284,7 @@ Configuration variables: - **id** (**Required**, int): The 24-bit ID to send. Each remote has a unique one. - **channel** (**Required**, int): The 8-bit channel to send, between 0 and 255 inclusive. -- **button** (**Required**, int): The 4-bit button to send, between 0 and 15 inclusive. +- **button** (**Required**, int): The 4-bit button to send, between 0 and 15 inclusive. - **check** (**Required**, int): The 4-bit check to send. Includes an indication that a button is being held down. See dumper output for more info. - All other options from :ref:`remote_transmitter-transmit_action`. @@ -911,7 +902,7 @@ remote_receiver instance: .. code-block:: yaml remote_receiver: - pin: D0 + pin: GPIOXX dump: all Compile and upload the code. While viewing the log output from the ESP, @@ -940,7 +931,7 @@ IR diode to a new pin on the ESP and configure a global ``remote_transmitter`` i .. code-block:: yaml remote_transmitter: - pin: D1 + pin: GPIOXX # Infrared remotes use a 50% carrier signal carrier_duty_percent: 50% @@ -986,7 +977,7 @@ First, connect the RF module to a pin on the ESP and set up a remote_receiver in .. code-block:: yaml remote_receiver: - pin: D0 + pin: GPIOXX dump: all # Settings to optimize recognition of RF devices tolerance: 50% @@ -1018,7 +1009,7 @@ You should see log output like below: .. code-block:: yaml remote_receiver: - pin: D0 + pin: GPIOXX dump: - rc_switch tolerance: 50% @@ -1036,7 +1027,7 @@ RF transmitter to a new pin on the ESP and configure a global ``remote_transmitt .. code-block:: yaml remote_transmitter: - pin: D1 + pin: GPIOXX # RF uses a 100% carrier signal carrier_duty_percent: 100% diff --git a/components/rtttl.rst b/components/rtttl.rst index d8e6e2c70..b502a649e 100644 --- a/components/rtttl.rst +++ b/components/rtttl.rst @@ -127,7 +127,7 @@ Common beeps You can do your own beep patterns too! Here's a short collection so you can just use right away or tweak them to your like: -.. code-block:: +.. code-block:: two_short:d=4,o=5,b=100:16e6,16e6 long:d=1,o=5,b=100:e6 @@ -165,7 +165,7 @@ Sample code output: - platform: esp8266_pwm - pin: D1 + pin: GPIOXX id: rtttl_out rtttl: diff --git a/components/sensor/adc.rst b/components/sensor/adc.rst index 3f6145292..fdb43a66a 100644 --- a/components/sensor/adc.rst +++ b/components/sensor/adc.rst @@ -22,7 +22,7 @@ ADC in your device to measure a voltage on certain pins. # Example configuration entry sensor: - platform: adc - pin: A0 + pin: GPIOXX name: "Living Room Brightness" update_interval: 60s diff --git a/components/sensor/adc128s102.rst b/components/sensor/adc128s102.rst index 779997910..780d016d4 100644 --- a/components/sensor/adc128s102.rst +++ b/components/sensor/adc128s102.rst @@ -6,8 +6,8 @@ ADC128S102 8-Channel 12-Bit A/D Converter :keywords: ADC128S102 :image: adc128s102.png -The ADC128S102 is a low-power, eight-channel CMOS 12-bit analog-to-digital converter specified for conversion -throughput rates of 500 ksps to 1 MSPS. The converter is based on a successive-approximation register architecture +The ADC128S102 is a low-power, eight-channel CMOS 12-bit analog-to-digital converter specified for conversion +throughput rates of 500 ksps to 1 MSPS. The converter is based on a successive-approximation register architecture with an internal track-and-hold circuit. .. figure:: images/adc128s102.png @@ -31,16 +31,9 @@ sensors for your projects. # Example configuration entry adc128s102: - cs_pin: GPIO15 + cs_pin: GPIOXX id: my_adc - sensor: - - platform: adc128s102 # Attached to pin 0 of the ADC128S102. - update_interval: 1s - adc128s102_id: my_adc - id: freezer_temp_source - channel: 0 # ADC128S102 channel - Configuration variables: - **id** (**Required**, :ref:`config-id`): The id to use for this ADC128S102 component. - **cs_pin** (**Required**, int): The SPI cable select pin to use @@ -52,6 +45,15 @@ The ``adc128s102`` sensor allows you to use your ADC128S102 12-Bit A/D Converter First, setup a :ref:`ADC128S102 Hub ` for your ADC128S102 sensor and then use this sensor platform to create individual sensors that will report the voltage to Home Assistant. +.. code-block:: yaml + + sensor: + - platform: adc128s102 # Attached to pin 0 of the ADC128S102. + update_interval: 1s + adc128s102_id: my_adc + id: freezer_temp_source + channel: 0 # ADC128S102 channel + Configuration variables: - **adc128s102_id** (**Required**, :ref:`config-id`): The id of the parent ADC128S102 component. diff --git a/components/sensor/ade7880.rst b/components/sensor/ade7880.rst index aca0c5a90..139aaf8e7 100644 --- a/components/sensor/ade7880.rst +++ b/components/sensor/ade7880.rst @@ -190,9 +190,9 @@ configured). sensor: - platform: ade7880 irq0_pin: - number: GPIO13 + number: GPIOXX irq1_pin: - number: GPIO5 + number: GPIOXX phase_a: name: Room Heater voltage: Voltage @@ -217,9 +217,9 @@ Heater Current', etc. sensor: - platform: ade7880 irq0_pin: - number: GPIO13 + number: GPIOXX irq1_pin: - number: GPIO5 + number: GPIOXX phase_a: voltage: Voltage current: @@ -249,11 +249,11 @@ configuration mode. sensor: - platform: ade7880 irq0_pin: - number: GPIO13 + number: GPIOXX irq1_pin: - number: GPIO5 + number: GPIOXX reset_pin: - number: GPIO16 + number: GPIOXX frequency: 60Hz phase_a: name: Phase A diff --git a/components/sensor/ade7953.rst b/components/sensor/ade7953.rst index f7e9d920c..c9aa54c02 100644 --- a/components/sensor/ade7953.rst +++ b/components/sensor/ade7953.rst @@ -35,7 +35,7 @@ Over I²C # Example configuration entry for i2c sensor: - platform: ade7953_i2c - irq_pin: GPIO16 + irq_pin: GPIOXX voltage: name: ADE7953 Voltage frequency: @@ -129,69 +129,35 @@ Over SPI .. code-block:: yaml - # Example configuration entry for SPI (taken from a Shelly Pro 4PM) + # Example configuration entry for SPI sensor: - platform: ade7953_spi - cs_pin: GPIO04 - irq_pin: GPIO35 - current_pga_gain_a: 2x - current_pga_gain_b: 2x - current_gain_a: 0x600000 - current_gain_b: 0x600000 + cs_pin: GPIOXX + irq_pin: GPIOXX voltage: name: "Voltage" - filters: - - delta: 1 frequency: name: ADE7953 Frequency - filters: - - delta: 0.1 current_a: name: "Current A" - filters: - - delta: 0.01 current_b: name: "Current B" - filters: - - delta: 0.01 power_factor_a: name: "Power Factor A" - filters: - - delta: 5 power_factor_b: name: "ADE7953 Power Factor B" - filters: - - delta: 5 apparent_power_a: name: "Apparent Power A" - filters: - - delta: 1 apparent_power_b: name: "Apparent Power B" - filters: - - delta: 1 active_power_a: name: "Power A" - id: active_power_1 - # active_power is inverted, so multiply by -1 - filters: - - multiply: -1 - - delta: 1 active_power_b: name: "Power B" - id: active_power_2 - # active_power is inverted, so multiply by -1 - filters: - - multiply: -1 - - delta: 1 reactive_power_a: name: "Reactive Power A" - filters: - - delta: 1 reactive_power_b: name: "Reactive Power B" - filters: - - delta: 1 Configuration variables: ************************ diff --git a/components/sensor/ads1118.rst b/components/sensor/ads1118.rst index 52947293b..416fcc05f 100644 --- a/components/sensor/ads1118.rst +++ b/components/sensor/ads1118.rst @@ -25,7 +25,7 @@ It uses the :ref:`SPI Bus ` for communication. .. code-block:: yaml ads1118: - cs_pin: GPIO15 + cs_pin: GPIOXX Configuration variables: ************************ @@ -46,14 +46,12 @@ sensor platform to create individual sensors that will report the voltage. .. code-block:: yaml - ads1118: - cs_pin: GPIO15 sensor: - platform: ads1118 - type: 'adc' - id: 'batt_volt' - name: "Battery Voltage" - multiplexer: 'A3_GND' + type: adc + id: batt_volt + name: Battery Voltage + multiplexer: A3_GND gain: 4.096 update_interval: .01s diff --git a/components/sensor/as3935.rst b/components/sensor/as3935.rst index d38520faa..c8e20951f 100644 --- a/components/sensor/as3935.rst +++ b/components/sensor/as3935.rst @@ -58,20 +58,10 @@ The ``as3935_spi`` sensor platform allows you to use your AS3935 sensor .. code-block:: yaml - # Example configuration for SPI (decide for one!) + # Example configuration for SPI as3935_spi: - cs_pin: GPIO12 - irq_pin: GPIO13 - # Example lightning and energy sensor - sensor: - - platform: as3935 - lightning_energy: - name: "Lightning Energy" - distance: - name: "Distance Storm" - binary_sensor: - - platform: as3935 - name: "Storm Alert" + cs_pin: GPIOXX + irq_pin: GPIOXX Configuration variables: @@ -117,19 +107,9 @@ The ``as3935_i2c`` sensor platform allows you to use your AS3935 sensor .. code-block:: yaml - # Example configuration for I²C (decide for one!) + # Example configuration for I²C as3935_i2c: - irq_pin: GPIO12 - # Example shared configuration - sensor: - - platform: as3935 - lightning_energy: - name: "Lightning Energy" - distance: - name: "Distance Storm" - binary_sensor: - - platform: as3935 - name: "Storm Alert" + irq_pin: GPIOXX Configuration variables: ************************ @@ -173,19 +153,22 @@ Sensor A sensor platform to read lightning data +.. code-block:: yaml + + sensor: + - platform: as3935 + lightning_energy: + name: Lightning Energy + distance: + name: Distance Storm + Configuration variables: - **lightning_energy** (*Optional*): Lightning energy value. According to the datasheet this is only a pure value that doesn't have any physical meaning. - - - **name** (**Required**, string): The name for the lightning energy sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. - **distance** (*Optional*): Distance in km to the front of the storm and not the distance to a lightning strike. - - - **name** (**Required**, string): The name for the distance sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. Binary Sensor @@ -193,11 +176,16 @@ Binary Sensor Binary sensor that indicates if a lightning strike was detected. +.. code-block:: yaml + + # Example storm alert binary sensor + binary_sensor: + - platform: as3935 + name: Storm Alert + Configuration variables: -- **name** (**Required**, string): The name of the binary sensor. -- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. -- All other options from :ref:`Binary Sensor `. +- All options from :ref:`Binary Sensor `. See Also diff --git a/components/sensor/as5600.rst b/components/sensor/as5600.rst index 51fe34b41..80126e3f5 100644 --- a/components/sensor/as5600.rst +++ b/components/sensor/as5600.rst @@ -30,7 +30,7 @@ the :ref:`I²C Bus ` and connect the sensor to the pins specified there. .. code-block:: yaml as5600: - dir_pin: 22 + dir_pin: GPIOXX start_position: 0deg range: 180deg @@ -39,7 +39,7 @@ Configuration variables: - **dir_pin** (*Optional*, int): The pin connected to the AS5600's direction pin. See :ref:`Direction ` for more information. -- **direction** (*Optional*, string): The direction that the magnet should rotate to increase values. +- **direction** (*Optional*, string): The direction that the magnet should rotate to increase values. Used in combination with the **dir_pin**. - ``clockwise`` (default) @@ -57,7 +57,7 @@ Configuration variables: - ``lsb2`` - ``lsb3`` -- **power_mode** (*Optional*, string): The power mode to run the sensor. Note: When **watchdog** is enabled, +- **power_mode** (*Optional*, string): The power mode to run the sensor. Note: When **watchdog** is enabled, it will switch the device to ``low3`` when there is not much change in position. - ``nominal`` (default) @@ -65,7 +65,7 @@ Configuration variables: - ``low2`` - ``low3`` -- **watchdog** (*Optional*, boolean): Whether to enable the watchdog that puts the the chip in to +- **watchdog** (*Optional*, boolean): Whether to enable the watchdog that puts the the chip in to low power mode 3. Check the datasheet for more information. Defaults to ``off``. - **slow_filter** (*Optional*, string): See datasheet. @@ -98,9 +98,9 @@ Direction The AS5600 has ``direction`` pin that controls which rotation direction will cause the position value to **increase**. This pin should be pulled low for clockwise, and pulled high for counterclockwise. If left floating, you are likely -to encounter erratic behavior. +to encounter erratic behavior. -If you would like the ESP controller to pull that pin high or low, you may configure the ``dir_pin`` and optionally, the +If you would like the ESP controller to pull that pin high or low, you may configure the ``dir_pin`` and optionally, the ``direction`` option to have the ESP controller pull the pin high or low. .. _as5600_position_range: @@ -136,7 +136,7 @@ For example, let's say we have the following component config: start_position: 90deg range: 180deg direction: clockwise - dir_pin: 22 + dir_pin: GPIOXX - If the magnet north was at the right side of the chip (i.e. 1024 / 90deg raw position), the scaled position would report a value of ``0``. - If the magnet north was at the bottom of the chip (i.e. 2048 / 180deg raw position), the scaled position would report a value of ``2048``. @@ -147,7 +147,7 @@ For example, let's say we have the following component config: .. note:: You may specify an ``end_position`` that is less than the ``start_position``. When doing so, the allowable range will start at the - ``start_position`` and continue through to the highest position value (i.e. ``4095``) and then continue from ``0`` until it reaches + ``start_position`` and continue through to the highest position value (i.e. ``4095``) and then continue from ``0`` until it reaches the ``end_position``. @@ -180,7 +180,7 @@ sensor platform to create individual sensors that will report the position to Ho .. code-block:: yaml as5600: - dir_pin: 22 + dir_pin: GPIOXX sensor: - platform: as5600 diff --git a/components/sensor/atm90e26.rst b/components/sensor/atm90e26.rst index 63394ab26..ffbfcd271 100644 --- a/components/sensor/atm90e26.rst +++ b/components/sensor/atm90e26.rst @@ -21,8 +21,8 @@ Configuration variables: - **cs_pin** (**Required**, :ref:`Pin Schema `): The pin CS is connected to. For the 6 channel meter main board, this will always be 5 and 4. For the add-on boards a jumper can be selected for each CS pin, but default to 0 and 16. - **line_frequency** (**Required**, string): The AC line frequency of the supply voltage. One of ``50Hz``, ``60Hz``. -- **meter_constant** (**Required**, float): The number of pulses per kWh. The ATM90E26 internally works based on pulses and - this value converts a pulse into Wh, which are emitted as ``forward_active_energy`` etc. Matching it against an existing +- **meter_constant** (**Required**, float): The number of pulses per kWh. The ATM90E26 internally works based on pulses and + this value converts a pulse into Wh, which are emitted as ``forward_active_energy`` etc. Matching it against an existing meter is useful in that it allows visual confirmation for some devices that blink an LED for each pulse. Common values are 1000 pulses/kWh, 1666.66 pulses/kWh, or 3200 pulses/kWh. See also **gain_metering** which determines after how much energy a pulse is emitted. @@ -111,13 +111,13 @@ Keeping the calibration values at the top of your yaml might make editing easier metering_cal: '7481' # default: 7481 - Calibrate this to match your meter based on the CF1 (CFx) pulse. spi: - clk_pin: 18 - miso_pin: 19 - mosi_pin: 23 + clk_pin: GPIOXX + miso_pin: GPIOXX + mosi_pin: GPIOXX sensor: - platform: atm90e26 - cs_pin: 5 + cs_pin: GPIOXX voltage: name: House Voltage accuracy_decimals: 1 diff --git a/components/sensor/atm90e32.rst b/components/sensor/atm90e32.rst index 198c3d118..000ccbd9a 100644 --- a/components/sensor/atm90e32.rst +++ b/components/sensor/atm90e32.rst @@ -168,7 +168,7 @@ a time-series-database, e.g. InfluxDB. sensor: #IC1 Main - platform: atm90e32 - cs_pin: 5 + cs_pin: GPIOXX phase_a: forward_active_energy: name: ${disp_name} ct1 FAWattHours @@ -208,13 +208,13 @@ Additional Examples # Example configuration entry for split single phase meter spi: - clk_pin: 18 - miso_pin: 19 - mosi_pin: 23 + clk_pin: GPIOXX + miso_pin: GPIOXX + mosi_pin: GPIOXX sensor: - platform: atm90e32 - cs_pin: 5 + cs_pin: GPIOXX phase_a: voltage: name: "EMON Line Voltage A" diff --git a/components/sensor/binary_sensor_map.rst b/components/sensor/binary_sensor_map.rst index 82e4ccf49..e23d0a014 100644 --- a/components/sensor/binary_sensor_map.rst +++ b/components/sensor/binary_sensor_map.rst @@ -6,17 +6,17 @@ Binary Sensor Map :image: binary_sensor_map.jpg The ``binary_sensor_map`` sensor platform allows you to map multiple :doc:`binary sensor ` -to an individual value. Depending on the state of each binary sensor, its associated configured parameters, and this sensor's mapping type, +to an individual value. Depending on the state of each binary sensor, its associated configured parameters, and this sensor's mapping type, the ``binary_sensor_map`` publishes a single numerical value. -Use this sensor to combine one or more binary sensors' ``ON`` or ``OFF`` states into a numerical value. Some possible use cases include +Use this sensor to combine one or more binary sensors' ``ON`` or ``OFF`` states into a numerical value. Some possible use cases include touch devices and determining Bayesian probabilities for an event. This platform supports three measurement types: ``BAYESIAN``, ``GROUP``, and ``SUM``. You need to specify your desired mapping with the ``type:`` configuration value. -When using the ``BAYESIAN`` type, add your binary sensors as ``observations`` to the binary sensor map. -If you use the ``GROUP`` or ``SUM`` type, add your binary sensors as ``channels``. +When using the ``BAYESIAN`` type, add your binary sensors as ``observations`` to the binary sensor map. +If you use the ``GROUP`` or ``SUM`` type, add your binary sensors as ``channels``. The maximum amount of observations/channels supported is 64. - ``BAYESIAN`` This type replicates Home Assistant's `Bayesian sensor `__. Based on the observation states, this sensor returns the Bayesian probability of a particular event occurring. The configured ``prior:`` probability is the likelihood that the Bayesian event is true, ignoring all external influences. Every observation has its own ``prob_given_true`` and ``prob_given_false`` parameters. The ``prob_given_true:`` value is the probability that the observation's binary sensor is ``ON`` when the Bayesian event is ``true``. The ``prob_given_false:`` value is the probability that the observation's binary sensor is ``ON`` when the Bayesian event is ``false``. Use an :doc:`/components/binary_sensor/analog_threshold` to convert this sensor's probability to a binary ``ON`` or ``OFF`` by setting an appropriate threshold. @@ -39,12 +39,12 @@ The maximum amount of observations/channels supported is 64. prob_given_false: 0.1 binary_sensor: - # If the Bayesian probability is greater than 0.6, + # If the Bayesian probability is greater than 0.6, # then predict the event is occuring - platform: analog_threshold name: "Bayesian Event Predicted State" sensor_id: bayesian_prob - threshold: 0.6 + threshold: 0.6 # ... - ``GROUP`` Each channel has its own ``value``. The sensor publishes the average value of all active @@ -78,7 +78,7 @@ The maximum amount of observations/channels supported is 64. channel: 0 id: touchkey0 # ... - + - ``SUM`` Each channel has its own ``value``. The sensor publishes the sum of all the active binary sensors values or ``0`` if no sensors are active. @@ -102,19 +102,19 @@ The maximum amount of observations/channels supported is 64. binary_sensor: - platform: gpio - pin: 4 + pin: GPIOXX id: bit0 - platform: gpio - pin: 5 + pin: GPIOXX id: bit1 - platform: gpio - pin: 6 + pin: GPIOXX id: bit2 - platform: gpio - pin: 7 + pin: GPIOXX id: bit3 # ... @@ -128,7 +128,7 @@ Configuration variables: - **binary_sensor** (**Required**): The id of the :doc:`binary sensor ` to add as a channel for this sensor. - **value** (**Required**): The value this channel should report when its binary sensor is active. -- **prior** (**Required for BAYESIAN type**, float between 0 and 1): The prior probability of the event. +- **prior** (**Required for BAYESIAN type**, float between 0 and 1): The prior probability of the event. - **observations** (**Required for BAYESIAN type**): A list of observations that influence the Bayesian probability of the event. - **binary_sensor** (**Required**): The id of the :doc:`binary sensor ` diff --git a/components/sensor/bl0939.rst b/components/sensor/bl0939.rst index d26792e22..59ed059fb 100644 --- a/components/sensor/bl0939.rst +++ b/components/sensor/bl0939.rst @@ -20,20 +20,8 @@ Additionally, you need to set the baud rate to 4800, parity to ``NONE`` and stop .. code-block:: yaml # Example configuration entry - # Disable logging over serial - logger: - baud_rate: 0 - - uart: - tx_pin: GPIO25 - rx_pin: GPIO26 - baud_rate: 4800 - parity: NONE - stop_bits: 2 - sensor: - platform: bl0939 - update_interval: 30s voltage: name: 'BL0939 Voltage' current_1: diff --git a/components/sensor/bme280.rst b/components/sensor/bme280.rst index 15b667518..36c597df5 100644 --- a/components/sensor/bme280.rst +++ b/components/sensor/bme280.rst @@ -9,7 +9,7 @@ BME280 Temperature+Pressure+Humidity Sensor The ``bme280`` sensor platform allows you to use your BME280 (`datasheet `__, `Adafruit`_) temperature, pressure and humidity sensors with ESPHome. The sensor -is used in *Forced Mode* where measurement is performed and then +is used in *Forced Mode* where measurement is performed and then the sensor returns to sleep mode until next measurement. The :ref:`I²C ` or :ref:`SPI ` is required to be set up in your configuration for this sensor to work. @@ -28,13 +28,10 @@ required to be set up in your configuration for this sensor to work. - platform: bme280_i2c temperature: name: "BME280 Temperature" - oversampling: 16x pressure: name: "BME280 Pressure" humidity: name: "BME280 Humidity" - address: 0x77 - update_interval: 60s # Example configuration entry SPI @@ -42,40 +39,31 @@ required to be set up in your configuration for this sensor to work. - platform: bme280_spi temperature: name: "BME280 Temperature" - oversampling: 16x pressure: name: "BME280 Pressure" humidity: name: "BME280 Humidity" - cs_pin: GPIO5 - update_interval: 60s + cs_pin: GPIOXX Configuration variables: ------------------------ - **temperature** (*Optional*): The information for the temperature sensor. - - **name** (**Required**, string): The name for the temperature - sensor. - **oversampling** (*Optional*): The oversampling parameter for the temperature sensor. See :ref:`Oversampling Options `. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - All other options from :ref:`Sensor `. - **pressure** (*Optional*): The information for the pressure sensor. - - **name** (**Required**, string): The name for the pressure sensor. - **oversampling** (*Optional*): The oversampling parameter for the temperature sensor. See :ref:`Oversampling Options `. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - All other options from :ref:`Sensor `. - **humidity** (*Optional*): The information for the pressure sensor. - - **name** (**Required**, string): The name for the humidity sensor. - **oversampling** (*Optional*): The oversampling parameter for the temperature sensor. See :ref:`Oversampling Options `. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - All other options from :ref:`Sensor `. - **address** (*Optional*, int): Manually specify the I²C address of diff --git a/components/sensor/cs5460a.rst b/components/sensor/cs5460a.rst index 0caa5b7ad..61a4136ce 100644 --- a/components/sensor/cs5460a.rst +++ b/components/sensor/cs5460a.rst @@ -35,11 +35,6 @@ driven by a GPIO or wired to VCC. .. code-block:: yaml # Example configuration entry - spi: - clk_pin: 18 - mosi_pin: 23 - miso_pin: 19 - sensor: - platform: cs5460a current: @@ -58,7 +53,7 @@ driven by a GPIO or wired to VCC. current_gain: 0.01 voltage_gain: 0.000573 pulse_energy: 1 Wh - cs_pin: 33 + cs_pin: GPIOXX Configuration variables: ------------------------ diff --git a/components/sensor/cse7761.rst b/components/sensor/cse7761.rst index 64bb889c0..b1e856586 100644 --- a/components/sensor/cse7761.rst +++ b/components/sensor/cse7761.rst @@ -20,16 +20,6 @@ Additionally, you need to set the baud rate to 38400 and parity to ``EVEN``. .. code-block:: yaml # Example configuration entry - # Disable logging over serial - logger: - baud_rate: 0 - - uart: - tx_pin: GPIO25 - rx_pin: GPIO26 - baud_rate: 38400 - parity: EVEN - sensor: - platform: cse7761 voltage: @@ -42,7 +32,6 @@ Additionally, you need to set the baud rate to 38400 and parity to ``EVEN``. name: 'CSE7761 Active Power 1' active_power_2: name: 'CSE7761 Active Power 2' - update_interval: 5s .. note:: diff --git a/components/sensor/dallas.rst b/components/sensor/dallas.rst index 45032c2d7..d5c046d9d 100644 --- a/components/sensor/dallas.rst +++ b/components/sensor/dallas.rst @@ -28,13 +28,7 @@ if you don't have massively long wires. # Example configuration entry dallas: - - pin: 23 - - # Individual sensors - sensor: - - platform: dallas - address: 0x1c0000031edd2a28 - name: "Livingroom Temperature" + - pin: GPIOXX Configuration variables: ************************ @@ -71,10 +65,6 @@ To initialize a sensor, first supply either ``address`` **or** ``index`` to iden .. code-block:: yaml - # Example configuration entry - dallas: - - pin: GPIO23 - # Individual sensors sensor: - platform: dallas @@ -114,7 +104,7 @@ the scanning will happen even with no sensors connected. For example with this c # Example configuration entry dallas: - - pin: GPIO23 + - pin: GPIOXX # Note you don't have to add any sensors at this point @@ -128,7 +118,7 @@ Now we can add the individual sensors to our configuration: # Example configuration entry dallas: - - pin: GPIO23 + - pin: GPIOXX sensor: - platform: dallas @@ -154,9 +144,9 @@ Use this if you have multiple dallas hubs: # Example configuration entry dallas: - - pin: GPIO23 + - pin: GPIOXX id: hub_1 - - pin: GPIO24 + - pin: GPIOXX id: hub_2 sensor: diff --git a/components/sensor/daly_bms.rst b/components/sensor/daly_bms.rst index cdb28600b..7fca68c04 100644 --- a/components/sensor/daly_bms.rst +++ b/components/sensor/daly_bms.rst @@ -15,18 +15,29 @@ The BMS communicates via :ref:`UART `. :align: center :width: 100.0% +Component/Hub +------------- .. code-block:: yaml - # Example configuration entry (ESP8266) - uart: - tx_pin: GPIO1 - rx_pin: GPIO3 - baud_rate: 9600 - + # Example configuration entry daly_bms: update_interval: 20s + +Configuration variables: +************************ + +- **update_interval** (*Optional*, :ref:`config-time`): Delay between data requests. +- **address** (*Optional*, int): Address to use, defaults to ``0x80``. + +Sensor +------ + +A sensor platform to read BMS data + +.. code-block:: yaml + sensor: - platform: daly_bms voltage: @@ -68,11 +79,81 @@ The BMS communicates via :ref:`UART `. cell_4_voltage: name: "Cell 4 Voltage" +Configuration variables: +************************ + +- **voltage** (*Optional*): Voltage of the battery pack connected to Daly BMS. + All options from :ref:`Sensor `. + +- **current** (*Optional*): Current flowing trough the BMS (input or output from batttery). + All options from :ref:`Sensor `. + +- **battery_level** (*Optional*): Battery level in % (SoC). + All options from :ref:`Sensor `. + +- **max_cell_voltage** (*Optional*): The cell of the battery with the higher voltage. + All options from :ref:`Sensor `. + +- **max_cell_voltage_number** (*Optional*): The cell number of the battery with the higher voltage. + All options from :ref:`Sensor `. + +- **min_cell_voltage** (*Optional*): The cell of the battery with the lower voltage. + All options from :ref:`Sensor `. + +- **min_cell_voltage_number** (*Optional*): The cell number of the battery with the lower voltage. + All options from :ref:`Sensor `. + +- **max_temperature** (*Optional*): The higher temperature measured from the temperature sensors. + All options from :ref:`Sensor `. + +- **max_temperature_probe_number** (*Optional*): The sensor number which has measured the higher temperature. + All options from :ref:`Sensor `. + +- **min_temperature** (*Optional*): The lower temperature measured from the temperature sensors. + All options from :ref:`Sensor `. + +- **min_temperature_probe_number** (*Optional*): The sensor number which has measured the lower temperature. + All options from :ref:`Sensor `. + +- **remaining_capacity** (*Optional*): The capacity in Ah left in the battery. + All options from :ref:`Sensor `. + +- **cells_number** (*Optional*): The number of cells in series in the battery pack. + All options from :ref:`Sensor `. + +- **temperature_1** (*Optional*): The first temperature sensor. + All options from :ref:`Sensor `. + +- **temperature_2** (*Optional*): The second temperature sensor. + All options from :ref:`Sensor `. + +- **cell_1_voltage** (*Optional*): The voltage of cell number 1. Cell number can be from 1 to 16. + All options from :ref:`Sensor `. + +Text Sensor +----------- + +Text sensor that indicates the status of BMS. + +.. code-block:: yaml + text_sensor: - platform: daly_bms status: name: "BMS Status" +Configuration variables: +************************ + +- **status** (*Optional*): The BMS Status (Charging, Discharging, Stationary). + All options from :ref:`Text Sensor `. + +Binary Sensor +------------- + +Binary sensor that indicates the status of MOS. + +.. code-block:: yaml binary_sensor: - platform: daly_bms @@ -81,163 +162,25 @@ The BMS communicates via :ref:`UART `. discharging_mos_enabled: name: "Discharging MOS" -Component/Hub -------------- - -Configuration variables: -************************ - -- **update_interval** (*Optional*, :ref:`config-time`): Delay between data requests. -- **address** (*Optional*, int): Address to use, defaults to ``0x80``. - -Sensor ------- - -A sensor platform to read BMS data - -Configuration variables: -************************ - -- **voltage** (*Optional*): Voltage of the battery pack connected to Daly BMS. - - - **name** (**Required**, string): The name for the voltage sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **current** (*Optional*): Current flowing trough the BMS (input or output from batttery). - - - **name** (**Required**, string): The name for the current sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **battery_level** (*Optional*): Battery level in % (SoC). - - - **name** (**Required**, string): The name for the SoC sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **max_cell_voltage** (*Optional*): The cell of the battery with the higher voltage. - - - **name** (**Required**, string): The name for the Max Cell Voltage sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **max_cell_voltage_number** (*Optional*): The cell number of the battery with the higher voltage. - - - **name** (**Required**, string): The name for the Max Cell Voltage Number sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **min_cell_voltage** (*Optional*): The cell of the battery with the lower voltage. - - - **name** (**Required**, string): The name for the Min Cell Voltage sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **min_cell_voltage_number** (*Optional*): The cell number of the battery with the lower voltage. - - - **name** (**Required**, string): The name for the Min Cell Voltage Number sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **max_temperature** (*Optional*): The higher temperature measured from the temperature sensors. - - - **name** (**Required**, string): The name for the Max Temperature sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **max_temperature_probe_number** (*Optional*): The sensor number which has measured the higher temperature. - - - **name** (**Required**, string): The name for the Max Temperature Probe Number sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **min_temperature** (*Optional*): The lower temperature measured from the temperature sensors. - - - **name** (**Required**, string): The name for the Min Temperature sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **min_temperature_probe_number** (*Optional*): The sensor number which has measured the lower temperature. - - - **name** (**Required**, string): The name for the Min Temperature Probe Number sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **remaining_capacity** (*Optional*): The capacity in Ah left in the battery. - - - **name** (**Required**, string): The name for the Remaining Capacity sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **cells_number** (*Optional*): The number of cells in series in the battery pack. - - - **name** (**Required**, string): The name for the Cells Number sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **temperature_1** (*Optional*): The first temperature sensor. - - - **name** (**Required**, string): The name for the first temperature sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **temperature_2** (*Optional*): The second temperature sensor. - - - **name** (**Required**, string): The name for the second temperature sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -- **cell_1_voltage** (*Optional*): The voltage of cell number 1. Cell number can be from 1 to 16. - - - **name** (**Required**, string): The name for the cell voltage sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. - -Text Sensor ------------ - -Text sensor that indicates the status of BMS. - -Configuration variables: -************************ - -- **status** (*Optional*): The BMS Status (Charging, Discharging, Stationary). - - - **name** (**Required**, string): The name for the BMS status text sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Text Sensor `. - -Binary Sensor -------------- - -Binary sensor that indicates the status of MOS. - Configuration variables: ************************ - **charging_mos_enabled** (*Optional*): The BMS charging MOS status to enable the recharge of the battery. - - - **name** (**Required**, string): The name for the charging MOS binary sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Binary Sensor `. + All options from :ref:`Binary Sensor `. - **discharging_mos_enabled** (*Optional*): The BMS discharging mos status to enable the load. - - - **name** (**Required**, string): The name for the discharging MOS binary sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Binary Sensor `. + All options from :ref:`Binary Sensor `. Control BMS ----------- At this moment Daly sensor platform don't suppport controlling you BMS, but you can make some stuff using uart.write -First you need to setup binary sensors for charging and disharging MOS - -.. code-block:: yaml +First you need to setup binary sensors for charging and disharging MOS + +.. code-block:: yaml + - binary_sensor: - platform: daly_bms charging_mos_enabled: @@ -249,11 +192,11 @@ First you need to setup binary sensors for charging and disharging MOS id: bin_daly_dischg_mos # binary MOS sensor must have ID to use with switch internal: True # but you can make it internal to avoid duplication -Then you can add switches - -.. code-block:: yaml +Then you can add switches + +.. code-block:: yaml + - switch: - platform: template name: "Daly Charging MOS" @@ -266,12 +209,12 @@ Then you can add switches turn_on_action: - uart.write: data: [0xA5, 0x40, 0xDA, 0x08, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xC8] - - logger.log: + - logger.log: format: "Send cmd to Daly: Set charge MOS on" turn_off_action: - uart.write: data: [0xA5, 0x40, 0xDA, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xC7] - - logger.log: + - logger.log: format: "Send cmd to Daly: Set charge MOS off" - platform: template @@ -285,20 +228,20 @@ Then you can add switches turn_on_action: - uart.write: data: [0xA5, 0x40, 0xD9, 0x08, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xC7] - - logger.log: + - logger.log: format: "Send cmd to Daly: Set discharge MOS on" turn_off_action: - uart.write: data: [0xA5, 0x40, 0xD9, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xC6] - - logger.log: + - logger.log: format: "Send cmd to Daly: Set discharge MOS off" Also you can add select to change battery level - -.. code-block:: yaml - +.. code-block:: yaml + + select: - platform: template name: "Daly Battery Level setup" @@ -318,7 +261,7 @@ Also you can add select to change battery level then: - uart.write: data: [0xA5, 0x40, 0x21, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03, 0xE8, 0xF9] - - logger.log: + - logger.log: format: "Send cmd to Daly: Set SOC to 100%" else: - if: @@ -327,7 +270,7 @@ Also you can add select to change battery level then: - uart.write: data: [0xA5, 0x40, 0x21, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0xEE, 0xFE] - - logger.log: + - logger.log: format: "Send cmd to Daly: Set SOC to 75%" else: - if: @@ -336,7 +279,7 @@ Also you can add select to change battery level then: - uart.write: data: [0xA5, 0x40, 0x21, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0xF4, 0x03] - - logger.log: + - logger.log: format: "Send cmd to Daly: Set SOC to 50%" else: - if: @@ -345,7 +288,7 @@ Also you can add select to change battery level then: - uart.write: data: [0xA5, 0x40, 0x21, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFA, 0x08] - - logger.log: + - logger.log: format: "Send cmd to Daly: Set SOC to 25%" else: - if: @@ -354,10 +297,10 @@ Also you can add select to change battery level then: - uart.write: data: [0xA5, 0x40, 0x21, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0E] - - logger.log: + - logger.log: format: "Send cmd to Daly: Set SOC to 0%" - - + + UART Connection --------------- @@ -368,15 +311,15 @@ Connect RX from BMS to TX in ESP board and TX from BMS to RX in ESP board :width: 100.0% Uart Pinout. - + **3.3v Warning:** some BMS 3.3v cant source large currents and may not work to properly power the ESP. If you are having WIFI connection issues or similar, try a different power source. There is 12-15v available on the Daly connector which via a proper step-down converter can properly power the ESP. On the ESP32 (untested on ESP8266) if you are having missing data (such as Temperature 1/2), it may be due to UART buffer size. Add the following to your configuration to increase the buffer from the default 256 to 512. -.. code-block:: +.. code-block:: - uart: + uart: ... rx_buffer_size: 512 diff --git a/components/sensor/growatt_solar.rst b/components/sensor/growatt_solar.rst index 5aefa3623..7d52e4c77 100644 --- a/components/sensor/growatt_solar.rst +++ b/components/sensor/growatt_solar.rst @@ -15,27 +15,16 @@ The ``Growatt Inverter`` sensor platform allows you to use growatt inverter data Growatt Logo The communication with this component is done over a :ref:`UART bus ` using :ref:`Modbus `. -You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set +You must therefore have a ``uart:`` and ``modbus:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 9600. .. code-block:: yaml - # Example configuration entry - uart: - - id: gw_uart - baud_rate: 9600 - tx_pin: GPIO1 - rx_pin: GPIO3 - - modbus: - uart_id: gw_uart - flow_control_pin: GPIO4 - + # Example configuration sensor: - platform: growatt_solar - update_interval: 10s protocol_version: RTU - + inverter_status: name: "Growatt Status Code" @@ -88,7 +77,7 @@ to some pins on your board and the baud rate set to 9600. energy_production_day: name: "Growatt Today's Generation" - + total_energy_production: name: "Growatt Total Energy Production" @@ -96,14 +85,12 @@ to some pins on your board and the baud rate set to 9600. name: "Growatt Inverter Module Temp" - - Configuration variables: ------------------------ - **inverter_status** (*Optional*): Status code of the inverter (0: waiting, 1: normal, 3:fault) -- **protocol_version** (*Optional*): Version of the protocol used by your inverter. +- **protocol_version** (*Optional*): Version of the protocol used by your inverter. Old inverters use RTU (default). Newer ones use RTU2 (e.g. MIC, MIN, MAX series) - **phase_a** (*Optional*): The group of exposed sensors for Phase A/1. diff --git a/components/sensor/haier.rst b/components/sensor/haier.rst index 9776656b7..d16bb56e7 100644 --- a/components/sensor/haier.rst +++ b/components/sensor/haier.rst @@ -15,19 +15,6 @@ Additional sensors for Haier Climate device. **These sensors are supported only .. code-block:: yaml # Example configuration entry - uart: - baud_rate: 9600 - tx_pin: 17 - rx_pin: 16 - id: ac_port - - climate: - - platform: haier - id: haier_ac - protocol: hOn - name: Haier AC - uart_id: ac_port - sensor: - platform: haier haier_id: haier_ac diff --git a/components/sensor/havells_solar.rst b/components/sensor/havells_solar.rst index dec07ff51..a3e46d1c8 100644 --- a/components/sensor/havells_solar.rst +++ b/components/sensor/havells_solar.rst @@ -17,23 +17,12 @@ with ESPHome. Havells On Grid Solar Inverter. The communication with this component is done via a :ref:`UART ` using :ref:`Modbus `. -You must therefore have a ``uart:`` entry in your configuration with both the TX and RX pins set +You must therefore have a ``uart:`` and ``modbus:`` entry in your configuration with both the TX and RX pins set to some pins on your board and the baud rate set to 9600. .. code-block:: yaml # Example configuration entry - uart: - - id: modbus_uart - baud_rate: 9600 - tx_pin: GPIO1 - rx_pin: GPIO3 - - - modbus: - uart_id: modbus_uart - flow_control_pin: GPIO4 - sensor: - platform: havells_solar update_interval: 60s diff --git a/components/sensor/hlw8012.rst b/components/sensor/hlw8012.rst index 4a635e7f7..89e940057 100644 --- a/components/sensor/hlw8012.rst +++ b/components/sensor/hlw8012.rst @@ -30,9 +30,9 @@ be measured at the same exact points in time. # Example configuration entry sensor: - platform: hlw8012 - sel_pin: 5 - cf_pin: 14 - cf1_pin: 13 + sel_pin: GPIOXX + cf_pin: GPIOXX + cf1_pin: GPIOXX current: name: "HLW8012 Current" voltage: @@ -69,11 +69,11 @@ Advanced Options: Defaults to the Sonoff POW's value ``0.001 ohm``. - **voltage_divider** (*Optional*, float): The value of the voltage divider on the board as ``(R_upstream + R_downstream) / R_downstream``. Defaults to the Sonoff POW's value ``2351``. -- **model** (*Optional*, string): The sensor model on the board, to set internal constant factors to convert pulses to measurements. - Possible values are ``HLW8012``, ``CSE7759``, ``BL0937``. Defaults to ``HLW8012``. +- **model** (*Optional*, string): The sensor model on the board, to set internal constant factors to convert pulses to measurements. + Possible values are ``HLW8012``, ``CSE7759``, ``BL0937``. Defaults to ``HLW8012``. CSE7759 uses same constants and it also works with default. Must be set for BL0937 to be able to calibrate all three measurements at the same time. - **change_mode_every** (*Optional*, int): After how many updates to cycle between the current/voltage measurement mode. - Note that the first value after switching is discarded because it is often inaccurate. When set to ``"never"`` the measurement mode will stay at the + Note that the first value after switching is discarded because it is often inaccurate. When set to ``"never"`` the measurement mode will stay at the set ``initial_mode``. Defaults to ``8``. - **initial_mode** (*Optional*, string): The initial measurement mode. Defaults to ``VOLTAGE``. Possible initial measurement modes are ``VOLTAGE`` or ``CURRENT``. @@ -89,9 +89,9 @@ the initial measurement mode to match whichever mode the device uses, and disabl # Example configuration entry for device with fixed measurement mode sensor: - platform: hlw8012 - sel_pin: 5 - cf_pin: 14 - cf1_pin: 13 + sel_pin: GPIOXX + cf_pin: GPIOXX + cf1_pin: GPIOXX current: name: "HLW8012 Current" voltage: @@ -114,11 +114,11 @@ when SEL=1 voltage is measured. To accommodate this change use the following con sensor: - platform: hlw8012 model: BL0937 - sel_pin: - number: 12 + sel_pin: + number: GPIOXX inverted: true - cf_pin: 4 - cf1_pin: 5 + cf_pin: GPIOXX + cf1_pin: GPIOXX current: name: "BL0937 Current" voltage: diff --git a/components/sensor/honeywellabp.rst b/components/sensor/honeywellabp.rst index 9ec686b9b..d85582e9a 100644 --- a/components/sensor/honeywellabp.rst +++ b/components/sensor/honeywellabp.rst @@ -6,7 +6,7 @@ Honeywell ABP Pressure Sensors :image: honeywellabp.jpg :keywords: Honeywell ABP -The ``honeywellabp`` sensor platform allows you to use your Honeywell ABP +The ``honeywellabp`` sensor platform allows you to use your Honeywell ABP (`website `__, `datasheet `__, `Mouser `_) pressure and temperature sensors with ESPHome. The :ref:`SPI ` is @@ -24,30 +24,27 @@ required to be set up in your configuration for this sensor to work sensor: - platform: honeywellabp pressure: - name: "Honeywell pressure" - unit_of_measurement: "psi" + name: Honeywell pressure min_pressure: 0 max_pressure: 15 temperature: - name: "Honeywell temperature" - cs_pin: GPIO5 #D5 + name: Honeywell temperature + cs_pin: GPIOXX Configuration variables: ------------------------ -The values for ``min_pressure`` and ``max_pressure`` can be found in the device datasheet for the specific device. These are used to calculate -the pressure reading published by the sensor. Some sensors measure pressure in ``bar`` or ``kPa``; set ``min_pressure`` and ``max_pressure`` to +The values for ``min_pressure`` and ``max_pressure`` can be found in the device datasheet for the specific device. These are used to calculate +the pressure reading published by the sensor. Some sensors measure pressure in ``bar`` or ``kPa``; set ``min_pressure`` and ``max_pressure`` to the measurement range and ``unit_of_measurement`` to the appropriate unit for your device. - **pressure** (*Optional*): The information for the pressure sensor. - - **name** (**Required**, string): The name for the pressure sensor. - **min_pressure** (**Required**, int or float): Minimum pressure for the pressure sensor, default unit ``psi``. - **max_pressure** (**Required**, int or float): Maximum pressure for the pressure sensor, default unit ``psi``. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - All other options from :ref:`Sensor `. -Some sensors do not have temperature sensing ability, see datasheet. In some cases the sensor may return a valid temperature even though the +Some sensors do not have temperature sensing ability, see datasheet. In some cases the sensor may return a valid temperature even though the datasheet indicates that the sensor does not measure temperature. - **temperature** (*Optional*): The information for the temperature sensor. diff --git a/components/sensor/hrxl_maxsonar_wr.rst b/components/sensor/hrxl_maxsonar_wr.rst index 6a091f369..7d442d664 100644 --- a/components/sensor/hrxl_maxsonar_wr.rst +++ b/components/sensor/hrxl_maxsonar_wr.rst @@ -6,7 +6,7 @@ HRXL/XL MaxSonar WR Series :image: hrxl_maxsonar_wr.jpg :keywords: ultrasonic, maxbotix, maxsonar -This sensor allows you to use HRXL MaxSonar WR series ultrasonic sensors by MaxBotix +This sensor allows you to use HRXL MaxSonar WR series ultrasonic sensors by MaxBotix (`datasheet `__) or the XL MaxSonar WR series (`datasheet `__) @@ -27,28 +27,15 @@ multiple times per second, filtering is highly recommended. .. code-block:: yaml # Example configuration entry - uart: - rx_pin: 36 - baud_rate: 9600 - sensor: - platform: "hrxl_maxsonar_wr" name: "Rainwater Tank" - # Tweak the filters for your application - filters: - - sliding_window_moving_average: - window_size: 12 - send_every: 12 - - or: - - throttle: "20min" - - delta: 0.02 Configuration variables: ------------------------ -- **name** (**Required**, string): The name of the sensor. -- All other options from :ref:`Sensor `. +- All options from :ref:`Sensor `. Advanced options: diff --git a/components/sensor/hydreon_rgxx.rst b/components/sensor/hydreon_rgxx.rst index aa3cc4237..04e08c06d 100644 --- a/components/sensor/hydreon_rgxx.rst +++ b/components/sensor/hydreon_rgxx.rst @@ -26,58 +26,40 @@ Device FAQ: ``__ .. code-block:: yaml # Example RG-9 entry - - uart: - rx_pin: GPIO16 - tx_pin: GPIO17 - baud_rate: 9600 - sensor: - platform: hydreon_rgxx - model: "RG_9" - id: "hydreon_1" - update_interval: 20s - disable_led: false + model: RG_9 + id: hydreon_1 moisture: - name: "Rain Level" + name: Rain Level temperature: - name: "Device Temperature" + name: Device Temperature binary_sensor: - platform: hydreon_rgxx - hydreon_rgxx_id: "hydreon_1" + hydreon_rgxx_id: hydreon_1 too_cold: - entity_category: diagnostic - name: "Temperature Status" + name: Temperature Status lens_bad: - entity_category: diagnostic - name: "Lens Status" + name: Lens Status em_sat: - entity_category: diagnostic - name: "Emitter Saturation" + name: Emitter Saturation .. code-block:: yaml # Example RG-15 entry - - uart: - rx_pin: GPIO16 - tx_pin: GPIO17 - baud_rate: 9600 - sensor: - platform: hydreon_rgxx - model: "RG_15" + model: RG_15 resolution: high - update_interval: 60s acc: - name: "rain" + name: Rain event_acc: - name: "rain event" + name: Rain Event" total_acc: - name: "rain total" + name: Rain Total" r_int: - name: "rain intensity" + name: Rain Intensity Configuration variables: ------------------------ diff --git a/components/sensor/kuntze.rst b/components/sensor/kuntze.rst index 6bd2372d7..76e222c74 100644 --- a/components/sensor/kuntze.rst +++ b/components/sensor/kuntze.rst @@ -48,12 +48,6 @@ A configured modbus component is optional. It will be automatically created. .. code-block:: yaml # Example configuration entry - uart: - - id: uart_bus - tx_pin: GPIO16 - rx_pin: GPIO17 - baud_rate: 19200 - parity: EVEN sensor: - platform: kuntze diff --git a/components/sensor/max31856.rst b/components/sensor/max31856.rst index 1d203e67e..420827b58 100644 --- a/components/sensor/max31856.rst +++ b/components/sensor/max31856.rst @@ -33,26 +33,19 @@ to have an :ref:`spi bus ` in your configuration with both **miso_pin** and .. code:: yaml # Example configuration entry - spi: - clk_pin: GPIO18 - miso_pin: GPIO19 - mosi_pin: GPIO23 - sensor: - platform: max31856 - name: "BBQ Temperature" - icon: "mdi:hamburger" - cs_pin: GPIO17 + name: BBQ Temperature + icon: mdi:hamburger + cs_pin: GPIOXX Configuration variables: ------------------------ -- **name** (**Required**, string): The name for the temperature sensor. - **cs_pin** (**Required**, :ref:`Pin Schema `): The Chip Select pin of the SPI interface. - **update_interval** (*Optional*, :ref:`config-time`): The interval to check the sensor. Defaults to ``60s``. - **mains_filter** (*Optional*, string): The mains power frequency to reject (``50 Hz`` or ``60 Hz``). Defaults to ``60 Hz``. - **spi_id** (*Optional*, :ref:`config-id`): Manually specify the ID of the :ref:`SPI Component ` if you want to use multiple SPI buses. -- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - All other options from :ref:`Sensor `. See Also diff --git a/components/sensor/mcp3204.rst b/components/sensor/mcp3204.rst index 117b9359f..ebf18d9e7 100644 --- a/components/sensor/mcp3204.rst +++ b/components/sensor/mcp3204.rst @@ -36,25 +36,9 @@ Most configurations will set the ``reference_voltage`` = VREF pin # Example configuration entry mcp3204: - cs_pin: GPIO15 + cs_pin: GPIOXX reference_voltage: 3.3V - # Example config of sensors. - # This is a small 1.5v solar panel power rail attached to pin 0 - # of the MCP3204 - sensor: - - platform: mcp3204 # Attached to pin 0 of the MCP3204. - update_interval: 1s - id: solar_voltage - number: 0 # MCP3204 pin number - - # In case MCP3208 is used. you can specify pin number > 4 - - platform: mcp3204 # Attached to pin 7 of the MCP3208. - update_interval: 1s - id: supply_voltage - number: 7 # MCP3208 pin number - - Configuration variables: ************************ @@ -70,14 +54,27 @@ The ``mcp3204`` sensor allows you to use your MCP3204 or MCP3208 12-Bit A/D Conv First, setup a :ref:`MCP3204 Hub ` for your MCP3204/8 sensor and then use this sensor platform to create individual sensors that will report the voltage to Home Assistant. +.. code-block:: yaml + + # Example config of sensors. + # This is a small 1.5v solar panel power rail attached to pin 0 + # of the MCP3204 + sensor: + - platform: mcp3204 # Attached to pin 0 of the MCP3204. + id: solar_voltage + number: 0 # MCP3204 pin number + + # In case MCP3208 is used. you can specify pin number > 4 + - platform: mcp3204 # Attached to pin 7 of the MCP3208. + id: supply_voltage + number: 7 # MCP3208 pin number + Configuration variables: ************************ - **mcp3204_id** (**Required**, :ref:`config-id`): The id of the parent MCP3204 component. -- **name** (**Required**, string): The name of the voltage sensor. - **number** (**Required**, int): The pin number of the MCP3204 - **update_interval** (*Optional*, :ref:`config-time`): The interval to check the sensor. Defaults to ``60s``. -- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - All other options from :ref:`Sensor `. See Also diff --git a/components/sensor/mhz19.rst b/components/sensor/mhz19.rst index 7b6e13ff5..0d3c8f313 100644 --- a/components/sensor/mhz19.rst +++ b/components/sensor/mhz19.rst @@ -26,36 +26,23 @@ TX/RX labels are from the perspective of the MH-Z19). Additionally, you need to .. code-block:: yaml # Example configuration entry - uart: - rx_pin: GPIO3 - tx_pin: GPIO1 - baud_rate: 9600 - sensor: - platform: mhz19 co2: - name: "MH-Z19 CO2 Value" + name: MH-Z19 CO2 Value temperature: - name: "MH-Z19 Temperature" - update_interval: 60s - automatic_baseline_calibration: false + name: MH-Z19 Temperature Configuration variables: ------------------------ - **co2** (**Required**): The CO_2 data from the sensor in parts per million (ppm). - - - **name** (**Required**, string): The name for the CO_2 sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. - **temperature** (**Required**): The information for the temperature sensor. Please note that this is not officially documented in the datasheet and seems to be quite inaccurate. - - - **name** (**Required**, string): The name for the temperature sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. - **update_interval** (*Optional*, :ref:`config-time`): The interval to check the sensor. Defaults to ``60s``. diff --git a/components/sensor/pmsx003.rst b/components/sensor/pmsx003.rst index 0ecee8b54..e51fe8e70 100644 --- a/components/sensor/pmsx003.rst +++ b/components/sensor/pmsx003.rst @@ -31,11 +31,6 @@ If you wish to use the optional ``update_interval`` ensure you have a ``tx_pin`` .. code-block:: yaml # Example configuration entry - uart: - rx_pin: GPIO23 - tx_pin: GPIO22 - baud_rate: 9600 - sensor: - platform: pmsx003 type: PMSX003 @@ -45,7 +40,6 @@ If you wish to use the optional ``update_interval`` ensure you have a ``tx_pin`` name: "Particulate Matter <2.5µm Concentration" pm_10_0: name: "Particulate Matter <10.0µm Concentration" - update_interval: 120s Configuration variables: ------------------------ diff --git a/components/sensor/pulse_counter.rst b/components/sensor/pulse_counter.rst index 865cda92f..9486bd4de 100644 --- a/components/sensor/pulse_counter.rst +++ b/components/sensor/pulse_counter.rst @@ -21,7 +21,7 @@ on the ESP32. However, due to the use of the pulse counter peripheral, a maximum # Example configuration entry sensor: - platform: pulse_counter - pin: 12 + pin: GPIOXX name: "Pulse Counter" Configuration variables @@ -72,7 +72,7 @@ count the light pulses on a power meter, you can do the following: # Example configuration entry sensor: - platform: pulse_counter - pin: 12 + pin: GPIOXX unit_of_measurement: 'kW' name: 'Power Meter House' filters: @@ -90,7 +90,7 @@ measure the total consumed energy in kWh. # Example configuration entry sensor: - platform: pulse_counter - pin: 12 + pin: GPIOXX unit_of_measurement: 'kW' name: 'Power Meter House' filters: diff --git a/components/sensor/pulse_meter.rst b/components/sensor/pulse_meter.rst index 5941c377b..785f299c5 100644 --- a/components/sensor/pulse_meter.rst +++ b/components/sensor/pulse_meter.rst @@ -22,7 +22,7 @@ Please note that it is not possible to use both of these two sensors on the same # Example configuration entry sensor: - platform: pulse_meter - pin: 12 + pin: GPIOXX name: "Pulse Meter" Configuration variables @@ -32,7 +32,7 @@ Configuration variables - **name** (**Required**, string): The name of the sensor. - **internal_filter** (*Optional*, :ref:`config-time`): If a pulse shorter than this time is detected, it is discarded. Defaults to ``13us``. - + This acts as a debounce filter to eliminate input noise, so choose a value a little less than your expected minimum pulse width. - **internal_filter_mode** (*Optional*, string): Determines how the internal filter is applied. @@ -62,7 +62,7 @@ For example, if you’re using the pulse meter with a photodiode to count the li state_class: measurement internal_filter: 20ms # Assuming maximum load of 16 kW and 10000 impulses per kWh, any pulses faster than 22.5 ms would exceed load. -10% ~= 20 ms. accuracy_decimals: 0 - pin: 12 + pin: GPIOXX filters: - multiply: 6 # (60s / impulse constant) * (1000W / 1kW) diff --git a/components/sensor/t6615.rst b/components/sensor/t6615.rst index ee47d00c8..8b2526d5e 100644 --- a/components/sensor/t6615.rst +++ b/components/sensor/t6615.rst @@ -29,26 +29,17 @@ regulator, so you may need some additional components to power up the sensor. .. code-block:: yaml # Example configuration entry - uart: - rx_pin: 1 - tx_pin: 3 - baud_rate: 19200 - sensor: - platform: t6615 co2: - name: "CO2" - update_interval: 60s + name: CO2 Configuration variables: ------------------------ - **co2** (**Required**): The CO_2 data from the sensor in parts per million (ppm). - - - **name** (**Required**, string): The name for the CO_2 sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. - **update_interval** (*Optional*, :ref:`config-time`): The interval to check the sensor. Defaults to ``60s``. diff --git a/components/sensor/teleinfo.rst b/components/sensor/teleinfo.rst index 5f3d786aa..27d97a281 100644 --- a/components/sensor/teleinfo.rst +++ b/components/sensor/teleinfo.rst @@ -52,44 +52,9 @@ simply press -/+ buttons on the counter and look for `Standard mode` or .. code-block:: yaml # Example configuration entry - uart: - id: uart_bus - rx_pin: GPIO3 - tx_pin: GPIO1 - baud_rate: 1200 - parity: EVEN - data_bits: 7 - teleinfo: id: myteleinfo - update_interval: 60s - historical_mode: true - sensor: - - platform: teleinfo - tag_name: "HCHC" - name: "hchc" - unit_of_measurement: "Wh" - icon: mdi:flash - teleinfo_id: myteleinfo - - platform: teleinfo - tag_name: "HCHP" - name: "hchp" - unit_of_measurement: "Wh" - icon: mdi:flash - teleinfo_id: myteleinfo - - platform: teleinfo - tag_name: "PAPP" - name: "papp" - unit_of_measurement: "VA" - icon: mdi:flash - teleinfo_id: myteleinfo - - text_sensor: - - platform: teleinfo - tag_name: "OPTARIF" - name: "optarif" - teleinfo_id: myteleinfo Configuration variables: ------------------------ @@ -112,17 +77,45 @@ In teleinfo platform: Sensor ****** +.. code-block:: yaml + + sensor: + - platform: teleinfo + tag_name: "HCHC" + name: "hchc" + unit_of_measurement: "Wh" + icon: mdi:flash + teleinfo_id: myteleinfo + - platform: teleinfo + tag_name: "HCHP" + name: "hchp" + unit_of_measurement: "Wh" + icon: mdi:flash + teleinfo_id: myteleinfo + - platform: teleinfo + tag_name: "PAPP" + name: "papp" + unit_of_measurement: "VA" + icon: mdi:flash + teleinfo_id: myteleinfo + - **tag_name** (**Required**, string): Specify the tag you want to retrieve from the Teleinformation. - **teleinfo_id** (*Optional*, :ref:`config-id`): Specify the ID of used hub. -- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - All other options from :ref:`Sensor `. Text Sensor *********** +.. code-block:: yaml + + text_sensor: + - platform: teleinfo + tag_name: "OPTARIF" + name: "optarif" + teleinfo_id: myteleinfo + - **tag_name** (**Required**, string): Specify the tag you want to retrieve from the Teleinformation. - **teleinfo_id** (*Optional*, :ref:`config-id`): Specify the ID of used hub. -- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - All other options from :ref:`Text Sensor `. diff --git a/components/sensor/tx20.rst b/components/sensor/tx20.rst index 566e8ca8b..b4414262f 100644 --- a/components/sensor/tx20.rst +++ b/components/sensor/tx20.rst @@ -32,29 +32,22 @@ connected to GND in the TX20. sensor: - platform: tx20 wind_speed: - name: "Wind speed" + name: Wind speed wind_direction_degrees: - name: "Wind direction degrees" + name: Wind direction degrees pin: - number: GPIO04 + number: GPIOXX Configuration variables: ------------------------ - **wind_speed** (**Required**): The information for the wind speed sensor. - - - **name** (**Required**, string): The name for the wind speed - sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. - **wind_direction_degrees** (**Required**): The information for the direction in degrees sensor. - - - **name** (**Required**, string): The name for the direction sensor. - - **id** (*Optional*, :ref:`config-id`): Set the ID of this sensor for use in lambdas. - - All other options from :ref:`Sensor `. + All options from :ref:`Sensor `. - **pin** (**Required**, :ref:`config-pin`): The pin, where the black or brown cable are connected. diff --git a/components/sensor/vl53l0x.rst b/components/sensor/vl53l0x.rst index 38c36d03a..86f173359 100644 --- a/components/sensor/vl53l0x.rst +++ b/components/sensor/vl53l0x.rst @@ -56,7 +56,6 @@ The :ref:`I²C Bus ` is required to be set up in your configuration for thi Configuration variables: ------------------------ -- **name** (**Required**, string): The name of the sensor. - **update_interval** (*Optional*, :ref:`config-time`): The interval to check the sensor. Defaults to ``60s``. - **signal_rate_limit** (*Optional*, float): Set the return signal rate limit in units of MCPS @@ -73,7 +72,6 @@ Configuration variables: on vl53l0x to enable/disable sensor. **Required** if not using address ``0x29`` which is the cause if you have multiple VL53L0X on the same i2c bus. In this case you have to assign a different pin to each VL53L0X. - **timeout** (*Optional*, :ref:`config-time`): Sensor setup timeout. Default to ``10ms``. -- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - All other options from :ref:`Sensor `. @@ -86,7 +84,7 @@ Configuration variables: name: "distance1" id: distance1 address: 0x41 - enable_pin: GPIO16 + enable_pin: GPIOXX timeout: 200us update_interval: 500ms unit_of_measurement: "m" @@ -95,7 +93,7 @@ Configuration variables: name: "distance2" id: distance2 address: 0x42 - enable_pin: GPIO17 + enable_pin: GPIOXX timeout: 200us update_interval: 500ms unit_of_measurement: "m" diff --git a/components/servo.rst b/components/servo.rst index 271a78d95..2a50844a6 100644 --- a/components/servo.rst +++ b/components/servo.rst @@ -34,7 +34,7 @@ only operate in this frequency range. output: - platform: esp8266_pwm id: pwm_output - pin: D1 + pin: GPIOXX frequency: 50 Hz Configuration variables: @@ -141,7 +141,7 @@ this will make the servo motor stop immediately and disable its active control. Home Assistant Configuration ---------------------------- -The easiest way to control your servo from Home Assistant is to add a ``number`` to your ESPHome +The easiest way to control your servo from Home Assistant is to add a ``number`` to your ESPHome configuration. See :ref:`Number ` for more information. .. code-block:: yaml diff --git a/components/sim800l.rst b/components/sim800l.rst index 58b7f0a17..4babcb9e6 100644 --- a/components/sim800l.rst +++ b/components/sim800l.rst @@ -346,7 +346,7 @@ Relay management commands received from an authorized sender: switch: - platform: gpio id: relay_1 - pin: 0 + pin: GPIOXX See Also diff --git a/components/sml.rst b/components/sml.rst index e049335f5..a9f835323 100644 --- a/components/sml.rst +++ b/components/sml.rst @@ -26,7 +26,9 @@ mature solution can be found `here `_ (in German). There are plenty of other examples and ready to buy solutions on the web. -Configuration +.. _sml-platform: + +Component/Hub ------------- As the communciation with the sensor is done using UART, you need to have the :ref:`UART bus ` @@ -36,14 +38,6 @@ smart meter. If you see checksum errors in the log try changing the interface pa .. code-block:: yaml # Example configuration entry - uart: - id: uart_bus - rx_pin: GPIO3 - baud_rate: 9600 - data_bits: 8 - parity: NONE - stop_bits: 1 - sml: id: mysml uart_id: uart_bus @@ -55,6 +49,19 @@ smart meter. If you see checksum errors in the log try changing the interface pa id(mqttclient).publish("gridmeter/sensor/sml/error", format_hex(bytes)); } + + +Configuration variables: + +- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. +- **uart_id** (*Optional*, :ref:`config-id`): Manually specify the ID of the :ref:`UART Component ` if you want + to use multiple UART buses. + +Sensor +------ + +.. code-block:: yaml + sensor: - platform: sml name: "Total energy" @@ -68,6 +75,18 @@ smart meter. If you see checksum errors in the log try changing the interface pa filters: - multiply: 0.0001 +- **obis_code** (*Required*, string): Specify the OBIS code you want to retrieve data for from the device. + The format must be (A-B:C.D.E, e.g. 1-0:1.8.0) +- **server_id** (*Optional*, string): Specify the device's server_id to retrieve the OBIS code from. Should be specified if more then one device is connected to the same hardware sensor component. +- **sml_id** (*Optional*, :ref:`config-id`): The ID of the :ref:`SML platform ` +- All other options from :ref:`Sensor `. + + +Text Sensor +----------- + +.. code-block:: yaml + text_sensor: - platform: sml name: "Manufacturer" @@ -76,31 +95,6 @@ smart meter. If you see checksum errors in the log try changing the interface pa obis_code: "129-129:199.130.3" format: text - -Configuration variables: ------------------------- - -.. _sml-platform: - -SML platform -************ - -- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. -- **uart_id** (*Optional*, :ref:`config-id`): Manually specify the ID of the :ref:`UART Component ` if you want - to use multiple UART buses. - -Sensor -****** - -- **obis_code** (*Required*, string): Specify the OBIS code you want to retrieve data for from the device. - The format must be (A-B:C.D.E, e.g. 1-0:1.8.0) -- **server_id** (*Optional*, string): Specify the device's server_id to retrieve the OBIS code from. Should be specified if more then one device is connected to the same hardware sensor component. -- **sml_id** (*Optional*, :ref:`config-id`): The ID of the :ref:`SML platform ` -- All other options from :ref:`Sensor `. - -Text Sensor -*********** - - **obis_code** (*Required*, string): Specify the OBIS code you want to retrieve data for from the device. The format must be (A-B:C.D.E, e.g. 1-0:1.8.0) - **server_id** (*Optional*, string): Specify the device's server_id to retrieve the OBIS code from. Should be specified if more then one device is connected to the same hardware sensor component. @@ -108,6 +102,7 @@ Text Sensor - **format** (*Optional*, string): Override the automatic interpretation of the transmitted binary data value. Possible values (`int`, `uint`, `bool`, `hex`, `text`). - All other options from :ref:`Text Sensor `. + Automations: ------------ diff --git a/components/sn74hc165.rst b/components/sn74hc165.rst index baa3f3263..6af4544a4 100644 --- a/components/sn74hc165.rst +++ b/components/sn74hc165.rst @@ -17,23 +17,12 @@ shift register to the pin QH of the next shift register. # Example configuration entry sn74hc165: - id: sn74hc165_hub - clock_pin: GPIO16 - data_pin: GPIO17 - load_pin: GPIO4 - clock_inhibit_pin: GPIO18 + clock_pin: GPIOXX + data_pin: GPIOXX + load_pin: GPIOXX + clock_inhibit_pin: GPIOXX sr_count: 2 - # Individual inputs - binary_sensor: - - platform: gpio - name: "SN74HC165 Pin #0" - pin: - sn74hc165: sn74hc165_hub - # Use pin number 0 - number: 0 - inverted: false - - Configuration variables: ************************ @@ -48,7 +37,20 @@ Configuration variables: Pin configuration variables: **************************** -- **SN74HC165** (**Required**, :ref:`config-id`): The id of the SN74HC165 component of the pin. +.. code-block:: yaml + + # Individual inputs + binary_sensor: + - platform: gpio + name: "SN74HC165 Pin #0" + pin: + sn74hc165: sn74hc165_hub + # Use pin number 0 + number: 0 + inverted: false + + +- **sn74hc165** (**Required**, :ref:`config-id`): The id of the SN74HC165 component of the pin. - **number** (**Required**, int): The pin number. - **inverted** (*Optional*, boolean): If received value should be treated as inverted. Defaults to ``false``. diff --git a/components/sn74hc595.rst b/components/sn74hc595.rst index 7d48a6192..3d68f6a3f 100644 --- a/components/sn74hc595.rst +++ b/components/sn74hc595.rst @@ -32,10 +32,10 @@ Over GPIO # Example configuration entry sn74hc595: - id: 'sn74hc595_hub' - data_pin: D5 - clock_pin: D8 - latch_pin: D7 - oe_pin: D6 + data_pin: GPIOXX + clock_pin: GPIOXX + latch_pin: GPIOXX + oe_pin: GPIOXX sr_count: 2 # Individual outputs @@ -73,11 +73,10 @@ Over SPI .. code-block:: yaml # Example configuration entry - spi: sn74hc595: - id: 'sn74hc595_hub' - latch_pin: D7 - oe_pin: D6 + latch_pin: GPIOXX + oe_pin: GPIOXX sr_count: 2 # Individual outputs diff --git a/components/speaker/i2s_audio.rst b/components/speaker/i2s_audio.rst index 34ff78bbf..92023ab37 100644 --- a/components/speaker/i2s_audio.rst +++ b/components/speaker/i2s_audio.rst @@ -12,7 +12,7 @@ This platform only works on ESP32 based chips. .. warning:: Audio and voice components consume a significant amount of resources (RAM, CPU) on the device. - + **Crashes are likely to occur** if you include too many additional components in your device's configuration. In particular, Bluetooth/BLE components are known to cause issues when used in combination with Voice Assistant and/or other audio components. @@ -23,7 +23,7 @@ This platform only works on ESP32 based chips. speaker: - platform: i2s_audio dac_type: external - i2s_dout_pin: GPIO22 + i2s_dout_pin: GPIOXX mode: mono Configuration variables: diff --git a/components/spi.rst b/components/spi.rst index 485e246fe..bf2f2543c 100644 --- a/components/spi.rst +++ b/components/spi.rst @@ -35,30 +35,30 @@ This component also accepts a list of controllers if you want to implement multi # Example configuration entry - single controller spi: - clk_pin: GPIO14 - mosi_pin: GPIO13 - miso_pin: GPIO12 + clk_pin: GPIOXX + mosi_pin: GPIOXX + miso_pin: GPIOXX # Example configuration entry - three controllers, one using quad SPI spi: - id: spi_bus0 - clk_pin: GPIO18 - mosi_pin: GPIO23 - miso_pin: GPIO19 + clk_pin: GPIOXX + mosi_pin: GPIOXX + miso_pin: GPIOXX interface: hardware - id: spi_bus1 - clk_pin: GPIO14 - mosi_pin: GPIO27 - miso_pin: GPIO26 + clk_pin: GPIOXX + mosi_pin: GPIOXX + miso_pin: GPIOXX interface: any - id: quad_spi_bus type: quad - clk_pin: GPIO47 + clk_pin: GPIOXX data_pins: - - 40 - - 41 - - 42 - - 43 + - GPIOXX + - GPIOXX + - GPIOXX + - GPIOXX Configuration variables: ------------------------ @@ -117,14 +117,14 @@ Reads and writes on the device can be performed with lambdas. For example: .. code-block:: yaml spi: - clk_pin: GPIO14 - mosi_pin: GPIO27 - miso_pin: GPIO26 + clk_pin: GPIOXX + mosi_pin: GPIOXX + miso_pin: GPIOXX interface: hardware spi_device: id: spidev - cs_pin: GPIO13 + cs_pin: GPIOXX data_rate: 2MHz mode: 3 bit_order: lsb_first diff --git a/components/sprinkler.rst b/components/sprinkler.rst index 2f7ec30dd..0221411f9 100644 --- a/components/sprinkler.rst +++ b/components/sprinkler.rst @@ -662,7 +662,7 @@ could easily be added by adding the ``pump_switch_id`` parameter and a :ref:`swi switch: - platform: gpio id: garden_sprinkler_valve - pin: 5 + pin: GPIOXX Single Controller, Three Valves, No Pump **************************************** @@ -707,13 +707,13 @@ This example illustrates a complete, simple three-valve system with no pump/upst switch: - platform: gpio id: lawn_sprinkler_valve_sw0 - pin: 0 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw1 - pin: 2 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw2 - pin: 4 + pin: GPIOXX Single Controller, Three Valves, Single Pump ******************************************** @@ -759,16 +759,16 @@ This example illustrates a complete three-valve system with a single pump/upstre switch: - platform: gpio id: sprinkler_pump_sw - pin: 12 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw0 - pin: 0 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw1 - pin: 2 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw2 - pin: 4 + pin: GPIOXX Single Controller, Three Latching Valves, Single Latching Pump ************************************************************** @@ -832,28 +832,28 @@ a common pump/upstream valve. switch: - platform: gpio id: sprinkler_pump_sw_off - pin: 14 + pin: GPIOXX - platform: gpio id: sprinkler_pump_sw_on - pin: 15 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw0_off - pin: 0 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw0_on - pin: 2 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw1_off - pin: 4 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw1_on - pin: 5 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw2_off - pin: 12 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw2_on - pin: 13 + pin: GPIOXX Dual Controller, Five Valves, Two Pumps *************************************** @@ -925,25 +925,25 @@ valves, each of which are shared between the two controllers: switch: - platform: gpio id: sprinkler_pump_sw0 - pin: 12 + pin: GPIOXX - platform: gpio id: sprinkler_pump_sw1 - pin: 13 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw0 - pin: 0 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw1 - pin: 2 + pin: GPIOXX - platform: gpio id: lawn_sprinkler_valve_sw2 - pin: 4 + pin: GPIOXX - platform: gpio id: garden_sprinkler_valve_sw0 - pin: 14 + pin: GPIOXX - platform: gpio id: garden_sprinkler_valve_sw1 - pin: 15 + pin: GPIOXX .. note:: @@ -1160,7 +1160,7 @@ How Do I... *********** - **...determine if the sprinkler controller is running?** - + Use the method ``optional active_valve()`` to check if there is an active valve. If the ``optional`` returned ``has_value()``, the sprinkler controller is running and you may use the ``value()`` method to check which specific valve is active. @@ -1225,7 +1225,7 @@ How Do I... } - **...determine the sprinkler controller's multiplier/repeat values?** - + Methods of interest in this case are: - ``float multiplier()`` diff --git a/components/status_led.rst b/components/status_led.rst index 26d9e2fdc..fa629893c 100644 --- a/components/status_led.rst +++ b/components/status_led.rst @@ -9,7 +9,7 @@ The ``status_led`` hooks into all ESPHome components and can indicate the status the device. Specifically, it will: - Blink slowly (about every second) when a **warning** is active. Warnings are active when for - example reading a sensor value fails temporarily, the WiFi/MQTT connections are disrupted, or + example reading a sensor value fails temporarily, the WiFi/MQTT connections are disrupted, or if the native API component is included but no client is connected. - Blink quickly (multiple times per second) when an **error** is active. Errors indicate that ESPHome has found an error while setting up. In most cases, ESPHome will still try to @@ -20,7 +20,7 @@ the device. Specifically, it will: # Example configuration entry status_led: - pin: GPIO2 + pin: GPIOXX .. note:: @@ -42,7 +42,7 @@ Configuration variables: status_led: pin: - number: D0 + number: GPIOXX inverted: true See Also diff --git a/components/stepper/index.rst b/components/stepper/index.rst index 10401e88a..ea3225b3c 100644 --- a/components/stepper/index.rst +++ b/components/stepper/index.rst @@ -45,12 +45,12 @@ Put this code into the configuration file on ESPHome for this device. stepper: - platform: a4988 id: my_stepper - step_pin: D0 - dir_pin: D1 + step_pin: GPIOXX + dir_pin: GPIOXX max_speed: 250 steps/s # Optional: - sleep_pin: D2 + sleep_pin: GPIOXX acceleration: inf deceleration: inf @@ -78,7 +78,7 @@ Configuration variables: - platform: a4988 # ... dir_pin: - number: D1 + number: GPIOXX inverted: true ULN2003 Component @@ -92,10 +92,10 @@ Put this code into the configuration file on ESPHome for this device. stepper: - platform: uln2003 id: my_stepper - pin_a: D0 - pin_b: D1 - pin_c: D2 - pin_d: D3 + pin_a: GPIOXX + pin_b: GPIOXX + pin_c: GPIOXX + pin_d: GPIOXX max_speed: 250 steps/s # Optional: @@ -273,7 +273,7 @@ Configuration variables: Home Assistant Configuration ---------------------------- -The easiest way to control your stepper from Home Assistant is to add a ``number`` to your ESPHome +The easiest way to control your stepper from Home Assistant is to add a ``number`` to your ESPHome configuration. See :ref:`Number ` for more information. .. code-block:: yaml diff --git a/components/switch/gpio.rst b/components/switch/gpio.rst index 4d69d4c5b..3bdc5e0eb 100644 --- a/components/switch/gpio.rst +++ b/components/switch/gpio.rst @@ -18,7 +18,7 @@ through this platform. # Example configuration entry switch: - platform: gpio - pin: 25 + pin: GPIOXX name: "Living Room Dehumidifier" Configuration variables: @@ -26,8 +26,6 @@ Configuration variables: - **pin** (**Required**, :ref:`Pin Schema `): The GPIO pin to use for the switch. -- **name** (**Required**, string): The name for the switch. -- **id** (*Optional*, :ref:`config-id`): Manually specify the ID used for code generation. - **interlock** (*Optional*, list): A list of other GPIO switches in an interlock group. See :ref:`switch-gpio-interlocking`. - **interlock_wait_time** (*Optional*, :ref:`config-time`): For interlocking mode, set how long @@ -47,7 +45,7 @@ To create an active-low switch (one that is turned off by default), use the :ref switch: - platform: gpio pin: - number: 25 + number: GPIOXX inverted: true Momentary Switch @@ -65,7 +63,7 @@ or closes the gate. The relay simulates the button press for 500ms. # Example configuration entry switch: - platform: gpio - pin: 25 + pin: GPIOXX id: relay name: "Gate Remote" icon: "mdi:gate" @@ -92,13 +90,13 @@ with a list of all the switches in the group. # Prevent relay #1 and relay #2 from being activated at the same time. switch: - platform: gpio - pin: GPIO25 + pin: GPIOXX name: "Relay #1" id: relay1 interlock: [relay2] - platform: gpio - pin: GPIO26 + pin: GPIOXX name: "Relay #2" id: relay2 interlock: [relay1] diff --git a/components/switch/output.rst b/components/switch/output.rst index b637b250c..5282f3564 100644 --- a/components/switch/output.rst +++ b/components/switch/output.rst @@ -16,7 +16,7 @@ The ``output`` switch platform allows you to use any output component as a switc # Example configuration entry output: - platform: gpio - pin: 25 + pin: GPIOXX id: 'generic_out' switch: - platform: output diff --git a/components/switch/uart.rst b/components/switch/uart.rst index 1be109264..98957a318 100644 --- a/components/switch/uart.rst +++ b/components/switch/uart.rst @@ -11,10 +11,6 @@ The ``uart`` switch platform allows you to send a pre-defined sequence of bytes .. code-block:: yaml # Example configuration entry - uart: - baud_rate: 9600 - tx_pin: D0 - switch: - platform: uart name: "UART String Output" diff --git a/components/text_sensor/wl_134.rst b/components/text_sensor/wl_134.rst index a8bfe6c33..0f55e7f01 100644 --- a/components/text_sensor/wl_134.rst +++ b/components/text_sensor/wl_134.rst @@ -10,20 +10,15 @@ The ``wl_134`` text sensor platform exposes the last read pet tag as text sensor .. code-block:: yaml # Example configuration entry - uart: - rx_pin: GPIO17 - baud_rate: 9600 - text_sensor: - platform: wl_134 name: Transponder Code - reset: true Configuration variables: ------------------------ - **reset** (*Optional*, boolean): Reset the text sensor state back to "" 1s after reading a tag. Defaults to ``false``. -- All options from :ref:`Text Sensor `. +- All other options from :ref:`Text Sensor `. See Also -------- diff --git a/components/tm1651.rst b/components/tm1651.rst index 8ace6218d..51dc85144 100644 --- a/components/tm1651.rst +++ b/components/tm1651.rst @@ -22,8 +22,8 @@ and brightness settings. All updates can be made via lambda expressions. tm1651: id: tm1651_battery - clk_pin: D6 - dio_pin: D5 + clk_pin: GPIOXX + dio_pin: GPIOXX Configuration variables: ************************ diff --git a/components/touchscreen/cst226.rst b/components/touchscreen/cst226.rst index a9ddfaeab..8ac6328ef 100644 --- a/components/touchscreen/cst226.rst +++ b/components/touchscreen/cst226.rst @@ -27,7 +27,7 @@ Base Touchscreen Configuration touchscreen: platform: cst226 id: my_touchscreen - interrupt_pin: GPIO3 + interrupt_pin: GPIOXX Configuration variables: ************************ diff --git a/components/touchscreen/cst816.rst b/components/touchscreen/cst816.rst index 62f3bb79a..53e13aaeb 100644 --- a/components/touchscreen/cst816.rst +++ b/components/touchscreen/cst816.rst @@ -28,8 +28,8 @@ Base Touchscreen Configuration touchscreen: platform: cst816 id: my_touchscreen - interrupt_pin: GPIO3 - reset_pin: GPIO21 + interrupt_pin: GPIOXX + reset_pin: GPIOXX Configuration variables: ************************ diff --git a/components/touchscreen/ektf2232.rst b/components/touchscreen/ektf2232.rst index 220c61a37..c156584b7 100644 --- a/components/touchscreen/ektf2232.rst +++ b/components/touchscreen/ektf2232.rst @@ -15,8 +15,8 @@ The :ref:`I²C ` is required to be set up in your configuration for this se # Example configuration entry touchscreen: - platform: ektf2232 - interrupt_pin: GPIO36 - rts_pin: GPIO16 + interrupt_pin: GPIOXX + rts_pin: GPIOXX Configuration variables: diff --git a/components/touchscreen/ft63x6.rst b/components/touchscreen/ft63x6.rst index b206d21cb..75e9208aa 100644 --- a/components/touchscreen/ft63x6.rst +++ b/components/touchscreen/ft63x6.rst @@ -14,35 +14,9 @@ The :ref:`I²C ` is required to be set up in your configuration for this se .. code-block:: yaml # Example configuration entry - esp32: - board: m5stack-core2 - framework: - type: arduino - - i2c: - sda: GPIO18 - scl: GPIO19 - scan: false - - output: - - platform: ledc - pin: GPIO23 - id: screen_led - - light: - - platform: monochromatic - output: screen_led - default_transition_length: 0.2s - name: 'Backlight' - restore_mode: ALWAYS_ON - touchscreen: - platform: ft63x6 - interrupt_pin: GPIO39 - on_touch: - - logger.log: - format: Touch %d at (%d, %d) - args: [touch.id, touch.x, touch.y] + interrupt_pin: GPIOXX Configuration variables: ------------------------ diff --git a/components/touchscreen/gt911.rst b/components/touchscreen/gt911.rst index a1182c6f8..517563f50 100644 --- a/components/touchscreen/gt911.rst +++ b/components/touchscreen/gt911.rst @@ -27,7 +27,7 @@ Base Touchscreen Configuration touchscreen: platform: gt911 id: my_touchscreen - interrupt_pin: GPIO3 + interrupt_pin: GPIOXX Configuration variables: ************************ diff --git a/components/touchscreen/index.rst b/components/touchscreen/index.rst index c16c93ecf..2b9170fc3 100644 --- a/components/touchscreen/index.rst +++ b/components/touchscreen/index.rst @@ -124,7 +124,7 @@ The calibration assumes a display oriented in a way that you will be using it, i touchscreen: platform: xpt2046 id: my_touchscreen - cs_pin: 17 + cs_pin: GPIOXX on_touch: - lambda: |- ESP_LOGI("cal", "x=%d, y=%d, x_raw=%d, y_raw=%0d", @@ -256,7 +256,7 @@ For example you could do: Be aware that you need to check the state flag every time to see if the touch is still valid. - state value 0. means the touch is invalid as the touch is no longer detected. -- state value 1 means is being the first time detected. +- state value 1 means is being the first time detected. - state value 2 means the touch is still being detected but is moved on the screen. - state value 4 and higher means a touch release is detected. diff --git a/components/touchscreen/tt21100.rst b/components/touchscreen/tt21100.rst index ec0be66da..22c9cb9f2 100644 --- a/components/touchscreen/tt21100.rst +++ b/components/touchscreen/tt21100.rst @@ -32,8 +32,8 @@ Base Touchscreen Configuration touchscreen: platform: tt21100 id: my_touchscreen - interrupt_pin: GPIO3 - reset_pin: GPIO48 + interrupt_pin: GPIOXX + reset_pin: GPIOXX Configuration variables: ************************ diff --git a/components/touchscreen/xpt2046.rst b/components/touchscreen/xpt2046.rst index 7de79555b..77db1dfba 100644 --- a/components/touchscreen/xpt2046.rst +++ b/components/touchscreen/xpt2046.rst @@ -28,8 +28,8 @@ The :ref:`SPI ` is required to be set up in your configuration for this sen touchscreen: platform: xpt2046 id: my_touchscreen - cs_pin: 17 - interrupt_pin: 16 + cs_pin: GPIOXX + interrupt_pin: GPIOXX update_interval: 50ms threshold: 400 calibration: diff --git a/components/tuya.rst b/components/tuya.rst index 0710fb7d7..d941b8cf6 100644 --- a/components/tuya.rst +++ b/components/tuya.rst @@ -16,18 +16,10 @@ Put the ``tuya`` component in the config and it will list the possible devices f .. code-block:: yaml - # Make sure logging is not using the serial port - logger: - baud_rate: 0 - - uart: - rx_pin: GPIO3 - tx_pin: GPIO1 - baud_rate: 9600 - # Register the Tuya MCU connection tuya: + Here is an example output for a Tuya fan controller: .. code-block:: text diff --git a/components/uart.rst b/components/uart.rst index e808d3290..963238166 100644 --- a/components/uart.rst +++ b/components/uart.rst @@ -30,7 +30,7 @@ In some cases only **TX** or **RX** exists as the device at the other end only a On the ESP32, this component uses the hardware UART units and is thus very accurate. On the ESP8266 however, ESPHome has to use a software implementation as there are no other hardware UART units available other than the ones used for logging. Therefore the UART data on the ESP8266 can have occasional data glitches especially with - higher baud rates. + higher baud rates. .. note:: @@ -43,8 +43,8 @@ In some cases only **TX** or **RX** exists as the device at the other end only a # Example configuration entry uart: - tx_pin: 1 - rx_pin: 3 + tx_pin: GPIOXX + rx_pin: GPIOXX baud_rate: 9600 Configuration variables: @@ -74,7 +74,7 @@ be accurate at higher baud rates. logger and leave others available. If you have configured the logger to use a different hardware UART, the pins used for hardware sharing change accordingly. -The ESP32 has three UARTs. ESP32 lite variant chips (ESP32-S3, ESP32-C3, ESP32-S2, etc) may have fewer UARTs (usually two). Any pair of GPIO pins can be used, as long as they support the proper output/input modes. +The ESP32 has three UARTs. ESP32 lite variant chips (ESP32-S3, ESP32-C3, ESP32-S2, etc) may have fewer UARTs (usually two). Any pair of GPIO pins can be used, as long as they support the proper output/input modes. The ESP8266 has two UARTs; the second of which is TX-only. Only a limited set of pins can be used. ``UART0`` may use either ``tx_pin: GPIO1`` and ``rx_pin: GPIO3``, or ``tx_pin: GPIO15`` and ``rx_pin: GPIO13``. ``UART1`` must diff --git a/components/vbus.rst b/components/vbus.rst index 6ff20add9..3f582d1f8 100644 --- a/components/vbus.rst +++ b/components/vbus.rst @@ -74,17 +74,9 @@ Component .. code-block:: yaml # Example configuration entry - uart: - id: resol - rx_pin: GPIO3 - baud_rate: 9600 - vbus: uart_id: resol - logger: - baud_rate: 0 # disable uart logger on ESP8266 - .. warning:: If you are using the :doc:`logger` make sure you are not using the same pins for it or otherwise disable the UART @@ -234,7 +226,7 @@ Configuration variables: - **source** (**Required**): The address corresponding to ``your device model`` (see below). - **command** (**Required**): The ``command`` corresponding to your device (see below). - **sensors** (**Required**): A list of :ref:`Sensor ` definitions that include a ``lambda`` to do the decoding and return a ``float`` value. - + - **lambda** (**Required**, :ref:`lambda `): Code to parse a value from the incoming data packets and return it. The data packet is in a ``std::vector`` called ``x``. diff --git a/components/wiegand.rst b/components/wiegand.rst index ba6cb6998..7234006f6 100644 --- a/components/wiegand.rst +++ b/components/wiegand.rst @@ -5,7 +5,7 @@ Wiegand keypad and tag reader :description: Wiegand-standard key input and card/tag reader panel :image: wiegand.jpg -The ``wiegand`` component allows you to integrate Wiegand-standard key +The ``wiegand`` component allows you to integrate Wiegand-standard key input and card or tag reader panels in Home Assistant. .. figure:: ../images/wiegand.jpg @@ -16,9 +16,9 @@ input and card or tag reader panels in Home Assistant. .. note:: - Some keypads are preconfigured by the factory to act as Wiegand input - devices. In order to work with this component, they may need to - be reconfigured to act as *Wiegand 26 output* or *Wiegand 34 output* + Some keypads are preconfigured by the factory to act as Wiegand input + devices. In order to work with this component, they may need to + be reconfigured to act as *Wiegand 26 output* or *Wiegand 34 output* devices. @@ -30,8 +30,8 @@ Component # Example configuration entry wiegand: - id: mykeypad - d0: GPIO5 - d1: GPIO4 + d0: GPIOXX + d1: GPIOXX on_key: - lambda: ESP_LOGI("KEY", "received key %d", x); on_tag: @@ -44,19 +44,19 @@ Component Configuration variables: - **id** (*Optional*, :ref:`config-id`): Set the ID of this device for use in lambdas. -- **d0** (**Required**, :ref:`Pin Schema `): The pin where the ``D0`` output +- **d0** (**Required**, :ref:`Pin Schema `): The pin where the ``D0`` output of the Wiegand's interface connects. -- **d1** (**Required**, :ref:`Pin Schema `): The pin where the ``D1`` output +- **d1** (**Required**, :ref:`Pin Schema `): The pin where the ``D1`` output of the Wiegand's interface connects. Automations: ------------ -- **on_key** (*Optional*, :ref:`Automation `): An automation to perform +- **on_key** (*Optional*, :ref:`Automation `): An automation to perform when a key has been pressed on the pad. The key is in a variable called ``x``. -- **on_tag** (*Optional*, :ref:`Automation `): An automation to perform - when a Wiegand-compatible card or a tag has been read by the device. The tag code is +- **on_tag** (*Optional*, :ref:`Automation `): An automation to perform + when a Wiegand-compatible card or a tag has been read by the device. The tag code is in a variable called ``x``. - **on_raw** (*Optional*, :ref:`Automation `): An automation to perform for any data sent by the device. The value is in a variable called ``value``, the number of @@ -66,7 +66,7 @@ Automations: .. note:: - Automatic handling of multiple keys (e.g. PIN code entry) is possible with the + Automatic handling of multiple keys (e.g. PIN code entry) is possible with the the :ref:`Key Collector ` component. Keys 10 and 11 are ``*`` and ``#``. They might be labelled as ``ENT`` or ``ESC``, diff --git a/cookbook/display_time_temp_oled.rst b/cookbook/display_time_temp_oled.rst index ea3317f12..0e1ecfaca 100644 --- a/cookbook/display_time_temp_oled.rst +++ b/cookbook/display_time_temp_oled.rst @@ -99,14 +99,14 @@ Note your ``address`` and ``model`` might be different, use the scan option to f .. code-block:: yaml i2c: - sda: D1 - scl: D2 + sda: GPIOXX + scl: GPIOXX scan: false display: - platform: ssd1306_i2c model: "SH1106 128x64" - reset_pin: D0 + reset_pin: GPIOXX address: 0x3C lambda: |- // Print "Mitt Smarta Hus" in top center. @@ -148,7 +148,7 @@ Below follows an example that replaces the "Mitt smarta hem" top printout with t display: - platform: ssd1306_i2c model: "SH1106 128x64" - reset_pin: D0 + reset_pin: GPIOXX address: 0x3C lambda: |- // Print "Alarm State: " in top center diff --git a/cookbook/garage-door.rst b/cookbook/garage-door.rst index 542bf4d14..92a3156e7 100644 --- a/cookbook/garage-door.rst +++ b/cookbook/garage-door.rst @@ -13,11 +13,11 @@ for a short period of time, the close/open action begins. switch: - platform: gpio - pin: D3 + pin: GPIOXX name: "Garage Door Open Switch" id: open_switch - platform: gpio - pin: D4 + pin: GPIOXX name: "Garage Door Close Switch" id: close_switch cover: diff --git a/cookbook/infostrip.rst b/cookbook/infostrip.rst index 1885882a0..e20060aa8 100644 --- a/cookbook/infostrip.rst +++ b/cookbook/infostrip.rst @@ -26,17 +26,9 @@ ESPHome configuration .. code-block:: yaml - esphome: - name: esp_infostrip - - esp8266: - board: d1_mini - - # TODO -> add your personal wifi, logging, api, ota settings here - uart: - rx_pin: 4 - tx_pin: 5 + rx_pin: GPIOXX + tx_pin: GPIOXX baud_rate: 9600 sensor: @@ -57,7 +49,7 @@ ESPHome configuration - platform: fastled_clockless chipset: WS2812B id: light_fastled - pin: D4 + pin: GPIOXX num_leds: 4 rgb_order: GRB name: "Infostrip" diff --git a/cookbook/lambda_magic.rst b/cookbook/lambda_magic.rst index 7f901283b..5aa4aaea6 100644 --- a/cookbook/lambda_magic.rst +++ b/cookbook/lambda_magic.rst @@ -13,7 +13,7 @@ These things don't need external or custom components, and show how powerful :re Display pages alternative ------------------------- -Some displays like :ref:`lcd-pcf8574` don't support pages natively, but you can easily implement them +Some displays like :ref:`lcd-pcf8574` don't support pages natively, but you can easily implement them using Lambdas: .. code-block:: yaml @@ -28,10 +28,10 @@ using Lambdas: case 1: it.print(0, 1, "Page1"); break; - case 2: + case 2: it.print(0, 1, "Page2"); break; - case 3: + case 3: it.print(0, 1, "Page3"); break; } @@ -104,8 +104,8 @@ Tested on both `arduino` and `esp-idf` platforms. Custom UART Text Sensor ----------------------- -Lots of devices communicate using the UART protocol. If you want to read -lines from uart to a Text Sensor you can do so using this code example. +Lots of devices communicate using the UART protocol. If you want to read +lines from uart to a Text Sensor you can do so using this code example. With this you can use automations or lambda to set switch or sensor states. @@ -115,17 +115,17 @@ With this you can use automations or lambda to set switch or sensor states. class UartReadLineSensor : public Component, public UARTDevice, public TextSensor { public: - UartReadLineSensor(UARTComponent *parent) : UARTDevice(parent) {} + UartReadLineSensor(UARTComponent *parent) : UARTDevice(parent) {} void setup() override { // nothing to do here - } + } int readline(int readch, char *buffer, int len) { static int pos = 0; int rpos; - + if (readch > 0) { switch (readch) { case '\n': // Ignore new-lines @@ -143,7 +143,7 @@ With this you can use automations or lambda to set switch or sensor states. } // No end of line has been found, so return -1. return -1; - } + } void loop() override { const int max_line_length = 80; @@ -157,7 +157,7 @@ With this you can use automations or lambda to set switch or sensor states. }; (Store this file in your configuration directory, for example ``uart_read_line_sensor.h``) - + And in YAML: .. code-block:: yaml @@ -166,15 +166,15 @@ And in YAML: esphome: includes: - uart_read_line_sensor.h - + logger: level: VERBOSE #makes uart stream available in esphome logstream baud_rate: 0 #disable logging over uart uart: id: uart_bus - tx_pin: D0 - rx_pin: D1 + tx_pin: GPIOXX + rx_pin: GPIOXX baud_rate: 9600 text_sensor: @@ -215,7 +215,7 @@ Then the switch uses the text sensor state to publish its own state. - uart.write: "\r*pow=on#\r" turn_off_action: - uart.write: "\r*pow=off#\r" - + interval: - interval: 10s then: @@ -228,13 +228,13 @@ Delaying Remote Transmissions The solution below handles the problem of RF frames being sent out by :doc:`/components/rf_bridge` (or :doc:`/components/remote_transmitter`) too quickly one after another when operating radio controlled -covers. The cover motors seem to need at least 600-700ms of silence between the individual code transmissions +covers. The cover motors seem to need at least 600-700ms of silence between the individual code transmissions to be able to recognize them. This can be solved by building up a queue of raw RF codes and sending them out one after the other with -(a configurable) delay between them. Delay is only added to the next commands coming from a list of -covers which have to be operated at once from Home Assistant. This is transparent to the system, which -will still look like they operate simultaneously. +(a configurable) delay between them. Delay is only added to the next commands coming from a list of +covers which have to be operated at once from Home Assistant. This is transparent to the system, which +will still look like they operate simultaneously. .. code-block:: yaml @@ -305,7 +305,7 @@ One Button Cover Control The configuration below shows how with a single button you can control the motion of a motorized cover by cycling between: open->stop->close->stop->... -In this example a :doc:`/components/cover/time_based` is used with the GPIO configuration of a Sonoff Dual R2. +In this example a :doc:`/components/cover/time_based` is used with the GPIO configuration of a Sonoff Dual R2. .. note:: diff --git a/custom/uart.rst b/custom/uart.rst index 40b71b668..c4426cc2d 100644 --- a/custom/uart.rst +++ b/custom/uart.rst @@ -59,8 +59,8 @@ And in YAML: uart: id: uart_bus - tx_pin: D0 - rx_pin: D1 + tx_pin: GPIOXX + rx_pin: GPIOXX baud_rate: 9600 custom_component: diff --git a/guides/automations.rst b/guides/automations.rst index f1cd253e6..7bfe0e3b5 100644 --- a/guides/automations.rst +++ b/guides/automations.rst @@ -18,18 +18,18 @@ Let's begin with an example to explain these concepts. Suppose you have this con switch: - platform: gpio - pin: GPIO3 + pin: GPIOXX name: "Living Room Dehumidifier" binary_sensor: - platform: gpio - pin: GPIO4 + pin: GPIOXX name: "Living Room Dehumidifier Toggle Button" With this file you can already perform some basic tasks. You can control the ON/OFF state of the dehumidifier in your living room from Home Assistant's front-end. But in many cases, controlling everything strictly from the frontend is quite a pain. That's why you have -decided to also install a simple push button next to the dehumidifier on pin GPIO4. +decided to also install a simple push button next to the dehumidifier on pin GPIOXX. A simple push on this button should toggle the state of the dehumidifier. You *could* write an automation to do this task in Home Assistant's automation engine, but @@ -46,13 +46,13 @@ For example, this configuration would achieve your desired behavior: switch: - platform: gpio - pin: GPIO3 + pin: GPIOXX name: "Living Room Dehumidifier" id: dehumidifier1 binary_sensor: - platform: gpio - pin: GPIO4 + pin: GPIOXX name: "Living Room Dehumidifier Toggle Button" on_press: then: @@ -418,7 +418,7 @@ All Conditions -------------- - :ref:`lambda ` -- :ref:`and ` / :ref:`or ` / :ref:`xor ` / :ref:`not ` +- :ref:`and ` / :ref:`or ` / :ref:`xor ` / :ref:`not ` - :ref:`for ` - :ref:`binary_sensor.is_on ` / :ref:`binary_sensor.is_off ` - :ref:`switch.is_on ` / :ref:`switch.is_off ` @@ -706,7 +706,7 @@ After this action the component will refresh at the original update_interval rat This will allow the component to resume automatic update at the defined interval. -This action also allows to change the update interval, calling it without suspend, +This action also allows to change the update interval, calling it without suspend, replace the poller directly. Please note that this only works with PollingComponent types and others will result in a @@ -724,7 +724,7 @@ compile error. # Change the poller interval on_...: then: - - component.resume: + - component.resume: id: my_component update_interval: 15s diff --git a/guides/configuration-types.rst b/guides/configuration-types.rst index 29e32a906..4f9ae825d 100644 --- a/guides/configuration-types.rst +++ b/guides/configuration-types.rst @@ -34,7 +34,7 @@ names `__, package from your distro or - install it yourself with ``pip install esptool`` (in case of Linux). + install it yourself with ``pip install esptool`` (in case of Linux). Before using ``esptool``, make sure you know which serial port your programming adapter is connected to. In Linux use the ``dmesg`` command afer you plug the device into the USB port to see the name of the newly detected serial port. @@ -119,7 +119,7 @@ Program flash with your firmware binary: .. note:: - If you're just seeing ``Connecting....____....`` on the screen and flashing fails: + If you're just seeing ``Connecting....____....`` on the screen and flashing fails: - verify that the device name of the port has not changed while you were re-plugging it too fast (eg. changed from ``/dev/ttyUSB0`` to ``/dev/ttyUSB1``). @@ -128,11 +128,11 @@ Program flash with your firmware binary: - for some devices you need to keep ``GPIO0`` and ``GND`` connected at least until flashing has begun. - for some devices you need to power-cycle in programming mode after erasing flash, they don't auto-reset. - it also might be a sign that ESP is defective, damaged or otherwise cannot be programmed. - + If you're in an RF noisy environment or your UART wires are a bit long, flashing can fail during transfer. Don't worry, an ESP won't brick just because of that. Put it again in programming mode and flash with a reduced baudrate for safer transfers: - + ``esptool.py --port /dev/ttyUSB0 --baud 460800 write_flash 0x0 your_node_firmware.bin`` diff --git a/guides/getting_started_command_line.rst b/guides/getting_started_command_line.rst index 5746fad08..9cff10fa3 100644 --- a/guides/getting_started_command_line.rst +++ b/guides/getting_started_command_line.rst @@ -40,7 +40,7 @@ If you want to use `docker-compose` instead, here's a sample file: privileged: true network_mode: host environment: - - USERNAME=test + - USERNAME=test - PASSWORD=ChangeMe .. note:: @@ -107,7 +107,7 @@ GPIO switch ` to our app. switch: - platform: gpio name: "Living Room Dehumidifier" - pin: 5 + pin: GPIO5 The configuration format should hopefully immediately seem similar to you. ESPHome has tried to keep it as close to Home Assistant’s @@ -224,7 +224,7 @@ To start the ESPHome dashboard, simply start ESPHome with the following command .. code-block:: bash # Install dashboard dependencies - pip install tornado esptool\ + pip install tornado esptool\ esphome dashboard config # On Docker, host networking mode is required for online status indicators diff --git a/guides/getting_started_hassio.rst b/guides/getting_started_hassio.rst index 32aad9a36..e1da95fa1 100644 --- a/guides/getting_started_hassio.rst +++ b/guides/getting_started_hassio.rst @@ -101,7 +101,7 @@ to the configuration like this: switch: - platform: gpio name: "Living Room Dehumidifier" - pin: 5 + pin: GPIO5 In above example, we're simply adding a switch that's called "Living Room Dehumidifier" (could control anything really, for example lights) and is connected to the pin ``GPIO5``.