Site updated at 2017-01-15 15:01:00 UTC
This commit is contained in:
parent
6538404279
commit
687d01500c
24 changed files with 66 additions and 56 deletions
|
@ -112,23 +112,25 @@
|
|||
</ul>
|
||||
|
||||
<h3><a class="title-link" name="getting-ready-for-chrome" href="#getting-ready-for-chrome"></a> Getting ready for Chrome</h3>
|
||||
<p>Create new project at <a href="https://console.cloud.google.com/home/dashboard">https://console.cloud.google.com/home/dashboard</a>
|
||||
Go to <a href="https://console.cloud.google.com/apis/credentials/domainverification">https://console.cloud.google.com/apis/credentials/domainverification</a> and verify your domain
|
||||
After that, go to <a href="https://console.firebase.google.com">https://console.firebase.google.com</a> and select import Google project, select the project you created
|
||||
Then, click the clogwheel on top left and select Project settings
|
||||
Select Cloud messaging tab
|
||||
if under server key is button Regenerate key, click that</p>
|
||||
|
||||
<ul>
|
||||
<li>Create new project at <a href="https://console.cloud.google.com/home/dashboard">https://console.cloud.google.com/home/dashboard</a>.</li>
|
||||
<li>Go to <a href="https://console.cloud.google.com/apis/credentials/domainverification">https://console.cloud.google.com/apis/credentials/domainverification</a> and verify your domain.</li>
|
||||
<li>After that, go to <a href="https://console.firebase.google.com">https://console.firebase.google.com</a> and select import Google project, select the project you created.</li>
|
||||
<li>Then, click the clogwheel on top left and select “Project settings”.</li>
|
||||
<li>Select Cloud messaging tab if under server key is button Regenerate key, click that.</li>
|
||||
</ul>
|
||||
|
||||
<h3><a class="title-link" name="requirements" href="#requirements"></a> Requirements</h3>
|
||||
|
||||
<p>The <code class="highlighter-rouge">html5</code> platform can only function if all of the following requirements are met:</p>
|
||||
|
||||
<ul>
|
||||
<li>You are using Chrome and/or Firefox on any desktop platform, ChromeOS or Android.</li>
|
||||
<li>You are using Chrome and/or Firefox on any desktop platform, ChromeOS, or Android.</li>
|
||||
<li>Your Home Assistant instance is exposed to the world.</li>
|
||||
<li>If using a proxy, basic auth must be off for registering or unregistering for push notifications. It can be re-enabled afterwards.</li>
|
||||
<li>pywebpush must be installed. libffi-dev, libpython-dev, and libssl-dev must be installed prior to pywebpush (i.e. pywebpush probably won’t automatically install).</li>
|
||||
<li>You have configured SSL for your Home Assistant. It doesn’t need to be configured in Home Assistant though, i.e. you can be running nginx in front of Home Assistant and this will still work. The certificate must be trustworthy (i.e. not self signed)</li>
|
||||
<li>If using a proxy, HTTP basic authentication must be off for registering or unregistering for push notifications. It can be re-enabled afterwards.</li>
|
||||
<li><code class="highlighter-rouge">pywebpush</code> must be installed. <code class="highlighter-rouge">libffi-dev</code>, <code class="highlighter-rouge">libpython-dev</code>, and <code class="highlighter-rouge">libssl-dev</code> must be installed prior to <code class="highlighter-rouge">pywebpush</code> (i.e. <code class="highlighter-rouge">pywebpush</code> probably won’t automatically install).</li>
|
||||
<li>You have configured SSL for your Home Assistant. It doesn’t need to be configured in Home Assistant though, i.e. you can be running <a href="/ecosystem/nginx/">NGINX</a> in front of Home Assistant and this will still work. The certificate must be trustworthy (i.e. not self signed).</li>
|
||||
<li>You are willing to accept the notification permission in your browser.</li>
|
||||
</ul>
|
||||
|
||||
|
@ -149,7 +151,7 @@ if under server key is button Regenerate key, click that</p>
|
|||
|
||||
<p>The <code class="highlighter-rouge">html5</code> platform accepts a standard notify payload. However, there are also some special features built in which you can control in the payload.</p>
|
||||
|
||||
<p>Any json examples below can be <a href="https://www.json2yaml.com/">converted to YAML</a> for automations.</p>
|
||||
<p>Any JSON examples below can be <a href="https://www.json2yaml.com/">converted to YAML</a> for automations.</p>
|
||||
|
||||
<h4><a class="title-link" name="actions" href="#actions"></a> Actions</h4>
|
||||
|
||||
|
|
|
@ -205,21 +205,29 @@
|
|||
</tbody>
|
||||
</table>
|
||||
|
||||
<p><strong>Windows Specific:</strong></p>
|
||||
<h2><a class="title-link" name="linux-specific" href="#linux-specific"></a> Linux specific</h2>
|
||||
|
||||
<p>When running this component on windows, <code class="highlighter-rouge">eth0</code> is not valid a valid network name. Typically, the default interface would be called <code class="highlighter-rouge">Local Area Connection</code>, so your config might look like</p>
|
||||
<p>To retrieve all available network interfaces on a Linux System, execute the <code class="highlighter-rouge">ifconfig</code> command.</p>
|
||||
|
||||
<div class="highlighter-rouge"><pre class="highlight"><code>sensor:
|
||||
- platform: systemmonitor
|
||||
resources:
|
||||
- type: network_in
|
||||
arg: 'Local Area Connection'
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>ifconfig -a | sed <span class="s1">'s/[ \t].*//;/^$/d'</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
<p>If you need to use some other interface, open a command prompt and type <code class="highlighter-rouge">ipconfig</code> to list all interface names. For example a wireless connection output from <code class="highlighter-rouge">ip_config</code> might look like</p>
|
||||
<h2><a class="title-link" name="windows-specific" href="#windows-specific"></a> Windows specific</h2>
|
||||
|
||||
<div class="highlighter-rouge"><pre class="highlight"><code>Wireless LAN adapter Wireless Network Connection:
|
||||
<p>When running this platform on Microsoft Windows, Typically, the default interface would be called <code class="highlighter-rouge">Local Area Connection</code>, so your configuration might look like:</p>
|
||||
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><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">systemmonitor</span>
|
||||
<span class="s">resources</span><span class="pi">:</span>
|
||||
<span class="pi">-</span> <span class="s">type</span><span class="pi">:</span> <span class="s">network_in</span>
|
||||
<span class="s">arg</span><span class="pi">:</span> <span class="s1">'</span><span class="s">Local</span><span class="nv"> </span><span class="s">Area</span><span class="nv"> </span><span class="s">Connection'</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
<p>If you need to use some other interface, open a commandline prompt and type <code class="highlighter-rouge">ipconfig</code> to list all interface names. For example a wireless connection output from <code class="highlighter-rouge">ifconfig</code> might look like:</p>
|
||||
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code>Wireless LAN adapter Wireless Network Connection:
|
||||
|
||||
Media State . . . . . . . . . . . : Media disconnected
|
||||
Connection-specific DNS Suffix . :
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue