Site updated at 2018-01-03 17:51:43 UTC

components/emulated_hue/index.html

@@ -74,8 +74,8 @@
     </h1>
   </header>
   <hr class="divider">
-  <p class="warning">
-At this time <code class="highlighter-rouge">emulated_hue</code> doesn’t appear to be working for new Google Home users. 
+  <p class="note warning">
+Be aware that <code class="highlighter-rouge">emulated_hue</code> doesn’t work for new <strong>Google Home</strong> users. If you’re a new user of Google Home, use the <a href="https://home-assistant.io/components/google_assistant/">Google Assistant component</a>.
 </p>
 <p>The <code class="highlighter-rouge">emulated_hue</code> component provides a virtual Philips Hue bridge, written entirely in software, that allows services that work with the Hue API to interact with Home Assistant
 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.

components/hue/index.html

@@ -90,7 +90,7 @@
   <li><strong>host</strong> (<em>Optional</em>): IP address of the device, eg. 192.168.1.10. Required if not using the <code class="highlighter-rouge">discovery</code> component to discover Hue bridges.</li>
   <li><strong>allow_unreachable</strong> (<em>Optional</em>): (true/false)  This will allow unreachable bulbs to report their state correctly.</li>
   <li><strong>filename</strong> (<em>Optional</em>): Make this unique if specifying multiple Hue hubs.</li>
-  <li><strong>allow_in_emulated_hue</strong> (<em>Optional</em>): )true/false) Enable this to block all Hue entities from being added to the <code class="highlighter-rouge">emulated_hue</code> component.</li>
+  <li><strong>allow_in_emulated_hue</strong> (<em>Optional</em>): (true/false) Enable this to block all Hue entities from being added to the <code class="highlighter-rouge">emulated_hue</code> component.</li>
   <li><strong>allow_hue_groups</strong> (<em>Optional</em>): (true/false) Enable this to stop Home Assistant from importing the groups defined on the Hue bridge.</li>
 </ul>
 <h3><a class="title-link" name="migrating-from-older-configuration" href="#migrating-from-older-configuration"></a> Migrating from older configuration</h3>

components/media_player.samsungtv/index.html

@@ -115,6 +115,7 @@
   <li>KS7502 (port must be set to 8001, and <code class="highlighter-rouge">pip3 install websocket-client</code> must be executed, turn on doesn’t work, turn off works fine)</li>
   <li>K5600AK (partially supported, turn on works but state is not updated)</li>
   <li>UE65KS8005 (port must be set to 8001, On/Off, Forward/Backward, Volume are OK, but no Play button)</li>
+  <li>UE6199UXZG (port must be set to 8001, On/Off, Forward/Backward, Volume control, but no Play button)</li>
 </ul>
 <p>Currently tested but not working models:</p>
 <ul>

components/pilight/index.html

@@ -74,8 +74,8 @@
     </h1>
   </header>
   <hr class="divider">
-  <p><a href="https://www.pilight.org/">Pilight</a> is a modular and open source solution to communicate with 433 MHz devices and runs on various small form factor computers. A lot of common <a href="https://wiki.pilight.org/doku.php/protocols">protocols</a> are already available.</p>
-<p>This pilight hub connects to the <a href="https://wiki.pilight.org/doku.php/pdaemon">pilight-daemon</a> via a socket connection to receive and send codes. Thus Home Assistant does not have to run on the computer in charge of the RF communication.</p>
+  <p><a href="https://www.pilight.org/">Pilight</a> is a modular and open source solution to communicate with 433 MHz devices and runs on various small form factor computers. A lot of common <a href="https://manual.pilight.org/protocols/index.html">protocols</a> are already available.</p>
+<p>This pilight hub connects to the <a href="https://manual.pilight.org/programs/daemon.html">pilight-daemon</a> via a socket connection to receive and send codes. Thus Home Assistant does not have to run on the computer in charge of the RF communication.</p>
 <p>The received and supported RF codes are put on the event bus of Home Assistant and are therefore directly usable by other components (e.g. automation). Additionally a send service is provided to send RF codes.</p>
 <p>To integrate pilight into Home Assistant, add the following section to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
@@ -87,11 +87,11 @@
 <p>Configuration variables:</p>
 <ul>
   <li><strong>host</strong> (<em>Required</em>): The IP address of the computer running the pilight-daemon, e.g. 192.168.1.32.</li>
-  <li><strong>port</strong> (<em>Required</em>): The network port to connect to. The usual port is <a href="https://www.pilight.org/development/api/">5000</a>.</li>
+  <li><strong>port</strong> (<em>Required</em>): The network port to connect to. The usual port is <a href="https://manual.pilight.org/development/api.html">5000</a>.</li>
   <li><strong>send_delay</strong> (<em>Optional</em>): You can define a send delay as a fraction of seconds if you experience transmission problems when you try to switch multiple switches at once. This can happen when you use a <a href="https://github.com/pilight/pilight-usb-nano">pilight USB Nano</a> as hardware and switches a whole group of multiple switches on or off. Tested values are between 0.3 and 0.8 seconds depending on the hardware.</li>
   <li><strong>whitelist</strong> (<em>Optional</em>): You can define a whitelist to prevent that too many unwanted RF codes (e.g. the neighbours weather station) are put on your HA event bus. All defined subsections have to be matched. A subsection is matched if one of the items are true.</li>
 </ul>
-<p>In this example only received RF codes using a daycom or Intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight <a href="https://www.pilight.org/development/api/">API</a>.</p>
+<p>In this example only received RF codes using a daycom or Intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight <a href="https://manual.pilight.org/development/api.html">API</a>.</p>
 <p>A full configuration sample could look like the sample below:</p>
 <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
 <span class="s">pilight</span><span class="pi">:</span>
@@ -108,11 +108,11 @@
 </div>
 <h2><a class="title-link" name="troubleshooting" href="#troubleshooting"></a> Troubleshooting</h2>
 <ul>
-  <li>A list of tested RF transceiver hardware is available <a href="https://wiki.pilight.org/doku.php/electronics">here</a>. This might be useful before buying.</li>
+  <li>A list of tested RF transceiver hardware is available <a href="https://manual.pilight.org/electronics/index.html">here</a>. This might be useful before buying.</li>
   <li>Sending commands is simple when the protocol is known by pilight, but receiving commands can be rather difficult. It can happen that the code is not correctly recognized due to different timings in the sending hardware or the RF receiver. If this happens follow these steps:</li>
 </ul>
 <ol>
-  <li><a href="https://www.pilight.org/get-started/installation/">Install</a> pilight from source (do not worry that is very easy) and only activate the protocols you are expecting in the pop up menu. This reduces false positives.</li>
+  <li><a href="https://manual.pilight.org/installation.html">Install</a> pilight from source (do not worry that is very easy) and only activate the protocols you are expecting in the pop up menu. This reduces false positives.</li>
   <li>Check the real timings of your device + RF receiver by running <code class="highlighter-rouge">pilight-debug</code>. Remember the <code class="highlighter-rouge">pulslen</code> parameter.</li>
   <li>Go to the <code class="highlighter-rouge">libs/pilight/protocols/433.92</code> subfolder of the pilight source code and open the .c file of your protocol. Search for <code class="highlighter-rouge">MIN_PULSE_LENGTH</code>, <code class="highlighter-rouge">MAX_PULSE_LENGTH </code> and <code class="highlighter-rouge">AVG_PULSE_LENGTH</code>. Change the pulse lengths to match your measured one. Recompile and install pilight by re-running <code class="highlighter-rouge">$ sudo ./setup.sh</code>.</li>
 </ol>

components/sensor.command_line/index.html

@@ -171,7 +171,6 @@
   <span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">command_line</span>
     <span class="s">name</span><span class="pi">:</span> <span class="s">Brightness</span>
     <span class="s">command</span><span class="pi">:</span> <span class="s2">"</span><span class="s">python3</span><span class="nv"> </span><span class="s">/path/to/script/arest-value.py"</span>
-    <span class="s">unit_of_measurement</span><span class="pi">:</span> <span class="s2">"</span><span class="s">°C"</span>
 </code></pre>
 </div>
 <h3><a class="title-link" name="usage-of-templating-in-command" href="#usage-of-templating-in-command"></a> Usage of templating in <code class="highlighter-rouge">command:</code></h3>
@@ -180,7 +179,7 @@
 <span class="s">sensor</span><span class="pi">:</span>
   <span class="pi">-</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">command_line</span>
     <span class="s">name</span><span class="pi">:</span> <span class="s">wind direction</span>
-    <span class="s">command</span><span class="pi">:</span> <span class="s1">'</span><span class="s">sh</span><span class="nv"> </span><span class="s">/home/pi/.homeassistant/scripts/wind_direction.sh</span><span class="nv"> </span><span class="s">'</span>
+    <span class="s">command</span><span class="pi">:</span> <span class="s1">'</span><span class="s">sh</span><span class="nv"> </span><span class="s">/home/pi/.homeassistant/scripts/wind_direction.sh</span><span class="nv"> </span><span class="s">{{</span><span class="nv"> </span><span class="s">states.sensor.wind_direction.state</span><span class="nv"> </span><span class="s">}}'</span>
     <span class="s">unit_of_measurement</span><span class="pi">:</span> <span class="s2">"</span><span class="s">Direction"</span>
 </code></pre>
 </div>