mirror of
https://github.com/esphome/esphome-docs.git
synced 2025-01-27 22:31:37 +01:00
fix typo in mqtt doc ypi -> you (#2776)
This commit is contained in:
parent
d493079e07
commit
4b729f9885
@ -83,7 +83,7 @@ Configuration variables:
|
|||||||
- **skip_cert_cn_check** (*Optional*, bool): Only with ``esp-idf``. Don't verify if the common name in the server certificate matches the value of ``broker``.
|
- **skip_cert_cn_check** (*Optional*, bool): Only with ``esp-idf``. Don't verify if the common name in the server certificate matches the value of ``broker``.
|
||||||
- **idf_send_async** (*Optional*, bool): Only with ``esp-idf``. If true publishing the message happens from the internal mqtt task. The client only enqueues the message. Defaults to ``false``.
|
- **idf_send_async** (*Optional*, bool): Only with ``esp-idf``. If true publishing the message happens from the internal mqtt task. The client only enqueues the message. Defaults to ``false``.
|
||||||
The advantage of asyncronous publishing is that it doesn't block the esphome main thread. The disadvantage is a delay (up to 1-2 seconds) until the messages are actually sent out.
|
The advantage of asyncronous publishing is that it doesn't block the esphome main thread. The disadvantage is a delay (up to 1-2 seconds) until the messages are actually sent out.
|
||||||
Set this to true if ypi send large amounts of of data over mqtt.
|
Set this to true if you send large amounts of of data over mqtt.
|
||||||
- **reboot_timeout** (*Optional*, :ref:`config-time`): The amount of time to wait before rebooting when no
|
- **reboot_timeout** (*Optional*, :ref:`config-time`): The amount of time to wait before rebooting when no
|
||||||
MQTT connection exists. Can be disabled by setting this to ``0s``. Defaults to ``15min``.
|
MQTT connection exists. Can be disabled by setting this to ``0s``. Defaults to ``15min``.
|
||||||
- **keepalive** (*Optional*, :ref:`config-time`): The time
|
- **keepalive** (*Optional*, :ref:`config-time`): The time
|
||||||
|
Loading…
Reference in New Issue
Block a user