jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2016-09-02 05:58:21 UTC

Browse source
This commit is contained in:
Travis CI 2016-09-02 05:58:21 +00:00
parent 863686bc07
commit c3d2095713
25 changed files with 60 additions and 50 deletions
Download patch file Download diff file Expand all files Collapse all files

10
components/ecobee/index.html
View file

@ -89,11 +89,11 @@
<hr class="divider">
<p>The Ecobee platform lets you control a thermostats and view sensor data from the <a href="https://ecobee.com">Ecobee</a> thermostat.</p>
<p>The <code class="highlighter-rouge">ecobee</code> component lets you control a thermostats and view sensor data from <a href="https://ecobee.com">ecobee</a> thermostats.</p>
<p>You will need to obtain an API key from ecobee’s <a href="https://www.ecobee.com/developers/">developer site</a> to use this component. To get the key, first you need to register your thermostat. Once you have done that, click on the ‘Become a developer’ link on the developer site. Login with your ecobee credentials, accept the SDK agreement, fill in the fields, and click save. Now login to the regular consumer portal, and in the hamburger menu there will br a new option ‘Developer’. Select that, then select ‘Create New’. Give your app a name (it appears to need to be unique across all users, as I tried ‘home-assistant’ and it said it was already in use) and a summary (neither of these are important as they are not used anywhere). For Authorization method select ‘ecobee PIN’. You don’t need an Application Icon or Detailed Description. Click Save. Now under the Name and Summary Section you will have an API key. Copy this key and use it in you configuration section below. Click the ‘X’ to close the Developer section.</p>
<p>You will need to obtain an API key from ecobee’s <a href="https://www.ecobee.com/developers/">developer site</a> to use this component. To get the key, first you need to register your thermostat. Once you have done that, click on the <strong>Become a developer</strong> link on the developer site. Login with your Ecobee credentials, accept the SDK agreement, fill in the fields, and click <strong>save</strong>. Now login to the regular consumer portal, and in the hamburger menu there will be a new option <strong>Developer</strong>. Select that, then select <strong>Create New</strong>. Give your app a name (it appears to need to be unique across all users, as I tried ‘home-assistant’ and it said it was already in use) and a summary (neither of these are important as they are not used anywhere). For Authorization method select <strong>ecobee PIN</strong>. You don’t need an Application Icon or Detailed Description. Click <strong>Save</strong>. Now under the Name and Summary Section you will have an API key. Copy this key and use it in you configuration section below. Click the <strong>X</strong> to close the Developer section.</p>
<p>The first time you run Home-Assistant with this component it will give you a PIN code that you need to authorize in the <a href="https://www.ecobee.com/consumerportal/index.html">ecobee consumer portal</a>. You can do this by clicking ‘Add Application’ in the ‘My Apps’ section in the sidebar. Enter the PIN code from the Home Assistant screeen. To get the PIN code select the item in the Ecobee card. If you do not have an Ecobee card, you may be using groups with default_view that don’t show the card. To get around this you can temporarily comment out the default_view section or add the configurator.ecobee component to your default_view and restart Home Assistant. Once you enter the PIN on the Ecobee site, wait approximately 5 minutes and then click on the ‘I have authorized the app’ link at the bottom of the Ecobee popup window. If everything worked correctly, you should now be able to restart Home Assistant again to see the full Ecobee card with all of the sensors populated or see the list of sensors in the developer tools. Now you can re-enable your default_view (if you had to disable it) and add the Ecobee sensors to a group and/or view.</p>
<p>The first time you run Home Assistant with this component it will give you a PIN code that you need to authorize in the <a href="https://www.ecobee.com/consumerportal/index.html">ecobee consumer portal</a>. You can do this by clicking <strong>Add Application</strong> in the <strong>My Apps</strong> section in the sidebar. Enter the PIN code from the Home Assistant screeen. To get the PIN code select the item in the ecobee card. If you do not have an ecobee card, you may be using groups with <code class="highlighter-rouge">default_view</code> that don’t show the card. To get around this you can temporarily comment out the <code class="highlighter-rouge">default_view</code> section or add the <code class="highlighter-rouge">configurator.ecobee</code> component to your <code class="highlighter-rouge">default_view</code> and restart Home Assistant. Once you enter the PIN on the ecobee site, wait approximately 5 minutes and then click on the <strong>I have authorized the app</strong> link at the bottom of the ecobee popup window. If everything worked correctly, you should now be able to restart Home Assistant again to see the full ecobee card with all of the sensors populated or see the list of sensors in the developer tools. Now you can re-enable your <code class="highlighter-rouge">default_view</code> (if you had to disable it) and add the ecobee sensors to a group and/or view.</p>
<p>To set it up, add the following information to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
@ -106,8 +106,8 @@
<p>Configuration variables:</p>
<ul>
<li><strong>api_key</strong> (<em>Required</em>): Your Ecobee api key.</li>
<li><strong>hold_temp</strong> (<em>Optional</em>): True/False whether or not to hold changes indefinitely (True) or until the next scheduled event (False, default).</li>
<li><strong>api_key</strong> (<em>Required</em>): Your ecobee API key.</li>
<li><strong>hold_temp</strong> (<em>Optional</em>): True/False whether or not to hold changes indefinitely (True) or until the next scheduled event. Defaults to <code class="highlighter-rouge">False</code>.</li>
</ul>
<p class="img">

8
components/sensor.fritzbox_callmonitor/index.html
View file

@ -90,8 +90,9 @@
<p>The <code class="highlighter-rouge">fritzbox_callmonitor</code> sensor monitors the call monitor exposed by <a href="http://avm.de/produkte/fritzbox/">AVM Fritz!Box</a> routers
on TCP port 1012. It will assume the values ‘idle’, ‘ringing’, ‘dialing’, or ‘talking’,
with the phone numbers involved contained in the state attributes.</p>
on TCP port 1012. It will assume the values <code class="highlighter-rouge">idle</code>, <code class="highlighter-rouge">ringing</code>, <code class="highlighter-rouge">dialing</code>, or <code class="highlighter-rouge">talking</code> with the phone numbers involved contained in the state attributes.</p>
<p>To activate the call monitor on your Fritz!Box, dial #96<em>5</em> from any phone connected to it.</p>
<p>To use the Fritz!Box call monitor in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
@ -124,6 +125,9 @@ with the phone numbers involved contained in the state attributes.</p>
<div class='brand-logo-container section'>
<img src='/images/supported_brands/avm.png' />
</div>
<div class='section'>
IoT class<sup><a href='/blog/2016/02/12/classifying-the-internet-of-things/#classifiers'><i class="icon-info-sign"></i></a></sup>: Local Polling
</div>
<div class='section'>
Introduced in release: 0.27
</div>