jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-26 02:37:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixing some incorrect references to localhost

Browse Source
This commit is contained in:
Jeremiah Wuenschel 2016-02-08 22:47:41 -08:00
parent f4d3666d7a
commit ec381cf5de
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
source/_posts/2016-02-09-Smarter-Smart-Things-with-MQTT-and-Home-Assistant.markdown
View File

@ -65,7 +65,7 @@ The MQTT Bridge only needs to know where your MQTT broker lives. If you are usin
```yaml ```yaml
--- ---
mqtt: mqtt:
host: localhost host: <IP of the host>
``` ```
Restart the bridge, and you are ready to go: Restart the bridge, and you are ready to go:
@ -131,7 +131,7 @@ Start digging through the [MQTT Components][mqtt-ha] in Home Assistant to find w
### Configuring with Docker-Compose ### Configuring with Docker-Compose
Our personal prefernce for starting the whole suite of software is to use a single Docker-Compose file. Our personal preference for starting the whole suite of software is to use a single Docker-Compose file.
Just create a file called docker-compose.yml like this: Just create a file called docker-compose.yml like this:
@ -161,7 +161,7 @@ homeassistant:
- mqtt - mqtt
``` ```
This will start home-assistant, MQTT, and the Bridge, in dependency order. All config can reference the name of the docker container instead of localhost (e.g. mqtt for the broker host in Home Assistant). This will start home-assistant, MQTT, and the Bridge, in dependency order. All config can reference the name of the docker container instead of using IP addresses (e.g. mqtt for the broker host in Home Assistant).
### How it works ### How it works