Site updated at 2017-11-25 22:46:28 UTC

components/device_tracker.nmap_tracker/index.html

@@ -75,7 +75,7 @@
   </header>
   <hr class="divider">
   <p>As an alternative to the router-based device tracking, it is possible to directly scan the network for devices by using Nmap. The IP addresses to scan can be specified in any format that Nmap understands, including the network-prefix notation (<code class="highlighter-rouge">192.168.1.1/24</code>) and the range notation (<code class="highlighter-rouge">192.168.1.1-255</code>).</p>
-<p>If you’re on Debian or Ubuntu, you might have to install the packages for <code class="highlighter-rouge">arp</code> and <code class="highlighter-rouge">nmap</code>. Do so by running <code class="highlighter-rouge">$ sudo apt-get install net-tools nmap</code>. On a Fedora host run <code class="highlighter-rouge">$ sudo dnf -y install nmap</code>.</p>
+<p>You might have to install the packages for <code class="highlighter-rouge">arp</code> and <code class="highlighter-rouge">nmap</code>. On Debian based hosts (for example Hassbian and Raspbian) do so by running <code class="highlighter-rouge">$ sudo apt-get install net-tools nmap</code>. On a Fedora host run <code class="highlighter-rouge">$ sudo dnf -y install nmap</code>.</p>
 <p class="note">
 If you are using <a href="/hassio/">Hass.io</a> then just move forward to the configuration as all requirements are already fulfilled.
 </p>

components/emulated_hue/index.html

@@ -81,7 +81,7 @@ At this time <code class="highlighter-rouge">emulated_hue</code> doesn’t appea
 entities. The driving use case behind this functionality is to allow Home Assistant to work with an Amazon Echo or Google Home with no set up cost outside of configuration changes.
 The virtual bridge has the ability to turn entities on or off, or change the brightness of dimmable lights. The volume level of media players can be controlled as brightness.</p>
 <p class="note">
-A physical Hue Bridge is required for the lights to function - this virtual bridge will not replace a physical bridge.
+A physical Hue Bridge is required for Philips Hue lights to function - this virtual bridge will not replace a physical bridge. Instead, it allows Home Assistant to represent non-Philips Hue devices to Amazon Echo as Philips Hue devices, which Amazon Echo can control with built-in support.
 </p>
 <p class="note">
 It is recommended to assign a static IP address to the computer running Home Assistant. This is because the Amazon Echo discovers devices by IP addresses, and if the IP changes, the Echo won’t be able to control it. This is easiest done from your router, see your router’s manual for details.

components/sensor.dsmr/index.html

@@ -164,6 +164,11 @@
 2001:raw:600:/dev/ttyUSB0:115200 NONE 1STOPBIT 8DATABITS XONXOFF LOCAL -RTSCTS
 </code></pre>
 </div>
+<p>or</p>
+<div class="language-sh highlighter-rouge"><pre class="highlight"><code><span class="c"># Example /etc/ser2net.conf for proxying USB/serial connections to DSMRv2.2 smart meters</span>
+2001:raw:600:/dev/ttyUSB0:9600 EVEN 1STOPBIT 7DATABITS XONXOFF LOCAL -RTSCTS
+</code></pre>
+</div>
 <p><a href="/getting-started/installation-raspberry-pi-image/">HASSbian</a> users have to give dialout permission to the user <code class="highlighter-rouge">homeassistant</code>:</p>
 <div class="highlighter-rouge"><pre class="highlight"><code>$ sudo usermod -a -G dialout homeassistant
 </code></pre>

components/vacuum.xiaomi_miio/index.html

@@ -221,7 +221,7 @@ mode with <code class="highlighter-rouge">remote_control_start</code>.</p>
 </table>
 <h2><a class="title-link" name="attributes" href="#attributes"></a> Attributes</h2>
 <p>In addition to <a href="https://home-assistant.io/components/vacuum/#attributes">all of the attributes provided by the <code class="highlighter-rouge">vacuum</code> component</a>,
-(<code class="highlighter-rouge">battery_icon</code>, <code class="highlighter-rouge">cleaned_area</code>, <code class="highlighter-rouge">fan_speed</code>, <code class="highlighter-rouge">fan_speed_list</code>, <code class="highlighter-rouge">status</code>, and 
+(<code class="highlighter-rouge">battery_icon</code>, <code class="highlighter-rouge">cleaned_area</code>, <code class="highlighter-rouge">fan_speed</code>, <code class="highlighter-rouge">fan_speed_list</code>, <code class="highlighter-rouge">status</code>, and
 <code class="highlighter-rouge">params</code>), the <code class="highlighter-rouge">xiaomi</code> platform introduces specific attributes. These are:</p>
 <ul>
   <li><code class="highlighter-rouge">cleaning_time</code></li>
@@ -308,6 +308,29 @@ easily via a hidden menu item at the Mi-Home app.
   <li>On the phone, you must confirm the backup. DO NOT enter any password and press the button to make the backup.</li>
   <li>Once you have confirmed the backup the token extraction will begin, it should appear in the MiToolKit shortly.</li>
 </ol>
+<h4><a class="title-link" name="linux-and-android-not-rooted" href="#linux-and-android-not-rooted"></a> Linux and Android (not rooted)</h4>
+<p>Follow the pairing process using your phone and Mi-Home app. You will be able to retrieve the token from a SQLite file inside your phone.</p>
+<p>Before you begin you need to install <code class="highlighter-rouge">libffi-dev</code> and <code class="highlighter-rouge">libssl-dev</code> by running the command below. This is needed for <code class="highlighter-rouge">python-mirobo</code> to be installed correctly.</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo apt-get install libffi-dev libssl-dev
+</code></pre>
+</div>
+<p>If your Home Assistant installation is running in a <a href="/docs/installation/virtualenv/#upgrading-home-assistant">Virtualenv</a>, make sure you activate it by running the commands below.</p>
+<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo su -s /bin/bash homeassistant
+<span class="gp">$ </span><span class="nb">source</span> /srv/homeassistant/bin/activate
+</code></pre>
+</div>
+<p>To fetch the token follow these instructions depending on your mobile phone platform.</p>
+<ol>
+  <li>Configure the robot with the Mi-Home app.</li>
+  <li>Enable developer mode, USB debugging and plug the Android phone into the computer.</li>
+  <li>Get ADB e.g. <code class="highlighter-rouge">apt-get install android-tools-adb</code> or <code class="highlighter-rouge">apt-get install adb</code></li>
+  <li><code class="highlighter-rouge">adb devices</code> should list your device. Consult ADB manual if necessary.</li>
+  <li>Issue a backup command via adb: <code class="highlighter-rouge">adb backup -noapk com.xiaomi.smarthome -f backup.ab</code> (set a password if prompted on your phone)</li>
+  <li>Download the ‘ADB Backup Extractor’ from <a href="https://sourceforge.net/projects/adbextractor/files/latest/download">here</a></li>
+  <li>Extract the data from the backup: <code class="highlighter-rouge">java -jar Android\ Backup\ Utilities/Android\ Backup\ Extractor/android-backup-extractor-20171005-bin/abe.jar unpack backup.ab unpacked.tar</code> (enter the password, if prompted)</li>
+  <li>Untar the unpacked data: <code class="highlighter-rouge">tar -xvf unpacked.tar</code></li>
+  <li><code class="highlighter-rouge">sqlite3 apps/com.xiaomi.smarthome/db/miio2.db 'select token from devicerecord where name = "Mi Robot Vacuum";'</code> returns the token for your Xiaomi vacuum bot.</li>
+</ol>
 <h4><a class="title-link" name="linux-and-android-rooted" href="#linux-and-android-rooted"></a> Linux and Android (rooted!)</h4>
 <p>Follow the pairing process using your phone and Mi-Home app. You will be able to retrieve the token from a SQLite file inside your phone.</p>
 <p>Before you begin you need to install <code class="highlighter-rouge">libffi-dev</code> and <code class="highlighter-rouge">libssl-dev</code> by running the command below. This is needed for <code class="highlighter-rouge">python-mirobo</code> to be installed correctly.</p>