From 12e2fab256d9d21b652ec66597c7c32f70d76b7a Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Mon, 24 Sep 2018 14:36:39 +0200 Subject: [PATCH] Update hassio_hass.md --- docs/hassio_hass.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hassio_hass.md b/docs/hassio_hass.md index 75c45161..8fe7470c 100644 --- a/docs/hassio_hass.md +++ b/docs/hassio_hass.md @@ -21,7 +21,7 @@ To develop for the frontend, we're going to need API access to the supervisor. First, make sure Home Assistant will load the Hass.io component by adding `hassio:` to your `configuration.yaml` file. Next, we will need to tell Hass.io component how to connect to the remote Hass.io instance, we do this by setting the `HASSIO` and `HASSIO_TOKEN` environment variables when starting Home Assistant. Note that the `HASSIO` value is not the same as the one that we saw above and the `HASSIO_TOKEN` is available inside log output of "Remote API Add-on" (This change every restart of this Add-on!). ```bash -HASSIO=127.0.0.1:10081 HASSIO_TOKEN= hass +HASSIO=:80 HASSIO_TOKEN= hass ``` Voila. Your local Home Assistant installation will now connect to a remote Hass.io instance.