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

Site updated at 2015-04-03 05:44:19 UTC

Browse source
This commit is contained in:
Paulus Schoutsen 2015-04-02 22:44:19 -07:00
parent 995b54cad1
commit a535e95231
19 changed files with 78 additions and 78 deletions
Download patch file Download diff file Expand all files Collapse all files

2
developers/api.html
View file

@ -103,7 +103,7 @@
<hr class="divider">
<p>Home Assistent runs a webserver accessible on port 8123.</p>
<p>Home Assistant runs a web server accessible on port 8123.</p>
<ul>
<li><a href="http://127.0.0.1:8123/">http://127.0.0.1:8123/</a> is an interface to control Home Assistant.</li>

2
developers/architecture.html
View file

@ -197,7 +197,7 @@ components within Home Assistant.</p>
<h2><a class='title-link' name='multiple-connected-instances' href='#multiple-connected-instances'></a> Multiple connected instances</h2>
<p>Home Assistant supports running multiple synchronzied instances using a master-slave model. Whenever <code>events.fire</code> or <code>states.set</code> is called on the salve it will forward it to the master. The master will replicate all events and changed states to its slaves.</p>
<p>Home Assistant supports running multiple synchronized instances using a master-slave model. Whenever <code>events.fire</code> or <code>states.set</code> is called on the salve it will forward it to the master. The master will replicate all events and changed states to its slaves.</p>
<p class='img'>
<a href='/images/architecture/architecture-remote.png'>

4
developers/creating_components.html
View file

@ -104,7 +104,7 @@
<p>Home Assistant offers <a href="/components/">built-in components</a> but it
is easy to built your own. If you are the kind of person that likes to learn from code rather then guide then head over to the <a href="https://github.com/balloob/home-assistant/tree/master/config/custom_components"><code>config/custom_compnents</code></a> folder in the repository for two example components.</p>
is easy to built your own. If you are the kind of person that likes to learn from code rather then guide then head over to the <a href="https://github.com/balloob/home-assistant/tree/master/config/custom_components"><code>config/custom_components</code></a> folder in the repository for two example components.</p>
<p>The first is <a href="https://github.com/balloob/home-assistant/blob/master/config/custom_components/hello_world.py">hello_world.py</a>, which is the classic Hello World example for Home Assistant. The second one is <a href="https://github.com/balloob/home-assistant/blob/master/config/custom_components/example.py">example.py</a> which showcases various ways you can tap into Home Assistant to be notified when certain events occur.</p>
@ -200,7 +200,7 @@ Home Assistant will use the directory that contains your config file as the dire
<h3><a class='title-link' name='example-on-using-the-configuration-parameter' href='#example-on-using-the-configuration-parameter'></a> Example on using the configuration parameter</h3>
<p>If your configuration file containes the following lines:</p>
<p>If your configuration file contains the following lines:</p>
<figure class='code'><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>

6
developers/frontend.html
View file

@ -115,10 +115,10 @@
</span><span class='line'> development: 1</span></code></pre></td></tr></table></div></figure>
<p>After turning on development mode, you will have to install the webcomponents that the frontend depends on. You can do this by running the <code>build_frontend</code> script.</p>
<p>After turning on development mode, you will have to install the web components that the frontend depends on. You can do this by running the <code>build_frontend</code> script.</p>
<p class='note warning'>
Do not use development mode in production. Home Assistant uses aggresive caching to improve the mobile experience. This is disabled during development so that you do not have to restart the server in between changes.
Do not use development mode in production. Home Assistant uses aggressive caching to improve the mobile experience. This is disabled during development so that you do not have to restart the server in between changes.
</p>
@ -131,7 +131,7 @@ Do not use development mode in production. Home Assistant uses aggresive caching
</span></code></pre></td></tr></table></div></figure>
<p>After that you can run <a href="https://github.com/balloob/home-assistant/blob/master/build_frontend"><code>./build_frontend</code></a> from the project directory. This will take all the used webcomponents and &lsquo;vulcanize&rsquo; it into a single file to be served by Home Assistant. The script also updates <a href="https://github.com/balloob/home-assistant/blob/master/homeassistant/components/http/frontend.py"><code>homeassistant/components/http/frontend.py</code></a> with an MD5 hash of the frontend.</p>
<p>After that you can run <a href="https://github.com/balloob/home-assistant/blob/master/build_frontend"><code>./build_frontend</code></a> from the project directory. This will take all the used web components and &lsquo;vulcanize&rsquo; it into a single file to be served by Home Assistant. The script also updates <a href="https://github.com/balloob/home-assistant/blob/master/homeassistant/components/http/frontend.py"><code>homeassistant/components/http/frontend.py</code></a> with an MD5 hash of the frontend.</p>
<h1><a class='title-link' name='adding-state-cards' href='#adding-state-cards'></a> Adding state cards</h1>