Embedded MQTT password change backport to 0.76 (#6020)

* Embedded MQTT password change backport to 0.76

* Fix formatting
This commit is contained in:
Jason Hu 2018-08-14 23:10:48 -07:00 committed by Paulus Schoutsen
parent 7060874322
commit b8e78b92a3

View File

@ -14,7 +14,7 @@ The MQTT component needs you to run an MQTT broker for Home Assistant to connect
### {% linkable_title Embedded broker %} ### {% linkable_title Embedded broker %}
Home Assistant contains an embedded MQTT broker. If no broker configuration is given, the [HBMQTT broker](https://pypi.python.org/pypi/hbmqtt) is started and Home Assistant connects to it. Embedded broker default configuration: Home Assistant contains an embedded MQTT broker called [HBMQTT](https://pypi.python.org/pypi/hbmqtt). If you don't have an MQTT broker, you can configure this one to be used. If configured, Home Assistant will automatically connect to it.
| Setting | Value | | Setting | Value |
| -------------- | ----- | | -------------- | ----- |
@ -22,15 +22,20 @@ Home Assistant contains an embedded MQTT broker. If no broker configuration is g
| Port | 1883 | | Port | 1883 |
| Protocol | 3.1.1 | | Protocol | 3.1.1 |
| User | homeassistant | | User | homeassistant |
| Password | Your API [password](/components/http/) | | Password | _password set under mqtt settings_ |
| Websocket port | 8080 | | Websocket port | 8080 |
```yaml ```yaml
# Example configuration.yaml entry # Example configuration.yaml entry
mqtt: mqtt:
broker:
password: hello
``` ```
<p class='note'>
Before release 0.76, the embedded broker would use your API password as a password to the MQTT user. This is no longer the case.
</p>
<p class='note warning'> <p class='note warning'>
There is [an issue](https://github.com/beerfactory/hbmqtt/issues/62) with the HBMQTT broker and the WebSocket connection that is causing a memory leak. If you experience this issue, consider using another broker like Mosquitto. There is [an issue](https://github.com/beerfactory/hbmqtt/issues/62) with the HBMQTT broker and the WebSocket connection that is causing a memory leak. If you experience this issue, consider using another broker like Mosquitto.
</p> </p>