Hass.io tweaks

source/_addons/duckdns.markdown

@@ -7,6 +7,7 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
+featured: true
 ---
 
 [Duck DNS](https://duckdns.org/) is a free service which will point a DNS (sub domains of duckdns.org) to an IP of your choice.

source/_addons/google_assistant.markdown

@@ -1,26 +1,28 @@
 ---
 layout: page
 title: "Google Assistant"
-description: "Enhance your Hass.io installation with google assistant."
+description: "Enhance your Hass.io installation with Google Assistant."
 date: 2017-04-30 13:28
 sidebar: true
 comments: false
 sharing: true
 footer: true
+featured: true
 ---
 
-[Google Assistant][GoogleAssistant] is an AI-powered voice assistant that runs on the Raspberry Pi and x86 platforms and interact over [api.ai] with Home-Assistant. You can also use [Google Actions][GoogleActions] to make extended functionality.
+[Google Assistant][GoogleAssistant] is an AI-powered voice assistant that runs on the Raspberry Pi and x86 platforms and interact over [api.ai] with Home-Assistant. You can also use [Google Actions][GoogleActions] to extend its functionality.
 
 To enable access to the Google Assistant API, do the following:
-1. In the Cloud Platform Console, go to the Projects page. Select an existing project or create a new [project]
-2. Enable the Google Assistant [API] on the project you selected
-3. Create an [OAuth Client ID][oauthclient] as type "others" and download the json file with arrow done on the right site.
 
-Now install and activate the [Samba] add-on so you can upload your credential file. Connect to the "share" Samba share and copy your training data over. Name the file `google_assistant.json`.
+1. In the [Cloud Platform Console][project], go to the Projects page. Select an existing project or create a new project
+2. Open the project. In the top of the page search for Google Assistant API or use [this link][API] and enable it.
+3. Create an [OAuth Client ID][oauthclient], pick type "Other", click "Create" and download the JSON file by clicking the Download JSON button on the right side.
 
-Now it's time to start Google Assistant for the first time. When the Google Assistant add-on starts, it will output your audio devices:
+Now install and activate the [Samba] add-on so you can upload your credential file. Connect to the "share" Samba share and copy your credentials over. Name the file `google_assistant.json`.
 
-```plain
+Now it's time to start Google Assistant for the first time. When the Google Assistant add-on starts, it will output your audio devices in the "Logs" card. You might have to hit "refresh" to get the latest logs:
+
+```text
 **** List of PLAYBACK Hardware Devices ****
 card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
   Subdevices: 8/8
@@ -35,20 +37,25 @@ card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
 card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
+card 1: Microphone [Yeti Stereo Microphone], device 0: USB Audio [USB Audio]
+  Subdevices: 1/1
+  Subdevice #0: subdevice #0
 ```
 
-You need to use this information to configure the `mic` and `speaker` configuration options. The format is `<card #>,<device #>`. On a Raspberry Pi 3, `0,0` is the built-in headset port, `0,1` is the HDMI port.
+You need to use this information to point the add-on at the right speakers and microphone. The information describes different cards and devices. On a Raspberry Pi 3, card 0 - device 0 is the built-in headset port, card 0 - device 1 is the HDMI port. In the example above, the USB microphone showed up as card 1 - device 0.
 
-We need also connect our Google Assistant with google account. Try open the oauth2 interface with http://hassio.local:9324 and follow the steps on that page.
+Find the microphone and speakers that you want to use and note down their device and card number. We will need that to configure the add-on options `mic` (microphone to use) and `speaker` (speaker to use). The format for these options is `<card #>,<device #>`. Change the configuration options and click save.
 
-Now that you've found the microphone and speaker addresses, it's time to configure Google Assistant and restart the add-on.
+The next step is to authenticate your Google account with Google Assistant. Start the add-on and click on the "OPEN WEB UI" button to start authentication.
 
 ### Add-On configuration
 
+Configuration example that uses the USB microphone and use the built-in headset audio output on the Raspberry Pi. Note that card and device numbers can differ on your device.
+
 ```json
 {
   "mic": "1,0",
-  "speaker": "1,0",
+  "speaker": "0,0",
   "client_secrets": "google_assistant.json",
 }
 ```

source/_addons/lets_encrypt.markdown

@@ -7,6 +7,7 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
+featured: true
 ---
 
 Setup and manage a [Let's Encrypt](https://letsencrypt.org/) certificate. This will create a certificate on the first run and renew it if the certificate is expiring in the next 30 days.

source/_addons/mosquitto.markdown

@@ -7,6 +7,7 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
+featured: true
 ---
 
 Set up a [mosquitto](https://mosquitto.org/) MQTT broker.

source/_addons/samba.markdown

@@ -7,6 +7,7 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
+featured: true
 ---
 
 This allows you to set up a [Samba](https://samba.org/) server to access hass.io folders using Windows network shares.

source/_addons/snips.markdown

@@ -17,7 +17,7 @@ Now install and activate the [Samba] add-on so you can upload your training data
 
 Now it's time to start Snips for the first time. When the Snips add-on starts, it will output your audio devices:
 
-```plain
+```text
 **** List of PLAYBACK Hardware Devices ****
 card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
   Subdevices: 8/8
@@ -34,9 +34,11 @@ card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
   Subdevice #0: subdevice #0
 ```
 
-You need to use this information to configure the `mic` and `speaker` configuration options. The format is `<card #>,<device #>`. On a Raspberry Pi 3, `0,0` is the built-in headset port, `0,1` is the HDMI port.
+You need to use this information to point the add-on at the right speakers and microphone. The information describes different cards and devices. On a Raspberry Pi 3, card 0 - device 0 is the built-in headset port, card 0 - device 1 is the HDMI port. In the example above, the USB microphone showed up as card 1 - device 0.
 
-Now that you've found the microphone and speaker addresses, it's time to configure Snips and restart the add-on.
+Find the microphone and speakers that you want to use and note down their device and card number. We will need that to configure the add-on options `mic` (microphone to use) and `speaker` (speaker to use). The format for these options is `<card #>,<device #>`. Change the configuration options and click save.
+
+Now start the add-on.
 
 ### Add-On configuration
 

source/_addons/ssh.markdown

@@ -7,6 +7,7 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
+featured: true
 ---
 
 Setting up an [SSH](https://openssh.org/) server allows access to your Hass.io folders with any SSH client. It include also a cli to access into Hass.IO api. Try it out:

source/addons/index.html

@@ -12,17 +12,30 @@ regenerate: true
 
 <p>Add-ons for Hass.io allows the user to extend the functionality around Home Assistant. This can be running an application that Home Assistant can integrate with (like an MQTT broker) or to share the configuration via Samba for easy editing from other computers. Add-ons can be configured via the Hass.io panel in Home Assistant.</p>
 
+<p>
+  Check the Hass.io forums for <a href='https://community.home-assistant.io/tags/hassio-repository'>add-on repositories managed by the community</a>.
+</p>
+
 {% assign addons = site.addons | sort: 'title' %}
 
+<h3>{% linkable_title Featured add-ons %}</h3>
+
 <ul>
-{% for addon in addons %}
+{% for addon in addons %}{% if addon.featured %}
   <li>
     <a href='{{ addon.url }}'>{{ addon.title }}</a><br>
     {{ addon.description }}
   </li>
-{% endfor %}
+{% endif %}{% endfor %}
 </ul>
 
-<p>
+<h3>{% linkable_title Other add-ons %}</h3>
-  Check the Hass.io forums for <a href='https://community.home-assistant.io/tags/hassio-repository'>add-on repositories managed by the community</a>.
+
-</p>
+<ul>
+{% for addon in addons %}{% if addon.featured != true %}
+  <li>
+    <a href='{{ addon.url }}'>{{ addon.title }}</a><br>
+    {{ addon.description }}
+  </li>
+{% endif %}{% endfor %}
+</ul>

source/hassio/index.markdown

@@ -21,14 +21,15 @@ The advantages of using Hass.io:
  - Easy installation and updates (powered by [ResinOS] and [Docker])
  - Management user interface integrated into Home Assistant
  - Easily create and restore full backups of your whole configuration.
- - One click install of many popular add-ons including voice assistant via [Snips.ai], encryption via [Let's Encrypt] and dynamic DNS via [Duck DNS].<br><br>[Browse available add-ons &raquo;][all]
+ - Easily install many popular add-ons including [Google Assistant], encryption via [Let's Encrypt] and dynamic DNS via [Duck DNS].<br><br>[Browse available add-ons &raquo;][all]<br><br>
- - Active community that is helpful and sharing add-ons including AppDaemon, Homebridge and InfluxDB.<br><br>[Browse the forums &raquo;][forums]<br>[Join the Hass.io chat &raquo;][chat]<br>[Browse community add-on repositories &raquo;][comm-add-ons]
+ - Active community that is helpful and sharing add-ons including AppDaemon, Homebridge and InfluxDB.<br><br>[Browse the forums &raquo;][forums]<br>[Join the Hass.io chat &raquo;][chat]<br>[Browse community add-on repositories &raquo;][comm-add-ons]<br><br>
 
 <p class='img'>
 <img src='/images/hassio/screenshots/dashboard.png'>
 Hass.io dashboard
 </p>
 
+[Google Assistant]: /addons/google_assistant/
 [Snips.ai]: /addons/snips/
 [Let's Encrypt]: /addons/lets_encrypt/
 [Duck DNS]: /addons/duckdns/