mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-10 10:56:49 +00:00
fix(mqtt.markdown): correct formatting and update links in MQTT docum… (#39453)
This commit is contained in:
parent
af4568c062
commit
0269a89723
@ -1078,7 +1078,7 @@ payload_not_available:
|
|||||||
required: false
|
required: false
|
||||||
type: string
|
type: string
|
||||||
default: offline
|
default: offline
|
||||||
{% endconfiguration %}
|
{% endconfiguration %}
|
||||||
|
|
||||||
{% enddetails %}
|
{% enddetails %}
|
||||||
|
|
||||||
@ -1221,7 +1221,7 @@ Setting up a light, switch etc. is similar but requires a `command_topic` as men
|
|||||||
- Configuration topic: `homeassistant/switch/irrigation/config`
|
- Configuration topic: `homeassistant/switch/irrigation/config`
|
||||||
- State topic: `homeassistant/switch/irrigation/state`
|
- State topic: `homeassistant/switch/irrigation/state`
|
||||||
- Command topic: `homeassistant/switch/irrigation/set`
|
- Command topic: `homeassistant/switch/irrigation/set`
|
||||||
- Payload:
|
- Payload:
|
||||||
|
|
||||||
```json
|
```json
|
||||||
{
|
{
|
||||||
@ -1367,7 +1367,7 @@ The following software has built-in support for MQTT discovery:
|
|||||||
- [Tasmota](https://github.com/arendst/Tasmota) (starting with 5.11.1e, development halted)
|
- [Tasmota](https://github.com/arendst/Tasmota) (starting with 5.11.1e, development halted)
|
||||||
- [TeddyCloud](https://github.com/toniebox-reverse-engineering/teddycloud)
|
- [TeddyCloud](https://github.com/toniebox-reverse-engineering/teddycloud)
|
||||||
- [Teleinfo MQTT](https://fmartinou.github.io/teleinfo2mqtt) (starting with 3.0.0)
|
- [Teleinfo MQTT](https://fmartinou.github.io/teleinfo2mqtt) (starting with 3.0.0)
|
||||||
- [Tydom2MQTT](https://fmartinou.github.io/tydom2mqtt/)
|
- [Tydom2MQTT](https://tydom2mqtt.github.io/tydom2mqtt/)
|
||||||
- [What's up Docker?](https://fmartinou.github.io/whats-up-docker/) (starting with 3.5.0)
|
- [What's up Docker?](https://fmartinou.github.io/whats-up-docker/) (starting with 3.5.0)
|
||||||
- [WyzeSense2MQTT](https://github.com/raetha/wyzesense2mqtt)
|
- [WyzeSense2MQTT](https://github.com/raetha/wyzesense2mqtt)
|
||||||
- [Xiaomi DaFang Hacks](https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks)
|
- [Xiaomi DaFang Hacks](https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks)
|
||||||
@ -1429,7 +1429,7 @@ Note that MQTT device payloads often contain information for updating multiple e
|
|||||||
|
|
||||||
### The last reported state attribute
|
### The last reported state attribute
|
||||||
|
|
||||||
Because MQTT state updates are often repeated frequently, even when no actual changes exist, it is up to the MQTT subscriber to determine whether a status update was received. If the latest update is missed, it might take some time before the next one arrives. If a retained payload exists at the broker, that value will be replayed first, but it will be an update of a previous last state.
|
Because MQTT state updates are often repeated frequently, even when no actual changes exist, it is up to the MQTT subscriber to determine whether a status update was received. If the latest update is missed, it might take some time before the next one arrives. If a retained payload exists at the broker, that value will be replayed first, but it will be an update of a previous last state.
|
||||||
|
|
||||||
MQTT devices often continuously generate numerous state updates. MQTT does not update `last_reported` to avoid impacting system stability unless `force_update` is set. Alternatively, an MQTT sensor can be created to measure the last update.
|
MQTT devices often continuously generate numerous state updates. MQTT does not update `last_reported` to avoid impacting system stability unless `force_update` is set. Alternatively, an MQTT sensor can be created to measure the last update.
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user