mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 15:26:59 +00:00
0.24 (#637)
* Persistant changed to persistent * Added log_attributes to the config documentation for statsd (#625) * Fix AsusWRT docs to prevent SSH key confusion (#623) pxssh is expecting the path to a private key, not a public key * add yahoo weather support (#621) * add yahoo weather * update with woeid not longer required * Doc for simplisafe alarm (#613) * Minor fixes * Rename the blog post for 0.24 * Initial blog post for 0.24 * Update sensor.apcupsd docs to reflect changes (#617) * Update sensor.apcupsd docs to reflect changes * Remove "type:" from configuration * Add apcupsd sensor breaking change * Added samsung models to the list of supported Samsung Smart TV's (#630) * Add IMAP sensor docs * Add IMAP sensor * add joaoapps join component and platform. (#633) * Add join * Added documentation of the KNX component (#611) * Added set_brightness to website docs. (#582) * Added configuration for card order to customize docs * Added configuration options to docs for the set_brightness command. * Revert "Added configuration for card order to customize docs" This reverts commit bd310fbd115c76bc49d994fff4ff3e1a0d0e9540. * Add new contributors * Add TP-Link smart plug docs * Sync with PR * update service (#634) * Move KNX docs to right folder * Fix typos and layout * Add missing KNX logo * Fix logo name * Fix category * Revert "Added set_brightness to website docs." (#636) * Add initial KNX docs for binary sensors and switches * Update title, desc, and date * Rename blog post * Update for 0.24 * pyhomematic update 0.1.9 * add example * Example config (#638) * Added dynamic entity tracking documentation (#641) * Change ordering * Added dynamic entity tracking documentation * Add more details * Add sqlalchemy as dep * Add various db_url * Added bah2830 configuration (#644) * update media_player.markdown (#643) * Rename release blog post * Add CARTO * Hide sensor.imap until stable * Typo edits (#642) * Update demo * Minor tweaking * Add additional example * Add simple example for renaming * Make it raw * Update camera.rpi_camera.markdown (#537) * Add link to binary version * Fix indent * Minor change for #537 * Update date
This commit is contained in:
Fabian Affolter
GitHub
parent
a0c4d4bf45
commit
034c831324
35
source/_components/alarm_control_panel.simplisafe.markdown
Normal file
35
source/_components/alarm_control_panel.simplisafe.markdown
Normal file
@ -0,0 +1,35 @@
|
|||||||
|
---
|
||||||
|
layout: page
|
||||||
|
title: "SimpliSafe Alarm Control Panel"
|
||||||
|
description: "Instructions how to integrate SimpliSafe into Home Assistant."
|
||||||
|
date: 2016-07-02 22:00
|
||||||
|
sidebar: true
|
||||||
|
comments: false
|
||||||
|
sharing: true
|
||||||
|
footer: true
|
||||||
|
logo: simplisafe.png
|
||||||
|
ha_release: 0.24
|
||||||
|
ha_category: Alarm
|
||||||
|
---
|
||||||
|
|
||||||
|
The `simplisafe` platform enables the ability to control a SimpliSafe control panel. [simplisafe.com](http://simplisafe.com/).
|
||||||
|
|
||||||
|
To enable this, add the following lines to your `configuration.yaml`:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
# Example configuration.yaml entry
|
||||||
|
alarm_control_panel:
|
||||||
|
platform: simplisafe
|
||||||
|
name: "HA Alarm"
|
||||||
|
code: PASSCODE
|
||||||
|
username: YOUR_USERNAME
|
||||||
|
password: YOUR_PASSWORD
|
||||||
|
```
|
||||||
|
|
||||||
|
Configuration variables:
|
||||||
|
|
||||||
|
- **username** (*Required*): Username for the SimpliSafe account.
|
||||||
|
- **password** (*Required*): Password for SimpliSafe account.
|
||||||
|
- **name** (*Optional*): The name of the alarm. Default is the SimpliSafe alarm id.
|
||||||
|
- **code** (*Optional*): Specifies a code to enable or disable the alarm in the frontend.
|
||||||
|
|
||||||
15
source/_components/binary_sensor.knx.markdown
Normal file
15
source/_components/binary_sensor.knx.markdown
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
---
|
||||||
|
layout: page
|
||||||
|
title: "KNX Binary Sensor"
|
||||||
|
description: "Instructions how to setup the KNX binary sensors within Home Assistant."
|
||||||
|
date: 2016-07-13 07:00
|
||||||
|
sidebar: true
|
||||||
|
comments: false
|
||||||
|
sharing: true
|
||||||
|
footer: true
|
||||||
|
logo: zknx.png
|
||||||
|
ha_category: Binary Sensor
|
||||||
|
ha_release: 0.24
|
||||||
|
---
|
||||||
|
|
||||||
|
To get your KNX binary sensors working with Home Assistant, follow the instructions for the [KNX component](/components/knx/).
|
||||||
@ -34,8 +34,8 @@ Configuration variables:
|
|||||||
- **protocol** (*Optional*): The protocol (`ssh` or `telnet`) to use. Defaults to `ssh`.
|
- **protocol** (*Optional*): The protocol (`ssh` or `telnet`) to use. Defaults to `ssh`.
|
||||||
- **mode** (*Optional*): The operating mode of the router (`router` or `ap`). Defaults to `router`.
|
- **mode** (*Optional*): The operating mode of the router (`router` or `ap`). Defaults to `router`.
|
||||||
- **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
|
- **username** (*Required*: The username of an user with administrative privileges, usually *admin*.
|
||||||
- **password** (*Optional*): The password for your given admin account (use this if no public key is given).
|
- **password** (*Optional*): The password for your given admin account (use this if no SSH key is given).
|
||||||
- **pub_key** (*Optional*): The public key for your given admin account (instead of password).
|
- **ssh_key** (*Optional*): The path to your SSH private key file associated with your given admin account (instead of password).
|
||||||
|
|
||||||
<p class='note warning'>
|
<p class='note warning'>
|
||||||
You need to enable telnet on your router if you choose to use `protocol: telnet`.
|
You need to enable telnet on your router if you choose to use `protocol: telnet`.
|
||||||
|
|||||||
@ -44,7 +44,7 @@ Configuration variables:
|
|||||||
- **local_ip** (*Required*): IP of device running Home Assistant
|
- **local_ip** (*Required*): IP of device running Home Assistant
|
||||||
- **local_port** (*Optional*): Port for connection with Home Assistant. Defaults to 8943.
|
- **local_port** (*Optional*): Port for connection with Home Assistant. Defaults to 8943.
|
||||||
- **remote_ip** (*Required*): IP of CCU/Homegear
|
- **remote_ip** (*Required*): IP of CCU/Homegear
|
||||||
- **remote_port** (*Required*): Port of Homegear/CCU XML-RPC Server (usually 2001)
|
- **remote_port** (*Optional*): Port of Homegear/CCU XML-RPC Server (usually 2001)
|
||||||
- **resolvenames** (*Optional*): <metadata, json, xml> Try to fetch device names. Defaults to `False` if not specified.
|
- **resolvenames** (*Optional*): <metadata, json, xml> Try to fetch device names. Defaults to `False` if not specified.
|
||||||
- **username** (*Optional*): When fetching names via JSON-RPC, you need to specify a user with guest-access to the CCU.
|
- **username** (*Optional*): When fetching names via JSON-RPC, you need to specify a user with guest-access to the CCU.
|
||||||
- **password** (*Optional*): When fetching names via JSON-RPC, you need to specify the password of the user you have configured above.
|
- **password** (*Optional*): When fetching names via JSON-RPC, you need to specify the password of the user you have configured above.
|
||||||
@ -83,3 +83,23 @@ automation:
|
|||||||
|
|
||||||
The channel parameter is equal to the channel of the button you are configuring the automation for. You can view the available channels in the UI you use to pair your devices.
|
The channel parameter is equal to the channel of the button you are configuring the automation for. You can view the available channels in the UI you use to pair your devices.
|
||||||
The name depends on if you chose to resolve names or not. If not, it will be the device ID (e.g. LEQ1234657). If you chose to resolve names (and that is successful), it will be the name you have set in your CCU or in the metadata (e.g. "Kitchen Switch").
|
The name depends on if you chose to resolve names or not. If not, it will be the device ID (e.g. LEQ1234657). If you chose to resolve names (and that is successful), it will be the name you have set in your CCU or in the metadata (e.g. "Kitchen Switch").
|
||||||
|
|
||||||
|
**Other events**
|
||||||
|
|
||||||
|
*homematic.keypress* see above.
|
||||||
|
*homematic.impulse* for impulse sensors with event_data 'name' and 'channel'.
|
||||||
|
|
||||||
|
**Service**
|
||||||
|
|
||||||
|
*homematic/virtualkey* simulate a keypress on CCU/Homegear with device or virtual keys.
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
...
|
||||||
|
|
||||||
|
action:
|
||||||
|
service: homematic.virtualkey
|
||||||
|
data:
|
||||||
|
address: BidCoS-RF
|
||||||
|
channel: 1
|
||||||
|
param: PRESS_LONG
|
||||||
|
```
|
||||||
|
|||||||
51
source/_components/joaoapps_join.markdown
Normal file
51
source/_components/joaoapps_join.markdown
Normal file
@ -0,0 +1,51 @@
|
|||||||
|
---
|
||||||
|
layout: page
|
||||||
|
title: "Joaoapps Join"
|
||||||
|
description: "Instructions for how to integrate the Join by Joaoapps service within Home Assistant."
|
||||||
|
date: 2016-07-12 10:49
|
||||||
|
sidebar: true
|
||||||
|
comments: false
|
||||||
|
sharing: true
|
||||||
|
footer: true
|
||||||
|
logo: joaoapps_join.png
|
||||||
|
ha_category: Hub
|
||||||
|
ha_release: "0.24"
|
||||||
|
---
|
||||||
|
|
||||||
|
|
||||||
|
The Join platform exposes services from [Join](http://joaoapps.com/join). In Home Assistant, the Join features are divided up in two locations, the Join component, and the Join notify platform. The notify platform allows us to send messages to Join devices, the the component allows us to access the other special features that Join offers.
|
||||||
|
|
||||||
|
In the configuartion.yaml you need to provide the device id of the target device. If you want to send to a group of devices, you need to provide an api key. You can find you device id and api key [here](https://joinjoaomgcd.appspot.com/).
|
||||||
|
|
||||||
|
To set it up, add the following information to your `configuration.yaml` file:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
notify:
|
||||||
|
- platform: joaoapps_join
|
||||||
|
device_id: d5asdfasdf54645h45h368761dfe5gt8a
|
||||||
|
name: droid *optional
|
||||||
|
api_key: asd97823jb628a34fwsdfwefd5384345tf2d *optional
|
||||||
|
|
||||||
|
joaoapps_join:
|
||||||
|
device_id: group.android
|
||||||
|
name: droid
|
||||||
|
api_key: asd97823jb628a34fwsdfwefd5384345tf2d
|
||||||
|
```
|
||||||
|
|
||||||
|
The notify service has a few optional parameters such as icon and smallicon. You can use them like so:
|
||||||
|
|
||||||
|
```json
|
||||||
|
{"message":"Hello!","title":"From Hass","data":{"icon":"https://goo.gl/KVqcYi","smallicon":"http://goo.gl/AU4Wf1"}}
|
||||||
|
```
|
||||||
|
|
||||||
|
The services exposed in the joaoapps_join component can be used with the service data described below:
|
||||||
|
|
||||||
|
| Service | Data |
|
||||||
|
|------------------------------ |------------------------------------------------------------------ |
|
||||||
|
| joaoapps_join/ring | |
|
||||||
|
| joaoapps_join/send_sms | {"number":"5553334444", "message":"Hello!"} |
|
||||||
|
| joaoapps_join/send_tasker | {"command":"test"} |
|
||||||
|
| joaoapps_join/send_url | {"url":"http://google.com"} |
|
||||||
|
| joaoapps_join/send_wallpaper | {"url":"http://www.planwallpaper.com/static/images/ZhGEqAP.jpg"} |
|
||||||
|
| joaoapps_join/send_file | {"url":"http://download.thinkbroadband.com/5MB.zip"} |
|
||||||
|
|
||||||
34
source/_components/knx.markdown
Normal file
34
source/_components/knx.markdown
Normal file
@ -0,0 +1,34 @@
|
|||||||
|
---
|
||||||
|
layout: page
|
||||||
|
title: "KNX"
|
||||||
|
description: "Instructions on how to integrate KXN components with Home Assistant."
|
||||||
|
date: 2016-06-08 12:00
|
||||||
|
sidebar: true
|
||||||
|
comments: false
|
||||||
|
sharing: true
|
||||||
|
footer: true
|
||||||
|
logo: knx.png
|
||||||
|
ha_category: DIY
|
||||||
|
ha_release: 0.24
|
||||||
|
---
|
||||||
|
|
||||||
|
[KNX/EIB](http://www.knx.org) integration for Home Assistant allows you to connect to a KNX bus. The component requires a local KNX/IP interface like the [Weinzierl 730](http://www.weinzierl.de/index.php/en/all-knx/knx-devices-en/knx-ip-interface-730-en). Through this it will send and receive commands to and from other devices to the KNX bus.
|
||||||
|
|
||||||
|
There is currently support for the following device types within Home Assistant:
|
||||||
|
|
||||||
|
- [Binary Sensor](/components/binary_sensor.knx)
|
||||||
|
- [Switch](/components/switch.knx)
|
||||||
|
|
||||||
|
The local ZigBee device (assuming XBee) must have an up to date Router or Coordinator API firmware installed.
|
||||||
|
|
||||||
|
A `knx` section must be present in the `configuration.yaml` file and contain the following options as required:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
knx:
|
||||||
|
host: IP_ADDRESS
|
||||||
|
port: PORT
|
||||||
|
```
|
||||||
|
|
||||||
|
- **host** (*Required*): The IP address of the KNX/IP interface to use. You can use "0.0.0.0" if your KNX/IP gateway supports discovery.
|
||||||
|
- **port** (*Optional*): The UDP port number. Defaults to `3671`.
|
||||||
|
|
||||||
@ -14,7 +14,7 @@ Interacts with media players on your network. Please check the sidebar for a ful
|
|||||||
## {% linkable_title Services %}
|
## {% linkable_title Services %}
|
||||||
|
|
||||||
### {% linkable_title Media control services %}
|
### {% linkable_title Media control services %}
|
||||||
Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`, `media_play_pause`, `media_play`, `media_pause`, `media_next_track`, `media_previous_track`
|
Available services: `turn_on`, `turn_off`, `toggle`, `volume_up`, `volume_down`, `media_play_pause`, `media_play`, `media_pause`, `media_next_track`, `media_previous_track`, `clear_playlist`
|
||||||
|
|
||||||
| Service data attribute | Optional | Description |
|
| Service data attribute | Optional | Description |
|
||||||
| ---------------------- | -------- | ----------- |
|
| ---------------------- | -------- | ----------- |
|
||||||
|
|||||||
@ -41,6 +41,8 @@ Currently known supported models:
|
|||||||
- ES5500
|
- ES5500
|
||||||
- ES6800
|
- ES6800
|
||||||
- F6500
|
- F6500
|
||||||
|
- EH5600
|
||||||
|
- F6400AF
|
||||||
|
|
||||||
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io).
|
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io).
|
||||||
The two letters at the beginning of the model number represent the region, UE is Europe, UN is North America and UA is Asia & Australia. The two numbers following that represent the screen size. If you add your model remember to remove these before adding them to the list.
|
The two letters at the beginning of the model number represent the region, UE is Europe, UN is North America and UA is Asia & Australia. The two numbers following that represent the screen size. If you add your model remember to remove these before adding them to the list.
|
||||||
|
|||||||
16
source/_components/notify.joaoapps_join.markdown
Normal file
16
source/_components/notify.joaoapps_join.markdown
Normal file
@ -0,0 +1,16 @@
|
|||||||
|
---
|
||||||
|
layout: page
|
||||||
|
title: "Join Notify"
|
||||||
|
description: "Instructions how to setup the Join notification platform within Home Assistant."
|
||||||
|
date: 2016-07-12 09:00
|
||||||
|
sidebar: true
|
||||||
|
comments: false
|
||||||
|
sharing: true
|
||||||
|
footer: true
|
||||||
|
logo: joaoapps_join.png
|
||||||
|
ha_category: Notifications
|
||||||
|
ha_release: "0.24"
|
||||||
|
---
|
||||||
|
|
||||||
|
See the [Joaoapps Join component page](/components/joaoapps/) for information how to get the join notify platform running.
|
||||||
|
|
||||||
@ -34,6 +34,7 @@ Once loaded, the `notify` platform will expose a service that can be called to s
|
|||||||
| `message` | no | Body of the notification.
|
| `message` | no | Body of the notification.
|
||||||
| `title` | yes | Title of the notification. Default is `Home Assistant`.
|
| `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.
|
| `target` | yes | Some platforms will allow specifying a recipient that will receive the notification. See your platform page if it is supported.
|
||||||
|
| `data` | yes | On platforms who have extended functionality. See your platform page if it is supported.
|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
|
|||||||
@ -66,3 +66,28 @@ Configuration variables:
|
|||||||
- **chat_id** (*Required*: The chat ID of your user.
|
- **chat_id** (*Required*: The chat ID of your user.
|
||||||
|
|
||||||
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
|
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
|
||||||
|
|
||||||
|
### Photo support
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
...
|
||||||
|
|
||||||
|
action:
|
||||||
|
service: notify.NOTIFIER_NAME
|
||||||
|
data:
|
||||||
|
title: test notify
|
||||||
|
message: That's a exemple
|
||||||
|
data:
|
||||||
|
photo:
|
||||||
|
- url: http://192.168.1.28/camera.jpg
|
||||||
|
username: admin
|
||||||
|
password: secrete
|
||||||
|
- file: /tmp/picture.jpg
|
||||||
|
caption: Picture Title xy
|
||||||
|
- url: http://somebla.ie/video.png
|
||||||
|
caption: I.e. for a Title
|
||||||
|
```
|
||||||
|
|
||||||
|
- **url** or **file** (*Required*): For local or remote path to a picture
|
||||||
|
- **caption** (*Optional*: Picture title
|
||||||
|
- **username** and **password** (*Optional*: For URL they require a basic auth
|
||||||
|
|||||||
@ -9,11 +9,16 @@ sharing: true
|
|||||||
footer: true
|
footer: true
|
||||||
logo: home-assistant.png
|
logo: home-assistant.png
|
||||||
ha_category: "History"
|
ha_category: "History"
|
||||||
featured: false
|
ha_release: pre 0.7
|
||||||
ha_release: "0.20"
|
|
||||||
---
|
---
|
||||||
|
|
||||||
The `recorder` component is storing details in the local database which then are handled by the [`history` component](/components/history/).
|
The `recorder` component is storing details in a database which then are handled by the [`history` component](/components/history/).
|
||||||
|
|
||||||
|
Home Assistant uses [SQLAlchemy](http://www.sqlalchemy.org/) as Object Relational Mapper (ORM). This means that you can now use **any** SQL backend for the recorder that is supported by SQLAlchemy, like [MySQL](https://www.mysql.com/), [MariaDB](https://mariadb.org/), or [PostgreSQL](https://www.postgresql.org/).
|
||||||
|
|
||||||
|
The default database engine is [SQLite](https://www.sqlite.org/) which doesn't require any configuration. The database is stored in your Home Assistant configuration directory (`.homeassistant`) and called `home-assistant.db`.
|
||||||
|
|
||||||
|
```bash
|
||||||
|
|
||||||
To setup the `recorder` component in your installation, add the following to your `configuration.yaml` file:
|
To setup the `recorder` component in your installation, add the following to your `configuration.yaml` file:
|
||||||
|
|
||||||
@ -26,4 +31,13 @@ recorder:
|
|||||||
Configuration variables:
|
Configuration variables:
|
||||||
|
|
||||||
- **purge_days** (*Optional*): Delete events and states older than x days.
|
- **purge_days** (*Optional*): Delete events and states older than x days.
|
||||||
|
- **db_url** (*Optional*): The URL which point to your database.
|
||||||
|
|
||||||
|
| Database engine | `db_url` |
|
||||||
|
| :---------------|:---------------------------------------------------------|
|
||||||
|
| SQLite | `sqlite:///PATH/TO/DB_NAME` |
|
||||||
|
| MySQL | `mysql://SERVER_IP/DB_NAME` |
|
||||||
|
| MySQL | `mysql://user:password@SERVER_IP/DB_NAME` |
|
||||||
|
| PostgreSQL | `postgresql://SERVER_IP/DB_NAME` |
|
||||||
|
| PostgreSQL | `postgresql://scott:tiger@SERVER_IP/DB_NAME` |
|
||||||
|
|
||||||
|
|||||||
@ -11,11 +11,30 @@ logo: apcupsd.png
|
|||||||
ha_category: Sensor
|
ha_category: Sensor
|
||||||
---
|
---
|
||||||
|
|
||||||
Any of the lines of output from the [apcaccess](http://linux.die.net/man/8/apcaccess) command can be used as a sensor device in Home Assistant. In order to create a sensor for a value, create an entity within a `sensor` section of your configuration. The following parameters may be used:
|
The `apcupsd` sensor platform to allow you to monitor a UPS (battery backup) by using data from the [apcaccess](http://linux.die.net/man/8/apcaccess) command.
|
||||||
|
|
||||||
- **name** (*Required*): The name you'd like to give the sensor in Home Assistant.
|
To add this platform to your installation, add the following to your `configuration.yaml` file:
|
||||||
- **platform** (*Required*): Set to `apcupsd`.
|
|
||||||
- **type** (*Required*): The label for the value you'd like to track based on the output of `apcaccess`. Refer to the examples for ideas.
|
```yaml
|
||||||
|
# Example configuration.yaml entry
|
||||||
|
sensor:
|
||||||
|
- platform: apcupsd
|
||||||
|
resources:
|
||||||
|
- bcharge
|
||||||
|
- linev
|
||||||
|
- loadpct
|
||||||
|
- nominv
|
||||||
|
- nompower
|
||||||
|
- numxfers
|
||||||
|
- outputv
|
||||||
|
- status
|
||||||
|
- timeleft
|
||||||
|
- tonbatt
|
||||||
|
```
|
||||||
|
|
||||||
|
Configuration variables:
|
||||||
|
|
||||||
|
- **resources** array (*Required*): Contains all entries to display.
|
||||||
|
|
||||||
#### Example
|
#### Example
|
||||||
|
|
||||||
@ -76,19 +95,13 @@ FIRMWARE : 70.11.I
|
|||||||
END APC : 2016-02-09 17:13:46 +0000
|
END APC : 2016-02-09 17:13:46 +0000
|
||||||
```
|
```
|
||||||
|
|
||||||
Use the (case insensitive) values from the left hand column as your `type`:
|
Use the (case insensitive) values from the left hand column:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
sensor:
|
sensor:
|
||||||
- name: Mains Voltage
|
- platform: apcupsd
|
||||||
platform: apcupsd
|
resources:
|
||||||
type: linev
|
- linev
|
||||||
|
- loadpct
|
||||||
- name: UPS Load
|
- itemp
|
||||||
platform: apcupsd
|
|
||||||
type: loadpct
|
|
||||||
|
|
||||||
- name: UPS Temperature
|
|
||||||
platform: apcupsd
|
|
||||||
type: itemp
|
|
||||||
```
|
```
|
||||||
|
|||||||
@ -40,3 +40,38 @@ Configuration variables:
|
|||||||
- **options** (*Optional*): A dictionary containing parameters to add to all requests to the Distance Matrix API. A full listing of available options can be found [here](https://developers.google.com/maps/documentation/distance-matrix/intro#RequestParameters).
|
- **options** (*Optional*): A dictionary containing parameters to add to all requests to the Distance Matrix API. A full listing of available options can be found [here](https://developers.google.com/maps/documentation/distance-matrix/intro#RequestParameters).
|
||||||
- **departure_time** (*Optional*): Can be `now`, a Unix timestamp, or a 24 hour time string like `08:00:00`. If you provide a time string, it will be combined with the current date to get travel time for that moment.
|
- **departure_time** (*Optional*): Can be `now`, a Unix timestamp, or a 24 hour time string like `08:00:00`. If you provide a time string, it will be combined with the current date to get travel time for that moment.
|
||||||
- **arrival_time** (*Optional*): See notes above for `departure_time`. `arrival_time` can not be `now`, only a Unix timestamp or time string. You can not provide both `departure_time` and `arrival_time`. If you do provide both, `arrival_time` will be removed from the request.
|
- **arrival_time** (*Optional*): See notes above for `departure_time`. `arrival_time` can not be `now`, only a Unix timestamp or time string. You can not provide both `departure_time` and `arrival_time`. If you do provide both, `arrival_time` will be removed from the request.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
###Dynamic Configuration
|
||||||
|
Tracking can be setup to track entities of type device_tracker, zone, and sensor. If an entity is placed in the origin or destination then every 5 minutes when the component updates it will use the latest location of that entity.
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
# Example entry for configuration.yaml
|
||||||
|
sensor:
|
||||||
|
# Tracking entity to entity
|
||||||
|
- platform: google_travel_time
|
||||||
|
name: Phone To Home
|
||||||
|
api_key: XXXX_XXXXX_XXXXX
|
||||||
|
origin: device_tracker.mobile_phone
|
||||||
|
destination: zone.home
|
||||||
|
|
||||||
|
# Tracking entity to zone friendly name
|
||||||
|
- platform: google_travel_time
|
||||||
|
name: Home To Eddie's House
|
||||||
|
api_key: XXXX_XXXXX_XXXXX
|
||||||
|
origin: zone.home
|
||||||
|
destination: Eddies House # Friendly name of a zone
|
||||||
|
```
|
||||||
|
|
||||||
|
####Entity Tracking
|
||||||
|
- **device_tracker**
|
||||||
|
- If state is a zone then the zone location will be used
|
||||||
|
- If state is not a zone it will look for the longitude and latitude attributes
|
||||||
|
- **zone**
|
||||||
|
- Uses the longitude and latitude attributes
|
||||||
|
- Can also be referenced by just the zone's friendly name found in the attributes.
|
||||||
|
- **sensor**
|
||||||
|
- If state is a zone or zone friendly name then will use the zone location
|
||||||
|
- All other states will be passed directly into the google API
|
||||||
|
- This includes all valid locations listed in the *Configuration Variables*
|
||||||
|
|||||||
38
source/_components/sensor.imap.markdown
Normal file
38
source/_components/sensor.imap.markdown
Normal file
@ -0,0 +1,38 @@
|
|||||||
|
---
|
||||||
|
layout: page
|
||||||
|
title: "IMAP Sensor"
|
||||||
|
description: "Instructions how to integrate IMAP sensors into Home Assistant."
|
||||||
|
date: 2016-07-11 06:00
|
||||||
|
sidebar: true
|
||||||
|
comments: false
|
||||||
|
sharing: true
|
||||||
|
footer: true
|
||||||
|
ha_category: Sensor
|
||||||
|
ha_release: 0.25
|
||||||
|
published: false
|
||||||
|
---
|
||||||
|
|
||||||
|
|
||||||
|
The `imap` sensor platform is observing your [IMAP server](https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol) and reporting the amount of unread emails.
|
||||||
|
|
||||||
|
To enable this sensor, add the following lines to your `configuration.yaml` file:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
# Example configuration.yaml entry
|
||||||
|
sensor:
|
||||||
|
- platform: imap
|
||||||
|
server: imap.gmail.com
|
||||||
|
port: 993
|
||||||
|
name: Emails
|
||||||
|
user: USERNAME
|
||||||
|
password: PASSWORD
|
||||||
|
```
|
||||||
|
|
||||||
|
Configuration variables:
|
||||||
|
|
||||||
|
- **server** (*Required*): The IP address or hostname of the IMAP server.
|
||||||
|
- **port** (*Required*): The port where the server is accessible.
|
||||||
|
- **name** (*Optional*): Name of the IMAP sensor.
|
||||||
|
- **user** (*Required*): Username for the IMAP server.
|
||||||
|
- **password** (*Required*): Password for the IMAP server.
|
||||||
|
|
||||||
69
source/_components/sensor.yweather.markdown
Normal file
69
source/_components/sensor.yweather.markdown
Normal file
@ -0,0 +1,69 @@
|
|||||||
|
---
|
||||||
|
layout: page
|
||||||
|
title: "Yahoo Weather"
|
||||||
|
description: "Instructions how to integrate Yahoo Weather within Home Assistant."
|
||||||
|
date: 2016-07-06 9:06
|
||||||
|
sidebar: true
|
||||||
|
comments: false
|
||||||
|
sharing: true
|
||||||
|
footer: true
|
||||||
|
logo: yahooweather.png
|
||||||
|
ha_category: Weather
|
||||||
|
ha_release: 0.24
|
||||||
|
---
|
||||||
|
|
||||||
|
|
||||||
|
The `yweather` platform uses [Yahoo Weather](http://https://www.yahoo.com/news/weather/) as an source for current meteorological data. The `forecast` will show you the condition for 5 days, 0 is the current day. You can use only `weather`, `temp_min`, and `temp_max` with forecast.
|
||||||
|
|
||||||
|
<p class='note warning'>
|
||||||
|
Use of the Yahoo Weather API should not exceed reasonable request volume. Access is limited to 2,000 signed calls per day.
|
||||||
|
</p>
|
||||||
|
|
||||||
|
The `woeid` (Where On Earth ID) for your location, as shown in the example below. You can find your woeid by copying the numeric digits at the end of the URL for your location at [Yahoo Weather](http://https://www.yahoo.com/news/weather/). If you don't add a woeid it generate it from Home Assistant's latitude and longitude.
|
||||||
|
|
||||||
|
To add Yahoo Weather to your installation, add the following to your `configuration.yaml` file:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
# Example configuration.yaml entry
|
||||||
|
sensor:
|
||||||
|
platform: yweather
|
||||||
|
woeid: YOUR_WOEID
|
||||||
|
forecast: 0 until 5
|
||||||
|
monitored_conditions:
|
||||||
|
- weather
|
||||||
|
- weather_current
|
||||||
|
- temp_min
|
||||||
|
- temp_max
|
||||||
|
- wind_speed
|
||||||
|
- pressure
|
||||||
|
- visibility
|
||||||
|
- humidity
|
||||||
|
- temperature
|
||||||
|
|
||||||
|
# Example configuration.yaml entry with forecast
|
||||||
|
sensor:
|
||||||
|
platform: yweather
|
||||||
|
woeid: YOUR_WOEID
|
||||||
|
forecast: 3
|
||||||
|
monitored_conditions:
|
||||||
|
- weather
|
||||||
|
- temp_min
|
||||||
|
- temp_max
|
||||||
|
```
|
||||||
|
|
||||||
|
Configuration variables:
|
||||||
|
|
||||||
|
- **woeid** (*Optional*): See above.
|
||||||
|
- **forecast** (*Optional*): Day of forecast. The default is the current day to display conditions.
|
||||||
|
- **monitored_conditions** array (*Required*): Conditions to display in the frontend.
|
||||||
|
- **weather**: A human-readable text summary with picture from yahoo.
|
||||||
|
- **weather_current**: A human-readable text summary with picture from yahoo from current conditon.
|
||||||
|
- **temperature**: The current temperature.
|
||||||
|
- **temp_min**: The minimal temperature of this day.
|
||||||
|
- **temp_max**: The maximum temperature of this day.
|
||||||
|
- **wind_speed**: The wind speed.
|
||||||
|
- **humidity**: The relative humidity.
|
||||||
|
- **pressure**: The sea-level air pressure in millibars.
|
||||||
|
- **visibility**: The average visibility.
|
||||||
|
|
||||||
|
Details about the API are available in the [Yahoo! EDeveloper Network](http://https://developer.yahoo.com/weather/).
|
||||||
@ -22,6 +22,7 @@ statsd:
|
|||||||
port: 20000
|
port: 20000
|
||||||
prefix: DB_TO_STORE_EVENTS
|
prefix: DB_TO_STORE_EVENTS
|
||||||
rate: 1
|
rate: 1
|
||||||
|
log_attributes: true
|
||||||
```
|
```
|
||||||
|
|
||||||
Configuration variables:
|
Configuration variables:
|
||||||
@ -30,6 +31,7 @@ Configuration variables:
|
|||||||
- **port** (*Optional*): Port to use. Defaults to 8125.
|
- **port** (*Optional*): Port to use. Defaults to 8125.
|
||||||
- **prefix** (*Optional*): Prefix to use. Defaults to `hass`.
|
- **prefix** (*Optional*): Prefix to use. Defaults to `hass`.
|
||||||
- **rate** (*Optional*): The sample rate. Defaults to 1.
|
- **rate** (*Optional*): The sample rate. Defaults to 1.
|
||||||
|
- **log_attributes** (*Optional*): Log state and attribute changes. This changes the default stats path.
|
||||||
|
|
||||||
StatsD supports various [backends](https://github.com/etsy/statsd/blob/master/docs/backend.md).
|
StatsD supports various [backends](https://github.com/etsy/statsd/blob/master/docs/backend.md).
|
||||||
|
|
||||||
|
|||||||
15
source/_components/switch.knx.markdown
Normal file
15
source/_components/switch.knx.markdown
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
---
|
||||||
|
layout: page
|
||||||
|
title: "KNX Switch"
|
||||||
|
description: "Instructions how to setup the KNX switches within Home Assistant."
|
||||||
|
date: 2016-07-13 07:00
|
||||||
|
sidebar: true
|
||||||
|
comments: false
|
||||||
|
sharing: true
|
||||||
|
footer: true
|
||||||
|
logo: zknx.png
|
||||||
|
ha_category: Switch
|
||||||
|
ha_release: 0.24
|
||||||
|
---
|
||||||
|
|
||||||
|
To get your KNX switches working with Home Assistant, follow the instructions for the [KNX component](/components/knx/).
|
||||||
37
source/_components/switch.tplink.markdown
Normal file
37
source/_components/switch.tplink.markdown
Normal file
@ -0,0 +1,37 @@
|
|||||||
|
---
|
||||||
|
layout: page
|
||||||
|
title: "TPLink Switch"
|
||||||
|
description: "Instructions how to integrate TPLink switches into Home Assistant."
|
||||||
|
date: 2016-07-13 08:00
|
||||||
|
sidebar: true
|
||||||
|
comments: false
|
||||||
|
sharing: true
|
||||||
|
footer: true
|
||||||
|
logo: tp-link.png
|
||||||
|
ha_category: Switch
|
||||||
|
---
|
||||||
|
|
||||||
|
|
||||||
|
The `tplink` switch platform allows you to control the state of your [TPLink smart switch](http://www.tp-link.com/en/products/list-5258.html).
|
||||||
|
|
||||||
|
Supported units:
|
||||||
|
|
||||||
|
- HS100
|
||||||
|
- HS110
|
||||||
|
|
||||||
|
To use your TPLink switch in your installation, add the following to your `configuration.yaml` file:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
# Example configuration.yaml entry
|
||||||
|
switch:
|
||||||
|
platform: tplink
|
||||||
|
host: IP_ADRRESS
|
||||||
|
name: TP-Link Switch
|
||||||
|
```
|
||||||
|
|
||||||
|
Configuration variables:
|
||||||
|
|
||||||
|
- **host** (*Required*): The IP address of your myStrom switch, eg. http://192.168.1.32
|
||||||
|
- **name** (*Optional*): The name to use when displaying this switch.
|
||||||
|
|
||||||
|
|
||||||
12
source/_cookbook/configuration_yaml_by_bah2830.markdown
Normal file
12
source/_cookbook/configuration_yaml_by_bah2830.markdown
Normal file
@ -0,0 +1,12 @@
|
|||||||
|
---
|
||||||
|
layout: page
|
||||||
|
title: "Configuration.yaml by bah2830"
|
||||||
|
description: ""
|
||||||
|
date: 2016-07-14 20:00
|
||||||
|
sidebar: true
|
||||||
|
comments: false
|
||||||
|
sharing: true
|
||||||
|
footer: true
|
||||||
|
ha_category: Example configuration.yaml
|
||||||
|
ha_external_link: https://github.com/bah2830/Home-Assistant-Configs
|
||||||
|
---
|
||||||
12
source/_cookbook/configuration_yaml_by_gstevenson.markdown
Normal file
12
source/_cookbook/configuration_yaml_by_gstevenson.markdown
Normal file
@ -0,0 +1,12 @@
|
|||||||
|
---
|
||||||
|
layout: page
|
||||||
|
title: "Configuration.yaml by gstevenson"
|
||||||
|
description: ""
|
||||||
|
date: 2016-07-13 21:58
|
||||||
|
sidebar: true
|
||||||
|
comments: false
|
||||||
|
sharing: true
|
||||||
|
footer: true
|
||||||
|
ha_category: Example configuration.yaml
|
||||||
|
ha_external_link: https://github.com/gstevenson/ha-config
|
||||||
|
---
|
||||||
@ -0,0 +1,95 @@
|
|||||||
|
---
|
||||||
|
layout: post
|
||||||
|
title: "0.24: SQLAlchemy, KNX, Join by Joaoapps, and SimpliSafe."
|
||||||
|
description: "This new release of Home Assistant contains support for KNX, Join by Joaoapps, and SimpliSafe. As of now our new database backend is SQLAlchemy which gives you more flexibility for storing your data."
|
||||||
|
date: 2016-07-16 12:00:00 +0000
|
||||||
|
date_formatted: "July 16, 2016"
|
||||||
|
author: Fabian Affolter
|
||||||
|
author_twitter: fabaff
|
||||||
|
comments: true
|
||||||
|
categories: Release-Notes
|
||||||
|
---
|
||||||
|
|
||||||
|
It's time for Home Assistant 0.24 and it's full of new integration for your Home. It contains some structural changes to our history which requires action from your end, so please keep reading.
|
||||||
|
|
||||||
|
[MapQuest] discontinued their free and direct tile access by Monday, July 11, 2016. With [CARTO] we found a very cool and suitable solution. They allow us to use their tile for the map. Thank you, [CARTO].
|
||||||
|
|
||||||
|
[Roy Hooper][@rhooper] did an amazing job migrating the history support from being tied to SQLite to use the ORM SQLAlchemy instead. This means that you can now use **any** SQL backend for the history. So besides SQLite you can now databases like MySQL or PostgreSQL. However, this does require that you install [SQLAlchemy] and run a command to migrate your existing history over. We tried to make the process as seamless as possible by introducing a new command line script:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
$ pip3 install SQLAlchemy
|
||||||
|
$ hass --script db_migrator --config /path/to/config
|
||||||
|
```
|
||||||
|
|
||||||
|
You can omit the `--config` option if you use the default configuration directory. Run the script with `--help` to get more options.
|
||||||
|
|
||||||
|
<img src='/images/supported_brands/yahooweather.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/joaoapps_join.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/knx.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/tp-link.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' />
|
||||||
|
|
||||||
|
- Config: Improved support for storing [secrets][secrets] ([@kellerza])
|
||||||
|
- Sensor: Support for [Yahoo! Weather][yahoo-weather] ([@pvizeli])
|
||||||
|
- Add scripts to command line to expose advanced options ([@balloob])
|
||||||
|
- Alarm: [SimpliSafe][simplisafe] is now supported ([@w1ll1am23])
|
||||||
|
- Core: Switch to SQLAlchemy for the Recorder component ([@rhooper])
|
||||||
|
- Support for [Join by Joaoapps][join-joaoapps] added incl. [Join Notify][join-notify] ([@nkgilley])
|
||||||
|
- Media Player: [Plex] will no longer spam the logs if server goes offline ([@dale3h])
|
||||||
|
- Sensor: [APCUPSd Sensor][apcupsd-sensor] now supports names, icons and units ([@dale3h])
|
||||||
|
- Lock: [Verisure] entities will now use name instead of serial number for entity id ([@turbokongen])
|
||||||
|
- [StatsD] can now also export attributes ([@bah2830])
|
||||||
|
- Support for [KNX] added ([@usul27])
|
||||||
|
- Switch: [TPLink] HS100/HS110 now supported ([@GadgetReactor])
|
||||||
|
- Stability fixes for [RFXTRX] ([@Danielhiversen])
|
||||||
|
- Tweaks to [Z-Wave] ([@turbokongen])
|
||||||
|
- Light: [Brightness] now clamped to 0-255 ([@keatontaylor])
|
||||||
|
- Thermostat: [Radiotherm] HVAC mode now supported ([@danieljkemp])
|
||||||
|
- Sensor: [Google Travel] times can now use dynamic locations for start/end ([@bah2830])
|
||||||
|
- Notify: Allow sending photos to [Telegram] ([@pvizeli])
|
||||||
|
- Frontend: Improve loading times ([@balloob])
|
||||||
|
- Frontend: Fix stream not reconnecting after standby ([@balloob])
|
||||||
|
- Frontend: Wait up to two seconds for new state before resetting toggle after toggling state ([@balloob])
|
||||||
|
|
||||||
|
### {% linkable_title Breaking changes %}
|
||||||
|
|
||||||
|
- Migrating existing databases (see above).
|
||||||
|
- The [APCUPSd Sensor][apcupsd-sensor] was updated. This will need that you modify your `configuration.yaml` file.
|
||||||
|
- Entity IDs of Verisure locks will change. This is a one time change but should improve readability.
|
||||||
|
|
||||||
|
### {% linkable_title FAQ %}
|
||||||
|
|
||||||
|
- Frequently asked questions about this release will show up here...
|
||||||
|
|
||||||
|
[@bah2830]: https://github.com/bah2830/
|
||||||
|
[@balloob]: https://github.com/balloob/
|
||||||
|
[@dale3h]: https://github.com/dale3h/
|
||||||
|
[@danieljkemp]: https://github.com/danieljkemp
|
||||||
|
[@GadgetReactor]: https://github.com/GadgetReactor
|
||||||
|
[@keatontaylor]: https://github.com/keatontaylor
|
||||||
|
[@kellerza]: https://github.com/kellerza/
|
||||||
|
[@nkgilley]: https://github.com/nkgilley
|
||||||
|
[@pvizeli]: https://github.com/pvizeli/
|
||||||
|
[@rhooper]: https://github.com/rhooper/
|
||||||
|
[@turbokongen]: https://github.com/turbokongen/
|
||||||
|
[@usul27]: https://github.com/usul27
|
||||||
|
[@w1ll1am23]: https://github.com/w1ll1am23/
|
||||||
|
|
||||||
|
[apcupsd-sensor]: /components/sensor.apcupsd/
|
||||||
|
[Brightness]: /components/light/
|
||||||
|
[CARTO]: https://carto.com/
|
||||||
|
[Google Travel]: /components/sensor.google_travel_time/
|
||||||
|
[imap-sensor]: /component/sensor.imap/
|
||||||
|
[join-joaoapps]: /components/joaoapps_join/
|
||||||
|
[join-notify]: /components/notify.joaoapps_join/
|
||||||
|
[KNX]: /components/knx/
|
||||||
|
[MapQuest]: https://www.mapquest.com/
|
||||||
|
[Plex]: /components/media_player.plex/
|
||||||
|
[Radiotherm]: /components/thermostat.radiotherm/
|
||||||
|
[recorder]: /components/recorder/
|
||||||
|
[secrets]: /topics/secrets/
|
||||||
|
[simplisafe]: /components/alarm_control_panel.simplisafe/
|
||||||
|
[SQLAlchemy]: http://www.sqlalchemy.org/
|
||||||
|
[StatD]: /components/statsd/
|
||||||
|
[Telegram]: /components/notify.telegram/
|
||||||
|
[TPLink]: /components/switch.tplink/
|
||||||
|
[Verisure]: /components/lock.verisure/
|
||||||
|
[yahoo-weather]: /components/sensor.yweather/
|
||||||
|
[Z-Wave]: /components/zwave/
|
||||||
|
|
||||||
@ -53,6 +53,7 @@ This page contains a list of people who have contributed in one way or another t
|
|||||||
- [Daniel Perna](https://github.com/danielperna84)
|
- [Daniel Perna](https://github.com/danielperna84)
|
||||||
- [Daniel Iversen](https://github.com/danielhiversen)
|
- [Daniel Iversen](https://github.com/danielhiversen)
|
||||||
- [Daniel J. Kemp](https://github.com/danieljkemp/)
|
- [Daniel J. Kemp](https://github.com/danieljkemp/)
|
||||||
|
- [Daniel Matuschek](https://github.com/usul27)
|
||||||
- [Dan Smith](https://github.com/kk7ds)
|
- [Dan Smith](https://github.com/kk7ds)
|
||||||
- [Dan Sullivan](https://github.com/dansullivan86/)
|
- [Dan Sullivan](https://github.com/dansullivan86/)
|
||||||
- [Daren Lord](https://github.com/Xorso)
|
- [Daren Lord](https://github.com/Xorso)
|
||||||
@ -68,6 +69,7 @@ This page contains a list of people who have contributed in one way or another t
|
|||||||
- [Finbarr Brady](https://github.com/fbradyirl)
|
- [Finbarr Brady](https://github.com/fbradyirl)
|
||||||
- [Flavio Castelli](https://github.com/flavio)
|
- [Flavio Castelli](https://github.com/flavio)
|
||||||
- [Florian Holzapfel](https://github.com/florianholzapfel)
|
- [Florian Holzapfel](https://github.com/florianholzapfel)
|
||||||
|
- [GadgetReactor](https://github.com/GadgetReactor)
|
||||||
- [Geoff Norton](https://github.com/kangaroo)
|
- [Geoff Norton](https://github.com/kangaroo)
|
||||||
- [goir](https://github.com/goir)
|
- [goir](https://github.com/goir)
|
||||||
- [gottsman](https://github.com/gottsman)
|
- [gottsman](https://github.com/gottsman)
|
||||||
@ -103,6 +105,7 @@ This page contains a list of people who have contributed in one way or another t
|
|||||||
- [Justin Moy](https://github.com/justincmoy)
|
- [Justin Moy](https://github.com/justincmoy)
|
||||||
- [Justyn Shull](https://github.com/justyns/)
|
- [Justyn Shull](https://github.com/justyns/)
|
||||||
- [Karen Goode](https://github.com/kfgoode)
|
- [Karen Goode](https://github.com/kfgoode)
|
||||||
|
- [Keaton Taylor](https://github.com/keatontaylor)
|
||||||
- [kennedyshead](https://github.com/kennedyshead)
|
- [kennedyshead](https://github.com/kennedyshead)
|
||||||
- [kixam](https://github.com/kixam)
|
- [kixam](https://github.com/kixam)
|
||||||
- [Kyle Hendricks](https://github.com/kylehendricks)
|
- [Kyle Hendricks](https://github.com/kylehendricks)
|
||||||
@ -119,7 +122,6 @@ This page contains a list of people who have contributed in one way or another t
|
|||||||
- [Matteo Lampugnani](https://github.com/t30)
|
- [Matteo Lampugnani](https://github.com/t30)
|
||||||
- [Matthew Treinish](https://github.com/mtreinish/)
|
- [Matthew Treinish](https://github.com/mtreinish/)
|
||||||
- [Michaël Arnauts](https://github.com/michaelarnauts)
|
- [Michaël Arnauts](https://github.com/michaelarnauts)
|
||||||
- [Michael Auchter](https://github.com/auchter)
|
|
||||||
- [Michael Gilbert](https://github.com/Zyell)
|
- [Michael Gilbert](https://github.com/Zyell)
|
||||||
- [Michael Kutý](https://github.com/michaelkuty)
|
- [Michael Kutý](https://github.com/michaelkuty)
|
||||||
- [Micha LaQua](https://github.com/milaq)
|
- [Micha LaQua](https://github.com/milaq)
|
||||||
|
|||||||
BIN
source/images/supported_brands/joaoapps_join.png
Normal file
BIN
source/images/supported_brands/joaoapps_join.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
BIN
source/images/supported_brands/knx.png
Normal file
BIN
source/images/supported_brands/knx.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 56 KiB |
BIN
source/images/supported_brands/simplisafe.png
Normal file
BIN
source/images/supported_brands/simplisafe.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 3.0 KiB |
BIN
source/images/supported_brands/yahooweather.png
Normal file
BIN
source/images/supported_brands/yahooweather.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
@ -15,11 +15,11 @@ hide_github_edit: true
|
|||||||
<div class="grid">
|
<div class="grid">
|
||||||
<div class="grid__item one-third lap-one-third palm-one-whole">
|
<div class="grid__item one-third lap-one-third palm-one-whole">
|
||||||
<div class='current-version material-card text'>
|
<div class='current-version material-card text'>
|
||||||
<h1>Current Version: 0.23.1</h1>
|
<h1>Current Version: 0.24</h1>
|
||||||
Released: <span class='release-date'>July 2, 2016</span>
|
Released: <span class='release-date'>July 16, 2016</span>
|
||||||
|
|
||||||
<div class='links'>
|
<div class='links'>
|
||||||
<a href='/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-sony-bravia-tv/'>Release notes</a>
|
<a href='/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/'>Release notes</a>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div class='join-community material-card text'>
|
<div class='join-community material-card text'>
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user