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

Merge branch 'current' into next

Browse source
This commit is contained in:
Fabian Affolter 2017-07-28 22:22:07 +02:00
commit a979bcd4e4
No known key found for this signature in database
GPG key ID: DDF3D6F44AAB1336
45 changed files with 304 additions and 83 deletions
Download patch file Download diff file Expand all files Collapse all files

1
source/developers/architecture.markdown
View file

@ -7,6 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
og_image: /images/architecture/ha_architecture.png
---
Before we dive into the Home Assistant architecture, let's get a clear overview of the home automation landscape as a whole. This way, we can show how the different parts of Home Assistant fit into the picture.

1
source/developers/architecture_components.markdown
View file

@ -7,6 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
og_image: /images/architecture/component_interaction.png
---
Home Assistant can be extended with **components**. Each component is responsible for a specific domain within Home Assistant. Components can listen for or trigger events, offer services, and maintain states. Components are written in Python and can do all the goodness that Python has to offer. Out of the box, Home Assistant offers a bunch of [built-in components]({{site_root}}/components/).

2
source/developers/hassio/addon_config.markdown
View file

@ -102,7 +102,7 @@ The config for an add-on is stored in `config.json`.
| ports | no | Network ports to expose from the container. Format is `"container-port/type": host-port`.
| host_network | no | If that is True, the add-on run on host network.
| devices | no | Device list to map into add-on. Format is: `<path_on_host>:<path_in_container>:<cgroup_permissions>`. i.e. `/dev/ttyAMA0:/dev/ttyAMA0:rwm`
| privileged | no | Privilege for access to hardware/system. Available access: `NET_ADMIN`
| privileged | no | Privilege for access to hardware/system. Available access: `NET_ADMIN`, `SYS_ADMIN`
| map | no | List of maps for additional hass.io folders. Possible values: `config`, `ssl`, `addons`, `backup`, `share`. Default it map it `ro`, you can change that if you add a ":rw" at the end of name.
| environment | no | A dict of environment variable to run add-on.
| options | yes | Default options value of the add-on

2
source/developers/hassio/debugging.markdown
View file

@ -31,7 +31,7 @@ Follow steps 1-4 under 'Generating a new SSH key' (The other sections are not ap
Step 3 in the link above, shows the path to the private key file `id_rsa` for your chosen operating system. Your public key, `id_rsa.pub`, is saved in the same folder. Next, copy your public key file to the root of your SD card.
<p class='note'>
Make sure when you are copying the public key to the root of the SD card that you rename the file correctly with no `.pub` file extension.
Make sure when you are copying the public key to the root of the /boot partition of the SD card that you rename the file correctly with no `.pub` file extension.
</p>
## {% linkable_title Checking the logs %}

1
source/developers/index.markdown
View file

@ -7,6 +7,7 @@ sidebar: true
comments: false
sharing: true
footer: true
og_image: /images/architecture/component_interaction.png
---
Welcome to the Home Assistant development documentation. This is the place to learn all about how Home Assistant works and how you can extend it with support for your devices and services!