Paulus Schoutsen
commit
b1f2947ed4
26 changed files with 417 additions and 111 deletions
|
|
@ -1,28 +1,26 @@
|
|||
# Home Assistant website
|
||||
|
||||
This is the source for the [Home Assistant](https://github.com/balloob/home-assistant) website available at [Home-Assistant.io](https://home-assistant.io). All commits made to the `master` branch will be automatically pushed to production.
|
||||
|
||||
Please point your Pull Request (PR) at the `next` branch.
|
||||
|
||||
## Preview Jekyll website locally
|
||||
|
||||
| Command | Action |
|
||||
|---|---|
|
||||
| `rake preview` | Preview site on [http://127.0.0.1:4000](http://127.0.0.1:4000)
|
||||
This is the source for the [Home-Assistant.io website](https://home-assistant.io) for the [Home Assistant project](https://github.com/balloob/home-assistant)
|
||||
|
||||
## Setup
|
||||
|
||||
_You need to have Ruby installed._
|
||||
Setting up to contribute to documentation and the process for submitting pull requests is [explained here](https://home-assistant.io/developers/website/).
|
||||
|
||||
- [Ruby installation instructions](https://www.ruby-lang.org/en/documentation/installation/)
|
||||
- For Fedora and CentOS check the last section of this file.
|
||||
## Create a new blog post
|
||||
|
||||
```bash
|
||||
$ git clone --recursive https://github.com/balloob/home-assistant.io.git
|
||||
$ cd home-assistant.io
|
||||
$ bundle
|
||||
$ rake new_post["title"]
|
||||
```
|
||||
|
||||
## Site preview
|
||||
|
||||
```bash
|
||||
$ rake preview
|
||||
```
|
||||
|
||||
This makes the preview available on [http://127.0.0.1:4000](http://127.0.0.1:4000).
|
||||
|
||||
|
||||
### Setup on Fedora and CentOS
|
||||
On Fedora > 22 or CentOS 7.1.1503 Ruby is not available by default. Please take the notes here as a little guide for the Ruby installation process.
|
||||
|
||||
|
|
@ -42,4 +40,4 @@ The last command will give you something like this `ruby 2.2.3p173 (2015-08-18 r
|
|||
$ gem install bundler
|
||||
```
|
||||
|
||||
Now please follow the Setup instructions above.
|
||||
Now you can follow the [setup instructions](https://home-assistant.io/developers/website/).
|
||||
|
|
|
|||
43
source/_components/camera.rpi_camera.markdown
Normal file
43
source/_components/camera.rpi_camera.markdown
Normal file
|
|
@ -0,0 +1,43 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Raspberry Pi Camera"
|
||||
description: "Instructions how to integrate Raspberry Pi within Home Assistant."
|
||||
date: 2016-04-08 10:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: raspberry-pi.png
|
||||
ha_category: Camera
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
The `rpi` platform allows you to integrate the Raspberry Pi camera into Home Assistant. This component uses the application "raspistill" to store the image from camera.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
camera:
|
||||
platform: raspberry_camera
|
||||
name: Raspberry Pi Camera
|
||||
image_width: 640
|
||||
image_height: 480
|
||||
image_quality: 7
|
||||
image_rotation: 0
|
||||
timelapse: 1000
|
||||
horizontal_flip: 0
|
||||
vertical_flip: 0
|
||||
file_path: /tmp/image.jpg
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **name** (optional): name of the camera
|
||||
- **image_width** (optional): set the image width (default: 640)
|
||||
- **image_height** (optional): set the image width (default: 480)
|
||||
- **image_quality** (optional): set the image quality (from 0 to 100, default: 7)
|
||||
- **image_rotation** (optional): Set image rotation (0-359, default: 0)
|
||||
- **horizontal_flip** (optional): Set horizontal flip (0 to disable, 1 to enable, default: 0)
|
||||
- **vertical_flip** (optional): Set vertical flip (0 to disable, 1 to enable, default: 0)
|
||||
- **timelapse** (optional): Takes a picture every <t>ms (default: 1000)
|
||||
- **file_path** (optional): Save the picture in a custom file path (default: camera components folder)
|
||||
|
|
@ -11,6 +11,9 @@ logo: yamaha.png
|
|||
ha_category: Media Player
|
||||
---
|
||||
|
||||
<p class='note warning'>
|
||||
Some users are experiencing errors loading the frontend while using this platform.
|
||||
</p>
|
||||
|
||||
The `yamaha` platform allows you to control [Yamaha Network Receivers](http://usa.yamaha.com/products/audio-visual/av-receivers-amps/rx) from Home Assistant.
|
||||
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ Home Assistant contains an embedded MQTT broker. If no broker configuration is g
|
|||
| Port | 1883
|
||||
| Protocol | 3.1.1
|
||||
| User | homeassistant
|
||||
| Password | Your API password
|
||||
| Password | Your API [password](/components/http/)
|
||||
| Websocket port | 8080
|
||||
|
||||
<p class='note'>
|
||||
|
|
@ -179,7 +179,7 @@ $ mosquitto_pub -h 127.0.0.1 -t home-assistant/switch/1/on -m "Switch is ON"
|
|||
If you are using the embeeded MQTT broker, the command looks a little different because you need to add the MQTT protocol version.
|
||||
|
||||
```bash
|
||||
$ mosquitto_pub -V mqttv311 -t hello -m world
|
||||
$ mosquitto_pub -V mqttv311 -t "hello" -m world
|
||||
```
|
||||
|
||||
or if you are using a API password.
|
||||
|
|
@ -212,7 +212,7 @@ $ mosquitto_sub -h 127.0.0.1 -v -t "home-assistant/#"
|
|||
For the embeeded MQTT broker the command looks like the sample below.
|
||||
|
||||
```bash
|
||||
$ mosquitto_sub -V mqttv311 -t # -v
|
||||
$ mosquitto_sub -v -V mqttv311 -t "#"
|
||||
```
|
||||
|
||||
Add the username `homeassistant` and your API password if needed.
|
||||
|
|
|
|||
|
|
@ -24,7 +24,6 @@ script:
|
|||
event_data:
|
||||
name: Paulus
|
||||
message: is waking up
|
||||
# Optional
|
||||
entity_id: device_tracker.paulus
|
||||
domain: light
|
||||
- alias: Bedroom lights on
|
||||
|
|
|
|||
32
source/_components/sensor.nzbget.markdown
Normal file
32
source/_components/sensor.nzbget.markdown
Normal file
|
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
layout: page
|
||||
title: "NZBGet"
|
||||
description: "Instructions how to integrate NZBGet within Home Assistant."
|
||||
date: 2016-04-08 19:59
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Sensor
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `NZBGet` platform will allow you to monitor your downloads with [NZBGet](http://NZBGet.net) from within Home Assistant and setup automation based on the information.
|
||||
|
||||
To use NZBGet with your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: nzbget
|
||||
base_url: http://192.168.1.18:6789
|
||||
username: apiuser
|
||||
password: apipass
|
||||
monitored_variables:
|
||||
- ArticleCacheMB
|
||||
- DownloadRate
|
||||
- DownloadPaused
|
||||
- FreeDiskSpaceMB
|
||||
- PostPaused
|
||||
- RemainingSizeMB
|
||||
```
|
||||
|
|
@ -77,4 +77,20 @@ sensor:
|
|||
```
|
||||
(please note the blank line to close the multi-line template)
|
||||
|
||||
### {% linkable_title Change the unit of measurment %}
|
||||
|
||||
With a template sensor it's easy to convert given values into others if the unit of measurement don't fit your needs.
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
platform: template
|
||||
sensors:
|
||||
transmission_down_speed_kbps:
|
||||
value_template: {% raw %}'{{ states.sensor.transmission_down_speed.state | multiply(1024) }}'{% endraw %}
|
||||
friendly_name: 'Transmission Down Speed'
|
||||
unit_of_measurement: 'kB/s'
|
||||
transmission_up_speed_kbps:
|
||||
value_template: {% raw %}'{{ states.sensor.transmission_up_speed.state | multiply(1024) }}'{% endraw %}
|
||||
friendly_name: 'Transmission Up Speed'
|
||||
unit_of_measurement: 'kB/s'
|
||||
```
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ To use the monitoring, your transmission client needs to allow remote access. If
|
|||
<img src='{{site_root}}/images/screenshots/transmission_perf.png' />
|
||||
</p>
|
||||
|
||||
If everthing is setup correctly, the details will show up in the frontend.
|
||||
If everything is setup correctly, the details will show up in the frontend.
|
||||
|
||||
<p class='img'>
|
||||
<img src='{{site_root}}/images/screenshots/transmission.png' />
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@
|
|||
<li><a href="/developers/add_new_platform/">
|
||||
Adding Platform Support
|
||||
</a></li>
|
||||
<li><a href="/developers/api/">API</a></li>
|
||||
<li><a href="/developers/api/">API and SSE</a></li>
|
||||
<li><a href="/developers/credits/">Credits</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ date_formatted: December 26, 2014
|
|||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Architecture
|
||||
categories: Internet-of-Things
|
||||
---
|
||||
|
||||
The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home.
|
||||
|
|
|
|||
|
|
@ -7,12 +7,12 @@ date_formatted: "January 19, 2016"
|
|||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Architecture
|
||||
categories: Internet-of-Things
|
||||
---
|
||||
|
||||
People often ask me about my vision for Home Assistant. Before I can describe where I want to go with Home Assistant, I should first talk about how home automation would look in my ideal world. This will be the aim of this post. I’m not going to focus on protocols, networks or specific hubs. That's all implementation details. Instead, this post will focus on what is most important: the interaction between the users and their home.
|
||||
|
||||
### You should not have to adapt to technology.
|
||||
### {% linkable_title You should not have to adapt to technology. %}
|
||||
|
||||
When people start using home automation, they always experience home control first: being able to control devices in new ways using a phone or computer. They believe the future is now and their app will be their remote for their lives. They only focus on what they are getting, not on what they are losing. You install some light bulbs and all of a sudden you are no longer able to use the light switches. You'll arrive at home at night and have to pull out your phone, open the app, let it connect and finally you'll be able to turn on the light. All while turning the light on could have been a switch away.
|
||||
|
||||
|
|
@ -21,19 +21,19 @@ Yes, you can solve this with presence detection. What if your phone runs out of
|
|||
If you find that using your new home devices is cumbersome, the promise of home automation technology has failed you. Your lights should work with both a switch (or button) at the entrance of your room and via presence detection. Honestly, there are hardly any valid use cases for being able to control lights from your phone except for showing off.
|
||||
<!--more-->
|
||||
|
||||
### You are not the only user of your home automation.
|
||||
### {% linkable_title You are not the only user of your home automation. %}
|
||||
|
||||
People tend to forget that they are not the only ones in their home. As the developer of your house you're enthusiastic about the possibilities and are willing to overlook flaws. Chances are very high that the other people in your household have different hobbies and just want to mind their own business.
|
||||
|
||||
This means that everything you automate has to work flawlessly. If you successfully manage to cause a response to some stimulus 90% of the time, you’re going to have a disproportionately poor experience 10% of the time. A common automation that fits this pattern is to fade the lights when you start watching a movie or series in the living room. It only works if everyone is watching.
|
||||
|
||||
### Limit the impact of false positives and negatives.
|
||||
### {% linkable_title Limit the impact of false positives and negatives. %}
|
||||
|
||||
With every automation, you always have to think: what will be the impact if it doesn’t work? Home automation is composed of many different systems by many different vendors that speak many different protocols: things will go wrong. It’s up to you to make sure that they have a limited impact when they fail. Ideally, devices should fall back to a pre-smart home experience. A Philips Hue bulb will act like a standard white light if turned on/off using a normal switch or when not connected to a hub. If things get worse when your system is out of order, your users will revolt. Take for example the Nest thermostat that [had a bug in the beginning of January][nest-bug] which caused it to stop heating the house, yikes!
|
||||
|
||||
[nest-bug]: http://www.nytimes.com/2016/01/14/fashion/nest-thermostat-glitch-battery-dies-software-freeze.html
|
||||
|
||||
### The perfect app is no app.
|
||||
### {% linkable_title The perfect app is no app. %}
|
||||
|
||||
Home automation should blend with your current workflow, not replace it. For most devices, there is no faster way to control most devices than how you are already doing it today. Most of the time, the best app is no app. The only interface that can be more convenient, and is accessible for visitors of your home of all ages is a voice interface. The industry has realized this too and there are some major players focussing on voice interaction. Take Apple for example: the only way to control your HomeKit devices is with Siri. Amazon has taken it one step further with the Amazon Echo, providing an always-listening connected speaker/microphone for the living room. I expect a lot more companies to join this segment in 2016.
|
||||
|
||||
|
|
@ -41,7 +41,7 @@ Voice interfaces are not perfect either. The speed at which you can issue comman
|
|||
|
||||
This however doesn’t mean there isn’t a place for apps, there definitely is. They are perfectly well-suited for checking in while you’re away, browsing the state changes of your house or making the lights go all funky when there are kids visiting.
|
||||
|
||||
### Your system should run at home, not in the cloud.
|
||||
### {% linkable_title Your system should run at home, not in the cloud. %}
|
||||
|
||||
The cloud is a magical thing. Somewhere in the world there are computers collecting the data that your house generates, testing them against your automation rules and sending commands back when needed. The cloud will receive updates and improve itself over time so it is able to serve you better. Until it’s not. There are many reasons why your home might lose its connection to the cloud. The internet can stop working, an update might have gone wrong or the servers running the cloud crash.
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ date_formatted: "February 12, 2016"
|
|||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Architecture
|
||||
categories: Internet-of-Things
|
||||
og_image: /images/blog/2016-02-classifying-internet-of-things/social.png
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,28 @@
|
|||
---
|
||||
layout: post
|
||||
title: "Your hub should be local and open"
|
||||
description: "Running a hub that depends on the cloud is a risk that can cost you your home automation."
|
||||
date: 2016-04-04 21:11:00 -0700
|
||||
date_formatted: "April 5, 2016"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Internet-of-Things
|
||||
---
|
||||
|
||||
Today the news spread that Google will be [shutting down the Revolv hubs][medium-revolv]. And shutting down here doesn't mean they stop selling or supporting them - no, they are sending an update to each hub to turn your perfectly fine home automation hub into a useless piece of plastic. The fact that this seemed like a good idea by Google astonishes me. If anything, they should have gone the same route as [ninjasphere]: open it all up and let people decide on the fate of their _own_ hub.
|
||||
|
||||
I've said it [before][perfect-cloud] but I'll repeat it again:
|
||||
|
||||
<blockquote>
|
||||
The cloud should be treated as an extension to your smart home instead of running it.
|
||||
</blockquote>
|
||||
|
||||
Your hub should not be affected when your internet breaks down or the company that sold you your hub goes out of business. It should work locally so that it can continue to work even long after the vendor goes out of business or decides to kill it. Preferably, your hub should also be open so that the community can take over development after the vendor stops caring.
|
||||
|
||||
Unless you can afford losing a product here and there, be cautious when buying IoT products that depend on the cloud from companies that are not well established. The chances are high that they go bankrupt or get acquired and closed. This however is easier said than done as [Gartner] predicts that by 2017, 50 percent of IoT solutions will originate in startups that are less than three years old.
|
||||
|
||||
[medium-revolv]: https://medium.com/@arlogilbert/the-time-that-tony-fadell-sold-me-a-container-of-hummus-cb0941c762c1#.rmppks86a
|
||||
[ninjasphere]: https://discuss.ninjablocks.com/t/ninja-blocks-whats-been-happening-whats-happening-next/3608
|
||||
[perfect-cloud]: /blog/2016/01/19/perfect-home-automation/#your-system-should-run-at-home-not-in-the-cloud
|
||||
[Gartner]: http://www.gartner.com/newsroom/id/2869521
|
||||
31
source/_posts/2016-04-07-static-website.markdown
Normal file
31
source/_posts/2016-04-07-static-website.markdown
Normal file
|
|
@ -0,0 +1,31 @@
|
|||
---
|
||||
layout: post
|
||||
title: "Static website"
|
||||
description: "Serving a static website with Home Assistant."
|
||||
date: 2016-04-07 06:28:00
|
||||
date_formatted: "April 7, 2016"
|
||||
author: Fabian Affolter
|
||||
author_twitter: fabaff
|
||||
comments: true
|
||||
categories: How-To
|
||||
og_image: /images/blog/2016-04-display/ha-display.png
|
||||
---
|
||||
|
||||
The frontend of Home Assistant is served with the help of a local web server. If you have [customized](/getting-started/devices/#customizing-devices-and-services) your installation you already use this functionality. The content of your folder `www` in your Home Assistant configuration directory (`.homeassistant`) is available under `/local` (eg. [https://localhost:8123/local](https://localhost:8123/local)).
|
||||
|
||||
But there is more you can do! You can not only host images for customization there but HTML files or even web applications including CSS and Javascript.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2016-04-display/ha-display.png' />
|
||||
</p>
|
||||
|
||||
<!--more-->
|
||||
|
||||
In the past the buzz word "Smart mirror" was used a couple of times in our [chatroom](https://gitter.im/balloob/home-assistant) and even made it into the [issue tracker](https://github.com/balloob/home-assistant/issues/1392). The existing solutions ([Smart mirror](http://docs.smart-mirror.io/), [MagicMirror](http://michaelteeuw.nl/tagged/magicmirror), and [HomeMirror](https://github.com/HannahMitt/HomeMirror)) seems to be overkill if you already have Home Assistant running somewhere in your house or apartment. Why not simple display a web page served by Home Assistant on the tablet? No app and no Raspberry Pi running in the background.
|
||||
|
||||
There are plenty of ways to achieve this...[RESTful API](/developers/rest_api/), [Python API](/developers/python_api/), or one of the [history components](/components/#history). If it is to be a web page I'm using the [MQTT Eventstream component](/components/mqtt_eventstream/) and [mqttws31.js](http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git/tree/src).
|
||||
|
||||
The [HBMQTT](https://pypi.python.org/pypi/hbmqtt) broker provides websockets support for MQTT and mqttws31.js included in web page gives you access to the MQTT messages. It's a matter of minutes. OK, it took a little longer because I'm not a Javascript guy to create the software part that will show details about your environment. The source is available at [https://github.com/fabaff/home-assistant-display](https://github.com/fabaff/home-assistant-display) and the screenshot above shows the result. I guess that every person who is familiar with Javascript would be able to reduce the amount of code and to make it more flexible. Well, it's a only prototype and showcase to include an image in this blog post.
|
||||
|
||||
I hope that this little article could give you an idea of extending Home Assistant in an unconventional way.
|
||||
|
||||
|
|
@ -0,0 +1,56 @@
|
|||
---
|
||||
layout: post
|
||||
title: "0.17: Onkyo, Panasonic, GTFS and config validation"
|
||||
description: "Home Assistant 0.17 has arrived."
|
||||
date: 2016-04-08 23:10:00 -0700
|
||||
date_formatted: "April 9, 2016"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Release-Notes
|
||||
---
|
||||
|
||||
Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we've been hard at work to introduce config validation! Especially huge thanks to @jaharkes for his hard work on this. Config validation is still in it's early stages. More common platforms and components have been added but we didn't do everything yet.
|
||||
|
||||
When we encounter an invalid config we will now write a warning to your logs. You can see those in the frontend by clicking on the last developer tool. We're looking into options to make it more clear - it is a work in progress.
|
||||
|
||||
Another big thing is the addition of GTFS support. You probably don't know it, but GTFS is the standard that public transit companies all over the world use to distribute their schedule. This means that you can now have the time of the next bus/train/etc right in your frontend.
|
||||
|
||||
<img src='/images/supported_brands/onkyo.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/loop.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/panasonic.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' />
|
||||
|
||||
- Config validation ([@balloob], [@jaharkes])
|
||||
- Sensor: [GTFS] support (public transit open standard) ([@robbiet480])
|
||||
- Camera: [Raspberry PI] support added ([@LucaSoldi])
|
||||
- Z-Wave: improved startup reliability ([@srcLurker])
|
||||
- Media Player: [Onkyo receiver] now supported ([@danieljkemp])
|
||||
- Sensor: [Loop Energy] now supported ([@pavoni])
|
||||
- Thermostat: [Z-Wave] now supported ([@coteyr], [@turbokongen], [@luxus])
|
||||
- Sensor: [NZBGet] now supported ([@justyns])
|
||||
- Media Player: [Panasonic Viera TV] now supported ([@florianholzapfel])
|
||||
- Thermostats: Use whole degrees if user uses Fahrenheit ([@JshWright])
|
||||
- Frontend: more material love ([@balloob])
|
||||
|
||||
[@balloob]: https://github.com/balloob/
|
||||
[@coteyr]: https://github.com/coteyr/
|
||||
[@danieljkemp]: https://github.com/danieljkemp/
|
||||
[@florianholzapfel]: https://github.com/florianholzapfel/
|
||||
[@jaharkes]: https://github.com/jaharkes/
|
||||
[@JshWright]: https://github.com/JshWright/
|
||||
[@justyns]: https://github.com/justyns/
|
||||
[@LucaSoldi]: https://github.com/LucaSoldi/
|
||||
[@luxus]: https://github.com/luxus/
|
||||
[@pavoni]: https://github.com/pavoni/
|
||||
[@robbiet480]: https://github.com/robbiet480/
|
||||
[@srcLurker]: https://github.com/srcLurker/
|
||||
[@turbokongen]: https://github.com/turbokongen/
|
||||
[GTFS]: /components/sensor.gtfs/
|
||||
[Loop Energy]: /components/sensor.loop_energy/
|
||||
[NZBGet]: /components/sensor.nzbget/
|
||||
[Onkyo receiver]: /components/media_player.onkyo/
|
||||
[Panasonic Viera TV]: /components/media_player.panasonic_viera/
|
||||
[Raspberry PI]: /components/camera.rpi_camera/
|
||||
[Z-Wave]: /components/thermostat.zwave/
|
||||
|
||||
### Breaking changes
|
||||
|
||||
As of now we are not aware of any breaking changes. However, it might be that Home Assistant will not start for you because of an invalid configuration. A common mistake that people are making is that they are still referring to `execute_service` in their script configs. This should be `service`.
|
||||
|
|
@ -31,3 +31,9 @@ Upon first run, the z-wave component will take time to initialize entities and e
|
|||
The alternative to a stick is a hub that supports Z-Wave. Home Assistant supports the following hubs with Z-Wave support:
|
||||
|
||||
- [Vera](/components/vera/)
|
||||
|
||||
|
||||
## {% linkable_title Modifying Zwave Device Settings %}
|
||||
You may wish to modify the zwave settings ozw*.xml file in your .homeassistant root folder, or certain situations/devices may require it (i.e. Aeon Multisensor 6). To do this, utilize [Open-Zwave Control Panel](https://github.com/OpenZWave/open-zwave-control-panel). Alternatively, use [Domoticz](https://www.domoticz.com/), which incorporates the Open-Zwave Control Panel project into an easy to use Raspberry Pi image.
|
||||
|
||||
The reasoning for using these tools is that your Zwave controller stores the values and data that are used to control the network. The XML file in the .homeassistant folder acts as a settings/values cache for the zwave network, so modifying it directly won't change the network values. The Open-Zwave Control Panel writes values directly to the network, and will provide you with an updated .xml file to overwrite in your .homeassistant folder. This is the most foolproof way to make modifications to your zwave devices.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Home Assistant API"
|
||||
description: "Home Assistant API documentation"
|
||||
title: "Home Assistant API/SSE"
|
||||
description: "Home Assistant API/SSE documentation"
|
||||
date: 2015-05-11 12:00
|
||||
sidebar: false
|
||||
comments: false
|
||||
|
|
@ -9,8 +9,10 @@ sharing: true
|
|||
footer: true
|
||||
---
|
||||
|
||||
Home Assistant is offering a RESTful API and a Python API for convenient access to
|
||||
a Home Assistant instance over HTTP.
|
||||
Home Assistant is offering a RESTful API and a Python API for convenient access to a Home Assistant instance over HTTP.
|
||||
|
||||
- [RESTful API](/developers/rest_api/)
|
||||
- [Python API](/developers/python_api/)
|
||||
|
||||
There is also support for [server-sent events](/developers/server_sent_events).
|
||||
|
||||
|
|
|
|||
|
|
@ -13,13 +13,16 @@ Home Assistant is built from the ground up to be easily-extensible by other deve
|
|||
|
||||
Home Assistant is open-source and MIT licensed. The source can be found here:
|
||||
|
||||
- [home-assistant](https://github.com/balloob/home-assistant) - Python server-backend
|
||||
- [home-assistant-js](https://github.com/balloob/home-assistant-js) - javascript-backend powering the client
|
||||
- [home-assistant](https://github.com/balloob/home-assistant) - Python server backend
|
||||
- [home-assistant-js](https://github.com/balloob/home-assistant-js) - JavaScript backend powering the client
|
||||
- [home-assistant-polymer](https://github.com/balloob/home-assistant-polymer) - Polymer UI
|
||||
|
||||
### {% linkable_title Starting development %}
|
||||
|
||||
You will need to set up a development environment if you want to start developing a new feature or component for Home Assistant. Please follow these steps to perform it. Visit the [the Home Assistant repository](https://github.com/balloob/home-assistant) first and click fork in the top right.
|
||||
You will need to set up a development environment if you want to start developing a new feature or component for Home Assistant. Please follow these steps to get setup.
|
||||
Visit the [the Home Assistant repository](https://github.com/balloob/home-assistant) first and click fork in the top right.
|
||||
|
||||
We suggest that you setup a [virtual environment](https://docs.python.org/3.4/library/venv.html) aka `venv` before running the setup script.
|
||||
|
||||
```bash
|
||||
$ git clone https://github.com/YOUR_GIT_USERNAME/home-assistant.git
|
||||
|
|
@ -28,13 +31,17 @@ $ git remote add upstream https://github.com/balloob/home-assistant.git
|
|||
$ script/setup
|
||||
```
|
||||
|
||||
We suggest that you setup a [virtual environment](https://docs.python.org/3.4/library/venv.html) aka `venv` before running the setup script.
|
||||
Testing your work requires `tox` to be installed:
|
||||
|
||||
```bash
|
||||
$ pip3 install tox
|
||||
```
|
||||
|
||||
After following these steps, running `hass` will invoke your local installation.
|
||||
|
||||
### {% linkable_title Submitting improvements %}
|
||||
|
||||
Improvements to Home Assistant should be submitted one feature at a time using Github pull requests.
|
||||
Improvements to Home Assistant should be submitted one feature at a time using GitHub [pull requests](https://help.github.com/articles/using-pull-requests).
|
||||
|
||||
1. From your fork, create a new branch to hold your changes
|
||||
`git checkout -b some-feature`
|
||||
|
|
@ -44,15 +51,10 @@ Improvements to Home Assistant should be submitted one feature at a time using G
|
|||
4. Commit the changes
|
||||
`git add .`
|
||||
`git commit -m "Added some-feature"`
|
||||
5. Push your commited changes back to your fork on GitHub
|
||||
5. Push your committed changes back to your fork on GitHub
|
||||
`git push origin HEAD`
|
||||
6. Follow [these steps](https://help.github.com/articles/creating-a-pull-request/) to create your pull request.
|
||||
|
||||
Note that the above requires `tox` to be installed. If you don't have it, do this:
|
||||
|
||||
```bash
|
||||
$ pip3 install tox
|
||||
```
|
||||
|
||||
### {% linkable_title Further reading %}
|
||||
|
||||
|
|
@ -61,5 +63,6 @@ $ pip3 install tox
|
|||
- [Creating a custom component](/developers/creating_components/)
|
||||
- [Adding support for a new platform](/developers/add_new_platform/)
|
||||
- [Rest API](/developers/api/)
|
||||
- [Server-sent events](/developers/server_sent_events/)
|
||||
- [Website](/developers/website/)
|
||||
|
||||
|
|
|
|||
47
source/developers/server_sent_events.markdown
Normal file
47
source/developers/server_sent_events.markdown
Normal file
|
|
@ -0,0 +1,47 @@
|
|||
---
|
||||
layout: page
|
||||
title: "Server-sent events"
|
||||
description: "Home Assistant Server-sent events documentation"
|
||||
date: 2016-04-08 07:00
|
||||
sidebar: false
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
---
|
||||
|
||||
The [server-sent events](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events) feature is a one-way channel from your Home Assistant server to a client which is acting as a consumer. For bi-directional communication check the [RESTful API](/developers/rest_api/) and [Python API](/developers/python_api/).
|
||||
|
||||
The URI that is generating the data is `/api/stream`.
|
||||
|
||||
A requirement on the client-side is existing support for the [EventSource](https://developer.mozilla.org/en-US/docs/Web/API/EventSource) interface.
|
||||
|
||||
There are various ways to access the stream. One is `curl`:
|
||||
|
||||
```bash
|
||||
$ curl -X GET -H "x-ha-access: YOUR_PASSWORD" http://localhost:8123/api/stream
|
||||
```
|
||||
|
||||
For more comfort put the HTML snippet below in a file `sse.html` in your `www` folder of your Home Assistant configuration directory (`.homeassistant`)
|
||||
|
||||
```html
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<body>
|
||||
<h1>Getting Home Assistant server events</h1>
|
||||
<div id="events"></div>
|
||||
<script type="text/javascript">
|
||||
var source = new EventSource("/api/stream");
|
||||
source.onmessage = function(event) {
|
||||
document.getElementById("events").innerHTML += event.data + "<br>";
|
||||
};
|
||||
</script>
|
||||
</body>
|
||||
</html>
|
||||
```
|
||||
|
||||
Visit [https://localhost:8123/local/sse.html](https://localhost:8123/local/sse.html) to see the stream of events.
|
||||
|
||||
### {% linkable_title Example %}
|
||||
|
||||
The [home-assistant-sse](https://github.com/fabaff/home-assistant-sse) repository contains an more advanced example.
|
||||
|
||||
|
|
@ -9,19 +9,28 @@ sharing: true
|
|||
footer: true
|
||||
---
|
||||
|
||||
The home of Home Assistant is [https://home-assistant.io](https://home-assistant.io). This is the place where we provide documentation and additional details about Home Assistant for end users and developers.
|
||||
The website you're reading now is the home of Home Assistant: [https://home-assistant.io](https://home-assistant.io). This is the place where we provide documentation and additional details about Home Assistant for end users and developers.
|
||||
|
||||
home-assistant.io is using the [Octopress](http://octopress.org/) framework for [Jekyll](http://github.com/mojombo/jekyll). To get more details, please checkout the [documentation](http://octopress.org/docs/). That means that creating a new page is simple. The pages are written in [markdown](http://daringfireball.net/projects/markdown/), you don't need to care about HTML or alike.
|
||||
home-assistant.io uses the [Octopress](http://octopress.org/) framework for [Jekyll](http://github.com/mojombo/jekyll). To get more details, please checkout the [Octopress documentation](http://octopress.org/docs/).
|
||||
That means that creating a new page is simple. The pages are written in [markdown](http://daringfireball.net/projects/markdown/); you don't need to care about HTML or the like.
|
||||
|
||||
To work on the website the process is no different to working on Home Assistant itself.
|
||||
The process for working on the website is no different from working on Home Assistant itself.
|
||||
|
||||
- Fork the home-assistant.io [git repository](https://github.com/balloob/home-assistant.io).
|
||||
To test your changes locally, you need to install the **Ruby** dependencies (gems):
|
||||
|
||||
- [Install Ruby](https://www.ruby-lang.org/en/documentation/installation/) if you don't have it already.
|
||||
- Install `bundler`, which is a dependency manager for Ruby: `gem install bundler`
|
||||
- In your home-assistant.io root directory, run `bundle` to install the gems you need.
|
||||
|
||||
Then you can work on the documentation:
|
||||
|
||||
- Fork home-assistant.io [git repository](https://github.com/balloob/home-assistant.io).
|
||||
- Create/edit/update a page in the directory `source/_components/` for your platform/component.
|
||||
- To test changes to home-assistant.io locally, run ``rake preview`` and navigate to http://127.0.0.1:4000.
|
||||
- Test your changes to home-assistant.io locally: run ``rake preview`` and navigate to [http://127.0.0.1:4000](http://127.0.0.1:4000)
|
||||
- Create a Pull Request (PR) against the **next** branch of home-assistant.io if your documentation is for a new feature, platform, or component.
|
||||
- Create a Pull Request (PR) against the **master** branch of home-assistant.io if you fix stuff, create Cookbook entries, or expand existing documentation.
|
||||
|
||||
For a platform page it would be the fastest way to make a copy of an existing page and edit it. The [component overview](/components/) is generated automatically, so there is no need to add a link to that your page.
|
||||
For a platform page, the fastest way is to make a copy of an existing page and edit it. The [component overview](/components/) is generated automatically, so there is no need to add a link to your page.
|
||||
|
||||
### {% linkable_title Code %}
|
||||
To take advantage of the built-in features of Octopress to display code snippets, just use the default markdown syntax. Please use `$` and `#` if it's a command and to differ from output.
|
||||
|
|
@ -37,7 +46,7 @@ If you want to display line numbers, add the following snippet somewhere on your
|
|||
```
|
||||
|
||||
### {% linkable_title Images, icons, and logos %}
|
||||
The images which are displayed on the pages are stored in various directories according their purpose.
|
||||
The images which are displayed on the pages are stored in various directories according to their purpose.
|
||||
|
||||
| Type | Location |
|
||||
| :----------- |:----------------------------------------------|
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ footer: true
|
|||
<label class='menu-selector synology' for='synology-install'>Synology NAS</label>
|
||||
|
||||
<div class='advanced-installs upstart' markdown='1'>
|
||||
Many linux distributions use the Upstart system (or similar) for managing daemons. Typically, systems based on Debian 7 or previous use Upstart. This includes Ubuntu releases before 15.04 and all current Raspian releases. If you are unsure if your system is using Upstart, you may check with the following command:
|
||||
Many linux distributions use the Upstart system (or similar) for managing daemons. Typically, systems based on Debian 7 or previous use Upstart. This includes Ubuntu releases before 15.04. If you are unsure if your system is using Upstart, you may check with the following command:
|
||||
|
||||
```bash
|
||||
$ ps -p 1 -o comm=
|
||||
|
|
|
|||
|
|
@ -9,26 +9,82 @@ sharing: true
|
|||
footer: true
|
||||
---
|
||||
|
||||
Home Assistant will create a configuration folder when it is run for the first time. The location of the folder differs between operating systems: on OS X/Linux it's `~/.homeassistant` and on Windows it's `%APPDATA%/.homeassistant`. If you want to use a different folder for configuration, run `hass --config path/to/config`.
|
||||
Home Assistant will create a configuration folder when it is run for the first time. The location of the folder differs between operating systems: on OS X and Linux it's `~/.homeassistant` and on Windows it's `%APPDATA%/.homeassistant`. If you want to use a different folder for configuration, run `hass --config path/to/config`.
|
||||
|
||||
Inside your configuration folder is the file `configuration.yaml`. This is the main file that contains which components will be loaded and what their configuration is.
|
||||
This file contains YAML code, which is explained briefly in [the configuration troubleshooting page](/getting-started/troubleshooting-configuration/). An example configuration file is located [here](https://github.com/balloob/home-assistant/blob/master/config/configuration.yaml.example).
|
||||
This file contains YAML code, which is explained briefly below.
|
||||
[An example configuration file is located here](https://github.com/balloob/home-assistant/blob/master/config/configuration.yaml.example).
|
||||
|
||||
When launched for the first time, Home Assistant will write a default configuration enabling the web interface and device discovery. It can take up to a minute for your devices to be discovered and show up in the interface.
|
||||
When launched for the first time, Home Assistant will write a default configuration file enabling the web interface and device discovery. It can take up to a minute for your devices to be discovered and show up in the user interface.
|
||||
|
||||
If you run into trouble while configuring Home Assistant, have a look at [the configuration troubleshooting page](/getting-started/troubleshooting-configuration/).
|
||||
|
||||
|
||||
<p class='note'>
|
||||
You will have to restart Home Assistant for changes in <code>configuration.yaml</code> to take effect.
|
||||
You will have to restart Home Assistant each time you make changes in <code>configuration.yaml</code> in order for these to take effect.
|
||||
</p>
|
||||
|
||||
### {% linkable_title YAML %}
|
||||
|
||||
Home Assistant uses the [YAML](http://yaml.org/) syntax for configuration. YAML might take a while to get used to but is really powerful in allowing you to express complex configurations.
|
||||
|
||||
For each component that you want to use in Home Assistant, you add code in your `configuraton.yaml` file to specify its settings.
|
||||
Example, the following code specifies that you want to use the [notify component](/components/notify) with the [pushbullet platform](/components/notify.pushbullet).
|
||||
|
||||
|
||||
```yaml
|
||||
notify:
|
||||
platform: pushbullet
|
||||
api_key: "o.1234abcd"
|
||||
name: pushbullet
|
||||
```
|
||||
|
||||
- A **component** provides the core logic for some functionality (like `notify` provides sending notifications).
|
||||
- A **platform** makes the connection to a specific software or hardware platform (like `pushbullet` works with the service from pushbullet.com).
|
||||
|
||||
The basics of YAML syntax are block collections and mappings containing key-value pairs.
|
||||
Each item in a collection starts with a `-` while mappings have the format `key: value`. If you specify duplicate keys, the last value for a key is used.
|
||||
|
||||
Note that indentation is an important part of specifying relationships using YAML. Things that are indented are nested "inside" things that are one level higher. So in the above example, `platform: pushbullet` is a property of (nested inside) the `notify` component.
|
||||
Getting the right indentation can be tricky if you're not using an editor with a fixed width font. Tabs are not allowed to be used for indentation. Convention is to use 2 spaces for each level of indentation.
|
||||
|
||||
Lines that start with **#** are comments and are ignored by the system.
|
||||
|
||||
The next example shows an [input_select](/components/input_select) component that uses a block collection for the options values.
|
||||
The other properties (like name) are specified using mappings. Note that the second line just has `threat:` with no value on the same line. Here threat is the name of the input_select and the values for it are everything nested below it.
|
||||
|
||||
```yaml
|
||||
input_select:
|
||||
threat:
|
||||
name: Threat level
|
||||
# A collection is used for options
|
||||
options:
|
||||
- 0
|
||||
- 1
|
||||
- 2
|
||||
- 3
|
||||
initial: 0
|
||||
```
|
||||
|
||||
The following example shows nesting a collection of mappings in a mapping.
|
||||
In Home Assistant, this would create two sensors that each use the MQTT platform but have different values for their `state_topic` (one of the properties used for MQTT sensors).
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
- platform: mqtt
|
||||
state_topic: sensor/topic
|
||||
- platform: mqtt
|
||||
state_topic: sensor2/topic
|
||||
```
|
||||
|
||||
|
||||
### {% linkable_title Setting up the basic info %}
|
||||
|
||||
By default Home Assistant will try to detect your location and will automatically select a temperature unit and time zone based on your location. You can overwrite this by adding the following information to your `configuration.yaml`:
|
||||
|
||||
```yaml
|
||||
homeassistant:
|
||||
# Omitted values in this section will be auto detected using freegeoip.net
|
||||
# Omitted values in this section will be auto detected using freegeoip.io
|
||||
|
||||
# Location required to calculate the time the sun rises and sets
|
||||
latitude: 32.87336
|
||||
|
|
@ -47,7 +103,7 @@ homeassistant:
|
|||
|
||||
### {% linkable_title Password protecting the web interface %}
|
||||
|
||||
The first thing you want to add is a password for the web interface. Use your favourite text editor to open the file `/config/configuration.yaml` and add the following to the `http` section:
|
||||
The first thing you will want to add is a password for the web interface. Use your favourite text editor to open `configuration.yaml` and edit the `http` section:
|
||||
|
||||
```yaml
|
||||
http:
|
||||
|
|
@ -68,4 +124,6 @@ To make Home Assistant accessible while away from home, you will have to setup p
|
|||
|
||||
Some Internet service providers will only offer dynamic IPs. This can cause you to be unable to access Home Assistant while away. You can solve this by using a free Dynamic DNS service like [DuckDNS](https://www.duckdns.org/).
|
||||
|
||||
You should definitely consider to encrypt your traffic if you are accessing your Home Assistant installation from abroad. For details please check the [Set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post.
|
||||
|
||||
### [Next step: Setting up devices »](/getting-started/devices/)
|
||||
|
|
|
|||
|
|
@ -39,6 +39,12 @@ If you prefer to watch a video tutorial, [tktino](https://github.com/tktino) has
|
|||
- [Mac OS X](https://www.youtube.com/watch?v=hej6ipN86ls)
|
||||
- [Ubuntu 14.04](https://www.youtube.com/watch?v=SXaAG1lGNH0)
|
||||
|
||||
### {% linkable_title Updating %}
|
||||
|
||||
To update Home Assistant to the latest release when available, run: `pip3 install --upgrade homeassistant`
|
||||
|
||||
You have to restart Home Assistant (`hass` itself or with the help of the autostarting daemon if you use any) for the changes to take effect.
|
||||
|
||||
</div> <!-- INSTALL-INSTRUCTIONS NORMAL -->
|
||||
|
||||
|
||||
|
|
@ -77,6 +83,11 @@ Running these commands will:
|
|||
|
||||
There is also a [video tutorial](https://www.youtube.com/watch?v=GjzOXkPb7XE) created by [brusc](https://github.com/brusc).
|
||||
|
||||
### {% linkable_title Updating %}
|
||||
|
||||
To update Home Assistant to the latest release when available, run: `pip3 install --upgrade homeassistant`
|
||||
|
||||
You have to restart Home Assistant (`hass` itself or with the help of the autostarting daemon if you use any) for the changes to take effect.
|
||||
|
||||
</div> <!-- INSTALL-INSTRUCTIONS RASPBERRY -->
|
||||
|
||||
|
|
@ -278,21 +289,15 @@ $ python3/pip3 install --upgrade homeassistant
|
|||
|
||||
If you run into any issues, please see [the troubleshooting page](/getting-started/troubleshooting/). It contains solutions to many of the more commonly encountered issues.
|
||||
|
||||
For additional help, in addition to this site, there are four sources:
|
||||
In addition to this site, check out these sources for additional help:
|
||||
|
||||
- [Forum](https://community.home-assistant.io/)
|
||||
- [Gitter Chatroom](https://gitter.im/balloob/home-assistant) for general Home Assistant discussions and questions.
|
||||
- [Forum](https://community.home-assistant.io) for Home Assistant discussions and questions.
|
||||
- [Gitter Chat Room](https://gitter.im/balloob/home-assistant) for real-time chat about Home Assistant.
|
||||
- [GitHub Page](https://github.com/balloob/home-assistant/issues) for issue reporting.
|
||||
|
||||
### {% linkable_title Updating %}
|
||||
|
||||
To update Home Assistant to the latest release run: `pip3 install --upgrade homeassistant`
|
||||
|
||||
You have to restart Home Assistant (`hass` itself or with the help of the autostarting daemon if you use any) for the changes to take effect.
|
||||
|
||||
### {% linkable_title What's next %}
|
||||
|
||||
If you want to have Home Assistant start on boot, autostart instructions can be found [here](/getting-started/autostart/).
|
||||
If you want to have Home Assistant start on boot, [autostart instructions can be found here](/getting-started/autostart/).
|
||||
|
||||
To see what Home Assistant can do, launch demo mode: `hass --demo-mode` or visit the [demo page](/demo).
|
||||
|
||||
|
|
|
|||
|
|
@ -15,49 +15,17 @@ Before we dive into common issues, make sure you know where your configuration d
|
|||
|
||||
Whenever a component or configuration option results in a warning, it will be stored in `home-assistant.log` in the configuration directory. This file is reset on start of Home Assistant.
|
||||
|
||||
### {% linkable_title YAML %}
|
||||
|
||||
Home Assistant uses the [YAML](http://yaml.org/) syntax for configuration. YAML can be confusing to start with but is really powerful in allowing you to express complex configurations.
|
||||
|
||||
The basics of YAML are block collections and mappings containing key-value pairs. Collections will have each item start with a `-` while mappings will have the format `key: value`. The last value for a key is used in case you specify a duplicate key.
|
||||
Note that the indentation is an important part of specifying relationships using YAML.
|
||||
|
||||
```yaml
|
||||
# A collection
|
||||
- hello
|
||||
- how
|
||||
- are
|
||||
- you
|
||||
|
||||
# Lookup mapping
|
||||
beer: ice cold # <-- will be ignored because key specified twice
|
||||
beer: warm
|
||||
wine: room temperature
|
||||
water: cold
|
||||
|
||||
# Nesting mappings (note the indentation)
|
||||
device_tracker:
|
||||
platform: mqtt
|
||||
|
||||
# Nesting a collection of mappings in a mapping
|
||||
sensor:
|
||||
- platform: mqtt
|
||||
state_topic: sensor/topic
|
||||
- platform: mqtt
|
||||
state_topic: sensor2/topic
|
||||
```
|
||||
|
||||
Indentation is used to specify which objects are nested under one another. Getting the right indentation can be tricky if you're not using an editor with a fixed width font. Tabs are not allowed to be used for indentation.
|
||||
|
||||
- To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack.
|
||||
- You can test your configuration using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/).
|
||||
|
||||
### {% linkable_title My component does not show up %}
|
||||
|
||||
When a component does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the `home-assistant.log` file and see if there are any errors related to your component you are trying to set up.
|
||||
|
||||
#### {% linkable_title Problems with the configuration %}
|
||||
|
||||
One of the most common problems with Home Assistant is an invalid `configuration.yaml` file.
|
||||
|
||||
- You can test your configuration using [this online YAML parser](http://yaml-online-parser.appspot.com/) or [YAML Lint](http://www.yamllint.com/).
|
||||
- To learn more about the quirks of YAML, read [YAML IDIOSYNCRASIES](https://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html) by SaltStack (the examples there are specific to SaltStack, but do explain YAML issues well).
|
||||
|
||||
`configuration.yaml` does not allow multiple sections to have the same name. If you want a specific platform to be loaded twice, append a [number or string](/getting-started/devices/#style-2) to the name or nest them using [this style](/getting-started/devices/#style-1).
|
||||
|
||||
```yaml
|
||||
|
|
@ -92,7 +60,7 @@ If you are using multiple files for your setup, make sure that the pointers are
|
|||
light: !include devices/lights.yaml
|
||||
sensor: !include devices/sensors.yaml
|
||||
```
|
||||
Contents of `lights.yaml`:
|
||||
Contents of `lights.yaml` (notice it does not contain `light: `):
|
||||
|
||||
```yaml
|
||||
- platform: hyperion
|
||||
|
|
|
|||
|
|
@ -15,10 +15,12 @@ There are various ways to get in touch with the Home Assistant community. It doe
|
|||
|
||||
- [Forum](https://community.home-assistant.io/)
|
||||
- [Gitter Chatroom](https://gitter.im/balloob/home-assistant) for general Home Assistant discussions and questions.
|
||||
- Follow us on [Twitter](https://twitter.com/home_assistant), use @home_assistant
|
||||
- Join the [Google+ community](https://plus.google.com/u/0/b/110560654828510104551/communities/106562234893511202708)
|
||||
|
||||
### {% linkable_title Bugs, Feature requests, and alike %}
|
||||
|
||||
Have you found an issue in your Home Assistant installation? Please report it in one of the issue trackers. Reporting it there makes it easier to track than in the Mailing list and ensures that it gets fixed.
|
||||
Have you found an issue in your Home Assistant installation? Please report it in one of the issue trackers. Reporting it there makes it easy to track and ensures that it gets fixed.
|
||||
|
||||
- [Issue tracker Home Assistant](https://github.com/balloob/home-assistant/issues)
|
||||
- [Issue tracker home-assistant.io](https://github.com/balloob/home-assistant.io/issues) (Website and documentation)
|
||||
|
|
|
|||
BIN
source/images/blog/2016-04-display/ha-display.png
Normal file
BIN
source/images/blog/2016-04-display/ha-display.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
Loading…
Add table
Add a link
Reference in a new issue