jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Remove broken redirect from (#4901)

Browse source
This commit is contained in:
Paulus Schoutsen 2018-03-11 15:04:50 -07:00 • committed by GitHub
parent 4887c9c993
commit 13464e509e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
14 changed files with 0 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

1
source/_docs/mqtt/broker.markdown
View file

@ -8,7 +8,6 @@ comments: false
sharing: true
footer: true
logo: mqtt.png
redirect_from: /components/mqtt/#picking-a-broker
---
The MQTT component needs you to run an MQTT broker for Home Assistant to connect to. There are four options, each with various degrees of ease of setup and privacy.

1
source/_docs/mqtt/discovery.markdown
View file

@ -8,7 +8,6 @@ comments: false
sharing: true
footer: true
logo: mqtt.png
redirect_from: /components/mqtt/#discovery
---
The discovery of MQTT devices will enable one to use MQTT devices with only minimal configuration effort on the side of Home Assistant. The configuration is done on the device itself and the topic used by the device. Similar to the [HTTP binary sensor](/components/binary_sensor.http/) and the [HTTP sensor](/components/sensor.http/). The basic idea is that the device itself adds its configuration into your `configuration.yaml` automatically. To prevent multiple identical entries if a device reconnects a unique identifier is necessary. Two parts are required on the device side: The configuration topic which contains the necessary device type and unique identifier and the remaining device configuration without the device type.

1
source/_docs/mqtt/logging.markdown
View file

@ -8,7 +8,6 @@ comments: false
sharing: true
footer: true
logo: mqtt.png
redirect_from: /components/mqtt/#logging
---
The [logger](/components/logger/) component allow the logging of received MQTT messages.

1
source/_docs/mqtt/processing_json.markdown
View file

@ -8,7 +8,6 @@ comments: false
sharing: true
footer: true
logo: mqtt.png
redirect_from: /components/mqtt/#processing-json
---
The MQTT [switch](/components/switch.mqtt/) and [sensor](/components/sensor.mqtt/) platforms support processing JSON over MQTT messages and parsing them using JSONPath. JSONPath allows you to specify where in the JSON the value resides that you want to use. The following examples will always return the value `100`.

1
source/_docs/mqtt/service.markdown
View file

@ -8,7 +8,6 @@ comments: false
sharing: true
footer: true
logo: mqtt.png
redirect_from: /components/mqtt/#publish-service
---
The MQTT component will register the service `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.

1
source/_docs/mqtt/testing.markdown
View file

@ -8,7 +8,6 @@ comments: false
sharing: true
footer: true
logo: mqtt.png
redirect_from: /components/mqtt/#testing-your-setup
---
The `mosquitto` broker package ships commandline tools (often as `*-clients` package) to send and receive MQTT messages. As an alternative have a look at [hbmqtt_pub](http://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_pub.html) and [hbmqtt_sub](http://hbmqtt.readthedocs.org/en/latest/references/hbmqtt_sub.html) which are provided by HBMQTT. For sending test messages to a broker running on localhost check the example below: