Merge branch 'esphome:current' into current

This commit is contained in:
optimusprimespace 2022-11-07 15:33:32 +01:00 committed by GitHub
commit 70876a5e83
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 8 additions and 3 deletions

View File

@ -56,6 +56,9 @@ Configuration variables:
- **command_throttle** (*Optional*, int): minimum time in milliseconds between 2 requests to the device. Default is 0ms
Because some modbus devices limit the rate of requests the interval between sending requests to the device can be modified.
- **update_interval** (*Optional*, :ref:`config-time`): The interval that the sensors should be checked.
Defaults to 60 seconds.
Example
-------

View File

@ -30,7 +30,7 @@ With Home Assistant 2021.6 or newer, entity state attributes can also be importe
Configuration variables:
------------------------
- **name** (**Required**, string): The name of the text sensor.
- **name** (*Optional*, string): The name of the text sensor.
- **entity_id** (**Required**, string): The entity ID to import from Home Assistant.
- **attribute** (*Optional*, string): The name of the state attribute to import from the
specified entity. The entity state is used when this option is omitted.

View File

@ -57,7 +57,9 @@ This powerful automation can be used to run automations at specific intervals at
specific times of day. The syntax is a subset of the `crontab <https://crontab.guru/>`__ syntax.
There are two ways to specify time intervals: Either with using the ``seconds:``, ``minutes:``, ...
keys as seen below or using a cron expression like ``* /5 * * * *``.
keys as seen below or using a cron alike expression like ``* /5 * * * *``.
Be aware normal cron implementations does not know about seconds like this esphome implementation, therefore you got 6 fields (seconds,minutes,hours,dayofmonth,month,dayofweek).
Basically, the automation engine looks at your configured time schedule every second and
evaluates if the automation should run.

View File

@ -804,7 +804,7 @@ This can't be used in a lambda as it would block all functioning of the device.
This :ref:`condition <config-condition>` allows you to check if a given script is running.
In case scripts are run in ``parallel``, this condition only tells you if at least one script
of the given id is running, not how many.
of the given id is running, not how many. Not designed for use with :ref:`while <while_action>`, instead try :ref:`script.wait <script-wait_action>`.
.. code-block:: yaml