diff --git a/source/_components/device_tracker.bluetooth_tracker.markdown b/source/_components/device_tracker.bluetooth_tracker.markdown index f8458551586..0a98675fbe9 100644 --- a/source/_components/device_tracker.bluetooth_tracker.markdown +++ b/source/_components/device_tracker.bluetooth_tracker.markdown @@ -13,7 +13,8 @@ ha_iot_class: "Local Poll" ha_release: 0.18 --- -This tracker discovers new devices on boot and tracks bluetooth devices periodically based on interval_seconds value. Devices discovered are stored with 'bt_' as the prefix for device mac in `known_devices.yaml`. +This tracker discovers new devices on boot and tracks bluetooth devices periodically based on interval_seconds value. It is not requiered to pair the devices with eachother! +Devices discovered are stored with 'bt_' as the prefix for device mac address in `known_devices.yaml`.

Requires PyBluez. If you are on raspbian, make sure you first install `bluetooth` and `libbluetooth-dev` by running `sudo apt install bluetooth libbluetooth-dev` diff --git a/source/_components/device_tracker.nmap_scanner.markdown b/source/_components/device_tracker.nmap_scanner.markdown index 8cc1d3816a5..06bd0210a45 100644 --- a/source/_components/device_tracker.nmap_scanner.markdown +++ b/source/_components/device_tracker.nmap_scanner.markdown @@ -9,7 +9,7 @@ sharing: true footer: true logo: nmap.png ha_category: Presence Detection -featured: true +featured: false --- diff --git a/source/_components/device_tracker.unifi.markdown b/source/_components/device_tracker.unifi.markdown index 6ddf9166065..1a0fd8524c8 100644 --- a/source/_components/device_tracker.unifi.markdown +++ b/source/_components/device_tracker.unifi.markdown @@ -25,6 +25,7 @@ device_tracker: port: PORT username: YOUR_ADMIN_USERNAME password: YOUR_ADMIN_PASSWORD + site_id: SITE_ID ``` Configuration variables: @@ -33,5 +34,6 @@ Configuration variables: - **port** (*Optional*): The port of your controller's web interface. Defaults to 8443. - **username** (*Required*: The username of an user with administrative privileges, usually *admin*. - **password** (*Required*): The password for your given admin account. +- **site_id** (*Optional*): Allows you to specify a site_id for device tracking. Defaults to "default". Found in the URL of the controller (i.e. https://CONTROLLER:PORT/manage/site/SITE_ID/dashboard) See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked. diff --git a/source/_components/discovery.markdown b/source/_components/discovery.markdown index 84698da53e0..763f6fe8276 100644 --- a/source/_components/discovery.markdown +++ b/source/_components/discovery.markdown @@ -20,7 +20,7 @@ Home Assistant can discover and automatically configure zeroconf/mDNS and uPnP d * Netgear routers * Plex Media Server -It will be able to add Google Chreomcasts and Belkin WeMo switches automatically, for Philips Hue it will require some configuration from the user. +It will be able to add Google Chromecasts and Belkin WeMo switches automatically, for Philips Hue it will require some configuration from the user. To load this component, add the following lines to your `configuration.yaml`: diff --git a/source/_components/hdmi_cec.markdown b/source/_components/hdmi_cec.markdown index 2c2603ca89d..905c67f85fa 100644 --- a/source/_components/hdmi_cec.markdown +++ b/source/_components/hdmi_cec.markdown @@ -25,9 +25,14 @@ The computer running Home Assistant must support CEC, and of course be connected [libcec](https://github.com/Pulse-Eight/libcec) must be installed for this component to work. Follow the installation instructions for your environment, provided at the link. `libcec` installs Python 3 bindings, by default as a system Python module. If you are running Home Assistant in a Python virtual environment, make sure it can access the system module, by either symlinking it or using the `--system-site-packages` flag. +#### {% linkable_title Symlinking into virtual environment %} + +`ln -s /usr/local/lib/python3.4/dist-packages/cec /lib/python3.4/site-packages` + ## {% linkable_title Configuration Example %} In the following example, a Pi Zero running Home Assistant is on a TV's HDMI port 1. HDMI port 2 is attached to a AV receiver. Three devices are attached to the AV receiver on HDMI ports 1 through 3. + ```yaml hdmi_cec: devices: diff --git a/source/_components/http.markdown b/source/_components/http.markdown index 973ac048044..98a88766f12 100644 --- a/source/_components/http.markdown +++ b/source/_components/http.markdown @@ -18,7 +18,6 @@ The `http` component serves all files and data required for the Home Assistant f http: api_password: YOUR_PASSWORD server_port: 12345 - development: 1 ssl_certificate: /etc/letsencrypt/live/hass.example.com/fullchain.pem ssl_key: /etc/letsencrypt/live/hass.example.com/privkey.pem cors_allowed_origins: @@ -29,6 +28,7 @@ http: Configuration variables: - **api_password** (*Optional*): Protect Home Assistant with a password. +- **server_host** (*Optional*): Only listen to incoming requests on specific ip/host (default: accept all) - **server_port** (*Optional*): Let you set a port to use. Defaults to 8123. - **development** (*Optional*): Disable caching and load unvulcanized assets. Useful for Frontend development. - **ssl_certificate** (*Optional*): Path to your TLS/SSL certificate to serve Home Assistant over a secure connection. diff --git a/source/_components/light.markdown b/source/_components/light.markdown index c54acd0ebb6..b2a244da8d2 100644 --- a/source/_components/light.markdown +++ b/source/_components/light.markdown @@ -33,7 +33,7 @@ Turns one light on or multiple lights on using [groups]({{site_root}}/components | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `entity_id` | no | String or list of strings that point at `entity_id`s of lights. Else targets all. -| `transition` | yes | Integer that represents the time the light should take to transition to the new state. *not supported by Wink +| `transition` | yes | Integer that represents the time the light should take to transition to the new state in seconds. *not supported by Wink | `profile` | yes | String with the name of one of the built-in profiles (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define a xy color and a brightness. If a profile is given and a brightness or xy color then the profile values will be overwritten. | `xy_color` | yes | A list containing two floats representing the xy color you want the light to be. Two comma seperated floats that represent the color in XY. | `rgb_color` | yes | A list containing three integers representing the xy color you want the light to be. Three comma seperated integers that represent the color in RGB @@ -41,6 +41,7 @@ Turns one light on or multiple lights on using [groups]({{site_root}}/components | `color_name` | yes | A human readable string of a color name, such as `blue` or `goldenrod` or [`chucknorris`](http://stackoverflow.com/questions/8318911/why-does-html-think-chucknorris-is-a-color). If your browser can display it, so can Home Assistant. | `brightness` | yes | Integer between 0 and 255 for how bright the color should be. | `flash` | yes | Tell light to flash, can be either value `short` or `long`. *not supported by Wink +| `effect`| yes | Applies an effect such as `colorloop` or `random`. ### {% linkable_title Service `light.turn_off` %} @@ -60,4 +61,4 @@ Toggles the state of one or multiple lights using [groups]({{site_root}}/compone | Service data attribute | Optional | Description | | ---------------------- | -------- | ----------- | | `entity_id` | no | String or list of strings that point at `entity_id`s of lights. Else targets all. -| `transition` | yes | Integer that represents the time the light should take to transition to the new state. +| `transition` | yes | Integer that represents the time the light should take to transition to the new state in seconds. diff --git a/source/_components/lirc.markdown b/source/_components/lirc.markdown index bacf8b3cb1f..3880f60ff48 100644 --- a/source/_components/lirc.markdown +++ b/source/_components/lirc.markdown @@ -23,9 +23,39 @@ Sending IR commands is not supported in this component (yet), but can be accompl To allow Home Assistant to talk to your IR receiver, you need to first make sure you have the correct dependencies installed: ```bash -$ sudo apt-get install lirc +$ sudo apt-get install lirc python3-lirc ``` +Check the version of `python3-lirc`: + +```bash +$ apt-cache show python3-lirc +Package: python3-lirc +Source: python-lirc +Version: 1.2.1-2 +``` + +If you do not have this version or you are running in a virtual environment, then your system will completely freeze with this component active. You will need to build `python3-lirc` from source. The version of this library in the Python package index is also broken, so the typical dependency system cannot fix this. Build it from source like this: + +As regular user: + +```bash +sudo apt-get install liblircclient-dev +``` + +As the user that runs hass: + +```bash +(hass) $ git clone https://github.com/tompreston/python-lirc.git +(hass) $ cd python-lirc +(hass) $ make py3 +(hass) $ python3 setup.py build +(hass) $ python3 setup.py install +``` + +If you are not using a virtual environment setup, then you'll need a `sudo` before the install line above. + +

If you are configuring on a Raspberry Pi, there are excellent instructions with GPIO schematics and driver configurations [here](http://alexba.in/blog/2013/01/06/setting-up-lirc-on-the-raspberrypi/). Consider following these.

@@ -60,10 +90,10 @@ end Test your LIRC installation before proceeding by running: ```bash -$ irexec -n home-assistant +$ ircat home-assistant ``` -and pressing some buttons on the remote. +and pressing some buttons on the remote. You should see them register on the screen if LIRC is properly configured. ### {% linkable_title Configuration Home Assistant %} @@ -73,10 +103,6 @@ and pressing some buttons on the remote. lirc: ``` -

-If you are on a Debian based system (like Raspberry Pi) and are having issues loading the component due to it being unable to install python-lirc, install it manually using `apt-get install python3-lirc`. -

- #### {% linkable_title Events %} The LIRC component fires `ir_command_received` events on the bus. You can capture the events and respond to them in automation scripts like this: diff --git a/source/_components/media_player.kodi.markdown b/source/_components/media_player.kodi.markdown index 851f3b520c4..fd7d5ccf387 100644 --- a/source/_components/media_player.kodi.markdown +++ b/source/_components/media_player.kodi.markdown @@ -37,4 +37,4 @@ Configuration variables: - **name** (*Optional*): The name of the device used in the frontend. - **username** (*Optional*): The XBMC/Kodi HTTP username. - **password** (*Optional*): The XBMC/Kodi HTTP password. -- **turn_off_action** (*Optional*): The desired turn off action. Options are `none`, `quit`, `hibernate`, `suspend`, `reboot`, or `poweroff`. Default `none`. +- **turn_off_action** (*Optional*): The desired turn off action. Options are `none`, `quit`, `hibernate`, `suspend`, `reboot`, or `shutdown`. Default `none`. diff --git a/source/_components/notify.instapush.markdown b/source/_components/notify.instapush.markdown index aeed476d1d6..4324d8da89c 100644 --- a/source/_components/notify.instapush.markdown +++ b/source/_components/notify.instapush.markdown @@ -17,6 +17,8 @@ The `instapush` platform uses [Instapush](https://instapush.im) to delivery noti The Instapush [Getting Started page](https://instapush.im/home/start/) will guide through the process of creating the required items. +To add Instapush to your installation, add the following to your `configuration.yaml` file: + ```yaml # Example configuration.yaml entry notify: @@ -33,10 +35,26 @@ Configuration variables: - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. - **api_key** (*Required*): Your API key for Instapush. - **app_secret** (*Required*): The secret for your created application. -- **event** (*Required*): TThe event +- **event** (*Required*): The event - **tracker** (*Required*): The name of tracker inside Instapush. -To retrieve those values for existing settings, log into your account at https://instapush.im and go to your **Dashboard**. Then click **APPS** tab, choose an app, and check the **Basic Info** section. The *Application ID* is the ``api_key`` and ``app_secret`` is the *Application Secret*. +To retrieve those values for existing settings, log into your account at [https://instapush.im](https://instapush.im) and go to your **Dashboard**. Then click **APPS** tab, choose an app, and check the **Basic Info** section. The *Application ID* is the ``api_key`` and ``app_secret`` is the *Application Secret*. + +Assuming that your setup looks look in the image below... + +

+ +

+ +...then your entry for the `configuration.yaml` file needs to be like this sample. + +```yaml +notify: + platform: instapush + [...] + event: msg + tracker: state +``` It's easy to test your Instapush setup outside of Home Assistant. Assuming you have an event *notification* and a tracker *home-assistant*, just fire a request and check the Instapush dashboard for a new entry. @@ -48,6 +66,7 @@ curl -X POST \ -d '{"event":"notification","trackers":{"home-assistant":"Switch 1"}}' \ https://api.instapush.im/v1/post ``` + For further details, please check the [API](https://instapush.im/developer/rest). To use notifications, please see the [getting started with automation page](/getting-started/automation/). diff --git a/source/_components/notify.markdown b/source/_components/notify.markdown index 74e0afed95a..096d57afd60 100644 --- a/source/_components/notify.markdown +++ b/source/_components/notify.markdown @@ -50,7 +50,7 @@ action: ### {% linkable_title Test if it works %} -A simple way to test if you have set up your notify platform correctly is to use **Call Service** from the **Developer Tools** to call your notify service. Choose your service (*notify/xyz*) from the list of **Available services:** and enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**. +A simple way to test if you have set up your notify platform correctly is to use service developer tool icon **Services** from the **Developer Tools**. Choose your service (*notify/xyz*) from the list of **Available services:** and enter something like the sample below into the **Service Data** field and hit **CALL SERVICE**. ```json { diff --git a/source/_components/persistent_notification.markdown b/source/_components/persistent_notification.markdown index 9746ef22002..b853432d46b 100644 --- a/source/_components/persistent_notification.markdown +++ b/source/_components/persistent_notification.markdown @@ -52,3 +52,5 @@ Choose /Browser/TorBrowser/Data/Tor/torrc-defaults` + +Once you have added the entry, restart the browser, and then browse to the "dot onion" site address to connect to your Home Assistant instance. + +For [Orbot: Tor on Android](https://guardianproject.info/apps/orbot), add it in **Orbot** -> **Menu** -> **Settings** to the "Torrc Custom Config" entry. Restart Orbot, and then use the [Orfox browser app](https://guardianproject.info/apps/orfox/), and browse to the "dot onion" site name to access your Home Assistant instance. You can also use Orbot's VPN mode, to enable Tor access from any application on your device, such as Tasker or Owntracks. + +On iOS, we have not fully tested this yet, but you should be able to add custom torrc entries on [Onion Browser](https://mike.tig.as/onionbrowser/), Red Onion or TOBY browsers, all available in the iTunes App Store. + +#### {% linkable_title Some More Advanced Ideas %} + +With this configuration, only you can access your Home Assistant instance Onion site through Tor, and no one else. You can share the authentication cookie with multiple devices and users, or you can generate a unique one for each - up to you! If you have multiple, say for an industrial, business or corporate configuration, this would provide an easy way to revoke access to a specific user or device. + +If you always access your Home Assistant instance via Tor, you can easily run this on an isolated "IoT" network segment at your install site, keeping your internal home network traffic seperate from any potentially compromised devices (like cheap "smart" lightbulbs with backdoors!). + +You could also use Tor as a means to connect your Home Assistant instance to a remote device, sensor or other service that you do not want to or connect provide a direct, open IP connection to. Again, Tor provides authenticated and confidential routing (aka "privacy and encryption") by default, without having to setup TLS/SSL or VPN. It is just important to secure IoT nodes within your network, as it is to secure remote access! + +As mentioned, with Orbot on Android, you can enable a "full device" VPN mode, that allows any app you have to tunnel through Tor, even if it is not Tor or proxy aware. This means you should be able to enter your "dot onion" Onion site address into any app you want to access to your Home Assistant instance, and it should work. + diff --git a/source/_includes/asides/developers_navigation.html b/source/_includes/asides/developers_navigation.html index aec578230d7..420d3bb2b48 100644 --- a/source/_includes/asides/developers_navigation.html +++ b/source/_includes/asides/developers_navigation.html @@ -9,7 +9,16 @@ + +
  • + {% active_link /developers/development/ Starting with Development %} +
  • @@ -26,6 +35,8 @@
  • {% active_link /developers/component_deps_and_reqs/ Requirements & Dependencies %}
  • {% active_link /developers/component_initialization/ Initialization %}
  • {% active_link /developers/component_events/ Handling events %}
    • +
  • {% active_link /developers/component_states/ States %}
    • +
  • {% active_link /developers/component_visibility/ Visibility %}
  • {% active_link /developers/component_generic_discovery/ Loading Platforms %}
  • {% active_link /developers/component_discovery/ Component Discovery %}
    • diff --git a/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-cherrypi.markdown b/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown similarity index 84% rename from source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-cherrypi.markdown rename to source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown index 22efbe70ac2..b28b26b7cd4 100644 --- a/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-cherrypi.markdown +++ b/source/_posts/2016-07-01-envisalink-homematic-hdmi-cec-and-sony-bravia-tv.markdown @@ -1,7 +1,7 @@ --- layout: post -title: "0.23: Envisalink, Homematic, HDMI-CEC and CherryPi" -description: "This new release of Home Assistant contains support for Envisalink, Homematic and HDMI-CEC. Additionaly was the Wink support improved and CherryPi is the new WSGI server." +title: "0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV" +description: "This new release of Home Assistant contains support for Envisalink, Homematic, Sony Bravia TV and HDMI-CEC. Additionaly was the Wink support improved and CherryPy is the new WSGI server." date: 2016-07-01 00:31:00 +0000 date_formatted: "July 1, 2016" author: Paulus Schoutsen @@ -18,7 +18,7 @@ This release brings support for two new ecosystems: [Envisalink] and [Homematic] On the config side, you can now [store your passwords][secrets] in your OS keyring or just in a standalone file. We also got a new service to reload the core config so no reboots needed anymore after changing customize settings! - + - Support for [Envisalink] added ([alarm control panel][envi-alarm], [binary sensor][envi-binary-sensor], [sensor][envi-sensor]) ([@cinntax]) - Support for [Homematic] added ([binary sensor][hm-binary-sensor], [light][hm-light], [rollershutter][hm-rollershutter], [sensor][hm-sensor], [switch][hm-switch]) ([@pvizeli], [@danielperna84]) @@ -44,10 +44,20 @@ On the config side, you can now [store your passwords][secrets] in your OS keyri - Lock: [Vera] now supported ([@rhooper]) - HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems ([@balloob]) -Breaking changes: +### {% linkable_title Breaking changes %} - Homematic thermostat configuration has changed and now depends on the new [Homematic] component. +### {% linkable_title Hotfix 0.23.1 - July 2 %} + +- Bump PyVera to 0.2.13 to fix traceback and pyvera thread dying related to bug ([@rhooper]) +- HTTP - SSL: Check for OP_NO_COMPRESSION support before trying to use it ([@AlucardZero]) +- Wink: Downgraded pubnub to work around pycryptodome conflicts ([@w1ll1am23]) + +### {% linkable_title FAQ %} + +- `elevation: ` was introduced to the configuration for weather/sunrise data. For existing [configurations][elevation] add the value shown in the warning `[homeassistant.config] Incomplete core config. Auto detected elevation: 665` to your `configuration.yaml` file. + [@AlucardZero]: https://github.com/AlucardZero/ [@aparraga]: https://github.com/aparraga/ [@Ardetus]: https://github.com/Ardetus/ @@ -94,3 +104,4 @@ Breaking changes: [reload core config service]: /getting-started/customizing-devices/#reloading-customize [Sony Bravia TV]: /components/media_player.braviatv/ [Raspberry Pi GPIO pins]: /components/garage_door.rpi_gpio/ +[elevation]: https://home-assistant.io/getting-started/basic/ diff --git a/source/_posts/2016-07-06-pocketchip-running-home-assistant.markdown b/source/_posts/2016-07-06-pocketchip-running-home-assistant.markdown new file mode 100644 index 00000000000..64ff15761ce --- /dev/null +++ b/source/_posts/2016-07-06-pocketchip-running-home-assistant.markdown @@ -0,0 +1,64 @@ +--- +layout: post +title: "PocketCHIP running Home Assistant" +description: "Taking Home Assistant for a spin on a PocketCHIP." +date: 2016-07-06 05:00:00 +0000 +date_formatted: "July 06, 2016" +author: Fabian Affolter +author_twitter: fabaff +comments: true +categories: How-To +og_image: /images/blog/2016-07-pocketchip/social.png +--- + + +Over a year ago I participated in the [kickstarter campaign](https://www.kickstarter.com/projects/1598272670/chip-the-worlds-first-9-computer/description) for "CHIP - The World's First Nine Dollar Computer" by [Next Thing Co.](https://www.nextthing.co/). I went for the PocketCHIP because of the idea. Display, built-in storage (thus no need for SD cards), battery-powered, and a keyboard are pretty nice features. Last week a package arrives... + + + +Thanks to [Next Thing Co.](https://www.nextthing.co/) and their CHIP which is actually 9 USD the space requirement for a single board computer has decreased. No Ethernet and HDMI output helped with that. But I guess that the next development cycle will allow us to put those boards in a matchbox including wired networking and a SATA interface. + +

    + + Size comparison of a Cubieboard, OrangePi One, and CHIP. +

    + +If you start using a PocketCHIP you will definitely look like a Blackberry or a GameBoy user. Typing is done with your thumbs :-) + +First a couple of tweaks like setting up `sudo`, upgrading the existing installation, change passwords, enabling ssh, and removal of the annoying stuff then installation of Home Assistant. There is not much to tell...it's straight-forward. For the sake of completeness below the notes about what I did. + +A Debian installation is available by default. This means that some dependencies for Home Assistant are missing. I haven't checked if a new build for the PocketCHIP would include them. So, after a `$ sudo apt-get update` installing those dependencies take a minute or two. + +```bash +$ sudo apt-get install python3-dev python3-pip python3-venv +``` + +As usual I run Python applications in a [venv](https://docs.python.org/3/library/venv.html). + +```bash +$ pvenv ha +``` + +Let's activate the created environment. + +```bash +$ cd ha +$ source bin/activate +``` + +If you haven't seen the next two commands already then you should visit our [frontsite](https://home-assistant.io/). + +```bash +$ pip3 install homeassistant +$ hass --open-ui +``` + +With `surf` the browsing experience on the low-resolution display is not that great. Most smartphones, even very cheap ones, have touchscreens with higher resolutions. Nevermind, [`midori`](https://twitter.com/fabaff/status/748852317047418880) is not better. + +

    + + PocketCHIP with Home Assistant frontend +

    + +Well, with PocketCHIP and Home Assistant you could run your home automation on a 49 USD device with a touchscreen, an integrated USP, and a keyboard. With the GPIO available on top of the display you could even connect your PocketCHIP directly to sensors and actuators. + diff --git a/source/_topics/secrets.markdown b/source/_topics/secrets.markdown index 20574301301..5b5096ea1bb 100644 --- a/source/_topics/secrets.markdown +++ b/source/_topics/secrets.markdown @@ -9,11 +9,11 @@ sharing: true footer: true --- -The `configuration.yaml` file a plain-text file thus it is readable for everyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. This separation can also help you to keep easier track of your passwords and API keys (as they are all stored at one place and no longer spread across the `configuration.yaml` file) if you don't want to [split up your configuration](topics/splitting_configuration/). +The `configuration.yaml` file a plain-text file thus it is readable for everyone who has access to the file. The file contains passwords and API tokens which need to be redacted if you want to share your configuration. This separation can also help you to keep easier track of your passwords and API keys (as they are all stored at one place and no longer spread across the `configuration.yaml` file) if you don't want to [split up your configuration](/topics/splitting_configuration/). ### {% linkable_title Using secrets.yaml %} -The workflow for the outsourcing in the `secrets.yaml` are very similar to the [splitting of the configuration](topics/splitting_configuration/). Create a `secrets.yaml` file in your Home assistant configuration directory (The location of the folder differs between operating systems: on OS X and Linux it's `~/.homeassistant` and on Windows it's `%APPDATA%/.homeassistant`). +The workflow for the outsourcing in the `secrets.yaml` are very similar to the [splitting of the configuration](/topics/splitting_configuration/). Create a `secrets.yaml` file in your Home assistant configuration directory (The location of the folder differs between operating systems: on OS X and Linux it's `~/.homeassistant` and on Windows it's `%APPDATA%/.homeassistant`). The entries for password and API keys in the `configuration.yaml` file usally looks like the example below. @@ -32,7 +32,7 @@ http: The `secrets.yaml` files stored the corresponding password assigned to the identifier. ```yaml -debug: 0 +logger: debug http_password: YOUR_PASSWORD ``` @@ -82,6 +82,6 @@ Please enter password for encrypted keyring: ```

    - With this configuration [autostart](/getting-started/autostart/) will no longer work. + If your are using the Python Keyring, [autostarting](/getting-started/autostart/) of Home Assistant will no longer work.

    diff --git a/source/demo/frontend.html b/source/demo/frontend.html index 25749213d31..15a27f939b9 100644 --- a/source/demo/frontend.html +++ b/source/demo/frontend.html @@ -8,7 +8,7 @@ if(i.length>1){for(var a=0;a--