From f8bf0b7d614e0998d48d7bb71db3c5447420acb6 Mon Sep 17 00:00:00 2001 From: Thomas Bertels <3265870+tbertels@users.noreply.github.com> Date: Thu, 21 Sep 2023 15:21:03 +0200 Subject: [PATCH 1/4] Typo in getting_started_hassio.rst (#3201) --- guides/getting_started_hassio.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/getting_started_hassio.rst b/guides/getting_started_hassio.rst index f5ffa5134..32aad9a36 100644 --- a/guides/getting_started_hassio.rst +++ b/guides/getting_started_hassio.rst @@ -82,7 +82,7 @@ in ``/config/esphome/garage-door.yaml``. command line is not very straightforward, but it's possible. To do that, install Home Assistant's SSH addon, configure a username and a password, and disable `Protection Mode` (please assess the risks you take with that). - Then, for example to access the logs form a device through an SSH client, + Then, for example to access the logs from a device through an SSH client, log in, and you can use a command like `docker exec -it addon_15ef4d2f_esphome esphome logs /config/esphome/garage-door.yaml`. See :doc:`getting_started_command_line` for more. From da43deb1a76442788ca412b201dd7c5394acde7c Mon Sep 17 00:00:00 2001 From: neeldaware Date: Sat, 23 Sep 2023 14:40:38 +1000 Subject: [PATCH 2/4] Update growatt_solar.rst (#3185) Added two missing configurable parameters - Polling interval and address. --- components/sensor/growatt_solar.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/components/sensor/growatt_solar.rst b/components/sensor/growatt_solar.rst index cd6bd18c9..b44244688 100644 --- a/components/sensor/growatt_solar.rst +++ b/components/sensor/growatt_solar.rst @@ -150,6 +150,10 @@ Configuration variables: kilo watt hours. All options from :ref:`Sensor `. - **inverter_module_temp** (*Optional*): Use the inverter module temperature value of the sensor in degree celsius. All options from :ref:`Sensor `. +- **update_interval** (*Optional*, :ref:`config-time`): The interval to check the + sensor. Defaults to ``10s``. +- **address** (*Optional*, int): The address of the sensor if multiple sensors are attached to + the same UART bus. You will need to set the address of each device manually. Defaults to ``1``. See Also -------- From 9ffbc6e94d7dfae0178e6a5dbb5c4a8ca3c8737b Mon Sep 17 00:00:00 2001 From: Torsten Paul Date: Sun, 24 Sep 2023 06:23:01 +0200 Subject: [PATCH 3/4] Fix typo in tm1637.rst (#3203) --- components/display/tm1637.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/display/tm1637.rst b/components/display/tm1637.rst index 502508671..9da0d458c 100644 --- a/components/display/tm1637.rst +++ b/components/display/tm1637.rst @@ -86,7 +86,7 @@ The TM1637 has a similar API to the fully fledged :ref:`display-engine`, but it' 7-segment displays don't have a concept of individual pixels. In the lambda you're passed a variable called ``it`` as with all other displays. In this case however, ``it`` is a TM1637 instance (see API Reference). -The most basic operation with the TM1637 is wiring a simple number to the screen as in the configuration example +The most basic operation with the TM1637 is writing a simple number to the screen as in the configuration example at the top of this page. But even though you're passing in a string (here ``"0123"``), ESPHome converts it into a representation that the TM1637 can understand: The exact pixels that should be turned on. And of course, not all characters can be represented. You can see a full list of characters :ref:`at the MAX7219 docs `. From 0e5de2debecf618e8fed6eb75e9025a1c1d05945 Mon Sep 17 00:00:00 2001 From: Kapil Yedidi Date: Sun, 24 Sep 2023 14:44:32 -0700 Subject: [PATCH 4/4] Fix typos in pmsa003i.rst (#3207) --- components/sensor/pmsa003i.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/components/sensor/pmsa003i.rst b/components/sensor/pmsa003i.rst index ca44c6675..02bed722f 100644 --- a/components/sensor/pmsa003i.rst +++ b/components/sensor/pmsa003i.rst @@ -30,17 +30,17 @@ The :ref:`I²C Bus ` is required to be set up in your configuration for thi pm_10_0: name: "PM10.0" pmc_0_3: - name: "PMC <0.3µm" + name: "PMC >0.3µm" pmc_0_5: - name: "PMC <0.5µm" + name: "PMC >0.5µm" pmc_1_0: - name: "PMC <1µm" + name: "PMC >1µm" pmc_2_5: - name: "PMC <2.5µm" + name: "PMC >2.5µm" pmc_5_0: - name: "PMC <5µm" + name: "PMC >5µm" pmc_10_0: - name: "PMC <10µm" + name: "PMC >10µm" Configuration variables: ------------------------