-There is currently a known issue with running this platform on a 64-bit version of Python. +There is currently a known issue with running this platform on a 64-bit version of Python and Windows.
If you are on Windows and you're using Python 3.5, download the Netifaces dependency here.
+ ++If you see `Not initializing discovery because could not install dependency netdisco==0.6.1` in the logs, you will need to install the `python3-dev` or `python3-devel` package on your system manually (eg. `sudo apt-get install python3-dev` or `sudo dnf -y install python3-devel`). On the next restart of home-assistant, discovery should work. If you still get an error, check if you have a compiler (`gcc`) available on your system. +
diff --git a/source/_components/garage_door.wink.markdown b/source/_components/garage_door.wink.markdown index 091f0584557..85fc8e388d1 100644 --- a/source/_components/garage_door.wink.markdown +++ b/source/_components/garage_door.wink.markdown @@ -11,8 +11,15 @@ logo: wink.png ha_category: Garage Door --- +Wink garage door functionality is currently limited to view only. Wink garage doors will still show the current state of the door, but control has been disabled for third parties. If you have a Chamberlain garage door, and would like to control it via Home Assistant, please contact Chamberlain and request that they re-enabled third-party control. -The Wink garage door platform allows you to control your [Wink](http://www.wink.com/) enabled garage door. +The following quote is from Wink. + ++As part of our agreement with Chamberlain, third-party access to control Chamberlain garage doors has been restricted. Please contact Chamberlain directly to inquire about permissions. ++ +~~The Wink garage door platform allows you to control your [Wink](http://www.wink.com/) enabled garage door.~~ The requirement is that you have setup your [Wink hub](/components/wink/). diff --git a/source/_components/http.markdown b/source/_components/http.markdown index e66976ca8d5..3490451a05d 100644 --- a/source/_components/http.markdown +++ b/source/_components/http.markdown @@ -31,10 +31,12 @@ Configuration variables: - **ssl_certificate** (*Optional*): Path to your TLS/SSL certificate to serve Home Assistant over a secure connection. - **ssl_key** (*Optional*): Path to your TLS/SSL key to serve Home Assistant over a secure connection. -On top of the `http` component is a [REST API](/developers/rest_api/) and a [Python API](/developers/python_api/) available. +The [Set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post gives you details about the encryption of your traffic using free certificates from [Let's Encrypt](https://letsencrypt.org/). + +On top of the `http` component is a [REST API](/developers/rest_api/) and a [Python API](/developers/python_api/) available. There is also support for [Server-sent events](/developers/server_sent_events/) available. The `http` platforms are not real platforms within the meaning of the terminology used around Home Assistant. Home Assistant's [REST API](/developers/rest_api/) sends and receives messages over HTTP. -To use those kind of sensors in your installation no configuration in Home Assistant is needed. All configuration is done on the devices themselves. This means that you must be able to edit the target URL or endpoint and the payload. The entity will be created after the first message has arrived. +To use those kind of [sensors](/components/sensor.http/) or [binary sensors](components/binary_sensor.http/) in your installation no configuration in Home Assistant is needed. All configuration is done on the devices themselves. This means that you must be able to edit the target URL or endpoint and the payload. The entity will be created after the first message has arrived. All [requests](/developers/rest_api/#post-apistatesltentity_id) need to be sent to the endpoint of the device and must be **POST**. diff --git a/source/_components/input_select.markdown b/source/_components/input_select.markdown index b8e574b91f8..dd626c689d6 100644 --- a/source/_components/input_select.markdown +++ b/source/_components/input_select.markdown @@ -11,7 +11,7 @@ logo: home-assistant.png ha_category: Automation --- -The `input_select` component allows the user to define a list of values that can be selected via the frontend and can be used within conditions of automation. +The `input_select` component allows the user to define a list of values that can be selected via the frontend and can be used within conditions of automation. When a user selectes a new item, a state transition event is generated. This state event can be used in an `automation` trigger. To enable this platform, add the following lines to your `configuration.yaml`: diff --git a/source/_components/input_slider.markdown b/source/_components/input_slider.markdown index 5fd9d136c42..9cd341aac9e 100644 --- a/source/_components/input_slider.markdown +++ b/source/_components/input_slider.markdown @@ -11,7 +11,7 @@ logo: home-assistant.png ha_category: Automation --- -The `input_slider` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. +The `input_slider` component allows the user to define values that can be controlled via the frontend and can be used within conditions of automation. Changes to the slider generate state events. These state events can be utilized as `automation` triggers as well. ```yaml # Example configuration.yaml entry @@ -21,6 +21,7 @@ input_slider: initial: 30 min: -20 max: 35 + step: 1 ``` Configuration variables: @@ -30,4 +31,5 @@ Configuration variables: - **initial** (*Optional*): Initial value when Home Assistant starts. - **min** (*Optional*): Minimum value for the slider. - **max** (*Optional*): Maximum value for the slider. +- **step** (*Optional*): Step value for the slider. diff --git a/source/_components/light.markdown b/source/_components/light.markdown index 56f078f65e3..c544d7d9af0 100644 --- a/source/_components/light.markdown +++ b/source/_components/light.markdown @@ -11,7 +11,7 @@ footer: true This component allows you to track and control various light bulbs. -It has [4 built-in light profiles](https://github.com/balloob/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) which you're able to extend by putting a `light_profiles.csv` file in your config dir. +It has [4 built-in light profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) which you're able to extend by putting a `light_profiles.csv` file in your config dir. Preferred way to setup the Philips Hue platform is through the [the discovery component]({{site_root}}/components/discovery/). For the Wink light platform enable [the wink component]({{site_root}}/components/wink/). diff --git a/source/_components/light.mysensors.markdown b/source/_components/light.mysensors.markdown index f6a74f40f8b..92b06ce9673 100644 --- a/source/_components/light.mysensors.markdown +++ b/source/_components/light.mysensors.markdown @@ -2,7 +2,7 @@ layout: page title: "MySensors Light" description: "Instructions how to integrate MySensors lights into Home Assistant." -date: 2016-03-02 18:20 +0100 +date: 2016-04-13 14:20 +0100 sidebar: true comments: false sharing: true @@ -33,5 +33,80 @@ V_TYPES with a star (\*) denotes required V_TYPES. Use either V_LIGHT or V_STATU For more information, visit the [serial api] of MySensors. +### {% linkable_title Example sketch %} + +```cpp +/* + * Documentation: http://www.mysensors.org + * Support Forum: http://forum.mysensors.org + * + * http://www.mysensors.org/build/dimmer + */ + +#include
-Some users are experiencing errors loading the frontend while using this platform. -
- The `yamaha` platform allows you to control [Yamaha Network Receivers](http://usa.yamaha.com/products/audio-visual/av-receivers-amps/rx) from Home Assistant. Supported devices: diff --git a/source/_components/mysensors.markdown b/source/_components/mysensors.markdown index 247cffe102a..21c23469150 100644 --- a/source/_components/mysensors.markdown +++ b/source/_components/mysensors.markdown @@ -2,7 +2,7 @@ layout: page title: "MySensors" description: "Instructions how to integrate MySensors sensors into Home Assistant." -date: 2016-02-18 20:13 +0100 +date: 2016-04-13 14:20 +0100 sidebar: true comments: false sharing: true @@ -31,7 +31,7 @@ mysensors: debug: true persistence: true version: '1.5' - optimistic: 'true' + optimistic: false ``` Configuration variables: diff --git a/source/_components/notify.markdown b/source/_components/notify.markdown index d475db0cb2c..2cd525cb2b7 100644 --- a/source/_components/notify.markdown +++ b/source/_components/notify.markdown @@ -35,9 +35,17 @@ Once loaded, the `notify` platform will expose a service that can be called to s | `title` | yes | Title of the notification. Default is `Home Assistant`. | `target` | yes | Some platforms will allow specifying a recipient that will receive the notification. See your platform page if it is supported. -The notification component supports specifying [templates] for both the `message` and the `title`. This will allow you to use the current state of Home Assistant in your notifications. +The notification component supports specifying [templates](/topics/templating/) for both the `message` and the `title`. This will allow you to use the current state of Home Assistant in your notifications. -[templates]: /topics/templating/ +In an [action](https://home-assistant.io/components/automation/#actions) of your [automation setup](/components/automation/) it could look like this with a customized subject. + +```yaml +action: + service: notify.notify + data: + message: "Your message goes here" + title: "Custom subject" +``` ### {% linkable_title Test if it works %} diff --git a/source/_components/notify.xmpp.markdown b/source/_components/notify.xmpp.markdown index f410411d006..0f51aa9ca88 100644 --- a/source/_components/notify.xmpp.markdown +++ b/source/_components/notify.xmpp.markdown @@ -22,6 +22,7 @@ notify: sender: YOUR_JID password: YOUR_JABBER_ACCOUNT_PASSWORD recipient: YOUR_RECIPIENT + tls: False ``` Configuration variables: @@ -29,7 +30,8 @@ Configuration variables: - **name** (*Optional*): Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`. - **sender** (*Required*): The Jabber ID (JID) that will act as origin of the messages. Add your JID including the domain, eg. your_name@jabber.org. - **password** (*Required*): The password for your given Jabber account. -- **priority** (*Required*): The Jabber ID (JID) that will receive the messages. +- **recipient** (*Required*): The Jabber ID (JID) that will receive the messages. +- **tls** (*Optional*): Allow to disable TLS. Defaults to true. All Jabber IDs (JID) must include the domain. Make sure that the password matches the account provided as sender. diff --git a/source/_components/sensor.dweet.markdown b/source/_components/sensor.dweet.markdown index 304fcffa282..5d20971bf49 100644 --- a/source/_components/sensor.dweet.markdown +++ b/source/_components/sensor.dweet.markdown @@ -21,7 +21,7 @@ sensor: platform: dweet name: Dweet.io Temperature device: THING_NAME - value_template: '{{ value_json.VARIABLE }}' + value_template: '{% raw %}{{ value_json.VARIABLE }}{% endraw %}' unit_of_measurement: "°C" ``` diff --git a/source/_components/sensor.loop_energy.markdown b/source/_components/sensor.loop_energy.markdown index d7800d4eb0e..df3e1d6c45f 100644 --- a/source/_components/sensor.loop_energy.markdown +++ b/source/_components/sensor.loop_energy.markdown @@ -26,7 +26,7 @@ You can then open your browser's console window, how you do this varies by brows This should show something like -```javascript +```yaml client_ip: "127.0.0.1" gas_secret: "GAS_SECRET" gas_serial: "GAS_SERIAL" @@ -44,8 +44,8 @@ Now you have the keys, add the following lines to your `configuration.yaml`, rep # Example configuration.yaml entry sensor: platform: loopenergy - electricity_serial: ELECRITCAL_SERIAL - electricity_secret: ELECTRICAL_OFFSET + electricity_serial: ELECTRICAL_SERIAL + electricity_secret: ELECTRICAL_SECRET gas_serial: GAS_SERIAL gas_secret: GAS_SECRET gas_type: metric @@ -63,3 +63,4 @@ Configuration variables: The electricity readings are updated every 10 seconds and the gas readings every 15 minutes. +The gas readings are experimental and not all gas meters are properly supported - so if the data you see doesn't agree with the readings you see via loop energy please report an issue. diff --git a/source/_components/sensor.mysensors.markdown b/source/_components/sensor.mysensors.markdown index 2b1c709c59f..9690ece312b 100644 --- a/source/_components/sensor.mysensors.markdown +++ b/source/_components/sensor.mysensors.markdown @@ -2,7 +2,7 @@ layout: page title: "MySensors Sensor" description: "Instructions how to integrate MySensors sensors into Home Assistant." -date: 2016-02-28 01:20 +0100 +date: 2016-04-13 14:20 +0100 sidebar: true comments: false sharing: true @@ -58,5 +58,53 @@ By using V_UNIT_PREFIX, it's possible to set a custom unit for any sensor. The s For more information, visit the [serial api] of MySensors. +### {% linkable_title Example sketch %} + +```cpp +/** + * Documentation: http://www.mysensors.org + * Support Forum: http://forum.mysensors.org + * + * http://www.mysensors.org/build/light + */ + +#include