From 1c8e1be57769a4ef846f2364ca29892a11910342 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Mon, 24 Jul 2017 07:39:24 -0700 Subject: [PATCH 01/81] Release 0.49.1 --- _config.yml | 6 +-- source/_posts/2017-07-16-release-49.markdown | 49 +++++++++++++++++++- 2 files changed, 50 insertions(+), 5 deletions(-) diff --git a/_config.yml b/_config.yml index 10e1ef759d7..7d840828153 100644 --- a/_config.yml +++ b/_config.yml @@ -143,11 +143,11 @@ social: # Home Assistant release details current_major_version: 0 current_minor_version: 49 -current_patch_version: 0 -date_released: 2017-07-16 +current_patch_version: 1 +date_released: 2017-07-24 # Either # or the anchor link to latest release notes in the blog post. # Must be prefixed with a # and have double quotes around it. # Major release: -patch_version_notes: "#" +patch_version_notes: "#release-0491---july-24" # Minor release (Example #release-0431---april-25): diff --git a/source/_posts/2017-07-16-release-49.markdown b/source/_posts/2017-07-16-release-49.markdown index 10ab8ca15e9..81aaab898ad 100644 --- a/source/_posts/2017-07-16-release-49.markdown +++ b/source/_posts/2017-07-16-release-49.markdown @@ -57,6 +57,25 @@ This feature has also been brought to you by [@Andrey-git]! Big shout out to him - Added media_extractor service ([@minchik] - [#8369]) ([media_extractor docs]) (new-platform) - Vizio SmartCast support ([@vkorn] - [#8260]) ([media_player.vizio docs]) (new-platform) +## {% linkable_title Release 0.49.1 - July 24 %} + +- Fix TP-Link device tracker regression since 0.49 ([@maikelwever] - [#8497]) ([device_tracker.tplink docs]) +- prometheus: Convert fahrenheit to celsius ([@rcloran] - [#8511]) ([prometheus docs]) +- Update dlib_face_detect.py ([@pvizeli] - [#8516]) ([image_processing.dlib_face_detect docs]) +- Realfix for dlib ([@pvizeli] - [#8517]) ([image_processing.dlib_face_detect docs]) +- Attach the `chat_id` for a callback query from a chat group (fixes #8461) ([@azogue] - [#8523]) ([telegram_bot docs]) +- Fix support for multiple Apple TVs ([@postlund] - [#8539]) +- LIFX: assume default features for unknown products ([@amelchio] - [#8553]) ([light.lifx docs]) +- Fix broken status update for lighting4 devices ([@ypollart] - [#8543]) ([rfxtrx docs]) ([binary_sensor.rfxtrx docs]) +- zha: Update to bellows 0.3.4 ([@rcloran] - [#8594]) ([zha docs]) +- Fix STATION_SCHEMA validation on longitude ([@clkao] - [#8610]) ([sensor.citybikes docs]) +- Bumped Amcrest version ([@tchellomello] - [#8624]) ([amcrest docs]) +- Check if /dev/input/by-id exists ([@schaal] - [#8601]) ([keyboard_remote docs]) +- Tado Fix #8606 ([@filcole] - [#8621]) ([climate.tado docs]) +- prometheus: Fix zwave battery level ([@rcloran] - [#8615]) ([prometheus docs]) +- ubus: Make multiple instances work again ([@glance-] - [#8571]) ([device_tracker.ubus docs]) +- Properly slugify switch.flux update service name ([@jawilson] - [#8545]) ([switch.flux docs]) + ## {% linkable_title If you need help... %} ...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks. @@ -395,7 +414,6 @@ amcrest: [light.zha docs]: https://home-assistant.io/components/light.zha/ [lutron docs]: https://home-assistant.io/components/lutron/ [media_extractor docs]: https://home-assistant.io/components/media_extractor/ -[media_extractor docs]: https://home-assistant.io/components/media_extractor/ [media_player.apple_tv docs]: https://home-assistant.io/components/media_player.apple_tv/ [media_player.denonavr docs]: https://home-assistant.io/components/media_player.denonavr/ [media_player.emby docs]: https://home-assistant.io/components/media_player.emby/ @@ -432,7 +450,6 @@ amcrest: [sensor.openweathermap docs]: https://home-assistant.io/components/sensor.openweathermap/ [sensor.otp docs]: https://home-assistant.io/components/sensor.otp/ [sensor.rflink docs]: https://home-assistant.io/components/sensor.rflink/ -[sensor.london_underground docs]: https://home-assistant.io/components/sensor.london_underground/ [sensor.uber docs]: https://home-assistant.io/components/sensor.uber/ [sensor.waqi docs]: https://home-assistant.io/components/sensor.waqi/ [sensor.yweather docs]: https://home-assistant.io/components/sensor.yweather/ @@ -460,3 +477,31 @@ amcrest: [forum]: https://community.home-assistant.io/ [issue]: https://github.com/home-assistant/home-assistant/issues [discord]: https://discord.gg/c5DvZ4e +[#8497]: https://github.com/home-assistant/home-assistant/pull/8497 +[#8511]: https://github.com/home-assistant/home-assistant/pull/8511 +[#8516]: https://github.com/home-assistant/home-assistant/pull/8516 +[#8517]: https://github.com/home-assistant/home-assistant/pull/8517 +[#8523]: https://github.com/home-assistant/home-assistant/pull/8523 +[#8539]: https://github.com/home-assistant/home-assistant/pull/8539 +[#8543]: https://github.com/home-assistant/home-assistant/pull/8543 +[#8553]: https://github.com/home-assistant/home-assistant/pull/8553 +[#8594]: https://github.com/home-assistant/home-assistant/pull/8594 +[#8610]: https://github.com/home-assistant/home-assistant/pull/8610 +[@clkao]: https://github.com/clkao +[@maikelwever]: https://github.com/maikelwever +[@ypollart]: https://github.com/ypollart +[binary_sensor.rfxtrx docs]: https://home-assistant.io/components/binary_sensor.rfxtrx/ +[telegram_bot docs]: https://home-assistant.io/components/telegram_bot/ +[#8545]: https://github.com/home-assistant/home-assistant/pull/8545 +[#8571]: https://github.com/home-assistant/home-assistant/pull/8571 +[#8601]: https://github.com/home-assistant/home-assistant/pull/8601 +[#8615]: https://github.com/home-assistant/home-assistant/pull/8615 +[#8621]: https://github.com/home-assistant/home-assistant/pull/8621 +[#8624]: https://github.com/home-assistant/home-assistant/pull/8624 +[@filcole]: https://github.com/filcole +[@glance-]: https://github.com/glance- +[@jawilson]: https://github.com/jawilson +[@schaal]: https://github.com/schaal +[device_tracker.ubus docs]: https://home-assistant.io/components/device_tracker.ubus/ +[keyboard_remote docs]: https://home-assistant.io/components/keyboard_remote/ +[switch.flux docs]: https://home-assistant.io/components/switch.flux/ From 8123a4f9dc21744a55525661b6e0566ba7754054 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Tue, 25 Jul 2017 00:24:50 +0200 Subject: [PATCH 02/81] Update addon_config.markdown --- source/developers/hassio/addon_config.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/developers/hassio/addon_config.markdown b/source/developers/hassio/addon_config.markdown index 426d3808ec2..c77fb780df1 100644 --- a/source/developers/hassio/addon_config.markdown +++ b/source/developers/hassio/addon_config.markdown @@ -102,7 +102,7 @@ The config for an add-on is stored in `config.json`. | ports | no | Network ports to expose from the container. Format is `"container-port/type": host-port`. | host_network | no | If that is True, the add-on run on host network. | devices | no | Device list to map into add-on. Format is: `::`. i.e. `/dev/ttyAMA0:/dev/ttyAMA0:rwm` -| privileged | no | Privilege for access to hardware/system. Available access: `NET_ADMIN` +| privileged | no | Privilege for access to hardware/system. Available access: `NET_ADMIN`, `SYS_ADMIN` | map | no | List of maps for additional hass.io folders. Possible values: `config`, `ssl`, `addons`, `backup`, `share`. Default it map it `ro`, you can change that if you add a ":rw" at the end of name. | environment | no | A dict of environment variable to run add-on. | options | yes | Default options value of the add-on From 3e8022f44c22eb4dbf2f0799af7ee1c22e0ebb6a Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Tue, 25 Jul 2017 08:15:53 +0200 Subject: [PATCH 03/81] Add details about default (fixes https://github.com/home-assistant/home-assistant/issues/8605) --- source/_components/binary_sensor.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/binary_sensor.markdown b/source/_components/binary_sensor.markdown index a2cc7ee8518..43b66dd453e 100644 --- a/source/_components/binary_sensor.markdown +++ b/source/_components/binary_sensor.markdown @@ -15,7 +15,7 @@ Knowing that there are only two states allows Home Assistant to represent these The way these sensors are displayed in the frontend can be modified in the [customize section](/getting-started/customizing-devices/). The following device classes are supported for binary sensors: -- **None**: Generic on/off +- **None**: Generic on/off. This is the default and doesn't need to be set. - **cold**: `On` means cold - **connectivity**: `On` means connection present, `Off` means no connection - **gas**: `On` means gas detected From b6d3bf2c300b85983174a5a87dd0880f37d01ab7 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Sun, 23 Jul 2017 14:55:12 -0700 Subject: [PATCH 04/81] Add blog post for hass.io --- sass/custom/_paulus.scss | 16 +++- .../2017-07-24-introducing-hassio.markdown | 93 +++++++++++++++++++ source/getting-started/index.markdown | 7 ++ source/index.html | 8 +- 4 files changed, 117 insertions(+), 7 deletions(-) create mode 100644 source/_posts/2017-07-24-introducing-hassio.markdown diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss index d428797a7f3..4d68fea3e37 100644 --- a/sass/custom/_paulus.scss +++ b/sass/custom/_paulus.scss @@ -118,16 +118,21 @@ $primary-color: #049cdb; } } - .founder-vision { + .highlight-blog-post { + font-size: 2.0rem; + line-height: 1.15; + padding: 15px; display: block; text-decoration: none; color: white; - padding: 15px; - font-size: 2.25rem; - line-height: 1.33333; transition: background-color .5s; background-color: #038FC7; + &.large { + font-size: 2.25rem; + line-height: 1.33333; + } + &:hover { background-color: lighten(#038FC7, 10%); } @@ -406,7 +411,8 @@ p.note { } .edit-github { - text-align: right; + float: right; + margin-left: 8px; margin-bottom: 8px; font-size: .8em; } diff --git a/source/_posts/2017-07-24-introducing-hassio.markdown b/source/_posts/2017-07-24-introducing-hassio.markdown new file mode 100644 index 00000000000..205e0c1192d --- /dev/null +++ b/source/_posts/2017-07-24-introducing-hassio.markdown @@ -0,0 +1,93 @@ +--- +layout: post +title: "Introducing Hass.io" +description: "The ultimate home automation hub has arrived." +date: 2017-07-24 00:02:05 +0000 +date_formatted: "July 24, 2017" +author: Paulus Schoutsen +author_twitter: balloob +comments: true +categories: Announcements +og_image: /images/hassio/screenshots/dashboard.png +--- + +**TL;DR:** Today we're introducing [Hass.io]. Hass.io is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration and can easily be extended using [Hass.io add-ons][addons]. + +---- + +Home Assistant is 2 months away from being 4 years old. In that time the Internet of Things has really taken off and we've seen many new devices and services. We saw the introduction of voice assistants like Google Home and new standards like Apple HomeKit. + +Some things have been supported natively in Home Assistant, others have been integrated into Home Assistant via third party applications. The latter has caused an increased maintenance burden for people running Home Assistant at home. + +So we decided to take a step back from day-to-day Home Assistant development and see if we could offer a solution that makes updating a breeze for our users. A solution that you can flash to your Raspberry Pi and no longer worry about. A solution that would still be local first and respect the user's privacy. + +And this is how [Pascal Vizeli] came up with Hass.io, an operating system based on [ResinOS] and [Docker]. Hass.io will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows taking/restoring snapshots of your configuration and can easily be extended using [Hass.io add-ons][addons]. + +

+ +Hass.io dashboard +

+ +To install add-ons, a user can browse the built-in add-on store and install, configure and update any available application. Want to turn your device into a Google Assistant or make your configuration accessible via Samba/Windows networking? Both are a couple of clicks away! ([Video demo - 38s, no audio][install-demo]) + +At launch we have included a couple of [built-in add-ons][addons] like [Google Assistant], [Let's Encrypt] and [Duck DNS]. Besides our internal add-ons, it is also possible to create and share your own add-on repositories. During our beta period we've already seen some great add-ons being shared: [Homebridge][olivierg], [InfluxDB][bestlibre], [HASS Configurator][danielperna] and [AppDaemon][vkorn]. + +As we strongly believe in the openness of technology, we are releasing Hass.io as [open source] under the Apache 2.0 license. That way any user can make sure that the code that runs in their homes is secure and safe. + +- [Learn more about Hass.io][Hass.io] +- [Install Hass.io][install] +- [Available add-ons][addons] + +Hass.io has been built by [Pascal Vizeli], the UI has been made by [Paulus Schoutsen] and [BRUHAutomation] made the introduction video. Big thanks to [Resin.io] for building ResinOS and helping us get started with it. Also a big thanks to the community for early feedback, helping out with the documentation and add-on development ❤️ + +_Some frequently asked questions are answered in the read more section._ + + + +#### {% linkable_title Do I need to use Hass.io to run Home Assistant? %} + +Hass.io is optional. You can still run Home Assistant standalone. + +#### {% linkable_title Which devices are supported at launch? %} + +Initially we support the Raspberry Pi 1, 2, 3 and Intel NUC. Advanced users can also [install Hass.io on a Linux server][advanced-install]. + +#### {% linkable_title Can I install packages or scripts on the machine? %} + +No, this is not possible as we're using stateless Docker containers. To install a package you'll have to write a local add-on that interacts with Home Assistant. See [our tutorial][run-local]. + +#### {% linkable_title Can I restore a snapshot on a different device? %} + +Yes, any Hass.io snapshot can be restored on any device. + +#### {% linkable_title The Hass.io configuration panel contains powerful tools. Why is there no security? %} + +We have already implemented the backend and plan to release the UI soon. + +#### {% linkable_title Is there a roadmap? %} + +We use [Pivotal Tracker] to track things that are in progress and what we might work on. + +[Hass.io]: /hassio +[install]: /hassio/installation +[Homebridge]: https://github.com/nfarina/homebridge +[hb-hass]: https://github.com/home-assistant/homebridge-homeassistant +[Pascal Vizeli]: https://github.com/pvizeli/ +[Paulus Schoutsen]: https://github.com/balloob/ +[ResinOS]: https://resinos.io/ +[Docker]: https://www.docker.com/ +[addons]: /addons/ +[bestlibre]: https://community.home-assistant.io/t/repository-bestlibre-addons-repository/18037 +[danielperna]: https://community.home-assistant.io/t/repository-hass-configurator/17838 +[olivierg]: https://community.home-assistant.io/t/repository-homebridge-add-on/18569 +[vkorn]: https://community.home-assistant.io/t/repository-few-addons/20659 +[install-demo]: https://youtu.be/NfyavpAg4as +[BRUHAutomation]: https://www.youtube.com/channel/UCLecVrux63S6aYiErxdiy4w +[open source]: https://github.com/home-assistant/hassio +[Google Assistant]: /addons/google_assistant/ +[Let's Encrypt]: /addons/lets_encrypt/ +[Duck DNS]: /addons/duckdns/ +[advanced-install]: /hassio/installation/#alternative-install-on-generic-linux-server +[Pivotal Tracker]: https://www.pivotaltracker.com/n/projects/2020851 +[run-local]: /hassio/run_local/ +[Resin.io]: https://resin.io diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index 35f02859150..921afe5b850 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -12,6 +12,12 @@ footer: true You will need to install Home Assistant before we can get started. You can install Home Assistant on your computer or you can turn a Raspberry Pi into a dedicated Home Assistant hub.
+ +
+ +
+
Install Hass.io on your Raspberry Pi 3
+
@@ -25,6 +31,7 @@ You will need to install Home Assistant before we can get started. You can insta
Install Home Assistant on your computer
+
For alternative installation methods please take a look at the [installation documentation](/docs/installation/). diff --git a/source/index.html b/source/index.html index 6cc53fb9748..ef9b2241c3d 100644 --- a/source/index.html +++ b/source/index.html @@ -34,6 +34,10 @@ hide_github_edit: true Chat
+ + + Read our founder's vision for the perfect home automation +
@@ -47,8 +51,8 @@ hide_github_edit: true {% endfor %}
- - Read our founder's vision for the perfect home automation + + Learn how Hass.io can turn your Raspberry Pi into the ultimate home automation hub From a183260cbb8b7709f4b1babafc2f3e7b21a0e68a Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Tue, 25 Jul 2017 00:54:58 -0700 Subject: [PATCH 05/81] Rename post to 25th --- ...io.markdown => 2017-07-25-introducing-hassio.markdown} | 8 ++++++-- source/hassio/index.markdown | 4 ++++ source/index.html | 2 +- 3 files changed, 11 insertions(+), 3 deletions(-) rename source/_posts/{2017-07-24-introducing-hassio.markdown => 2017-07-25-introducing-hassio.markdown} (96%) diff --git a/source/_posts/2017-07-24-introducing-hassio.markdown b/source/_posts/2017-07-25-introducing-hassio.markdown similarity index 96% rename from source/_posts/2017-07-24-introducing-hassio.markdown rename to source/_posts/2017-07-25-introducing-hassio.markdown index 205e0c1192d..bc2db41f2ca 100644 --- a/source/_posts/2017-07-24-introducing-hassio.markdown +++ b/source/_posts/2017-07-25-introducing-hassio.markdown @@ -2,8 +2,8 @@ layout: post title: "Introducing Hass.io" description: "The ultimate home automation hub has arrived." -date: 2017-07-24 00:02:05 +0000 -date_formatted: "July 24, 2017" +date: 2017-07-25 00:02:05 +0000 +date_formatted: "July 25, 2017" author: Paulus Schoutsen author_twitter: balloob comments: true @@ -38,6 +38,10 @@ As we strongly believe in the openness of technology, we are releasing Hass.io a - [Install Hass.io][install] - [Available add-ons][addons] +
+ +
+ Hass.io has been built by [Pascal Vizeli], the UI has been made by [Paulus Schoutsen] and [BRUHAutomation] made the introduction video. Big thanks to [Resin.io] for building ResinOS and helping us get started with it. Also a big thanks to the community for early feedback, helping out with the documentation and add-on development ❤️ _Some frequently asked questions are answered in the read more section._ diff --git a/source/hassio/index.markdown b/source/hassio/index.markdown index 7fc9ceb660e..f39127e997c 100644 --- a/source/hassio/index.markdown +++ b/source/hassio/index.markdown @@ -24,6 +24,10 @@ The advantages of using Hass.io: - Easily install many popular add-ons including [Google Assistant], encryption via [Let's Encrypt] and dynamic DNS via [Duck DNS].

[Browse available add-ons »][all]

- Active community that is helpful and sharing add-ons including AppDaemon, Homebridge and InfluxDB.

[Browse the forums »][forums]
[Join the Hass.io chat »][chat]
[Browse community add-on repositories »][comm-add-ons]

+
+ +
+

Hass.io dashboard diff --git a/source/index.html b/source/index.html index ef9b2241c3d..c91666fa76e 100644 --- a/source/index.html +++ b/source/index.html @@ -51,7 +51,7 @@ hide_github_edit: true {% endfor %}

- + Learn how Hass.io can turn your Raspberry Pi into the ultimate home automation hub From e9b2dc34a6afe9139160900bfc13adecf9763a23 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Tue, 25 Jul 2017 15:21:48 +0200 Subject: [PATCH 06/81] Update title --- source/hassio/index.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/hassio/index.markdown b/source/hassio/index.markdown index 7fc9ceb660e..b3059cb0f2b 100644 --- a/source/hassio/index.markdown +++ b/source/hassio/index.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Hass.io" -description: "Manage your Home Assistant and custom addons over Samba." +description: "Manage your Home Assistant and custom addons." date: 2017-04-30 13:28 sidebar: true comments: false From d541c0a2b0876359188188962eecc9e428593d75 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Tue, 25 Jul 2017 08:46:15 -0700 Subject: [PATCH 07/81] Final tweaks --- .../2017-07-25-introducing-hassio.markdown | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/source/_posts/2017-07-25-introducing-hassio.markdown b/source/_posts/2017-07-25-introducing-hassio.markdown index bc2db41f2ca..3a181997f61 100644 --- a/source/_posts/2017-07-25-introducing-hassio.markdown +++ b/source/_posts/2017-07-25-introducing-hassio.markdown @@ -11,13 +11,13 @@ categories: Announcements og_image: /images/hassio/screenshots/dashboard.png --- -**TL;DR:** Today we're introducing [Hass.io]. Hass.io is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration and can easily be extended using [Hass.io add-ons][addons]. +**TL;DR:** Today we're introducing [Hass.io]. Hass.io is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration and can easily be extended using [Hass.io add-ons][addons] including [Google Assistant] and [Let's Encrypt]. ---- Home Assistant is 2 months away from being 4 years old. In that time the Internet of Things has really taken off and we've seen many new devices and services. We saw the introduction of voice assistants like Google Home and new standards like Apple HomeKit. -Some things have been supported natively in Home Assistant, others have been integrated into Home Assistant via third party applications. The latter has caused an increased maintenance burden for people running Home Assistant at home. +Some things have been supported natively in Home Assistant, others have been integrated into Home Assistant via third party applications. All these moving parts caused our users to spend a lot of time maintaining their systems and applications instead of automating their homes. So we decided to take a step back from day-to-day Home Assistant development and see if we could offer a solution that makes updating a breeze for our users. A solution that you can flash to your Raspberry Pi and no longer worry about. A solution that would still be local first and respect the user's privacy. @@ -38,19 +38,19 @@ As we strongly believe in the openness of technology, we are releasing Hass.io a - [Install Hass.io][install] - [Available add-ons][addons] +_Some frequently asked questions are answered below in the read more section._ +
Hass.io has been built by [Pascal Vizeli], the UI has been made by [Paulus Schoutsen] and [BRUHAutomation] made the introduction video. Big thanks to [Resin.io] for building ResinOS and helping us get started with it. Also a big thanks to the community for early feedback, helping out with the documentation and add-on development ❤️ -_Some frequently asked questions are answered in the read more section._ - -#### {% linkable_title Do I need to use Hass.io to run Home Assistant? %} +#### {% linkable_title Will Hass.io be the only way to run Home Assistant? %} -Hass.io is optional. You can still run Home Assistant standalone. +Hass.io is and will always be optional. You can still run Home Assistant wherever you can run Python. #### {% linkable_title Which devices are supported at launch? %} @@ -64,9 +64,9 @@ No, this is not possible as we're using stateless Docker containers. To install Yes, any Hass.io snapshot can be restored on any device. -#### {% linkable_title The Hass.io configuration panel contains powerful tools. Why is there no security? %} +#### {% linkable_title The Hass.io configuration panel contains powerful tools. Why is there no extra security besides the Home Assistant login? %} -We have already implemented the backend and plan to release the UI soon. +This is in the works. We have already implemented [the backend](https://github.com/home-assistant/hassio/pull/41) and plan to release the UI soon. #### {% linkable_title Is there a roadmap? %} From 1c86dbbb9e49412ecf93baafc56cc73908512499 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Tue, 25 Jul 2017 22:39:20 -0700 Subject: [PATCH 08/81] Fix press images --- sass/custom/_paulus.scss | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sass/custom/_paulus.scss b/sass/custom/_paulus.scss index 4d68fea3e37..56d86c93af2 100644 --- a/sass/custom/_paulus.scss +++ b/sass/custom/_paulus.scss @@ -189,6 +189,8 @@ $primary-color: #049cdb; border: 0; box-shadow: none; margin: 15px; + width: 200px; + max-width: 40%; } } } From f88e0336b7803caf9707b576a4368d91acafce14 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Tue, 25 Jul 2017 23:21:45 -0700 Subject: [PATCH 09/81] Add some og image to dev docs --- source/developers/architecture.markdown | 1 + source/developers/architecture_components.markdown | 1 + source/developers/index.markdown | 1 + 3 files changed, 3 insertions(+) diff --git a/source/developers/architecture.markdown b/source/developers/architecture.markdown index 2e967a087c5..422777573b4 100644 --- a/source/developers/architecture.markdown +++ b/source/developers/architecture.markdown @@ -7,6 +7,7 @@ sidebar: true comments: false sharing: true footer: true +og_image: /images/architecture/ha_architecture.png --- Before we dive into the Home Assistant architecture, let's get a clear overview of the home automation landscape as a whole. This way, we can show how the different parts of Home Assistant fit into the picture. diff --git a/source/developers/architecture_components.markdown b/source/developers/architecture_components.markdown index eff2ff1f2e6..095a4f73781 100644 --- a/source/developers/architecture_components.markdown +++ b/source/developers/architecture_components.markdown @@ -7,6 +7,7 @@ sidebar: true comments: false sharing: true footer: true +og_image: /images/architecture/component_interaction.png --- Home Assistant can be extended with **components**. Each component is responsible for a specific domain within Home Assistant. Components can listen for or trigger events, offer services, and maintain states. Components are written in Python and can do all the goodness that Python has to offer. Out of the box, Home Assistant offers a bunch of [built-in components]({{site_root}}/components/). diff --git a/source/developers/index.markdown b/source/developers/index.markdown index f1fb27273db..c801866e6aa 100644 --- a/source/developers/index.markdown +++ b/source/developers/index.markdown @@ -7,6 +7,7 @@ sidebar: true comments: false sharing: true footer: true +og_image: /images/architecture/component_interaction.png --- Welcome to the Home Assistant development documentation. This is the place to learn all about how Home Assistant works and how you can extend it with support for your devices and services! From e158ea881a48407118246a8589cbfa98715953e4 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Wed, 26 Jul 2017 16:37:53 +0200 Subject: [PATCH 10/81] Update zwave.markdown --- source/hassio/zwave.markdown | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/source/hassio/zwave.markdown b/source/hassio/zwave.markdown index 1bb70e851ba..e67bde5858f 100644 --- a/source/hassio/zwave.markdown +++ b/source/hassio/zwave.markdown @@ -20,3 +20,12 @@ If you need GPIO on raspberry-pi3 for you Z-Wave module add follow line into `co ``` dtoverlay=pi3-miniuart-bt ``` + +HUSBZB-1: +``` +zwave: + usb_path: /dev/ttyUSB0 + +zha: + usb_path: /dev/ttyUSB1 +``` From 115b2172e146eeb2e5fb0aec9932f9f22c48c3c9 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Wed, 26 Jul 2017 16:38:09 +0200 Subject: [PATCH 11/81] Update zwave.markdown --- source/hassio/zwave.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/hassio/zwave.markdown b/source/hassio/zwave.markdown index e67bde5858f..3a14c3e8196 100644 --- a/source/hassio/zwave.markdown +++ b/source/hassio/zwave.markdown @@ -22,7 +22,7 @@ dtoverlay=pi3-miniuart-bt ``` HUSBZB-1: -``` +```yaml zwave: usb_path: /dev/ttyUSB0 From 1d5a72f7bac40981ac435c5a5e41d05c84b446fe Mon Sep 17 00:00:00 2001 From: Corban Mailloux Date: Wed, 26 Jul 2017 12:18:53 -0400 Subject: [PATCH 12/81] Grammar and typo corrections. (#3058) --- source/_components/media_extractor.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_components/media_extractor.markdown b/source/_components/media_extractor.markdown index 888568ac343..f5a7de8c88e 100644 --- a/source/_components/media_extractor.markdown +++ b/source/_components/media_extractor.markdown @@ -13,7 +13,7 @@ ha_release: 0.49 --- -The `media_extractor` component gets an stream URL and send it to a media player entity. +The `media_extractor` component gets a stream URL and sends it to a media player entity. To use the media extractor service in your installation, add the following to your `configuration.yaml` file: @@ -24,7 +24,7 @@ media_extractor: ### {% linkable_title Use the service %} -Go the the "Developer Tools", then to "Call Service", and choose `media_extractor/play_media` from the list of available services. Fill the "Service Data" field as shown in the example below and hit "CALL SERVICE". +Go to the "Developer Tools," then to "Call Service," and choose `media_extractor/play_media` from the list of available services. Fill the "Service Data" field as shown in the example below and hit "CALL SERVICE." This will download the file from the given URL. From 820b4c58faeecee39ae9a74c1386988c73690f80 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dawid=20Wr=C3=B3bel?= Date: Wed, 26 Jul 2017 12:20:28 -0400 Subject: [PATCH 13/81] Patch 1 (#3057) Update Onkyo and Pioneer media players documentation --- source/_components/media_player.onkyo.markdown | 6 +++--- source/_components/media_player.pioneer.markdown | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/source/_components/media_player.onkyo.markdown b/source/_components/media_player.onkyo.markdown index f0fb1580963..e78075c01a5 100644 --- a/source/_components/media_player.onkyo.markdown +++ b/source/_components/media_player.onkyo.markdown @@ -1,7 +1,7 @@ --- layout: page title: "Onkyo" -description: "Instructions how to integrate Onkyo receivers into Home Assistant." +description: "Instructions how to integrate Onkyo and some Pioneer receivers into Home Assistant." date: 2016-03-30 08:00 sidebar: true comments: false @@ -14,9 +14,9 @@ ha_iot_class: "Local Polling" --- -The `onkyo` platform allows you to control a [Onkyo receiver](http://www.onkyo.com/) from Home Assistant. Please be aware that you need to enable "Network Standby" for this component to work in your Hardware. +The `onkyo` platform allows you to control a [Onkyo](http://www.onkyo.com/) and some recent [Pioneer](http://www.pioneerelectronics.com) receivers from Home Assistant. Please be aware that you need to enable "Network Standby" for this component to work in your Hardware. -To add an Onkyo receiver to your installation, add the following to your `configuration.yaml` file: +To add an Onkyo or Pioneer receiver to your installation, add the following to your `configuration.yaml` file: ```yaml # Example configuration.yaml entry diff --git a/source/_components/media_player.pioneer.markdown b/source/_components/media_player.pioneer.markdown index 720241193d9..66086c5ded3 100644 --- a/source/_components/media_player.pioneer.markdown +++ b/source/_components/media_player.pioneer.markdown @@ -14,7 +14,7 @@ ha_release: 0.19 ha_iot_class: "Local Polling" --- -The `pioneer` platform allows you to control Pioneer Network Receivers. +The `pioneer` platform allows you to control Pioneer Network Receivers. Please note, however, that the more recent Pioneer models work with [Onkyo](/components/media_player.onkyo/) platform instead. To add a Pioneer receiver to your installation, add the following to your `configuration.yaml` file: From 4e9202fa70895e9b659e27c19bf916673d2d6564 Mon Sep 17 00:00:00 2001 From: mjj4791 Date: Wed, 26 Jul 2017 18:23:59 +0200 Subject: [PATCH 14/81] Add weather-station map and usage statement (#3053) Add link to weather-station map (google maps) and added usage statement --- source/_components/sensor.buienradar.markdown | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/source/_components/sensor.buienradar.markdown b/source/_components/sensor.buienradar.markdown index b7a4b8714a9..b42e120eddf 100644 --- a/source/_components/sensor.buienradar.markdown +++ b/source/_components/sensor.buienradar.markdown @@ -14,8 +14,9 @@ ha_iot_class: "Cloud Polling" --- -The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as an source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a webservice that provides detailed weather information for users in The Netherlands. -The relevant weatherstation used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). The selected weatherstation will provide all weather data, with the exception of the forecasted precipitaion. The forecasted precipitation data will be retrieved from buienradar using your actual gps-location (and not the location of the nearest weatherstation). +The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as an source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a webservice that provides detailed weather information for users in The Netherlands. The relevant weatherstation used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). A map of all available weatherstations can be found [here](https://www.google.com/maps/d/embed?mid=1NivHkTGQUOs0dwQTnTMZi8Uatj0). + +The selected weatherstation will provide all weather data, with the exception of the forecasted precipitation. The forecasted precipitation data will be retrieved from buienradar using your actual gps-location (and not the location of the nearest weatherstation). To integrate `buienradar` with Home Assistant, add the following section to your `configuration.yaml` file: @@ -42,7 +43,7 @@ Configuration variables: - `sensor.br_ground_temperature`, since no name has been set for the sensor and the default display name for monitored condition `groundtemperature` is `Ground Temperature` - **latitude** (*Optional*): Latitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.nl. - **longitude** (*Optional*): Longitude to use for selection of data source location. Longitude and latitude will be taken from Home Assistant configuration, but can be overridden/changed in this component to select a different location for buienradar.nl. -- **timeframe** (*Optional*): Minutes to look ahead for precipitation (5..120) [default: 60]. +- **timeframe** (*Optional*): Minutes to look ahead for precipitation forecast (5..120) [default: 60]. - **monitored_conditions** array (*Required*): One or more conditions to display in the frontend. - **stationname**: The name of the selected meteo-station. - **symbol**: A symbol for the current weather. @@ -66,6 +67,8 @@ Full configuration example where location is manually specified: ```yaml # Example configuration.yaml entry - platform: buienradar + name: 'volkel' + # Force 'Meetstation Volkel' to be used: latitude: 51.65 longitude: 5.70 monitored_conditions: @@ -86,4 +89,6 @@ Full configuration example where location is manually specified: - precipitation_forecast_average - precipitation_forecast_total ``` - + +[Usage statement:](https://www.buienradar.nl/overbuienradar/gratis-weerdata) +> Buienradar makes free weatherdata available for use by individuals and businesses (website/intranet). The use of the weatherdata is allowed for **non-commercial purposes**. Please refer to the full usage statement linked above to confirm your usage or to request permission. From ed2942b4d80166f984ce59c5e367452ad65598e5 Mon Sep 17 00:00:00 2001 From: JudgeDredd Date: Wed, 26 Jul 2017 12:24:49 -0400 Subject: [PATCH 15/81] add unit_of_measurement customization to documentation (#3050) add unit_of_measurement customization to documentation --- source/_docs/configuration/customizing-devices.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_docs/configuration/customizing-devices.markdown b/source/_docs/configuration/customizing-devices.markdown index 8da78ab7a68..23411246de3 100644 --- a/source/_docs/configuration/customizing-devices.markdown +++ b/source/_docs/configuration/customizing-devices.markdown @@ -67,6 +67,7 @@ homeassistant: | `assumed_state` | For switches with an assumed state two buttons are shown (turn off, turn on) instead of a switch. By setting `assumed_state` to `false` you will get the default switch icon. | `device_class` | Sets the class of the device, changing the device state and icon that is displayed on the UI (see below). | `initial_state` | Sets the initial state for automations. `on` or `off`. +| `unit_of_measurement` | Defines the units of measurement, if any. ### {% linkable_title Device Class %} From 3c2262dd9759b9cee2920372f72e71c1ebaad553 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Wed, 26 Jul 2017 09:24:50 -0700 Subject: [PATCH 16/81] Add video to SSH addon --- source/_addons/ssh.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_addons/ssh.markdown b/source/_addons/ssh.markdown index 44cdbe6c8f4..068afe4e63c 100644 --- a/source/_addons/ssh.markdown +++ b/source/_addons/ssh.markdown @@ -31,6 +31,10 @@ Configuration variables: - **authorized_keys** (*Required*): Your public-keys for authorized keyfile. Every element will be a line inside that file. +
+ +
+ [win]: https://www.digitalocean.com/community/tutorials/how-to-create-ssh-keys-with-putty-to-connect-to-a-vps [other]: https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/ From 211ce813a00937e1343dcca10c2bfa41e8fcf883 Mon Sep 17 00:00:00 2001 From: mjj4791 Date: Wed, 26 Jul 2017 18:33:07 +0200 Subject: [PATCH 17/81] Add weather-station map and usage statement (#3052) Add link to weather-station map (google maps) and added usage statement --- source/_components/weather.buienradar.markdown | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/source/_components/weather.buienradar.markdown b/source/_components/weather.buienradar.markdown index 07da95af18c..682e85c2827 100644 --- a/source/_components/weather.buienradar.markdown +++ b/source/_components/weather.buienradar.markdown @@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling" --- The `buienradar` platform uses [buienradar.nl](http://buienradar.nl/) as an source for current meteorological data for your location. The weather forecast is delivered by Buienradar, who provides a webservice that provides detailed weather information for users in The Netherlands. -The relevant weatherstation used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). +The relevant weatherstation used will be automatically selected based on the location specified in the Home Assistant configuration (or in the buienradar weather/sensor component). A map of all available weatherstations can be found [here](https://www.google.com/maps/d/embed?mid=1NivHkTGQUOs0dwQTnTMZi8Uatj0). To add the buienradar weather to your installation, add the following to your `configuration.yaml` file: @@ -38,7 +38,8 @@ A full configuration example: # Example configuration.yaml entry weather: - platform: buienradar - name: buienradar + name: 'volkel' + # Force 'Meetstation Volkel' to be used: latitude: 51.65 longitude: 5.70 forecast: True @@ -48,3 +49,6 @@ weather: This platform is an alternative to the [`buienradar`](/components/sensor.buienradar/) sensor. The weather platform is easier to configure but less customisable.

+ +[Usage statement:](https://www.buienradar.nl/overbuienradar/gratis-weerdata) +> Buienradar makes free weatherdata available for use by individuals and businesses (website/intranet). The use of the weatherdata is allowed for **non-commercial purposes**. Please refer to the full usage statement linked above to confirm your usage or to request permission. From c220bf375d53fb3ad2b37a7cc20dd7326f787c05 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Wed, 26 Jul 2017 19:32:16 +0200 Subject: [PATCH 18/81] Update zwave.markdown --- source/hassio/zwave.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/hassio/zwave.markdown b/source/hassio/zwave.markdown index 3a14c3e8196..84b2ccf45c6 100644 --- a/source/hassio/zwave.markdown +++ b/source/hassio/zwave.markdown @@ -28,4 +28,5 @@ zwave: zha: usb_path: /dev/ttyUSB1 + database_path: /config/zigbee.db ``` From 7f8b7a760c34fdeb941aa8a759d0cb6e7283fbe5 Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Wed, 26 Jul 2017 19:48:23 +0200 Subject: [PATCH 19/81] Update mosquitto.markdown --- source/_addons/mosquitto.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_addons/mosquitto.markdown b/source/_addons/mosquitto.markdown index 397b7b8f95c..7d2c2c2de4a 100644 --- a/source/_addons/mosquitto.markdown +++ b/source/_addons/mosquitto.markdown @@ -22,7 +22,7 @@ Set up a [mosquitto](https://mosquitto.org/) MQTT broker. ], "customize": { "active": false, - "folder": "mosquitto + "folder": "mosquitto", } } ``` From 1f3bc2b563c6a36307ef64d1436a22cffe32fac6 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Wed, 26 Jul 2017 22:39:01 +0200 Subject: [PATCH 20/81] HASSbian documentation (#3063) * Remove Hassbian * Replace Hassbian with Hass.io * Move Hassbian docs to installation folder * Update navigation * Update redirects * Update link --- source/_docs/{ => installation}/hassbian.markdown | 0 .../hassbian/common-tasks.markdown | 4 ++-- .../hassbian/customization.markdown | 2 +- .../hassbian/installation.markdown | 2 +- .../hassbian/integrations.markdown | 2 +- .../{ => installation}/hassbian/upgrading.markdown | 2 +- source/_includes/asides/docs_navigation.html | 12 ++---------- source/docs/index.markdown | 6 +++--- source/getting-started/index.markdown | 6 ------ 9 files changed, 11 insertions(+), 25 deletions(-) rename source/_docs/{ => installation}/hassbian.markdown (100%) rename source/_docs/{ => installation}/hassbian/common-tasks.markdown (98%) rename source/_docs/{ => installation}/hassbian/customization.markdown (97%) rename source/_docs/{ => installation}/hassbian/installation.markdown (97%) rename source/_docs/{ => installation}/hassbian/integrations.markdown (98%) rename source/_docs/{ => installation}/hassbian/upgrading.markdown (94%) diff --git a/source/_docs/hassbian.markdown b/source/_docs/installation/hassbian.markdown similarity index 100% rename from source/_docs/hassbian.markdown rename to source/_docs/installation/hassbian.markdown diff --git a/source/_docs/hassbian/common-tasks.markdown b/source/_docs/installation/hassbian/common-tasks.markdown similarity index 98% rename from source/_docs/hassbian/common-tasks.markdown rename to source/_docs/installation/hassbian/common-tasks.markdown index 262770e8d20..ce294b5c1b9 100644 --- a/source/_docs/hassbian/common-tasks.markdown +++ b/source/_docs/installation/hassbian/common-tasks.markdown @@ -7,13 +7,13 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /getting-started/hassbian-common-tasks/ +redirect_from: /docs/hassbian/common-tasks/ --- ### {% linkable_title Login to the Raspberry Pi %} To login to your Raspberry Pi running HASSbian you're going to be using a ssh client. Depending on your platform there are several alternatives for doing this. Linux and Max OS generally have a ssh client installed. Windows users are recommended to download and install the ssh client [Putty][ssh-putty]. -Connect to the Raspberry Pi over ssh. Default user name is `pi` and password is `raspberry`. +Connect to the Raspberry Pi over ssh. Default user name is `pi` and password is `raspberry`. Linux and Mac OS users execute the following command in a terminal. ```bash diff --git a/source/_docs/hassbian/customization.markdown b/source/_docs/installation/hassbian/customization.markdown similarity index 97% rename from source/_docs/hassbian/customization.markdown rename to source/_docs/installation/hassbian/customization.markdown index dfc566f1ff8..1b295b83efe 100644 --- a/source/_docs/hassbian/customization.markdown +++ b/source/_docs/installation/hassbian/customization.markdown @@ -7,7 +7,7 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /getting-started/hassbian-customization/ +redirect_from: /docs/hassbian/customization/ --- To allow you to customize your installation further, we have included a tool called `hassbian-config`. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. diff --git a/source/_docs/hassbian/installation.markdown b/source/_docs/installation/hassbian/installation.markdown similarity index 97% rename from source/_docs/hassbian/installation.markdown rename to source/_docs/installation/hassbian/installation.markdown index e1e2cd5516b..df50d186801 100644 --- a/source/_docs/hassbian/installation.markdown +++ b/source/_docs/installation/hassbian/installation.markdown @@ -7,7 +7,7 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /getting-started/installation-raspberry-pi-image/ +redirect_from: /docs/hassbian/installation/ --- The easiest way to install Home Assistant on your Raspberry Pi is by using HASSbian: a Raspberry Pi image with Home Assistant built-in. The image will install the latest version of Home Assistant on initial boot (~10 minutes). diff --git a/source/_docs/hassbian/integrations.markdown b/source/_docs/installation/hassbian/integrations.markdown similarity index 98% rename from source/_docs/hassbian/integrations.markdown rename to source/_docs/installation/hassbian/integrations.markdown index fe1cebcf400..e48f9e35367 100644 --- a/source/_docs/hassbian/integrations.markdown +++ b/source/_docs/installation/hassbian/integrations.markdown @@ -7,7 +7,7 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /getting-started/hassbian-installation/ +redirect_from: /docs/hassbian/integrations/ --- Some components that are specific for the Raspberry Pi can require some further configuration outside of Home Assistant. All commands below are assumed to be executed with the `pi` account. For full documentation of these components refer to the [components](/components) page. diff --git a/source/_docs/hassbian/upgrading.markdown b/source/_docs/installation/hassbian/upgrading.markdown similarity index 94% rename from source/_docs/hassbian/upgrading.markdown rename to source/_docs/installation/hassbian/upgrading.markdown index 0af3dc90c83..0ac77e21b12 100644 --- a/source/_docs/hassbian/upgrading.markdown +++ b/source/_docs/installation/hassbian/upgrading.markdown @@ -7,7 +7,7 @@ sidebar: true comments: false sharing: true footer: true -redirect_from: /getting-started/hassbian-upgrading/ +redirect_from: /docs/hassbian/upgrading/ --- HASSbian is based on Raspbian and uses the same repositories. Any changes to Raspbian will be reflected in HASSbian. To update and upgrade system packages and installed software (excluding Home Assistant) do the following. diff --git a/source/_includes/asides/docs_navigation.html b/source/_includes/asides/docs_navigation.html index 24d52934717..c6c9b967f1d 100644 --- a/source/_includes/asides/docs_navigation.html +++ b/source/_includes/asides/docs_navigation.html @@ -8,22 +8,14 @@
  • {% active_link /docs/installation/ Installation %}
      +
    • {% active_link /docs/hassio/ Hass.io %}
    • {% active_link /docs/installation/virtualenv/ Python Virtual Env %}
      • +
    • {% active_link /docs/installation/hassbian/ Hassbian %}
    • {% active_link /docs/installation/raspberry-pi-all-in-one/ Raspberry Pi All-in-One %}
    • {% active_link /docs/installation/updating/ Updating %}
    • {% active_link /docs/installation/troubleshooting/ Troubleshooting %}
    • -
  • - {% active_link /docs/hassbian/ Hassbian %} -
      -
    • {% active_link /docs/hassbian/installation/ Installation %}
      • -
    • {% active_link /docs/hassbian/customization/ Customization %}
      • -
    • {% active_link /docs/hassbian/common-tasks/ Common tasks %}
      • -
    • {% active_link /docs/hassbian/integrations/ Integrations %}
      • -
    • {% active_link /docs/hassbian/upgrading/ Upgrading %}
      • -
    -
  • {% active_link /docs/configuration/ Configuration %}