Fix broken links (#19619)

Co-authored-by: Franck Nijhof <frenck@frenck.nl>
This commit is contained in:
Stefan 2021-10-11 12:49:46 +02:00 committed by GitHub
parent 101c248088
commit 911a2c585e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 9 additions and 6 deletions

View File

@ -13,4 +13,3 @@ logger:
logs: logs:
homeassistant.components.mqtt: debug homeassistant.components.mqtt: debug
``` ```

View File

@ -6,7 +6,7 @@ logo: mqtt.png
The MQTT integration will register the service `mqtt.publish` which allows publishing messages to MQTT topics. There are two ways of specifying your payload. You can either use `payload` to hard-code a payload or use `payload_template` to specify a [template](/topics/templating/) that will be rendered to generate the payload. The MQTT integration will register the service `mqtt.publish` which allows publishing messages to MQTT topics. There are two ways of specifying your payload. You can either use `payload` to hard-code a payload or use `payload_template` to specify a [template](/topics/templating/) that will be rendered to generate the payload.
### Service `mqtt.publish` ## Service `mqtt.publish`
| Service data attribute | Optional | Description | | Service data attribute | Optional | Description |
| ---------------------- | -------- | ----------- | | ---------------------- | -------- | ----------- |
@ -26,10 +26,12 @@ payload: on
``` ```
{% raw %} {% raw %}
```yaml ```yaml
topic: home-assistant/light/1/state topic: home-assistant/light/1/state
payload_template: "{{ states('device_tracker.paulus') }}" payload_template: "{{ states('device_tracker.paulus') }}"
``` ```
{% endraw %} {% endraw %}
`payload` must be a string. If you want to send JSON then you need to format/escape it properly. Like: `payload` must be a string. If you want to send JSON then you need to format/escape it properly. Like:

View File

@ -20,7 +20,7 @@ Home Assistant allows users to share their usage data via the analytics integrat
The information sent depends on what options you opt-in to. You can opt-in during onboarding and by going to **{% my general title="Configuration >> General" %}** . The information sent depends on what options you opt-in to. You can opt-in during onboarding and by going to **{% my general title="Configuration >> General" %}** .
**{% my general badge %}** {% my general badge %}
When enabled, data will be sent 15 minutes after each start, and every 24h after startup. Sent data is printed to your log. When enabled, data will be sent 15 minutes after each start, and every 24h after startup. Sent data is printed to your log.
@ -74,7 +74,7 @@ This includes:
- The names of all your core integrations - The names of all your core integrations
- The names and versions of all your custom integrations if you have any - The names and versions of all your custom integrations if you have any
- Boolean to indicate that the [`energy` integration](/integrations/energy) is configured - Boolean to indicate that the [energy integration](/integrations/energy) is configured
If your system includes the Supervisor, this will also contain: If your system includes the Supervisor, this will also contain:

View File

@ -14,7 +14,7 @@ It's been a busy week with a lot of announcements around IoT standards, so I tho
## New IoT standard announced ## New IoT standard announced
As it's been a while, the industry has announced yet a new effort to create a new IoT standard called [Project Connected Home over IP](https://www.connectedhomeip.com/). I think that there are a few interesting bits to this standard: As it's been a while, the industry has announced yet a new effort to create a new IoT standard called [Project Matter](https://buildwithmatter.com) (formally called: 'Connected Home over IP'). I think that there are a few interesting bits to this standard:
The standard will be royalty-free. This is big, as it means that it will be easy for companies to build products. Take, for example, Homekit, which is a great IP-based local standard. Homekit has strict licensing and royalties, which prevented it from widespread adoption. The standard will be royalty-free. This is big, as it means that it will be easy for companies to build products. Take, for example, Homekit, which is a great IP-based local standard. Homekit has strict licensing and royalties, which prevented it from widespread adoption.

View File

@ -130,7 +130,7 @@ fulfilled in this release.
For example, the [Kostal Plenticore Solar Inverter](/integrations/kostal_plenticore), For example, the [Kostal Plenticore Solar Inverter](/integrations/kostal_plenticore),
[PVOutput](/integrations/pvoutput), [Fronius](/integrations/fronius), [PVOutput](/integrations/pvoutput), [Fronius](/integrations/fronius),
[SolaX Power](/integrations/solax), [Growatt](/integrations/growatt_server), [SolaX Power](/integrations/solax), [Growatt](/integrations/growatt_server),
[Solar-Log](/integrations/solar_log), [YouLess](/integrations/youless), [Solar-Log](/integrations/solarlog), [YouLess](/integrations/youless),
[Emoncms](/integrations/emoncms), [Modbus](/integrations/modbus), [Emoncms](/integrations/emoncms), [Modbus](/integrations/modbus),
and many more have added support for all the energy goodness. and many more have added support for all the energy goodness.

View File

@ -1078,6 +1078,7 @@
/integrations/climate.modbus /integrations/modbus /integrations/climate.modbus /integrations/modbus
/integrations/cover.modbus /integrations/modbus /integrations/cover.modbus /integrations/modbus
/integrations/fan.xiaomi_miio /integrations/xiaomi_miio /integrations/fan.xiaomi_miio /integrations/xiaomi_miio
/integrations/google /integrations/calendar.google
/integrations/light.xiaomi_miio /integrations/xiaomi_miio /integrations/light.xiaomi_miio /integrations/xiaomi_miio
/integrations/lovelace /lovelace /integrations/lovelace /lovelace
/integrations/remote.xiaomi_miio /integrations/xiaomi_miio /integrations/remote.xiaomi_miio /integrations/xiaomi_miio
@ -2057,6 +2058,7 @@
/integrations/scene.knx /integrations/knx#scene /integrations/scene.knx /integrations/knx#scene
/integrations/sensor.knx /integrations/knx#sensor /integrations/sensor.knx /integrations/knx#sensor
/integrations/switch.knx /integrations/knx#switch /integrations/switch.knx /integrations/knx#switch
/integrations/trace /docs/automation/troubleshooting
/integrations/weather.knx /integrations/knx#weather /integrations/weather.knx /integrations/knx#weather
/integrations/zigbee /integrations/xbee /integrations/zigbee /integrations/xbee
/integrations/hassio /hassio /integrations/hassio /hassio