Site updated at 2017-04-24 07:38:00 UTC
This commit is contained in:
Travis CI
parent
4fce8893fb
commit
e5000d9263
35 changed files with 79 additions and 80 deletions
2
atom.xml
2
atom.xml
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Announcements | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/announcements/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Community | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/community/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Device-Tracking | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/device-tracking/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: ESP8266 | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/esp8266/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: How-To | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/how-to/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: iBeacons | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/ibeacons/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Internet-of-Things | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/internet-of-things/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: IoT-Data | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/iot-data/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Merchandise | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/merchandise/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Micropython | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/micropython/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: MQTT | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/mqtt/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Organisation | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/organisation/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: OwnTracks | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/owntracks/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Presence-Detection | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/presence-detection/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Public-Service-Announcement | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/public-service-announcement/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Release-Notes | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/release-notes/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Survey | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/survey/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Talks | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/talks/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Technology | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/technology/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: User-Stories | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/user-stories/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Video | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/video/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Website | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/website/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-04-24T06:16:24+00:00</updated>
|
||||
<updated>2017-04-24T07:33:59+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -87,10 +87,10 @@ You can manually rename the created entities by using Home Assistants <a href="h
|
|||
</ul>
|
||||
<p>Configuration variables (host):</p>
|
||||
<ul>
|
||||
<li><strong>ip</strong> (<em>Required</em>): IP of CCU/Homegear</li>
|
||||
<li><strong>port</strong> (<em>Optional</em>): Port of CCU/Homegear XML-RPC Server (default is 2001, use 2000 for wired and 2010 for IP)</li>
|
||||
<li><strong>callback_ip</strong> (<em>Optional</em>): Set this, if HASS is reachable under a different IP from the CCU (NAT, Docker etc.)</li>
|
||||
<li><strong>callback_port</strong> (<em>Optional</em>): Set this, if HASS is reachable under a different port from the CCU (NAT, Docker etc.)</li>
|
||||
<li><strong>ip</strong> (<em>Required</em>): IP address of CCU/Homegear device.</li>
|
||||
<li><strong>port</strong> (<em>Optional</em>): Port of CCU/Homegear XML-RPC Server. Default is 2001, use 2000 for wired and 2010 for IP.</li>
|
||||
<li><strong>callback_ip</strong> (<em>Optional</em>): Set this, if Home Assistant is reachable under a different IP from the CCU (NAT, Docker etc.).</li>
|
||||
<li><strong>callback_port</strong> (<em>Optional</em>): Set this, if Home Assistant is reachable under a different port from the CCU (NAT, Docker etc.).</li>
|
||||
<li><strong>resolvenames</strong> (<em>Optional</em>): [<code class="highlighter-rouge">metadata</code>, <code class="highlighter-rouge">json</code>, <code class="highlighter-rouge">xml</code>] Try to fetch device names. Defaults to <code class="highlighter-rouge">false</code> if not specified.</li>
|
||||
<li><strong>username</strong> (<em>Optional</em>): When fetching names via JSON-RPC, you need to specify a user with guest-access to the CCU.</li>
|
||||
<li><strong>password</strong> (<em>Optional</em>): When fetching names via JSON-RPC, you need to specify the password of the user you have configured above.</li>
|
||||
|
|
@ -128,8 +128,8 @@ You can manually rename the created entities by using Home Assistants <a href="h
|
|||
</ol>
|
||||
<p>Resolving names can take some time. So when you start Home Assistant you won’t see you devices at first. For a setup with 20+ devices it can take up to a minute until all devices show up in the UI.</p>
|
||||
<h3><a class="title-link" name="multiple-hosts" href="#multiple-hosts"></a> Multiple hosts</h3>
|
||||
<p>In order to allow communication with multiple hosts or different protocols in parallel (wireless, wired and ip), multiple connections will be established, each to the configured destination. The name you choose for the host has to be unique and limited to ASCII letters.<br />
|
||||
Using multiple hosts has the drawback, that the services (explained below) may not work as expected. Only one connection can be used for services, which limits the devices/variables a service can use to the scope/protocol of the host.<br />
|
||||
<p>In order to allow communication with multiple hosts or different protocols in parallel (wireless, wired and ip), multiple connections will be established, each to the configured destination. The name you choose for the host has to be unique and limited to ASCII letters.
|
||||
Using multiple hosts has the drawback, that the services (explained below) may not work as expected. Only one connection can be used for services, which limits the devices/variables a service can use to the scope/protocol of the host.
|
||||
This does <em>not</em> affect the entites in Home Assistant. They all use their own connection and work as expected.</p>
|
||||
<h3><a class="title-link" name="reading-attributes-of-entities" href="#reading-attributes-of-entities"></a> Reading attributes of entities</h3>
|
||||
<p>Most devices have, besides their state, additional attributes like their battery state or valve position. These can be accessed using templates in automations, or even as their own entities using the <a href="https://home-assistant.io/components/sensor.template/">template sensor</a> component. Here’s an example of a template sensor that exposes the valve state of a thermostat.</p>
|
||||
|
|
@ -143,7 +143,7 @@ This does <em>not</em> affect the entites in Home Assistant. They all use their
|
|||
</code></pre>
|
||||
</div>
|
||||
<h3><a class="title-link" name="variables" href="#variables"></a> Variables</h3>
|
||||
<p>It is possible to read and set values of system variables you have setup on the CCU/Homegear. The supported types for setting values are float- and bool-variables. <br />
|
||||
<p>It is possible to read and set values of system variables you have setup on the CCU/Homegear. The supported types for setting values are float- and bool-variables.
|
||||
The states of the variables are available through the attributes of your hub entity (e.g. <code class="highlighter-rouge">homematic.rf</code>). Use templates (as mentioned above) to make your variables available to automations or as entities.
|
||||
The values of variables are polled from the CCU/Homegear in an interval of 30 seconds. Setting the value of a variable happens instantly and is directly pushed.</p>
|
||||
<h3><a class="title-link" name="events" href="#events"></a> Events</h3>
|
||||
|
|
@ -211,7 +211,7 @@ The name depends on if you chose to resolve names or not. If not, it will be the
|
|||
</code></pre>
|
||||
</div>
|
||||
<h4><a class="title-link" name="advanced-examples" href="#advanced-examples"></a> Advanced examples</h4>
|
||||
<p>If you are familiar with the internals of HomeMatic devices, you can manually set values on the devices. This can serve as a workaround if support for a device is currently not available, or only limited functionality has been implemented.<br />
|
||||
<p>If you are familiar with the internals of HomeMatic devices, you can manually set values on the devices. This can serve as a workaround if support for a device is currently not available, or only limited functionality has been implemented.
|
||||
Using this service provides you direct access to the setValue-method of the primary connection. If you have multiple hosts, you may select the one hosting a specific device by providing the proxy-parameter with a value equivalent to the name you have chosen. In the example configuration from above <code class="highlighter-rouge">rf</code>, <code class="highlighter-rouge">wired</code> and <code class="highlighter-rouge">ip</code> would be valid values.</p>
|
||||
<p>Manually turn on a switch actor</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="nn">...</span>
|
||||
|
|
|
|||
|
|
@ -137,17 +137,17 @@ When the keyboard reconnects, an event <code class="highlighter-rouge">keyboard_
|
|||
</code></pre>
|
||||
</div>
|
||||
<h2><a class="title-link" name="permissions" href="#permissions"></a> Permissions</h2>
|
||||
<p>There might be permissions problems with the event input device file. If this is the case, the user that hass runs as must be allowed read and write permissions with:</p>
|
||||
<div class="highlighter-rouge"><pre class="highlight"><code>sudo setfacl -m u:HASS_USER:rw /dev/input/event*
|
||||
<p>There might be permissions problems with the event input device file. If this is the case, the user that Home Assistant runs as must be allowed read and write permissions with:</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo setfacl -m u:HASS_USER:rw /dev/input/event<span class="k">*</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>where <code class="highlighter-rouge">HASS_USER</code> is the user hass runs as.</p>
|
||||
<p>where <code class="highlighter-rouge">HASS_USER</code> is the user who runs Home Assistant.</p>
|
||||
<p>If you want to make this permanent, you can use a udev rule that sets it for all event input devices. Add a file <code class="highlighter-rouge">/etc/udev/rules.d/99-userdev-input.rules</code> containing:</p>
|
||||
<div class="highlighter-rouge"><pre class="highlight"><code>KERNEL=="event*", SUBSYSTEM=="input", RUN+="/usr/bin/setfacl -m u:HASS_USER:rw $env{DEVNAME}"
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="nv">KERNEL</span><span class="o">==</span><span class="s2">"event*"</span>, <span class="nv">SUBSYSTEM</span><span class="o">==</span><span class="s2">"input"</span>, RUN+<span class="o">=</span><span class="s2">"/usr/bin/setfacl -m u:HASS_USER:rw </span><span class="nv">$env</span><span class="s2">{DEVNAME}"</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>You can check ACLs permissions with</p>
|
||||
<div class="highlighter-rouge"><pre class="highlight"><code>getfacl /dev/input/event*
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>getfacl /dev/input/event<span class="k">*</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
</article>
|
||||
|
|
|
|||
|
|
@ -268,7 +268,7 @@
|
|||
</code></pre>
|
||||
</div>
|
||||
<h3><a class="title-link" name="making-notifications-work-with-nginx-proxy" href="#making-notifications-work-with-nginx-proxy"></a> Making notifications work with NGINX proxy</h3>
|
||||
<p>If you use <a href="/ecosystem/nginx/">NGINX</a> as an proxy with authentication in front of HASS, you may have trouble with receiving events back to HASS. It’s because of authentication token that cannot be passed through the proxy.</p>
|
||||
<p>If you use <a href="/ecosystem/nginx/">NGINX</a> as an proxy with authentication in front of your Home Assistant instance, you may have trouble with receiving events back to Home Assistant. It’s because of authentication token that cannot be passed through the proxy.</p>
|
||||
<p>To solve the issue put additional location into your nginx site’s configuration:</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>location /api/notify.html5/callback <span class="o">{</span>
|
||||
<span class="k">if</span> <span class="o">(</span><span class="nv">$http_authorization</span> <span class="o">=</span> <span class="s2">""</span><span class="o">)</span> <span class="o">{</span> <span class="k">return </span>403; <span class="o">}</span>
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@
|
|||
<hr class="divider">
|
||||
<p>Notification platform for <a href="https://play.google.com/store/apps/details?id=de.cyberdream.androidtv.notifications.google&hl=de">Notifications for Android TV</a> and <a href="https://play.google.com/store/apps/details?id=de.cyberdream.firenotifications.google">Notifications for FireTV</a>.
|
||||
The notifications are in the global scope of your Android TV device. They will be displayed regardless of which application is running.
|
||||
The In-App purchases only apply to the client for Android smartphones, so there isn’t any limit when pushing notifications from HASS.</p>
|
||||
The In-App purchases only apply to the client for Android smartphones, so there isn’t any limit when pushing notifications from Home Assistant.</p>
|
||||
<p>To enable the notification platform, add the following 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>
|
||||
<span class="s">notify</span><span class="pi">:</span>
|
||||
|
|
|
|||
|
|
@ -84,9 +84,9 @@
|
|||
</div>
|
||||
<p>Configuration variables:</p>
|
||||
<ul>
|
||||
<li><strong>name</strong> (<em>Required</em>): The hub’s name to display in the front end.</li>
|
||||
<li><strong>name</strong> (<em>Required</em>): The hub’s name to display in the frontend.</li>
|
||||
<li><strong>host</strong> (<em>Required</em>): The Harmony device’s IP address.</li>
|
||||
<li><strong>port</strong> (<em>Optional</em>): The Harmony device’s port. 5222 is default.</li>
|
||||
<li><strong>port</strong> (<em>Optional</em>): The Harmony device’s port. Defaults to 5222.</li>
|
||||
<li><strong>activity</strong> (<em>Optional</em>): Activity to use when turnon service is called without any data.</li>
|
||||
<li><strong>scan_interval</strong> (<em>Optional</em>): Amount in seconds in between polling for device’s current activity. Defaults to 30 seconds.</li>
|
||||
</ul>
|
||||
|
|
@ -99,10 +99,10 @@
|
|||
</ul>
|
||||
<p>Supported services:</p>
|
||||
<ul>
|
||||
<li><strong>Turn Off</strong>: Turn off all devices that were switched on from the start of the current activity</li>
|
||||
<li><strong>Turn On</strong>: Start an activity, will start the default activity from configuration.yaml if no activity is specified. The specified activity can either be the activity name or the activity ID from the configuration file written to your HASS config directory. The service will respond faster if the activity ID is passed instead of the name</li>
|
||||
<li><strong>Send Command</strong>: Send a command to one device, device ID and available commands are written to the configuration file at startup</li>
|
||||
<li><strong>Sync</strong>: Synchronizes the Harmony device with the Harmony web service if any changes are made from the web portal or app</li>
|
||||
<li><strong>Turn Off</strong>: Turn off all devices that were switched on from the start of the current activity.</li>
|
||||
<li><strong>Turn On</strong>: Start an activity, will start the default activity from configuration.yaml if no activity is specified. The specified activity can either be the activity name or the activity ID from the configuration file written to your <a href="/docs/configuration/">Home Assistant configuration directory</a>. The service will respond faster if the activity ID is passed instead of the name.</li>
|
||||
<li><strong>Send Command</strong>: Send a command to one device, device ID and available commands are written to the configuration file at startup.</li>
|
||||
<li><strong>Sync</strong>: Synchronizes the Harmony device with the Harmony web service if any changes are made from the web portal or app.</li>
|
||||
</ul>
|
||||
<h3><a class="title-link" name="examples" href="#examples"></a> Examples</h3>
|
||||
<p>A template switch can be used to display and control the state of an activity in the frontend.</p>
|
||||
|
|
@ -131,7 +131,7 @@
|
|||
<span class="s">friendly_name</span><span class="pi">:</span> <span class="s1">'</span><span class="s">bedroom'</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>The example below shows how to control an <code class="highlighter-rouge">input_boolean</code> switch using the Harmony remote’s current activity. The switch will turn on when the remote’s state changes and the Kodi activity is started and off when the remote’s state changes and the current activity is PowerOff.</p>
|
||||
<p>The example below shows how to control an <code class="highlighter-rouge">input_boolean</code> switch using the Harmony remote’s current activity. The switch will turn on when the remote’s state changes and the Kodi activity is started and off when the remote’s state changes and the current activity is PowerOff.</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">automation</span><span class="pi">:</span>
|
||||
<span class="pi">-</span> <span class="s">alias</span><span class="pi">:</span> <span class="s2">"</span><span class="s">Watch</span><span class="nv"> </span><span class="s">TV</span><span class="nv"> </span><span class="s">started</span><span class="nv"> </span><span class="s">from</span><span class="nv"> </span><span class="s">harmony</span><span class="nv"> </span><span class="s">hub"</span>
|
||||
<span class="s">trigger</span><span class="pi">:</span>
|
||||
|
|
|
|||
|
|
@ -143,7 +143,7 @@ When re-flashing the Arduino MEGA, disconnect the ESP8266 to avoid programming d
|
|||
<h3><a class="title-link" name="technical-overview" href="#technical-overview"></a> Technical overview</h3>
|
||||
<ul>
|
||||
<li>The<code class="highlighter-rouge">rflink</code> Python module a asyncio transport/protocol is setup that fires an callback for every (valid/supported) packet received by the RFLink gateway.</li>
|
||||
<li>This component uses this callback to distribute ‘rflink packet events’ over the HASS bus which can be subscribed to by entities/platform implementations.</li>
|
||||
<li>This component uses this callback to distribute ‘rflink packet events’ over Home Assistant’s bus which can be subscribed to by entities/platform implementations.</li>
|
||||
<li>The platform implementions take care of creating new devices (if enabled) for unsees incoming packet id’s.</li>
|
||||
<li>Device entities take care of matching to the packet ID, interpreting and performing actions based on the packet contents. Common entitiy logic is maintained in this main component.</li>
|
||||
</ul>
|
||||
|
|
@ -157,14 +157,14 @@ When re-flashing the Arduino MEGA, disconnect the ESP8266 to avoid programming d
|
|||
</code></pre>
|
||||
</div>
|
||||
<p>This will give you output looking like this:</p>
|
||||
<div class="highlighter-rouge"><pre class="highlight"><code>17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: 20;00;Nod
|
||||
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: o RadioFrequencyLink - R
|
||||
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: FLink Gateway V1.1 - R45
|
||||
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] received data: ;
|
||||
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] got packet: 20;00;Nodo RadioFrequencyLink - RFLink Gateway V1.1 - R45;
|
||||
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] decoded packet: {'firmware': 'RFLink Gateway', 'revision': '45', 'node': 'gateway', 'protocol': 'unknown', 'hardware': 'Nodo RadioFrequencyLink', 'version': '1.1'}
|
||||
17-03-07 20:12:05 DEBUG (MainThread) [rflink.protocol] got event: {'version': '1.1', 'firmware': 'RFLink Gateway', 'revision': '45', 'hardware': 'Nodo RadioFrequencyLink', 'id': 'rflink'}
|
||||
17-03-07 20:12:05 DEBUG (MainThread) [homeassistant.components.rflink] event of type unknown: {'version': '1.1', 'firmware': 'RFLink Gateway', 'revision': '45', 'hardware': 'Nodo RadioFrequencyLink', 'id': 'rflink'}
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>17-03-07 20:12:05 DEBUG <span class="o">(</span>MainThread<span class="o">)</span> <span class="o">[</span>rflink.protocol] received data: 20;00;Nod
|
||||
17-03-07 20:12:05 DEBUG <span class="o">(</span>MainThread<span class="o">)</span> <span class="o">[</span>rflink.protocol] received data: o RadioFrequencyLink - R
|
||||
17-03-07 20:12:05 DEBUG <span class="o">(</span>MainThread<span class="o">)</span> <span class="o">[</span>rflink.protocol] received data: FLink Gateway V1.1 - R45
|
||||
17-03-07 20:12:05 DEBUG <span class="o">(</span>MainThread<span class="o">)</span> <span class="o">[</span>rflink.protocol] received data: ;
|
||||
17-03-07 20:12:05 DEBUG <span class="o">(</span>MainThread<span class="o">)</span> <span class="o">[</span>rflink.protocol] got packet: 20;00;Nodo RadioFrequencyLink - RFLink Gateway V1.1 - R45;
|
||||
17-03-07 20:12:05 DEBUG <span class="o">(</span>MainThread<span class="o">)</span> <span class="o">[</span>rflink.protocol] decoded packet: <span class="o">{</span><span class="s1">'firmware'</span>: <span class="s1">'RFLink Gateway'</span>, <span class="s1">'revision'</span>: <span class="s1">'45'</span>, <span class="s1">'node'</span>: <span class="s1">'gateway'</span>, <span class="s1">'protocol'</span>: <span class="s1">'unknown'</span>, <span class="s1">'hardware'</span>: <span class="s1">'Nodo RadioFrequencyLink'</span>, <span class="s1">'version'</span>: <span class="s1">'1.1'</span><span class="o">}</span>
|
||||
17-03-07 20:12:05 DEBUG <span class="o">(</span>MainThread<span class="o">)</span> <span class="o">[</span>rflink.protocol] got event: <span class="o">{</span><span class="s1">'version'</span>: <span class="s1">'1.1'</span>, <span class="s1">'firmware'</span>: <span class="s1">'RFLink Gateway'</span>, <span class="s1">'revision'</span>: <span class="s1">'45'</span>, <span class="s1">'hardware'</span>: <span class="s1">'Nodo RadioFrequencyLink'</span>, <span class="s1">'id'</span>: <span class="s1">'rflink'</span><span class="o">}</span>
|
||||
17-03-07 20:12:05 DEBUG <span class="o">(</span>MainThread<span class="o">)</span> <span class="o">[</span>homeassistant.components.rflink] event of <span class="nb">type </span>unknown: <span class="o">{</span><span class="s1">'version'</span>: <span class="s1">'1.1'</span>, <span class="s1">'firmware'</span>: <span class="s1">'RFLink Gateway'</span>, <span class="s1">'revision'</span>: <span class="s1">'45'</span>, <span class="s1">'hardware'</span>: <span class="s1">'Nodo RadioFrequencyLink'</span>, <span class="s1">'id'</span>: <span class="s1">'rflink'</span><span class="o">}</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
</article>
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@
|
|||
<hr class="divider">
|
||||
<p>The <code class="highlighter-rouge">dnsip</code> sensor will expose an IP address, fetched via DNS resolution, as its value. There are two operational modes:</p>
|
||||
<ol>
|
||||
<li>When you enable the sensor with minimal configuration, it will query <a href="https://www.opendns.com/">OpenDNS</a>’ nameserver with the hostname <code class="highlighter-rouge">myip.opendns.com</code>, which will resolve to your external/public IP address.</li>
|
||||
<li>When you enable the sensor with minimal configuration, it will query the <a href="https://www.opendns.com/">OpenDNS</a> nameservers with the hostname <code class="highlighter-rouge">myip.opendns.com</code>, which will resolve to your external/public IP address.</li>
|
||||
<li>If you specify a <code class="highlighter-rouge">hostname</code>, a regular DNS lookup will be performed, providing you the IP the hostname resolves to.</li>
|
||||
</ol>
|
||||
<p>You may also override the nameserver that is being used by setting the <code class="highlighter-rouge">resolver</code> parameter to any nameserver you like.</p>
|
||||
|
|
@ -82,7 +82,7 @@
|
|||
<ul>
|
||||
<li><strong>hostname</strong> (<em>Optional</em>): The hostname for which to perform the DNS query. Default: <code class="highlighter-rouge">myip.opendns.com</code> (special hostname that resolves to your public IP)</li>
|
||||
<li><strong>resolver</strong> (<em>Optional</em>): The DNS server to target the query at. Default: <code class="highlighter-rouge">208.67.222.222</code> (OpenDNS)</li>
|
||||
<li><strong>ipv6</strong> (<em>Optional</em>): Set this to <code class="highlighter-rouge">true</code> or <code class="highlighter-rouge">false</code> if IPv6 should be used. When resolving the public IP, this will be the IP of the machine HASS is running on.</li>
|
||||
<li><strong>ipv6</strong> (<em>Optional</em>): Set this to <code class="highlighter-rouge">true</code> or <code class="highlighter-rouge">false</code> if IPv6 should be used. When resolving the public IP, this will be the IP of the machine where Home Assistant is running on.</li>
|
||||
<li><strong>resolver_ipv6</strong> (<em>Optional</em>): The IPv6 DNS server to target the query at. Default: <code class="highlighter-rouge">2620:0:ccc::2</code> (OpenDNS)</li>
|
||||
<li><strong>scan_interval</strong> (<em>Optional</em>): Defines number of seconds for polling interval. Default: <code class="highlighter-rouge">120</code> seconds.</li>
|
||||
</ul>
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p>The <a href="https://www.open-homeautomation.com/2016/08/23/reverse-engineering-the-mi-plant-sensor/">Mi Flora plant sensor</a> is a small Bluetooth Low Energy device that monitors not only the moisture, but also light, temperature and conductivity. As only a single BLE device can be polled at the same time, the library implements locking to make sure this is the case.</p>
|
||||
<p>The <code class="highlighter-rouge">miflora</code> sensor platform allows one to monitor to plants. The <a href="https://www.aliexpress.com/item/Newest-Original-Xiaomi-Flora-Monitor-Digital-Plants-Flowers-Soil-Water-Light-Tester-Sensor-Monitor-for-Aquarium/32685750372.html">Mi Flora plant sensor</a> is a small Bluetooth Low Energy device that monitors not only the moisture, but also light, temperature and conductivity. As only a single BLE device can be polled at the same time, the library implements locking to make sure this is the case.</p>
|
||||
<p>To use your Mi Flora plant sensor in your installation, add the following 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>
|
||||
<span class="s">sensor</span><span class="pi">:</span>
|
||||
|
|
|
|||
|
|
@ -66,12 +66,11 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p>The <code class="highlighter-rouge">modem_callerid</code> sensor platform uses an available modem for collecting caller ID information. It requires a Hayes AT compatible modem that supports caller ID detection (via AT+VCID=1).</p>
|
||||
<p>The <code class="highlighter-rouge">modem_callerid</code> sensor platform uses an available modem for collecting caller ID information. It requires a Hayes AT compatible modem that supports caller ID detection (via AT+VCID=1).</p>
|
||||
<p>To enable the sensor, add the following lines to your <code class="highlighter-rouge">configuration.yaml</code>:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
<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">modem_callerid</span>
|
||||
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>Configuration variables:</p>
|
||||
|
|
@ -81,7 +80,7 @@
|
|||
</ul>
|
||||
<p>To find the path of your USB modem, run:</p>
|
||||
<p><code class="highlighter-rouge">$ ls /dev/ttyACM*</code></p>
|
||||
<p>If <code class="highlighter-rouge">hass</code> runs with another user (e.g. <em>homeassistant</em> on Hassbian) give access to the stick with:</p>
|
||||
<p>If Home Assistant (<code class="highlighter-rouge">hass</code>) runs with another user (e.g. <code class="highlighter-rouge">homeassistant</code> on Hassbian) give access to the stick with:</p>
|
||||
<p><code class="highlighter-rouge">$ sudo usermod -a -G dialout homeassistant</code></p>
|
||||
<p>Depending on what’s plugged into your USB ports, the name found above may change. You can lock in a name, such as <code class="highlighter-rouge">/dev/modem</code>, by following <a href="http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/">these instructions</a>.</p>
|
||||
<p>When the sensor detects a new call, it’s state changes to ‘ring’ for each ring and ‘callerid’ when caller id information is received. It returns to ‘idle’ once ringing stops. The state event includes an attribute payload that includes the time of the call, name and number.</p>
|
||||
|
|
@ -91,7 +90,7 @@
|
|||
<span class="s">trigger</span><span class="pi">:</span>
|
||||
<span class="s">platform</span><span class="pi">:</span> <span class="s">state</span>
|
||||
<span class="s">entity_id</span><span class="pi">:</span> <span class="s">sensor.modem_callerid</span>
|
||||
<span class="s">state</span><span class="pi">:</span> <span class="s2">"</span><span class="s">callerid"</span>
|
||||
<span class="s">state</span><span class="pi">:</span> <span class="s2">"</span><span class="s">callerid"</span>
|
||||
<span class="s">action</span><span class="pi">:</span>
|
||||
<span class="s">service</span><span class="pi">:</span> <span class="s">notify.notify</span>
|
||||
<span class="s">data</span><span class="pi">:</span>
|
||||
|
|
|
|||
|
|
@ -101,7 +101,7 @@
|
|||
<p>The <code class="highlighter-rouge">su</code> command means ‘switch’ user. We use the ‘-s’ flag because the <code class="highlighter-rouge">homeassistant</code> user is a system user and doesn’t have a default shell by default (to prevent attackers from being able to log in as that user).</p>
|
||||
<h3><a class="title-link" name="step-4-set-up-the-virtualenv" href="#step-4-set-up-the-virtualenv"></a> Step 4: Set up the virtualenv</h3>
|
||||
<p>All this step does is stick a Python environment in the directory we’re using. That’s it. It’s just a directory. There’s nothing special about it, and it is entirely self-contained.</p>
|
||||
<p>It will include a <code class="highlighter-rouge">bin</code> directory, which will contain all the executables used in the virtualenv (including hass itself). It also includes a script called <code class="highlighter-rouge">activate</code> which we will use to activate the virtualenv.</p>
|
||||
<p>It will include a <code class="highlighter-rouge">bin</code> directory, which will contain all the executables used in the virtualenv (including Home Assistant itself). It also includes a script called <code class="highlighter-rouge">activate</code> which we will use to activate the virtualenv.</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>virtualenv -p python3 /srv/homeassistant
|
||||
</code></pre>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -123,10 +123,10 @@ Instead of <code class="highlighter-rouge">make install</code>, you can alternat
|
|||
<li><strong>ignored</strong> (<em>Optional</em>): Ignore this entity completely. It won’t be shown in the Web Interface and no events are generated for it.</li>
|
||||
<li><strong>refresh_value</strong> (<em>Optional</em>): Enable refreshing of the node value. Only the light component uses this. Defaults to False.</li>
|
||||
<li><strong>delay</strong> (<em>Optional</em>): Specify the delay for refreshing of node value. Only the light component uses this. Defaults to 2 seconds.</li>
|
||||
<li><strong>invert_openclose_buttons</strong> (<em>Optional</em>): Inverts function of the open and close buttons for the cover domain. Defaults to False</li>
|
||||
<li><strong>invert_openclose_buttons</strong> (<em>Optional</em>): Inverts function of the open and close buttons for the cover domain. Defaults to <code class="highlighter-rouge">False</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><strong>debug</strong> (<em>Optional</em>): Print verbose z-wave info to log. Defaults to False.</li>
|
||||
<li><strong>debug</strong> (<em>Optional</em>): Print verbose z-wave info to log. Defaults to <code class="highlighter-rouge">False</code>.</li>
|
||||
</ul>
|
||||
<p>To find the path of your Z-Wave USB stick or module, run:</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>ls /dev/ttyUSB<span class="k">*</span>
|
||||
|
|
@ -135,7 +135,7 @@ Instead of <code class="highlighter-rouge">make install</code>, you can alternat
|
|||
<p>Or, on some other systems (such as Raspberry Pi), use:</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>ls /dev/ttyACM<span class="k">*</span>
|
||||
|
||||
<span class="c"># If `hass` runs with another user (e.g. *homeassistant* on Hassbian) give access to the stick with:</span>
|
||||
<span class="c"># If Home Assistant (`hass`) runs with another user (e.g. *homeassistant* on Hassbian) give access to the stick with:</span>
|
||||
<span class="gp">$ </span>sudo usermod -a -G dialout homeassistant
|
||||
</code></pre>
|
||||
</div>
|
||||
|
|
|
|||
30
sitemap.xml
30
sitemap.xml
|
|
@ -3193,62 +3193,62 @@
|
|||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/demo/frontend.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/demo/index.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/demo/panels/ha-panel-dev-event.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/demo/panels/ha-panel-dev-info.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/demo/panels/ha-panel-dev-service.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/demo/panels/ha-panel-dev-state.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/demo/panels/ha-panel-dev-template.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/demo/panels/ha-panel-history.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/demo/panels/ha-panel-iframe.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/demo/panels/ha-panel-logbook.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/demo/panels/ha-panel-map.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/googlef4f3693c209fe788.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:05+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:06+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:06+00:00</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://home-assistant.io/static/mdi-demo.html</loc>
|
||||
<lastmod>2017-04-24T06:15:38+00:00</lastmod>
|
||||
<lastmod>2017-04-24T07:33:06+00:00</lastmod>
|
||||
</url>
|
||||
</urlset>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue