Upstream/esphome-docs
1
0
Fork 0
mirror of https://github.com/esphome/esphome-docs.git synced 2025-01-22 21:41:39 +01:00
Code Issues Projects Releases Wiki Activity

Improve dsmr telegram timeouts (#1650)

Browse Source
This commit is contained in:
Maurice Makaay 2021-11-29 16:40:59 +01:00 committed by GitHub
parent 3ad562c594
commit bb1435b35c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
components/sensor/dsmr.rst
View File

@ -53,8 +53,11 @@ Configuration variables:
the P1 port's Data Request pin. Defaults to not using a Data Request pin.
See :ref:`Using the P1 Data Request pin <sensor-dsmr-request_pin>`.
- **request_interval** (*Optional*, :ref:`config-time`): The minimum time between two telegram readings.
Defaults to ``0``, meaning that the pace at which the smart meter sends its data determines the update frequency.
Defaults to ``0ms``, meaning that the pace at which the smart meter sends its data determines the update frequency.
This works best in combination with a ``request_pin``, but this option will work without one too.
- **receive_timeout** (*Optional*, :ref:`config-time`): The timeout on incoming data while reading a telegram.
When no new data arrive within the given timeout, the device will consider the current telegram a loss and
starts looking for the header of the next telegram. Defaults to ``200ms``.
- **id** (*Optional*, :ref:`config-id`): Manually specify the ID of the DSMR if you have multiple components.
Sensor