mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-24 09:46:59 +00:00
Paulus Schoutsen
GitHub
commit
ae7e28d022
@ -139,12 +139,12 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 53
|
||||
current_patch_version: 1
|
||||
date_released: 2017-09-12
|
||||
current_minor_version: 54
|
||||
current_patch_version: 0
|
||||
date_released: 2017-09-23
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
# Major release:
|
||||
patch_version_notes: "#release-0531---september-11"
|
||||
patch_version_notes: "#"
|
||||
# Minor release (Example #release-0431---april-25):
|
||||
|
||||
@ -19,22 +19,91 @@ Please visit the [Abode website](https://goabode.com/) for further information a
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- [Alarm Control Panel](/components/alarm_control_panel.abode/): Reports on current alarm status and can be used to arm/disarm the system
|
||||
- [Binary Sensor](/components/binary_sensor.abode/): Reports on `Door Contacts` (open or closed), `Motion Camera` (motion detected or not), `Water Sensors` (detected or not), `Keypad` (online or not), `Glass Break` (online or not), `Status Display` (online or not)
|
||||
- [Cover](/components/cover.abode/): Reports on `Secure Barriers` (open or closed) and can be used to open/close the cover
|
||||
- [Lock](/components/cover.abode/): Reports on `Door Locks` (locked or unlocked) and can be used to lock/unlock the door
|
||||
- [Switch](/components/switch.abode/): Reports on `Power Switch Sensors` (on or off) and can be used to turn the power switch sensor on/off
|
||||
- [Alarm Control Panel](/components/alarm_control_panel.abode/): Reports on the current alarm status and can be used to arm and disarm the system.
|
||||
- [Binary Sensor](/components/binary_sensor.abode/): Reports on `Quick Actions`, `Door Contacts`, `Connectivity` sensors (remotes, keypads, and status indicators), `Moisture` sensors, and `Motion` or `Occupancy` sensors.
|
||||
- [Camera](/components/camera.abode/): Reports on `Camera` devices and will download and show the latest captured still image.
|
||||
- [Cover](/components/cover.abode/): Reports on `Secure Barriers` and can be used to open and close the cover.
|
||||
- [Lock](/components/cover.abode/): Reports on `Door Locks` and can be used to lock and unlock the door.
|
||||
- [Light](/components/light.abode/): Reports on `Dimmer` lights and can be used to dim, change color, or turn the light on and off.
|
||||
- [Switch](/components/switch.abode/): Reports on `Power Switch` devices and can be used to turn the power switch on and off. Also reports on `Automations` set up in the Abode system and allows you to activate or deactivate them.
|
||||
|
||||
An `abode` section must be present in the `configuration.yaml` file and contain the following options as required:
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use Abode devices in your installation, add the following `abode` section to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
abode:
|
||||
username: abode_username
|
||||
password: abode_password
|
||||
name: Abode Alarm System
|
||||
polling: False
|
||||
exclude:
|
||||
- 'ZW:0000000034'
|
||||
- 'RF:00000011'
|
||||
lights:
|
||||
- 'ZW:0000000022'
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **username** (*Required*): Username for the Abode account.
|
||||
- **password** (*Required*): Password for Abode account.
|
||||
- **username** (*Required*): Username for your Abode account.
|
||||
- **password** (*Required*): Password for your Abode account.
|
||||
- **name** (*Optional*): The name for your alarm controller.
|
||||
- **polling** (*Optional*): Enable polling if cloud push updating is less reliable. Will update the devices once every 30 seconds. Defaults to False.
|
||||
- **exclude** (*Optional*): A list of devices to exclude from Home Assistant by their Abode `device_id`, found within the component attributes.
|
||||
- **lights** (*Optional*): A list of switch devices that Home Assistant should treat as lights by the switches Abode `device_id`, found within the component attributes.
|
||||
|
||||
## {% linkable_title Events %}
|
||||
|
||||
There are a number of events that can be triggered from Abode. They are grouped into the below events:
|
||||
|
||||
- **abode_alarm**: Fired when an alarm event is triggered from Abode. This includes Smoke, CO, Panic, and Burglar alarms.
|
||||
- **abode_alarm_end**: Fired when an alarm end event is triggered from Abode.
|
||||
- **abode_automation**: Fired when an Automation is triggered from Abode.
|
||||
- **abode_panel_fault**: Fired when there is a fault with the Abode hub. This includes events like loss of power, low battery, tamper switches, polling failures, and signal interference.
|
||||
- **abode_panel_restore**: Fired when the panel fault is restored.
|
||||
|
||||
All events have the fields:
|
||||
|
||||
Field | Description
|
||||
----- | -----------
|
||||
`device_id` | The Abode device ID of the event.
|
||||
`device_name` | The Abode device name of the event.
|
||||
`device_type` | The Abode device type of the event.
|
||||
`event_code` | The event code of the event.
|
||||
`event_name` | The name of the event.
|
||||
`event_type` | The type of the event.
|
||||
`event_utc` | The UTC timestamp of the event.
|
||||
`user_name` | The Abode user that triggered the event, if applicable.
|
||||
`date` | The date of the event in the format `MM/DD/YYYY`.
|
||||
`time` | The time of the event in the format `HH:MM AM`.
|
||||
|
||||
There is a unique list of known event_codes that can be found [here](https://github.com/MisterWil/abodepy/files/1262019/timeline_events.txt).
|
||||
|
||||
## {% linkable_title Services %}
|
||||
|
||||
### {% linkable_title Service `change_setting` %}
|
||||
|
||||
Change settings on your Abode system. For a full list of settings and valid values, consult the [AbodePy settings section](https://github.com/MisterWil/abodepy/blob/master/README.rst#settings).
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `setting` | No | The setting you wish to change.
|
||||
| `value` | No | The value you wish to change the setting to.
|
||||
|
||||
### {% linkable_title Service `capture_image` %}
|
||||
|
||||
Request a new still image from your Abode IR camera.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | No | String or list of strings that point at `entity_id`s of Abode cameras.
|
||||
|
||||
### {% linkable_title Service `trigger_quick_action` %}
|
||||
|
||||
Trigger a quick action automation on your Abode system.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | No | String or list of strings that point at `entity_id`s of binary_sensors that represent your Abode quick actions.
|
||||
@ -28,6 +28,24 @@ Configuration variables:
|
||||
- **pending_time** (*Optional*): The time in seconds of the pending time before arming the alarm. Default is 60 seconds.
|
||||
- **trigger_time** (*Optional*): The time in seconds of the trigger time in which the alarm is firing. Default is 120 seconds.
|
||||
- **disarm_after_trigger** (*Optional*): If true, the alarm will automatically disarm after it has been triggered instead of returning to the previous state.
|
||||
- **armed_home|armed_away|armed_night|triggered** (*Optional*): State specific settings
|
||||
- **pending_time**: State specific pending time override.
|
||||
|
||||
In the config example below, armed_home state will have no pending time and triggered state will have pending time of 20 second whereas armed_away state will have a default pending time of 30 seconds.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
alarm_control_panel:
|
||||
- platform: manual
|
||||
name: Home Alarm
|
||||
code: 1234
|
||||
pending_time: 30
|
||||
armed_home:
|
||||
pending_time: 0
|
||||
triggered:
|
||||
pending_time: 20
|
||||
trigger_time: 4
|
||||
```
|
||||
|
||||
## {% linkable_title Examples %}
|
||||
|
||||
|
||||
@ -0,0 +1,20 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Satel Integra Alarm Control Panel"
|
||||
description: "Instructions how to setup the Satel Integra control panel within Home Assistant."
|
||||
date: 2017-09-07 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: satel.jpg
|
||||
ha_category: Alarm
|
||||
ha_release: 0.54
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
The `satel_integra` alarm control panel platform allows you to control your [SatelIntegra](http://www.satel.pl/en/) alarms.
|
||||
|
||||
The requirement is that you have setup your [SatelIntegra hub](/components/satel_integra/).
|
||||
|
||||
@ -57,6 +57,7 @@ Configuration variables:
|
||||
- **username** (*Optional*): The username to your Axis device. Default 'root'.
|
||||
- **password** (*Optional*): The password to your Axis device. Default 'pass'.
|
||||
- **trigger_time** (*Optional*): Minimum time (in seconds) a sensor should keep its positive value. Default 0.
|
||||
- **http_port** (*Optional*): Configure port web server of device is accessible from. Default 80.
|
||||
- **location** (*Optional*): Physical location of your Axis device. Default not set.
|
||||
- **include** (*Required*): This cannot be empty else there would be no use adding the device at all.
|
||||
- **camera**: Stream MJPEG video to Home Assistant.
|
||||
|
||||
@ -15,6 +15,8 @@ ha_iot_class: "Cloud Push"
|
||||
|
||||
The `abode` security control panel platform allows you to control your [Abode](https://goabode.com/) alarms.
|
||||
|
||||
This component will automatically add `Door Contact`, `Motion Camera`, `Water Sensor`, `Keypad`, `Glass Break`, and `Status Display` binary sensors that are configured in your Abode account.
|
||||
This component will add `Door Contacts`, `Connectivity` sensors (remotes, keypads, and status indicators), `Moisture` sensors, and `Motion` or `Occupancy` sensors.
|
||||
|
||||
This component will also list all Abode `Quick Actions` that are set up. You can trigger these quick actions by passing the `entity_id` of your quick action binary sensor to the [trigger_quick_action service](/components/abode/#trigger_quick_action).
|
||||
|
||||
The requirement is that you have setup your [Abode hub](/components/abode/).
|
||||
|
||||
28
source/_components/binary_sensor.doorbird.markdown
Normal file
28
source/_components/binary_sensor.doorbird.markdown
Normal file
@ -0,0 +1,28 @@
|
||||
---
|
||||
layout: page
|
||||
title: "DoorBird Binary Sensor"
|
||||
description: "Instructions how to integrate DoorBird video doorbell state into Home Assistant."
|
||||
date: 2017-08-06 11:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: doorbird.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: "0.54"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `doorbird` binary sensor platform allows Home Assistant to monitor when your [DoorBird](http://www.doorbird.com/) doorbell rings.
|
||||
|
||||
<p class='note'>
|
||||
You must have the [DoorBird component](/components/doorbird/) configured to use this binary sensor.
|
||||
</p>
|
||||
|
||||
To enable the binary sensor, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
binary_sensor:
|
||||
- platform: doorbird
|
||||
```
|
||||
20
source/_components/binary_sensor.satel_integra.markdown
Normal file
20
source/_components/binary_sensor.satel_integra.markdown
Normal file
@ -0,0 +1,20 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Satel Integra Binary Sensor"
|
||||
description: "Instructions how to integrate Satel Integra binary sensors into Home Assistant."
|
||||
date: 2017-09-07 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: satel.jpg
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.54
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `satel_integra` binary sensor allows you to monitor your [SatelIntegra](http://www.satel.pl/en/) alarm zones (inputs).
|
||||
|
||||
Check the [type/class](/components/binary_sensor/) list for a possible visualization of your zone.
|
||||
|
||||
The requirement is that you have setup your [SatelIntegra hub](/components/satel_integra/).
|
||||
@ -14,9 +14,9 @@ ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
The `xiaomi` binary sensor platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) binary sensors.
|
||||
The `xiaomi aqara` binary sensor platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) binary sensors.
|
||||
|
||||
The requirement is that you have setup the [`xiaomi` component](/components/xiaomi/).
|
||||
The requirement is that you have setup the [`xiaomi aqara` component](/components/xiaomi_aqara/).
|
||||
|
||||
|
||||
### {% linkable_title Type of sensors supported %}
|
||||
@ -118,7 +118,7 @@ The requirement is that you have setup the [`xiaomi` component](/components/xiao
|
||||
data:
|
||||
title: Fire alarm!
|
||||
message: Fire/Smoke detected!
|
||||
- service: xiaomi.play_ringtone
|
||||
- service: xiaomi_aqara.play_ringtone
|
||||
data:
|
||||
gw_mac: xxxxxxxxxxxx
|
||||
ringtone_id: 2
|
||||
@ -174,7 +174,7 @@ Available events are `single`, `double`, `hold`, `long_click_press` and `long_cl
|
||||
entity_id: binary_sensor.switch_158d000xxxxxc2
|
||||
click_type: long_click_press
|
||||
action:
|
||||
service: xiaomi.play_ringtone
|
||||
service: xiaomi_aqara.play_ringtone
|
||||
data:
|
||||
gw_mac: xxxxxxxxxxxx
|
||||
ringtone_id: 8
|
||||
136
source/_components/calendar.todoist.markdown
Normal file
136
source/_components/calendar.todoist.markdown
Normal file
@ -0,0 +1,136 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Todoist"
|
||||
description: "Instructions on how to integrate Todoist into Home Assistant."
|
||||
date: 2017-08-31 2:22
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: todoist.png
|
||||
ha_category: Calendar
|
||||
ha_iot_class: "Cloud Polling"
|
||||
ha_release: 0.54
|
||||
---
|
||||
|
||||
|
||||
This platform allows you to connect to your [Todoist Projects](https://todoist.com) and generate binary sensors. A different sensor will be created for each individual project, or you can specify "custom" projects which match against criteria you set (more on that below). These sensors will be `on` if you have a task due in that project or `off` if all the tasks in the project are completed or if the project doesn't have any tasks at all. All tasks get updated roughly every 15 minutes.
|
||||
|
||||
### {% linkable_title Prerequisites %}
|
||||
|
||||
You need to determine your Todoist API token. This is fairly simple to do; just go [to the Integrations section on your Todoist settings page](https://todoist.com/Users/viewPrefs?page=authorizations) and find the section labeled "API token" at the bottom of the page. Copy that token and use it in your configuration file.
|
||||
|
||||
### {% linkable_title Basic Setup %}
|
||||
|
||||
To integrate Todoist in Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
calendar:
|
||||
- platform: todoist
|
||||
token: API_token_created_from_steps_above
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **token** (*Required*): The API token used to authorize Home Assistant to access your projects.
|
||||
- **custom_projects** (*Optional*): Details on any "custom" binary sensor projects you want to create.
|
||||
- **name** (*Required*): The name of your custom project. Only required if you specify that you want to create a custom project.
|
||||
- **due_date_days** (*Optional*): Only include tasks due within this many days. If you don't have any tasks with a due date set, this returns nothing.
|
||||
- **labels** (*Optional*): Only include tasks with at least one of these labels (i.e., this works as an `or` statement)..
|
||||
- **include_projects** (*Optional*): Only include tasks in these projects. Tasks in all other projects will be ignored.
|
||||
|
||||
|
||||
### {% linkable_title Custom Projects %}
|
||||
Creating custom projects is super-easy and quite powerful. All you need to run the basic Todoist projects is your API token, but if you wanted, you could go even deeper. Here's an example:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
calendar:
|
||||
- platform: todoist
|
||||
token: !secret todoist_token
|
||||
custom_projects:
|
||||
- name: 'All Projects'
|
||||
- name: 'Due Today'
|
||||
due_date_days: 0
|
||||
- name: 'Due This Week'
|
||||
due_date_days: 7
|
||||
- name: 'Math Homework'
|
||||
labels:
|
||||
- Homework
|
||||
include_projects:
|
||||
- Mathematical Structures II
|
||||
- Calculus II
|
||||
```
|
||||
|
||||
(See [here](https://home-assistant.io/docs/configuration/secrets/) for more details about what that `!secret` does -- it's not exclusive to Todoist, and can help keep your API keys and passwords a little safer!)
|
||||
|
||||
As you can see, there are 4 custom projects here:
|
||||
|
||||
- A project containing *all* of the tasks on this account.
|
||||
|
||||
- A project containing *all* the tasks on this account that are due today.
|
||||
|
||||
- A project containing *all* the tasks on this account due within the next week.
|
||||
|
||||
- A project containing everything with the label "Homework", taking only 2 projects into account.
|
||||
|
||||
You can mix-and-match these attributes to create all sorts of custom projects. You can even use [IFTTT](https://ifttt.com/todoist) to create a task with a certain label, then have Home Assistant do some kind of automation when a task with that label comes due.
|
||||
|
||||
Home Assistant does its best to determine what task in each project is "most" important, and it's that task which has its state reported. You can access the other tasks you have due soon via the `all_tasks` array (see below).
|
||||
|
||||
### {% linkable_title Sensor attributes %}
|
||||
|
||||
- **offset_reached**: Not used.
|
||||
|
||||
- **all_day**: `True` if the reported task doesn't have a due date. `False` if there is a due date set.
|
||||
|
||||
- **message**: The title of the "most important" task coming up in this project.
|
||||
|
||||
- **description**: A URL pointing to the task on the Todoist website.
|
||||
|
||||
- **location**: Not used.
|
||||
|
||||
- **start_time**: The last time the Todoist component got updated. Usually within the last 15 minutes.
|
||||
|
||||
- **end_time**: When the task is due.
|
||||
|
||||
- **all_tasks**: A list of all tasks in this project, sorted from most important to least important.
|
||||
|
||||
- **priority**: The priority Todoist reports this task as having. 1 means lowest priority, 4 means highest. Note that this is the **opposite** of how things are displayed in the Todoist app!
|
||||
|
||||
- **task_comments**: Any comments added to this task.
|
||||
|
||||
- **task_labels**: All labels associated with this task.
|
||||
|
||||
- **overdue**: Whether the reported task is past its due date.
|
||||
|
||||
- **due_today**: Whether the reported task is due today.
|
||||
|
||||
### {% linkable_title Services %}
|
||||
|
||||
Todoist also comes with access to a service, `todoist.new_task`. This service can be used to create a new Todoist task. You can specify labels and a project, or you can leave them blank, and the task will go to your "Inbox" project.
|
||||
|
||||
Here's an example JSON payload:
|
||||
|
||||
```json
|
||||
{
|
||||
"content": "Pick up the mail",
|
||||
"project": "Errands",
|
||||
"labels":"Homework,School",
|
||||
"priority":3,
|
||||
"due_date":"2017-09-12 14:00"
|
||||
}
|
||||
```
|
||||
|
||||
- **content** (*Required*): The name of the task you want to create.
|
||||
|
||||
- **project** (*Optional*): The project to put the task in.
|
||||
|
||||
- **labels** (*Optional*): Any labels you want to add to the task, separated by commas.
|
||||
|
||||
- **priority** (*Optional*): The priority of the task, from 1-4. Again, 1 means least important, and 4 means most important.
|
||||
|
||||
- **due_date** (*Optional*): When the task should be due, in either YYYY-MM-DD format or YYYY-MM-DD HH:MM format.
|
||||
|
||||
Note that there's (currently) no way to mark tasks as done through Home Assistant; task names do not necessarily have to be unique, so you could find yourself in a situation where you close the wrong task.
|
||||
20
source/_components/camera.abode.markdown
Normal file
20
source/_components/camera.abode.markdown
Normal file
@ -0,0 +1,20 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Abode Camera"
|
||||
description: "Instructions how to integrate Abode cameras into Home Assistant."
|
||||
date: 2017-08-26 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: abode.jpg
|
||||
ha_release: 0.54
|
||||
ha_category: Camera
|
||||
ha_iot_class: "Cloud Push"
|
||||
---
|
||||
|
||||
The `abode` security control panel platform allows you to control your [Abode](https://goabode.com/) alarms.
|
||||
|
||||
This component will automatically add `Cameras` configured in your Abode account. You can request a new still image capture by passing the `entity_id` of your cameras to the [capture_image service](/components/abode/#capture_image).
|
||||
|
||||
The requirement is that you have setup your [Abode hub](/components/abode/).
|
||||
32
source/_components/camera.doorbird.markdown
Normal file
32
source/_components/camera.doorbird.markdown
Normal file
@ -0,0 +1,32 @@
|
||||
---
|
||||
layout: page
|
||||
title: "DoorBird Camera"
|
||||
description: "Instructions how to integrate DoorBird video doorbell images into Home Assistant."
|
||||
date: 2017-08-06 11:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: doorbird.png
|
||||
ha_category: Camera
|
||||
ha_release: "0.54"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `doorbird` implementation allows you to view the live video and saved images from your [DoorBird](http://www.doorbird.com/) device in Home Assistant.
|
||||
|
||||
<p class='note'>
|
||||
You must have the [DoorBird component](/components/doorbird/) configured to use this camera.
|
||||
</p>
|
||||
|
||||
To enable the camera, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
camera:
|
||||
- platform: doorbird
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **last_visitor** (*Optional*): Adds a second camera that shows the last picture taken when someone rang the doorbell. Default is `false`.
|
||||
@ -14,7 +14,7 @@ ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
The `xiaomi` cover platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) covers.
|
||||
The `xiaomi aqara` cover platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) covers.
|
||||
|
||||
The requirement is that you have setup [Xiaomi](/components/xiaomi/).
|
||||
The requirement is that you have setup [Xiaomi aqara](/components/xiaomi_aqara/).
|
||||
|
||||
37
source/_components/device_tracker.keenetic_ndms2.markdown
Normal file
37
source/_components/device_tracker.keenetic_ndms2.markdown
Normal file
@ -0,0 +1,37 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Keenetic NDMS2 Routers"
|
||||
description: "Instructions how to integrate Keenetic NDMS2 Routers into Home Assistant."
|
||||
date: 2017-09-15 15:40
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: keenetic.png
|
||||
ha_category: Presence Detection
|
||||
ha_release: 0.54
|
||||
---
|
||||
|
||||
This component offers presence detection by examining devices connected to a [Keenetic](https://keenetic.net/)
|
||||
Router running NDMS2 firmware.
|
||||
|
||||
To use a Keenetic router in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
device_tracker:
|
||||
- platform: keenetic_ndms2
|
||||
host: !secret router_ip
|
||||
username: !secret router_username
|
||||
password: !secret router_password
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Required*): The IP address of your router, e.g. 192.168.1.1.
|
||||
- **username** (*Required*): The username to login into the router (user should have read access to web interface of the router).
|
||||
- **password** (*Required*): The password for the specified username.
|
||||
- **interface** (*Optional*): Ihe internal name of the interface to get devices connected to. Default is 'Home'. For expert users only.
|
||||
|
||||
|
||||
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
|
||||
@ -36,5 +36,6 @@ Configuration variables:
|
||||
|
||||
List of models that are known to use port 80:
|
||||
- Nighthawk X4S - AC2600 (R7800)
|
||||
- Orbi
|
||||
|
||||
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
|
||||
|
||||
32
source/_components/doorbird.markdown
Normal file
32
source/_components/doorbird.markdown
Normal file
@ -0,0 +1,32 @@
|
||||
---
|
||||
layout: page
|
||||
title: "DoorBird"
|
||||
description: "Instructions on how to integrate your DoorBird video doorbell with Home Assistant."
|
||||
date: 2017-08-06 11:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: doorbird.png
|
||||
ha_category: Hub
|
||||
ha_release: "0.54"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `doorbird` implementation allows you to integrate your [DoorBird](http://www.doorbird.com/) device in Home Assistant.
|
||||
|
||||
To connect your device, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
doorbird:
|
||||
host: IP_OR_HOSTNAME
|
||||
username: abcdef0001
|
||||
password: xxxxxxxxxx
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Required*): The LAN IP address or hostname of your device. You can find this by going to the [DoorBird Online check](http://www.doorbird.com/checkonline) and entering the information from the paper that was included in the box.
|
||||
- **username** (*Required*): The username of a non-administrator user account on the device.
|
||||
- **password** (*Required*): The password for the user specified.
|
||||
20
source/_components/light.abode.markdown
Normal file
20
source/_components/light.abode.markdown
Normal file
@ -0,0 +1,20 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Abode Light"
|
||||
description: "Instructions how to integrate Abode lights into Home Assistant."
|
||||
date: 2017-08-26 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: abode.jpg
|
||||
ha_release: 0.54
|
||||
ha_category: Light
|
||||
ha_iot_class: "Cloud Push"
|
||||
---
|
||||
|
||||
The `abode` security control panel platform allows you to control your [Abode](https://goabode.com/) alarms.
|
||||
|
||||
This component will automatically add `Lights` configured in your Abode account. You can reclassify `Switches` to show up within Home Assistant as lights by listing the Abode device ID in your [configuration](/components/abode/#configuration).
|
||||
|
||||
The requirement is that you have setup your [Abode hub](/components/abode/).
|
||||
@ -14,7 +14,7 @@ ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
The `xiaomi` light platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) lights.
|
||||
The `xiaomi aqara` light platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) lights.
|
||||
|
||||
The requirement is that you have setup [Xiaomi](/components/xiaomi/).
|
||||
The requirement is that you have setup [Xiaomi aqara](/components/xiaomi_aqara/).
|
||||
|
||||
@ -13,7 +13,7 @@ ha_version: 0.53
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `xiaomi_philipslight` platform allows you to control the state of your Xiaomi Philips LED Ball Lamp and Xiaomi Philips LED Ceiling Lamp.
|
||||
The `xiaomi_miio` platform allows you to control the state of your Xiaomi Philips LED Ball Lamp and Xiaomi Philips LED Ceiling Lamp.
|
||||
|
||||
Currently, the supported features are `on`, `off`, `set_cct` (colortemp) , `set_bright` (brightness).
|
||||
|
||||
@ -24,7 +24,7 @@ To add a Xiaomi Philips Light to your installation, add the following to your co
|
||||
```yaml
|
||||
# Example configuration.yaml entries
|
||||
light:
|
||||
- platform: xiaomi_philipslight
|
||||
- platform: xiaomi_miio
|
||||
name: Xiaomi Philips Smart LED Ball
|
||||
host: 192.168.130.67
|
||||
token: YOUR_TOKEN
|
||||
37
source/_components/mqtt_statestream.markdown
Normal file
37
source/_components/mqtt_statestream.markdown
Normal file
@ -0,0 +1,37 @@
|
||||
---
|
||||
layout: page
|
||||
title: "MQTT Statestream"
|
||||
description: "Instructions how to setup MQTT Statestream within Home Assistant."
|
||||
date: 2017-09-11 08:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Other
|
||||
ha_release: 0.54
|
||||
ha_iot_class: depends
|
||||
---
|
||||
|
||||
The `mqtt_statestream` component publishes state changes in Home Assistant to individual MQTT topics.
|
||||
|
||||
To enable MQTT Statestream in Home Assistant, add the following section to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
mqtt_statestream:
|
||||
base_topic: homeassistant
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **base_topic** (*Required*): Base topic used to generate the actual topic used to publish.
|
||||
|
||||
## Operation
|
||||
|
||||
When any Home Assistant entity changes, this component will publish that change to MQTT.
|
||||
|
||||
The topic for each entity is different, so you can easily subscribe other systems to just the entities you are interested in.
|
||||
The topic will be in the form `base_topic/domain/entity/state`.
|
||||
|
||||
For example, with the example configuration above, if an entity called 'light.master_bedroom_dimmer' is turned on, this component will publish `on` to `homeassistant/light/master_bedroom_dimmer/state`.
|
||||
79
source/_components/satel_integra.markdown
Normal file
79
source/_components/satel_integra.markdown
Normal file
@ -0,0 +1,79 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Satel Integra Alarm"
|
||||
description: "Instructions on how to integrate a Satel Integra alarm panel with Home Assistant using an ETHM network extension from Satel."
|
||||
date: 2017-09-07 13:28
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: satel.jpg
|
||||
ha_category: Hub
|
||||
ha_release: 0.54
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `satel_integra` component will allow Home Assistant users who own a Satel Integra alarm panel to leverage their alarm system and its sensors to provide Home Assistant with information about their homes. Connectivity between Home Assistant and the alarm is accomplished through a ETHM extension module that must be installed in the alarm.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- [Binary Sensor](/components/binary_sensor.satel_integra/): Reports on zone statuses
|
||||
- [Alarm Control Panel](/components/alarm_control_panel.satel_integra/): Reports on alarm status, and can be used to arm/disarm the system
|
||||
|
||||
The module communicates via Satel's open TCP protocol published on their website. It subscribes for new events coming from alarm system and reacts to them immediately.
|
||||
|
||||
**IMPORTANT:** The library currently doesn't support encrypted connection to your alarm, so you need **to turn off encryption for integration protocol**. In Polish: "koduj integracje" must be unchecked. You will find this setting in your DLOADX program.
|
||||
|
||||
A `satel_integra` section must be present in the `configuration.yaml` file and contain the following options as required:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
satel_integra:
|
||||
host: 192.168.1.100
|
||||
port: 7094
|
||||
partition: 1
|
||||
arm_home_mode: 1
|
||||
|
||||
zones:
|
||||
01:
|
||||
name: 'Bedroom'
|
||||
type: 'motion'
|
||||
02:
|
||||
name: 'Hall'
|
||||
type: 'motion'
|
||||
30:
|
||||
name: 'Kitchen - smoke'
|
||||
type: 'smoke'
|
||||
113:
|
||||
name: 'Entry door'
|
||||
type: 'opening'
|
||||
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Required*): The IP address of the Satel Integra ETHM module on your home network, if using socket type. Default: `localhost`
|
||||
- **port** (*Optional*): The port on which the ETHM module listens for clients using integration protocol. Default: `7094`
|
||||
- **partition** (*Optional*): The partition to operate on. Integra can support multiple partitions, this platform only supports one. Default: `1`
|
||||
- **arm_home_mode** (*Optional*): The mode in which arm Satel Integra when 'arm home' is used. Possible options are `1`,`2` or `3`, default being `1`. For more information on what are the differences between them, please refer to Satel Integra manual.
|
||||
- **zones** (*Optional*): This module does not discover currently which zones are actually in use, so it will only monitor the ones defined in the config. For each zone, a proper ID mus be given as well as it's name (does not need to match the one specified in Satel Integra alarm). For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.alarmdecoder/) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.*
|
||||
|
||||
List of all zone IDs can be taken from DloadX program.
|
||||
|
||||
Having configured the zones, you can use them for automation, such as to react on the movement in your bedroom.
|
||||
For example:
|
||||
|
||||
```yaml
|
||||
alias: Flick the input switch when movement in bedroom detected
|
||||
trigger:
|
||||
platform: state
|
||||
entity_id: 'binary_sensor.bedroom'
|
||||
to: 'on'
|
||||
action:
|
||||
service: input_boolean.turn_on
|
||||
data:
|
||||
entity_id: input_boolean.movement_detected
|
||||
|
||||
```
|
||||
|
||||
Enjoy!
|
||||
@ -14,10 +14,11 @@ ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
The `airvisual` sensor platform queries the [AirVisual](https://airvisual.com/) API for air quality
|
||||
data on the nearest city to a latitude and longitude. The resulting information
|
||||
creates sensors for the Air Quality Index (AQI), the human-friendly air quality
|
||||
level, and the main pollutant of that area. Sensors that conform to either/both
|
||||
the [U.S. and Chinese air quality standards](http://www.clm.com/publication.cfm?ID=366) can be created.
|
||||
data. Data can be collected via latitude/longitude or by city/state/country.
|
||||
The resulting information creates sensors for the Air Quality Index (AQI), the
|
||||
human-friendly air quality level, and the main pollutant of that area. Sensors
|
||||
that conform to either/both the [U.S. and Chinese air quality standards](http://www.clm.com/publication.cfm?ID=366) can be
|
||||
created.
|
||||
|
||||
This platform requires an AirVisual API key, which can be obtained [here](https://airvisual.com/api). Note
|
||||
that the platform was designed using the "Community" package; the "Startup"
|
||||
@ -29,10 +30,10 @@ The "Community" API key is limited to 10,000 calls per month. In order to leave
|
||||
a buffer, the `airvisual` platform queries the API every 10 minutes.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Configuring the Platform %}
|
||||
## {% linkable_title Configuring the Platform via Latitude/Longitude %}
|
||||
|
||||
To enable this platform, add the following lines to your `configuration.yaml`
|
||||
file:
|
||||
To enable the platform and gather data via latitude/longitude, add the
|
||||
following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
@ -52,12 +53,60 @@ Configuration variables:
|
||||
- **monitored_conditions** (*Required*): the air quality standard(s) to use
|
||||
(`us` for U.S., `cn` for Chinese)
|
||||
- **latitude** (*Optional*): the latitude to monitor; if excluded, the latitude
|
||||
defined in `configuration.yaml` will be used
|
||||
defined under the `homeassistant` key in `configuration.yaml` will be used
|
||||
- **longitude** (*Optional*): the longitude to monitor; if excluded, the longitude
|
||||
defined in `configuration.yaml` will be used
|
||||
defined under the `homeassistant` key in `configuration.yaml` will be used
|
||||
- **radius** (*Optional*): the radius (in meters) around the latitude/longitude to
|
||||
search for the nearest city; defaults to `1000`
|
||||
|
||||
## {% linkable_title Configuring the Platform via City/State/Country %}
|
||||
|
||||
To enable the platform and gather data via city/state/country, add the
|
||||
following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
- platform: airvisual
|
||||
api_key: abc123
|
||||
monitored_conditions:
|
||||
- us
|
||||
- cn
|
||||
city: southend-on-sea
|
||||
state: essex
|
||||
country: uk
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **api_key** (*Required*): your AirVisual API key
|
||||
- **monitored_conditions** (*Required*): the air quality standard(s) to use
|
||||
(`us` for U.S., `cn` for Chinese)
|
||||
- **city** (*Optional*): the city to monitor
|
||||
- **state** (*Optional*): the state/region to monitor
|
||||
- **country** (*Optional*): the country to monitor
|
||||
|
||||
To easily determine the proper values for a particular location, use the
|
||||
[AirVisual region directory](https://airvisual.com/world). Once you browse to the particular city you want,
|
||||
take note of the breadcrumb title, which is of the form
|
||||
`country > state/region > city`. Use this information to fill out
|
||||
`configuration.yaml`.
|
||||
|
||||
For example, Sao Paulo, Brazil shows a breadcrumb title of
|
||||
`Brazil > Sao Paulo > Sao Paulo` – thus, the proper configuration would look
|
||||
like this:
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
- platform: airvisual
|
||||
api_key: abc123
|
||||
monitored_conditions:
|
||||
- us
|
||||
- cn
|
||||
city: sao-paulo
|
||||
state: sao-paulo
|
||||
country: brazil
|
||||
```
|
||||
|
||||
## {% linkable_title Sensor Types %}
|
||||
|
||||
When configured, the platform will create three sensors for each configured
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
layout: page
|
||||
title: "One wire Sensor"
|
||||
description: "Instructions how to integrate One wire (1-wire) sensors into Home Assistant."
|
||||
date: 2016-01-17 07:15
|
||||
date: 2017-09-15 10:10
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
@ -22,9 +22,25 @@ Supported devices:
|
||||
- [DS1822](https://datasheets.maximintegrated.com/en/ds/DS1822.pdf)
|
||||
- [DS1825](https://datasheets.maximintegrated.com/en/ds/DS1825.pdf)
|
||||
- [DS28EA00](https://datasheets.maximintegrated.com/en/ds/DS28EA00.pdf) temperature sensors
|
||||
- [DS2406/TAI-8570] (https://datasheets.maximintegrated.com/en/ds/DS2406.pdf) Temperature and pressure sensor made by AAG
|
||||
- [DS2438/B1-R1-A] (https://datasheets.maximintegrated.com/en/ds/DS2438.pdf) Temperature, pressure and humidity sensor by AAG
|
||||
|
||||
The 1-Wire bus can be connected directly to the IO pins of Raspberry Pi or using dedicated interface adapter (e.g [DS9490R](https://datasheets.maximintegrated.com/en/ds/DS9490-DS9490R.pdf)). When an interface adapter is used, sensors can be accessed on Linux hosts via [owfs 1-Wire file system](http://owfs.org/). When using an interface adapter and the owfs, the 'mount_dir' option must be configured to correspond a directory, where owfs device tree has been mounted. If you are using Raspberry Pi and IO pin connected bus setup, don't use the 'mount_dir' option.
|
||||
|
||||
<p class='note warning'>
|
||||
This component has been modified to work with devices with multiple sensors which will cause a discontinuity in recorded values. Existing devices will receive a new ID and therefore show up as new devices.
|
||||
If you wish to maintain continuity it can be resolved in the database by renaming the old devices to the new names.
|
||||
|
||||
Connect to your database using the instructions from https://home-assistant.io/docs/backend/database/
|
||||
Check the names of sensors:
|
||||
SELECT entity_id, COUNT(*) as count FROM states GROUP BY entity_id ORDER BY count DESC LIMIT 10;
|
||||
Alter the names of sensors using the following examples:
|
||||
UPDATE states SET entity_id='sensor.<sensor_name>_temperature' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%\u00b0C%';
|
||||
UPDATE states SET entity_id='sensor.<sensor_name>_pressure' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%mb%';
|
||||
UPDATE states SET entity_id='sensor.<sensor_name>_humidity' WHERE entity_id LIKE 'sensor.<sensor_name>%' AND attributes LIKE '%%%' ESCAPE '';
|
||||
Remember to replace <sensor_name> with the actual name of the sensor as seen in the SELECT query.
|
||||
</p>
|
||||
|
||||
To enable One wire sensors in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
|
||||
@ -14,13 +14,13 @@ ha_release: pre 0.7
|
||||
---
|
||||
|
||||
|
||||
The `swiss_public_transport` sensor will give you the next two departure times from a given location to another one in Switzerland.
|
||||
The `swiss_public_transport` sensor will give you the next three departure times from a given location to another one in Switzerland.
|
||||
|
||||
The [Stationboard](http://transport.opendata.ch/examples/stationboard.html) website can help to determine the exact name of the start and the end station. With the station names it's necessary to search for the ID of those stations:
|
||||
The [Swiss public transport API](http://transport.opendata.ch/) only allows 1000 requests per 24 hours.
|
||||
|
||||
http://transport.opendata.ch/v1/locations?query=[Station name]
|
||||
The [Stationboard](http://transport.opendata.ch/examples/stationboard.html) website can help to determine the exact name of the start and the end station.
|
||||
|
||||
If the score is 100 ("score":"100" in the response), it is a perfect match. Then add the data to your `configuration.yaml` file as shown in the example:
|
||||
Then add the data to your `configuration.yaml` file as shown in the example:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -34,5 +34,6 @@ Configuration variables:
|
||||
|
||||
- **from** (*Required*): The ID of the station of the start station.
|
||||
- **to** (*Required*): The ID of the station of the end station.
|
||||
- **name** (*Optional*): The name of the sensor. Defaults to 'Next Departure'.
|
||||
|
||||
The public timetables are coming from [Swiss public transport](http://transport.opendata.ch).
|
||||
|
||||
31
source/_components/sensor.worxlandroid.markdown
Normal file
31
source/_components/sensor.worxlandroid.markdown
Normal file
@ -0,0 +1,31 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Worx Landroid"
|
||||
description: "Instructions how to integrate Worx Landroid WG796E.1 or WG797E as sensors within Home Assistant."
|
||||
date: 2017-09-12 13:23
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: DIY
|
||||
ha_release: 0.54
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `worxlandroid` sensor platform allows you to get the current state, battery level and error status Worx Landroid WG796E.1 or WG797E.
|
||||
|
||||
To use your Worx Landroid mower in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
platform: worxlandroid
|
||||
host: 192.168.0.10
|
||||
pin: 1234
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Required*): The ip address or host name of the mower.
|
||||
- **pin** (*Required*): The pin code for the mower.
|
||||
- **allow_unreachable** (*Optional*): This will allow the mower to be outside of wifi range without raising an error (default: True).
|
||||
@ -14,7 +14,7 @@ ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
The `xiaomi` sensor platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) sensors.
|
||||
The `xiaomi aqara` sensor platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) sensors.
|
||||
|
||||
The requirement is that you have setup [Xiaomi](/components/xiaomi/).
|
||||
The requirement is that you have setup [Xiaomi aqara](/components/xiaomi_aqara/).
|
||||
|
||||
@ -15,6 +15,8 @@ ha_iot_class: "Cloud Push"
|
||||
|
||||
The `abode` security control panel platform allows you to control your [Abode](https://goabode.com/) alarms.
|
||||
|
||||
This component will automatically add `Power Switch Sensors` configured in your Abode account.
|
||||
This component will automatically add `Power Switches` configured in your Abode account. You can reclassify switches to show up within Home Assistant as `Lights` by listing the Abode device ID in your [configuration](/components/abode/#configuration).
|
||||
|
||||
This component will also list all Abode `Automations` that are set up within the Abode system, allowing you to activate and deactivate the automations.
|
||||
|
||||
The requirement is that you have setup your [Abode hub](/components/abode/).
|
||||
|
||||
@ -31,12 +31,17 @@ Configuration variables:
|
||||
- **mac** (*Required*): Device MAC address.
|
||||
- **timeout** (*Optional*): Timeout in seconds for the connection to the device.
|
||||
- **friendly_name** (*Optional*): The name used to display the switch in the frontend.
|
||||
- **type** (*Required for some models*): Switch type. Choose one from: `rm`, `rm2`, `rm_mini`, `rm_pro_phicomm`, `rm2_home_plus`, `rm2_home_plus_gdt`, `rm2_pro_plus`, `rm2_pro_plus2`, `rm2_pro_plus_bl`, `rm_mini_shate`, `sp1`, `sp2`, `honeywell_sp2`, `sp3`, `spmini2` or `spminiplus`.
|
||||
- **type** (*Required for some models*): Switch type. Choose one from: `rm`, `rm2`, `rm_mini`, `rm_pro_phicomm`, `rm2_home_plus`, `rm2_home_plus_gdt`, `rm2_pro_plus`, `rm2_pro_plus2`, `rm2_pro_plus_bl`, `rm_mini_shate`, `sp1`, `sp2`, `honeywell_sp2`, `sp3`, `spmini2`, `spminiplus` or `mp1`.
|
||||
- **switches** (*Optional*): The array that contains all switches.
|
||||
- **identifier** (*Required*): Name of the command switch as slug. Multiple entries are possible.
|
||||
- **friendly_name** (*Optional*): The name used to display the switch in the frontend.
|
||||
- **command_on** (*Required*): Base64 encoded packet from RM device to take for on.
|
||||
- **command_off** (*Required*): Base64 encoded packet from RM device to take for off.
|
||||
- **slots** (*Optional*): Friendly names of 4 slots of MP1 power strip. If not configured, slot name will be `switch's friendly_name + 'slot {slot_index}'`. e.g 'MP1 slot 1'
|
||||
- **slot_1** (*Optional*)
|
||||
- **slot_2** (*Optional*)
|
||||
- **slot_3** (*Optional*)
|
||||
- **slot_4** (*Optional*)
|
||||
|
||||
Information about how to install on Windows can be found [here](https://home-assistant.io/components/sensor.broadlink/#microsoft-windows-installation)
|
||||
|
||||
@ -103,6 +108,24 @@ switch:
|
||||
friendly_name: 'Humidifier'
|
||||
```
|
||||
|
||||
Example config for `mp1` device:
|
||||
|
||||
```yaml
|
||||
switch:
|
||||
- platform: broadlink
|
||||
host: IP_ADDRESS
|
||||
mac: 'MAC_ADDRESS'
|
||||
type: mp1
|
||||
friendly_name: 'MP1'
|
||||
slots:
|
||||
# friendly name of slots - optional
|
||||
# if not set, slot name will be switch's friendly_name + 'slot {slot_index}'. e.g 'MP1 slot 1'
|
||||
slot_1: 'TV slot'
|
||||
slot_2: 'Xbox slot'
|
||||
slot_3: 'Fan slot'
|
||||
slot_4: 'Speaker slot'
|
||||
```
|
||||
|
||||
### {% linkable_title Service `send_packet` %}
|
||||
|
||||
You can use the service broadlink/send_packet to directly send IR packets without the need to assign a switch entity for each command.
|
||||
|
||||
35
source/_components/switch.doorbird.markdown
Normal file
35
source/_components/switch.doorbird.markdown
Normal file
@ -0,0 +1,35 @@
|
||||
---
|
||||
layout: page
|
||||
title: "DoorBird Switch"
|
||||
description: "Instructions how to integrate DoorBird video doorbell relays into Home Assistant."
|
||||
date: 2017-08-06 11:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: doorbird.png
|
||||
ha_category: Switch
|
||||
ha_release: "0.54"
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `doorbird` switch platform allows you to power relays in your [DoorBird](http://www.doorbird.com/) video doorbell device.
|
||||
|
||||
<p class='note'>
|
||||
You must have the [DoorBird component](/components/doorbird/) configured to use this switch.
|
||||
</p>
|
||||
|
||||
To enable this switch, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
- platform: doorbird
|
||||
switches:
|
||||
- light_on
|
||||
- open_door
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **switches** (*Required*): A list of switches to include. Possible entries are `light_on` for control of the IR array and `open_door` for control of an electronic door strike or alarm.
|
||||
@ -29,7 +29,9 @@ Configuration variables:
|
||||
|
||||
- **resource** (*Required*): The resource or endpoint that contains the value.
|
||||
- **name** (*Optional*): Name of the REST switch.
|
||||
- **method** (*Optional*): HTTP method to use (`post` or `put`). Defaults to `post`.
|
||||
- **method** (*Optional*): HTTP method to use (`post` or `put`). Defaults to `post`.
|
||||
- **username** (*Optional*): The username for accessing the REST endpoint.
|
||||
- **password** (*Optional*): The password for accessing the REST endpoint.
|
||||
- **body_on** (*Optional*): The body of the POST request that commands the switch to become enabled. Default is "ON". This value can be a [template](/topics/templating/).
|
||||
- **body_off** (*Optional*): The body of the POST request that commands the switch to become disabled. Default is "OFF". This value can also be a [template](/topics/templating/).
|
||||
- **is_on_template** (*Optional*): A [template](/docs/configuration/templating/#processing-incoming-data) that determines the state of the switch from the value returned by the GET request on the resource URL. This template should compute to a boolean (True or False). If the value is valid JSON, it will be available in the template as the variable `value_json`. Default is equivalent to `'{% raw %}{{ value_json == body_on }}{% endraw %}'`. This means that by default, the state of the switch is on if and only if the response to the GET request matches .
|
||||
|
||||
44
source/_components/switch.telnet.markdown
Normal file
44
source/_components/switch.telnet.markdown
Normal file
@ -0,0 +1,44 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Telnet Switch"
|
||||
description: "Instructions how to integrate telnet switches into Home Assistant."
|
||||
date: 2017-08-10 19:19
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Switch
|
||||
ha_release: 0.54
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
The `telnet` switch platform allows you to control devices with telnet commands.
|
||||
|
||||
To enable this switch, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
platform: telnet
|
||||
switches:
|
||||
projector:
|
||||
resource: "host_or_ip"
|
||||
port: 4002
|
||||
command_on: "PWR ON"
|
||||
command_off: "PWR OFF"
|
||||
command_state: "PWR?"
|
||||
value_template: '{% raw %}{{ value == "PWR=01" }}{% endraw %}'
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **switches** (*Required*): The array that contains all switches.
|
||||
- **identifier** (*Required*): Name of the switch as slug. Multiple entries are possible.
|
||||
- **resource** (*Required*): Host or IP of the device.
|
||||
- **port** (*Optional*): Port to connect to. Default is 23 if not defined.
|
||||
- **command_on** (*Required*): Command to turn device on.
|
||||
- **command_off** (*Required*): Command to turn device off.
|
||||
- **command_state** (*Required*): Command to determine the state of the switch. If not defined the switch will assume successful state changes.
|
||||
- **value_template** (*Required*): The template evaluating to `true` will indicate the switch is on.
|
||||
- **name** (*Optional*): The name used to display the switch in the frontend.
|
||||
@ -14,7 +14,7 @@ ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
|
||||
The `xiaomi` switch platform allows you to get data from your [Xiaomi](http://www.mi.com/en/) switches.
|
||||
The `xiaomi aqara` switch platform allows you to get data from your [Xiaomi aqara](http://www.mi.com/en/) switches.
|
||||
|
||||
The requirement is that you have setup [Xiaomi](/components/xiaomi/).
|
||||
The requirement is that you have setup [Xiaomi aqara](/components/xiaomi_aqara/).
|
||||
|
||||
@ -26,13 +26,13 @@ tts:
|
||||
Configuration variables:
|
||||
|
||||
- **api_key** (*Required*): API Key for use this service.
|
||||
- **language** (*Optional*): The language to use. Defaults to `en-us`. Supported `en-EN`, `ru-RU`, `uk-UK`, `tr-TR`.
|
||||
- **language** (*Optional*): The language to use. Defaults to `en-US`. Supported `en-US`, `ru-RU`, `uk-UK`, `tr-TR`.
|
||||
- **codec** (*Optional*): Audo codec. Default is `mp3`. Supported us `mp3`, `wav`, `opus`.
|
||||
- **voice** (*Optional*): Speaker voice. Default is `zahar`. Supported female voices are `jane`, `oksana`, `alyss`, 'omazh` and male voices are `zahar` and `ermil`.
|
||||
- **voice** (*Optional*): Speaker voice. Default is `zahar`. Supported female voices are `jane`, `oksana`, `alyss`, `omazh` and male voices are `zahar` and `ermil`.
|
||||
- **emotion** (*Optional*): Speaker emotional intonation. Default is `neutral`. Also supported are `good` (freindly) and `evil` (angry)
|
||||
- **speed** (*Optional*): Speech speed. Default value is `1`. Highest speed is `3` and lowest `0,1`
|
||||
|
||||
See on api [documentation](https://tech.yandex.com/speechkit/cloud/doc/dg/concepts/speechkit-dg-tts-docpage/) for details. N.B. english version of documentation is outdated. So you could receive api key [here](https://developer.tech.yandex.ru/)
|
||||
Please check the [API documentation](https://tech.yandex.com/speechkit/cloud/doc/guide/concepts/tts-http-request-docpage/) for details. It seems that the English version of documentation is outdated. You could request an API key [by email](https://tech.yandex.com/speechkit/cloud/) or [online](https://developer.tech.yandex.ru/).
|
||||
|
||||
A full configuration sample:
|
||||
|
||||
|
||||
137
source/_components/vacuum.mqtt.markdown
Normal file
137
source/_components/vacuum.mqtt.markdown
Normal file
@ -0,0 +1,137 @@
|
||||
---
|
||||
layout: page
|
||||
title: "MQTT Vacuum"
|
||||
description: "Instructions how to integrate your MQTT enabled Vacuum within Home Assistant."
|
||||
date: 2017-09-11 20:26
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: mqtt.png
|
||||
ha_category: Vacuum
|
||||
ha_release: 0.54
|
||||
---
|
||||
|
||||
The `mqtt` component allows you to control your MQTT-enabled vacuum.
|
||||
|
||||
To add your MQTT vacuum to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
vacuum:
|
||||
- platform: mqtt
|
||||
name: "MQTT Vacuum"
|
||||
supported_features:
|
||||
- turn_on
|
||||
- turn_off
|
||||
- pause
|
||||
- stop
|
||||
- return_home
|
||||
- battery
|
||||
- status
|
||||
- locate
|
||||
- clean_spot
|
||||
- fan_speed
|
||||
- send_command
|
||||
command_topic: "vacuum/command"
|
||||
battery_level_topic: "vacuum/state"
|
||||
battery_level_template: "{{ value_json.battery_level }}"
|
||||
charging_topic: "vacuum/state"
|
||||
charging_template: "{{ value_json.charging }}"
|
||||
cleaning_topic: "vacuum/state"
|
||||
cleaning_template: "{{ value_json.cleaning }}"
|
||||
docked_topic: "vacuum/state"
|
||||
docked_template: "{{ value_json.docked }}"
|
||||
fan_speed_topic: "vacuum/state"
|
||||
fan_speed_template: "{{ value_json.fan_speed }}"
|
||||
set_fan_speed_topic: "vacuum/set_fan_speed"
|
||||
fan_speed_list:
|
||||
- min
|
||||
- medium
|
||||
- high
|
||||
- max
|
||||
send_command_topic: 'vacuum/send_command'
|
||||
```
|
||||
|
||||
Basic Configuration variables:
|
||||
|
||||
- **name** (*Optional*): The name of the vacuum. Defaults to `MQTT Vacuum`.
|
||||
- **supported_features** (*Optional*): List of features that the vacuum supports (possible values are `turn_on`, `turn_off`, `pause`, `stop`, `return_home`, `battery`, `status`, `locate`, `clean_spot`, `fan_speed`, `send_command`). Defaults to `turn_on`, `turn_off`, `stop`, `return_home`, `status`, `battery`, `clean_spot`.
|
||||
- **command_topic** (*Optional*): The MQTT topic to publish commands to control the vacuum.
|
||||
|
||||
Advanced Configuration variables:
|
||||
|
||||
- **qos** (*Optional*): The maximum QoS level of the state topic. Defaults to `0`. Will also be used when publishing messages.
|
||||
- **retain** (*Optional*): If the published message should have the retain flag on or not. Defaults to `false`.
|
||||
- **payload_turn_on** (*Optional*): The payload to send to the `command_topic` to begin the cleaning cycle. Defaults to `turn_on`.
|
||||
- **payload_turn_off** (*Optional*): The payload to send to the `command_topic` to turn the vacuum off. Defaults to `turn_off`.
|
||||
- **payload_return_to_base** (*Optional*): The payload to send to the `command_topic` to tell the vacuum to return to base. Defaults to `return_to_base`.
|
||||
- **payload_stop** (*Optional*): The payload to send to the `command_topic` to stop the vacuum. Defaults to `stop`.
|
||||
- **payload_clean_spot** (*Optional*): The payload to send to the `command_topic` to begin a spot cleaning cycle. Defaults to `clean_spot`.
|
||||
- **payload_locate** (*Optional*): The payload to send to the `command_topic` to locate the vacuum (typically plays a song). Defaults to `locate`.
|
||||
- **payload_start_pause** (*Optional*): The payload to send to the `command_topic` to start or pause the vacuum. Defaults to `start_pause`.
|
||||
- **battery_level_topic** (*Optional*): The MQTT topic subscribed to receive battery level values from the vacuum.
|
||||
- **battery_level_template** (*Optional*): Defines a [template](/topics/templating/) to define the battery level of the vacuum.
|
||||
- **charging_topic** (*Optional*): The MQTT topic subscribed to receive charging state values from the vacuum.
|
||||
- **charging_template** (*Optional*): Defines a [template](/topics/templating/) to define the charging state of the vacuum.
|
||||
- **cleaning_topic** (*Optional*): The MQTT topic subscribed to receive cleaning state values from the vacuum.
|
||||
- **cleaning_template** (*Optional*): Defines a [template](/topics/templating/) to define the cleaning state of the vacuum.
|
||||
- **docked_topic** (*Optional*): The MQTT topic subscribed to receive docked state values from the vacuum.
|
||||
- **docked_template** (*Optional*): Defines a [template](/topics/templating/) to define the docked state of the vacuum.
|
||||
- **fan_speed_topic** (*Optional*): The MQTT topic subscribed to receive fan speed values from the vacuum.
|
||||
- **fan_speed_template** (*Optional*): Defines a [template](/topics/templating/) to define the fan speed of the vacuum.
|
||||
- **set_fan_speed_topic** (*Optional*): The MQTT topic to publish commands to control the vacuum's fan speed.
|
||||
- **fan_speed_list** (*Optional*): List of possible fan speeds for the vacuum.
|
||||
- **send_command_topic** (*Optional*): The MQTT topic to publish custom commands to the vacuum.
|
||||
|
||||
### {% linkable_title Default MQTT Protocol %}
|
||||
|
||||
The above configuration for this component expects an MQTT protocol like the following.
|
||||
|
||||
#### Basic Commands
|
||||
|
||||
MQTT topic: `vacuum/command`
|
||||
|
||||
Possible MQTT payloads:
|
||||
- `turn_on` - Begin cleaning
|
||||
- `turn_off` - Turn the Vacuum off
|
||||
- `return_to_base` - Return to base/dock
|
||||
- `stop` - Stop the Vacuum
|
||||
- `clean_spot` - Initialize a spot cleaning cycle
|
||||
- `locate` - Locate the vacuum (typically by playing a song)
|
||||
- `start_pause` - Toggle the vacuum between cleaning and stopping
|
||||
|
||||
#### Set Fan Speed
|
||||
|
||||
MQTT topic: `vacuum/set_fan_speed`
|
||||
|
||||
Possible MQTT payloads:
|
||||
- `min` - Minimum fan speed
|
||||
- `medium` - Medium fan speed
|
||||
- `high` - High fan speed
|
||||
- `max` - Max fan speed
|
||||
|
||||
#### Send Custom Command
|
||||
|
||||
MQTT topic: `vacuum/send_command`
|
||||
|
||||
MQTT payload for `send_command` can be an arbitrary value handled by the vacuum's MQTT-enabled firmware.
|
||||
|
||||
#### Status/Sensor Updates
|
||||
|
||||
MQTT topic: `vacuum/state`
|
||||
|
||||
MQTT payload:
|
||||
```json
|
||||
{
|
||||
"battery_level": 61,
|
||||
"docked": true,
|
||||
"cleaning": false,
|
||||
"charging": true,
|
||||
"fan_speed": "off"
|
||||
}
|
||||
```
|
||||
|
||||
### {% linkable_title Retrofitting a non-wifi Roomba with an ESP8266 %}
|
||||
|
||||
- [This repo](https://github.com/johnboiles/esp-roomba-mqtt) has MQTT client firmware for retrofitting your old Roomba.
|
||||
@ -13,7 +13,7 @@ ha_release: 0.51
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `xiaomi` vacuum platform allows you to control the state of your [Xiaomi Mi Robot Vacuum](http://www.mi.com/roomrobot/).
|
||||
The `xiaomi miio` vacuum platform allows you to control the state of your [Xiaomi Mi Robot Vacuum](http://www.mi.com/roomrobot/).
|
||||
|
||||
Current supported features are `turn_on`, `pause`, `stop`, `return_to_home`, `turn_off` (stops goes to dock), `locate`, `clean_spot`, `set_fanspeed` and even remote control your robot.
|
||||
|
||||
@ -24,7 +24,7 @@ To add a vacuum to your installation, add the following to your `configuration.y
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
vacuum:
|
||||
- platform: xiaomi
|
||||
- platform: xiaomi_miio
|
||||
host: 192.168.1.2
|
||||
token: YOUR_TOKEN
|
||||
```
|
||||
@ -13,7 +13,7 @@ ha_release: "0.50"
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `xiaomi` platform allows you to integrate the following [Xiaomi](http://www.mi.com/en/) devices into Home Assistant.
|
||||
The `xiaomi aqara` platform allows you to integrate the following [Xiaomi](http://www.mi.com/en/) devices into Home Assistant.
|
||||
|
||||
- Temperature and Humidity Sensor (1st and 2nd generation)
|
||||
- Motion Sensor (1st and 2nd generation)
|
||||
@ -52,7 +52,7 @@ To enable Xiaomi gateway in your installation, add the following to your `config
|
||||
|
||||
```yaml
|
||||
# You can leave mac empty if you only have one gateway.
|
||||
xiaomi:
|
||||
xiaomi_aqara:
|
||||
gateways:
|
||||
- mac:
|
||||
key: xxxxxxxxxxxxxxxx
|
||||
@ -62,7 +62,7 @@ xiaomi:
|
||||
|
||||
```yaml
|
||||
# 12 characters mac can be obtained from the gateway.
|
||||
xiaomi:
|
||||
xiaomi_aqara:
|
||||
gateways:
|
||||
- mac: xxxxxxxxxxxx
|
||||
key: xxxxxxxxxxxxxxxx
|
||||
@ -74,7 +74,7 @@ xiaomi:
|
||||
|
||||
```yaml
|
||||
# 12 characters MAC can be obtained from the gateway.
|
||||
xiaomi:
|
||||
xiaomi_aqara:
|
||||
interface: '192.168.0.1'
|
||||
gateways:
|
||||
- mac: xxxxxxxxxxxx
|
||||
@ -108,7 +108,7 @@ Automation example
|
||||
entity_id: binary_sensor.switch_158d000xxxxxc2
|
||||
click_type: long_click_press
|
||||
action:
|
||||
service: xiaomi.play_ringtone
|
||||
service: xiaomi_aqara.play_ringtone
|
||||
data:
|
||||
gw_mac: xxxxxxxxxxxx
|
||||
ringtone_id: 8
|
||||
@ -122,7 +122,7 @@ Automation example
|
||||
entity_id: binary_sensor.switch_158d000xxxxxc2
|
||||
click_type: single
|
||||
action:
|
||||
service: xiaomi.stop_ringtone
|
||||
service: xiaomi_aqara.stop_ringtone
|
||||
data:
|
||||
gw_mac: xxxxxxxxxxxx
|
||||
```
|
||||
@ -35,7 +35,7 @@ The best way to show what AppDaemon does is through a few simple examples.
|
||||
Let's start with a simple App to turn a light on every night at sunset and off every morning at sunrise. Every App when first started will have its `initialize()` function called, which gives it a chance to register a callback for AppDaemons's scheduler for a specific time. In this case, we are using `run_at_sunrise()` and `run_at_sunset()` to register two separate callbacks. The argument `0` is the number of seconds offset from sunrise or sunset and can be negative or positive. For complex intervals, it can be convenient to use Python's `datetime.timedelta` class for calculations. When sunrise or sunset occurs, the appropriate callback function, `sunrise_cb()` or `sunset_cb()`, is called, which then makes a call to Home Assistant to turn the porch light on or off by activating a scene. The variables `args["on_scene"]` and `args["off_scene"]` are passed through from the configuration of this particular App, and the same code could be reused to activate completely different scenes in a different version of the App.
|
||||
|
||||
```python
|
||||
import homeassistant.appapi as appapi
|
||||
import appdaemon.appapi as appapi
|
||||
|
||||
class OutsideLights(appapi.AppDaemon):
|
||||
|
||||
|
||||
@ -69,7 +69,7 @@ This is also fairly easy to achieve with Home Assistant automations, but we are
|
||||
Our next example is to turn on a light when motion is detected and it is dark, and turn it off after a period of time. This time, the `initialize()` function registers a callback on a state change (of the motion sensor) rather than a specific time. We tell AppDaemon that we are only interested in state changesd where the motion detector comes on by adding an additional parameter to the callback registration - `new = "on"`. When the motion is detected, the callack function `motion()` is called, and we check whether or not the sun has set using a built-in convenience function: `sun_down()`. Next, we turn the light on with `turn_on()`, then set a timer using `run_in()` to turn the light off after 60 seconds, which is another call to the scheduler to execute in a set time from now, which results in `AppDaemon` calling `light_off()` 60 seconds later using the `turn_off()` call to actually turn the light off. This is still pretty simple in code terms:
|
||||
|
||||
```python
|
||||
import homeassistant.appapi as appapi
|
||||
import appdaemon.appapi as appapi
|
||||
|
||||
class FlashyMotionLights(appapi.AppDaemon):
|
||||
|
||||
|
||||
@ -37,9 +37,9 @@ optional arguments:
|
||||
--log-rotate-days LOG_ROTATE_DAYS
|
||||
Enables daily log rotation and keeps up to the
|
||||
specified days
|
||||
--log-file LOG_FILE Log file to write to. If not set, CONFIG/home-
|
||||
assistant.log is used
|
||||
--runner On restart exit with code 100
|
||||
--script ... Run one of the embedded scripts
|
||||
--daemon Run Home Assistant as daemon
|
||||
```
|
||||
|
||||
|
||||
|
||||
355
source/_posts/2017-09-23-release-54.markdown
Normal file
355
source/_posts/2017-09-23-release-54.markdown
Normal file
@ -0,0 +1,355 @@
|
||||
---
|
||||
layout: post
|
||||
title: "0.54: Todoist, DoorBird, Abode cameras"
|
||||
description: "4 years of Home Assistant is celebrated with another great release."
|
||||
date: 2017-09-23 00:11:05
|
||||
date_formatted: "September 23, 2017"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Release-Notes
|
||||
og_image: /images/blog/2017-09-0.54/components.png
|
||||
---
|
||||
|
||||
<a href='/components/#version/0.54'><img src='/images/blog/2017-09-0.54/components.png' style='border: 0;box-shadow: none;'></a>
|
||||
|
||||
We're approaching the end of September and that means that it was our birthday! We are now officially 4 years old and are getting more amazing with every release. This release too will include some great new stuff and tons of bugfixes. Included is a bug fix by [@fanthos] that should fix the frontend in some browsers. If you had issues with your browser before, make sure to check out this release.
|
||||
|
||||
This release we've started the work to make our Xiaomi integrations more robust. This meant that we've had to rename the components to make it more clear which of the Xiaomi protocols are being used. We have some developers working on making this very affordable home automation solution a first class citizen in the Home Assistant ecosystem, stay tuned for more integrations!
|
||||
|
||||
Another cool thing in this release is the new [`mqtt_statestream`][mqtt_statestream docs] component to export state changes to MQTT. Each entity will be exported on their own topic which makes it very easy to subscribe to individual entity updates.
|
||||
|
||||
## {% linkable_title New Platforms %}
|
||||
|
||||
- Added mqtt_statestream component ([@mw-white] - [#9286]) ([mqtt_statestream docs]) (new-platform)
|
||||
- Add support for Todoist platform ([@Jay2645] - [#9236]) ([calendar.todoist docs]) (new-platform)
|
||||
- DoorBird Component ([@Klikini] - [#9281]) ([doorbird docs]) ([binary_sensor.doorbird docs]) ([camera.doorbird docs]) ([switch.doorbird docs]) (new-platform)
|
||||
- Basic MQTT vacuum support ([@johnboiles] - [#9386]) ([vacuum docs]) ([vacuum.mqtt docs]) (new-platform)
|
||||
- Added Zyxel Keenetic NDMS2 based routers support for device tracking ([@foxel] - [#9315]) ([device_tracker.keenetic_ndms2 docs]) (new-platform)
|
||||
- Telnet switch ([@multiholle] - [#8913]) ([switch.telnet docs]) (new-platform)
|
||||
- Abode services, events, lights, cameras, automations, quick actions. ([@MisterWil] - [#9310]) ([abode docs]) ([alarm_control_panel.abode docs]) ([binary_sensor.abode docs]) ([camera.abode docs]) ([cover.abode docs]) ([light.abode docs]) ([lock.abode docs]) ([switch.abode docs]) (new-platform)
|
||||
- Added satel_integra alarm panel and binary sensor platform ([@c-soft] - [#9336]) ([satel_integra docs]) ([alarm_control_panel.satel_integra docs]) ([binary_sensor.satel_integra docs]) (new-platform)
|
||||
- Worx Landroid sensor ([@nilzen] - [#9416]) ([sensor.worxlandroid docs]) (new-platform)
|
||||
|
||||
## {% linkable_title If you need help... %}
|
||||
...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
|
||||
|
||||
## {% linkable_title Reporting Issues %}
|
||||
Experiencing issues introduced by this release? Please report them in our [issue tracker][issue]. Make sure to fill in all fields of the issue template.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## {% linkable_title Breaking Changes %}
|
||||
|
||||
- Sensor - OneWire: This update changes the names of the sensors from `<sensor_name>` to `<sensor_name> <Sensor_type>` ([@tcastberg] - [#9404]) ([sensor.onewire docs]) (breaking change)
|
||||
- Renamed Xiaomi platforms to include their protocol names. xiaomi -> xiaomi_aqara, xiaomi_aqara.switch, xiaomi_aqara.light, xiaomi_aqara.binary_sensor, ... and vacuum.xiaomi, xiaomi_philipslight -> xiaomi_miio, vacuum.xiaomi_miio, light.xiaomi_miio ([@danielhiversen] - [#9426]) (breaking change)
|
||||
- Swiss Public Transport sensor: All times handled by the Swiss Public Transport sensor are now in ISO 8601 format. Please update your templates sensors and automations. ([@fabaff] - [#9129]) ([sensor.swiss_public_transport docs]) (breaking change)
|
||||
- iOS: All category identifiers need to be lowercase. If you do not update, it will break actionable notifications to IOS devices sent by scripts/automations. ([@rbflurry] - [#9427]) (breaking change)
|
||||
- Fitbit: Put endpoints behind `/api` like the other oauth-using components ([@happyleavesaoc] - [#9460]) ([sensor.fitbit docs]) (breaking change)
|
||||
- Version 0.53 introduced a bug in the HomeMatic component which breaks the usage of system variables on the CCU / Homegear. This has not been fixed yet. If you are using these variables in your automations you should skip updates until the bug has been resolved. Upgrading is safe however if you only interact with devices.
|
||||
|
||||
## {% linkable_title All changes %}
|
||||
|
||||
- Add HTTP Basic auth to RESTful Switch ([@amelchio] - [#9162]) ([switch.rest docs])
|
||||
- Bump pywebpush and pyJWT versions ([@fanaticDavid] - [#9355]) ([notify.html5 docs])
|
||||
- Add /usr/sbin to PATH ([@morberg] - [#9364])
|
||||
- Add polling interval service and setting available through zwave node entity panel ([@turbokongen] - [#9056]) ([zwave docs])
|
||||
- Round off probability to 2 decimals. ([@arsaboo] - [#9365]) ([binary_sensor.bayesian docs])
|
||||
- Added mqtt_statestream component ([@mw-white] - [#9286]) ([mqtt_statestream docs]) (new-platform)
|
||||
- typo in waypoint import topic preventing waypoint import ([@diplix] - [#9338]) ([device_tracker.owntracks docs])
|
||||
- Cleanup and simplitfy the async state update ([@pvizeli] - [#9390])
|
||||
- Update cloud auth ([@balloob] - [#9357])
|
||||
- Allow multiple observations of same entity ([@jlmcgehee21] - [#9391]) ([binary_sensor.bayesian docs])
|
||||
- Break up Alexa per functionality ([@balloob] - [#9400]) ([alexa docs])
|
||||
- Upgrade psutil to 5.3.1 ([@fabaff] - [#9403]) ([sensor.systemmonitor docs])
|
||||
- fix mopar sensor ([@happyleavesaoc] - [#9389]) ([sensor.mopar docs])
|
||||
- Support specifying no Apple TVs ([@postlund] - [#9394]) ([apple_tv docs])
|
||||
- Update netdisco to 1.2.0 ([@balloob] - [#9408])
|
||||
- components/xiaomi: Add initial discovery using NetDisco. ([@pfalcon] - [#9283])
|
||||
- Fix copy&paste mistake ([@tinloaf] - [#9378])
|
||||
- Added log-file command line flag ([@TD22057] - [#9422])
|
||||
- Add LC_CTYPE to environment variables in macOS ([@morberg] - [#9227])
|
||||
- Added more devices and types to onewire ([@tcastberg] - [#9404]) ([sensor.onewire docs]) (breaking change)
|
||||
- Bump uvcclient to 0.10.1 to work with beta NVR releases ([@antonym] - [#9423]) ([camera.uvc docs])
|
||||
- full RGB support for users of tradfri GW ([@spektren] - [#9411]) ([light.tradfri docs])
|
||||
- Add support for Todoist platform ([@Jay2645] - [#9236]) ([calendar.todoist docs]) (new-platform)
|
||||
- Fix artwork bug in Apple TV ([@postlund] - [#9415]) ([media_player.apple_tv docs])
|
||||
- Bump python-mirobo for improved device support and introduce API changes. ([@syssi] - [#9424])
|
||||
- MPD small improvements ([@pdanilew] - [#9301]) ([media_player.mpd docs])
|
||||
- update broadlink.py to add support for MP1 switch ([@giangvo] - [#9222]) ([switch.broadlink docs])
|
||||
- Fix displaying of friendly_name for light template component ([@rollbrettler] - [#9413]) ([light.template docs])
|
||||
- Improve Python script ([@doudz] - [#9417]) ([python_script docs])
|
||||
- Add manual alarm_control_panel pending time per state ([@snjoetw] - [#9264]) ([alarm_control_panel.manual docs])
|
||||
- Rename xiaomi #9425 ([@danielhiversen] - [#9426]) (breaking change)
|
||||
- Bump version of aioautomatic ([@armills] - [#9435]) ([device_tracker.automatic docs])
|
||||
- Fix russound_rio for python 3.4 ([@wickerwaka] - [#9428]) ([media_player.russound_rio docs])
|
||||
- Basic MQTT vacuum support ([@johnboiles] - [#9386]) ([vacuum docs]) ([vacuum.mqtt docs]) (new-platform)
|
||||
- Optimaze vacuum mqtt platform ([@pvizeli] - [#9439]) ([vacuum.mqtt docs])
|
||||
- Polymer access to log file broken when using new log file command line ([@TD22057] - [#9437])
|
||||
- Allow empty hostnames when detecting devices with the aruba device_tracker. ([@michaelarnauts] - [#9440]) ([device_tracker.aruba docs])
|
||||
- mqtt_statestream: Update to append 'state' to topic for future use with mqtt discovery ([@mw-white] - [#9446]) ([mqtt_statestream docs])
|
||||
- Fix for DTE Energy Bridge returning the wrong units from time to time ([@kylehendricks] - [#9246]) ([sensor.dte_energy_bridge docs])
|
||||
- Refactor Swiss Public Transport sensor ([@fabaff] - [#9129]) ([sensor.swiss_public_transport docs]) (breaking change)
|
||||
- Added Zyxel Keenetic NDMS2 based routers support for device tracking ([@foxel] - [#9315]) ([device_tracker.keenetic_ndms2 docs]) (new-platform)
|
||||
- Add city/state/country options and fix bugs for airvisual ([@bachya] - [#9436]) ([sensor.airvisual docs])
|
||||
- Fix emulated hue warning message ([@astone123] - [#9452]) ([emulated_hue docs])
|
||||
- Alexa smart home native support ([@pvizeli] - [#9443])
|
||||
- fix for Twitter notifications without media ([@MikeChristianson] - [#9448])
|
||||
- Load WebComponent polyfill on header. ([@fanthos] - [#9438])
|
||||
- Fix issue 5728: Emulated Hue UPnP crashes on special characters. ([@SqyD] - [#9453])
|
||||
- Ios notify camera fix ([@rbflurry] - [#9427]) (breaking change)
|
||||
- Adds MQTT Fan Discovery ([@hufman] - [#9463])
|
||||
- Upgrade sqlalchemy to 1.1.14 ([@fabaff] - [#9458])
|
||||
- Upgrade uber_rides to 0.6.0 ([@fabaff] - [#9457]) ([sensor.uber docs])
|
||||
- Upgrade youtube_dl to 2017.9.15 ([@fabaff] - [#9456])
|
||||
- DoorBird Component ([@Klikini] - [#9281]) ([doorbird docs]) ([binary_sensor.doorbird docs]) ([camera.doorbird docs]) ([switch.doorbird docs]) (new-platform)
|
||||
- Fix recorder does not vacuum SQLite DB on purge ([@milanvo] - [#9469])
|
||||
- fitbit fixes ([@happyleavesaoc] - [#9460]) ([sensor.fitbit docs]) (breaking change)
|
||||
- Fix typo in services.yaml ([@mika] - [#9475])
|
||||
- Upgrade pyasn1 to 0.3.5 and pyasn1-modules to 0.1.4 ([@fabaff] - [#9474]) ([notify.xmpp docs])
|
||||
- Xiaomi Gateway: Allow static configuration of a gateway without discovery ([@syssi] - [#9464]) ([xiaomi_aqara docs])
|
||||
- Added support for the DTE Energy Bridge v2 ([@Blender3D] - [#9431]) ([sensor.dte_energy_bridge docs])
|
||||
- Telnet switch ([@multiholle] - [#8913]) ([switch.telnet docs]) (new-platform)
|
||||
- Abode services, events, lights, cameras, automations, quick actions. ([@MisterWil] - [#9310]) ([abode docs]) ([alarm_control_panel.abode docs]) ([binary_sensor.abode docs]) ([camera.abode docs]) ([cover.abode docs]) ([light.abode docs]) ([lock.abode docs]) ([switch.abode docs]) (new-platform)
|
||||
- Added satel_integra alarm panel and binary sensor platform ([@c-soft] - [#9336]) ([satel_integra docs]) ([alarm_control_panel.satel_integra docs]) ([binary_sensor.satel_integra docs]) (new-platform)
|
||||
- Worx Landroid sensor ([@nilzen] - [#9416]) ([sensor.worxlandroid docs]) (new-platform)
|
||||
- Fix universal media_player mute ([@colindunn] - [#9462]) ([media_player.universal docs])
|
||||
- Small improvement of KNX Covers ([@Julius2342] - [#9476])
|
||||
- Upgrade async_timeout to 1.4.0 ([@fabaff] - [#9488])
|
||||
- Bump version of abodepy ([@MisterWil] - [#9491]) ([abode docs])
|
||||
- Upgrade coinmarketcap to 4.1.1 ([@fabaff] - [#9490]) ([sensor.coinmarketcap docs])
|
||||
- Upgrade blockchain to 1.4.0 ([@fabaff] - [#9489])
|
||||
- Solve Recorder component failing when using Axis component ([@Kane610] - [#9293]) ([axis docs]) ([camera.axis docs])
|
||||
- switch to pypi for xiaomi gw ([@danielhiversen] - [#9498]) ([xiaomi_aqara docs])
|
||||
- renamed add_devices to async_add_devices according to hass naming scheme ([@Julius2342] - [#9485]) ([binary_sensor.knx docs]) ([climate.knx docs]) ([light.knx docs]) ([sensor.knx docs]) ([switch.knx docs])
|
||||
- Revert "renamed add_devices to async_add_devices according to hass naming scheme (#9485)" ([@pvizeli] - [#9503]) ([alarm_control_panel.spc docs]) ([binary_sensor.knx docs]) ([binary_sensor.spc docs]) ([climate.knx docs]) ([light.knx docs]) ([sensor.citybikes docs]) ([sensor.knx docs]) ([sensor.worxlandroid docs]) ([switch.knx docs])
|
||||
- LIFX: fix multi-zone color restore after effects ([@amelchio] - [#9492]) ([light.lifx docs])
|
||||
- renamed add_devices to async_add_devices according to hass naming scheme (second try after failed #9485) ([@Julius2342] - [#9505]) ([alarm_control_panel.spc docs]) ([binary_sensor.knx docs]) ([binary_sensor.spc docs]) ([climate.knx docs]) ([light.knx docs]) ([sensor.citybikes docs]) ([sensor.knx docs]) ([sensor.worxlandroid docs]) ([switch.knx docs])
|
||||
- Xiaomi pycryptodome ([@danielhiversen] - [#9511]) ([xiaomi_aqara docs])
|
||||
- Bumped pyhomematic, additional device support ([@danielperna84] - [#9506]) ([homematic docs]) ([sensor.homematic docs])
|
||||
- abode: Bump abodepy dependency to 0.11.7 ([@vickyg3] - [#9504]) ([abode docs])
|
||||
- abode: Set device_type in state attributes ([@vickyg3] - [#9515]) ([abode docs])
|
||||
- update xiaomi aqara lib ([@danielhiversen] - [#9520]) ([xiaomi_aqara docs])
|
||||
- added services.yaml integration for input_boolean ([@skalavala] - [#9519]) ([input_boolean docs])
|
||||
- Add reload service to python_script ([@doudz] - [#9512]) ([python_script docs])
|
||||
- MQTT Binary Sensor - Add availability_topic for online/offline status ([@marthoc] - [#9507]) ([binary_sensor.mqtt docs])
|
||||
- Fix typo within cover/knx https://github.com/XKNX/xknx/issues/64 ([@Julius2342] - [#9527]) ([cover.knx docs])
|
||||
- LIFX: improve performance of setting multi-zone lights to a single color ([@amelchio] - [#9526]) ([light.lifx docs])
|
||||
|
||||
[#8913]: https://github.com/home-assistant/home-assistant/pull/8913
|
||||
[#9056]: https://github.com/home-assistant/home-assistant/pull/9056
|
||||
[#9129]: https://github.com/home-assistant/home-assistant/pull/9129
|
||||
[#9162]: https://github.com/home-assistant/home-assistant/pull/9162
|
||||
[#9222]: https://github.com/home-assistant/home-assistant/pull/9222
|
||||
[#9227]: https://github.com/home-assistant/home-assistant/pull/9227
|
||||
[#9236]: https://github.com/home-assistant/home-assistant/pull/9236
|
||||
[#9246]: https://github.com/home-assistant/home-assistant/pull/9246
|
||||
[#9264]: https://github.com/home-assistant/home-assistant/pull/9264
|
||||
[#9281]: https://github.com/home-assistant/home-assistant/pull/9281
|
||||
[#9283]: https://github.com/home-assistant/home-assistant/pull/9283
|
||||
[#9286]: https://github.com/home-assistant/home-assistant/pull/9286
|
||||
[#9293]: https://github.com/home-assistant/home-assistant/pull/9293
|
||||
[#9301]: https://github.com/home-assistant/home-assistant/pull/9301
|
||||
[#9310]: https://github.com/home-assistant/home-assistant/pull/9310
|
||||
[#9315]: https://github.com/home-assistant/home-assistant/pull/9315
|
||||
[#9336]: https://github.com/home-assistant/home-assistant/pull/9336
|
||||
[#9338]: https://github.com/home-assistant/home-assistant/pull/9338
|
||||
[#9355]: https://github.com/home-assistant/home-assistant/pull/9355
|
||||
[#9357]: https://github.com/home-assistant/home-assistant/pull/9357
|
||||
[#9364]: https://github.com/home-assistant/home-assistant/pull/9364
|
||||
[#9365]: https://github.com/home-assistant/home-assistant/pull/9365
|
||||
[#9378]: https://github.com/home-assistant/home-assistant/pull/9378
|
||||
[#9386]: https://github.com/home-assistant/home-assistant/pull/9386
|
||||
[#9389]: https://github.com/home-assistant/home-assistant/pull/9389
|
||||
[#9390]: https://github.com/home-assistant/home-assistant/pull/9390
|
||||
[#9391]: https://github.com/home-assistant/home-assistant/pull/9391
|
||||
[#9394]: https://github.com/home-assistant/home-assistant/pull/9394
|
||||
[#9400]: https://github.com/home-assistant/home-assistant/pull/9400
|
||||
[#9403]: https://github.com/home-assistant/home-assistant/pull/9403
|
||||
[#9404]: https://github.com/home-assistant/home-assistant/pull/9404
|
||||
[#9408]: https://github.com/home-assistant/home-assistant/pull/9408
|
||||
[#9411]: https://github.com/home-assistant/home-assistant/pull/9411
|
||||
[#9413]: https://github.com/home-assistant/home-assistant/pull/9413
|
||||
[#9415]: https://github.com/home-assistant/home-assistant/pull/9415
|
||||
[#9416]: https://github.com/home-assistant/home-assistant/pull/9416
|
||||
[#9417]: https://github.com/home-assistant/home-assistant/pull/9417
|
||||
[#9422]: https://github.com/home-assistant/home-assistant/pull/9422
|
||||
[#9423]: https://github.com/home-assistant/home-assistant/pull/9423
|
||||
[#9424]: https://github.com/home-assistant/home-assistant/pull/9424
|
||||
[#9426]: https://github.com/home-assistant/home-assistant/pull/9426
|
||||
[#9427]: https://github.com/home-assistant/home-assistant/pull/9427
|
||||
[#9428]: https://github.com/home-assistant/home-assistant/pull/9428
|
||||
[#9431]: https://github.com/home-assistant/home-assistant/pull/9431
|
||||
[#9435]: https://github.com/home-assistant/home-assistant/pull/9435
|
||||
[#9436]: https://github.com/home-assistant/home-assistant/pull/9436
|
||||
[#9437]: https://github.com/home-assistant/home-assistant/pull/9437
|
||||
[#9438]: https://github.com/home-assistant/home-assistant/pull/9438
|
||||
[#9439]: https://github.com/home-assistant/home-assistant/pull/9439
|
||||
[#9440]: https://github.com/home-assistant/home-assistant/pull/9440
|
||||
[#9443]: https://github.com/home-assistant/home-assistant/pull/9443
|
||||
[#9446]: https://github.com/home-assistant/home-assistant/pull/9446
|
||||
[#9448]: https://github.com/home-assistant/home-assistant/pull/9448
|
||||
[#9452]: https://github.com/home-assistant/home-assistant/pull/9452
|
||||
[#9453]: https://github.com/home-assistant/home-assistant/pull/9453
|
||||
[#9456]: https://github.com/home-assistant/home-assistant/pull/9456
|
||||
[#9457]: https://github.com/home-assistant/home-assistant/pull/9457
|
||||
[#9458]: https://github.com/home-assistant/home-assistant/pull/9458
|
||||
[#9460]: https://github.com/home-assistant/home-assistant/pull/9460
|
||||
[#9462]: https://github.com/home-assistant/home-assistant/pull/9462
|
||||
[#9463]: https://github.com/home-assistant/home-assistant/pull/9463
|
||||
[#9464]: https://github.com/home-assistant/home-assistant/pull/9464
|
||||
[#9469]: https://github.com/home-assistant/home-assistant/pull/9469
|
||||
[#9474]: https://github.com/home-assistant/home-assistant/pull/9474
|
||||
[#9475]: https://github.com/home-assistant/home-assistant/pull/9475
|
||||
[#9476]: https://github.com/home-assistant/home-assistant/pull/9476
|
||||
[#9485]: https://github.com/home-assistant/home-assistant/pull/9485
|
||||
[#9488]: https://github.com/home-assistant/home-assistant/pull/9488
|
||||
[#9489]: https://github.com/home-assistant/home-assistant/pull/9489
|
||||
[#9490]: https://github.com/home-assistant/home-assistant/pull/9490
|
||||
[#9491]: https://github.com/home-assistant/home-assistant/pull/9491
|
||||
[#9492]: https://github.com/home-assistant/home-assistant/pull/9492
|
||||
[#9498]: https://github.com/home-assistant/home-assistant/pull/9498
|
||||
[#9503]: https://github.com/home-assistant/home-assistant/pull/9503
|
||||
[#9504]: https://github.com/home-assistant/home-assistant/pull/9504
|
||||
[#9505]: https://github.com/home-assistant/home-assistant/pull/9505
|
||||
[#9506]: https://github.com/home-assistant/home-assistant/pull/9506
|
||||
[#9507]: https://github.com/home-assistant/home-assistant/pull/9507
|
||||
[#9511]: https://github.com/home-assistant/home-assistant/pull/9511
|
||||
[#9512]: https://github.com/home-assistant/home-assistant/pull/9512
|
||||
[#9515]: https://github.com/home-assistant/home-assistant/pull/9515
|
||||
[#9519]: https://github.com/home-assistant/home-assistant/pull/9519
|
||||
[#9520]: https://github.com/home-assistant/home-assistant/pull/9520
|
||||
[#9526]: https://github.com/home-assistant/home-assistant/pull/9526
|
||||
[#9527]: https://github.com/home-assistant/home-assistant/pull/9527
|
||||
[@MisterWil]: https://github.com/MisterWil
|
||||
[@pdanilew]: https://github.com/pdanilew
|
||||
[@marthoc]: https://github.com/marthoc
|
||||
[@spektren]: https://github.com/spektren
|
||||
[@Blender3D]: https://github.com/Blender3D
|
||||
[@Jay2645]: https://github.com/Jay2645
|
||||
[@Julius2342]: https://github.com/Julius2342
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@Klikini]: https://github.com/Klikini
|
||||
[@MikeChristianson]: https://github.com/MikeChristianson
|
||||
[@SqyD]: https://github.com/SqyD
|
||||
[@TD22057]: https://github.com/TD22057
|
||||
[@amelchio]: https://github.com/amelchio
|
||||
[@antonym]: https://github.com/antonym
|
||||
[@armills]: https://github.com/armills
|
||||
[@arsaboo]: https://github.com/arsaboo
|
||||
[@astone123]: https://github.com/astone123
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@c-soft]: https://github.com/c-soft
|
||||
[@colindunn]: https://github.com/colindunn
|
||||
[@danielhiversen]: https://github.com/danielhiversen
|
||||
[@danielperna84]: https://github.com/danielperna84
|
||||
[@diplix]: https://github.com/diplix
|
||||
[@doudz]: https://github.com/doudz
|
||||
[@fabaff]: https://github.com/fabaff
|
||||
[@fanaticDavid]: https://github.com/fanaticDavid
|
||||
[@fanthos]: https://github.com/fanthos
|
||||
[@foxel]: https://github.com/foxel
|
||||
[@giangvo]: https://github.com/giangvo
|
||||
[@happyleavesaoc]: https://github.com/happyleavesaoc
|
||||
[@hufman]: https://github.com/hufman
|
||||
[@jlmcgehee21]: https://github.com/jlmcgehee21
|
||||
[@johnboiles]: https://github.com/johnboiles
|
||||
[@kylehendricks]: https://github.com/kylehendricks
|
||||
[@michaelarnauts]: https://github.com/michaelarnauts
|
||||
[@mika]: https://github.com/mika
|
||||
[@milanvo]: https://github.com/milanvo
|
||||
[@morberg]: https://github.com/morberg
|
||||
[@multiholle]: https://github.com/multiholle
|
||||
[@mw-white]: https://github.com/mw-white
|
||||
[@nilzen]: https://github.com/nilzen
|
||||
[@pfalcon]: https://github.com/pfalcon
|
||||
[@postlund]: https://github.com/postlund
|
||||
[@pvizeli]: https://github.com/pvizeli
|
||||
[@rbflurry]: https://github.com/rbflurry
|
||||
[@rollbrettler]: https://github.com/rollbrettler
|
||||
[@skalavala]: https://github.com/skalavala
|
||||
[@snjoetw]: https://github.com/snjoetw
|
||||
[@syssi]: https://github.com/syssi
|
||||
[@tcastberg]: https://github.com/tcastberg
|
||||
[@tinloaf]: https://github.com/tinloaf
|
||||
[@turbokongen]: https://github.com/turbokongen
|
||||
[@vickyg3]: https://github.com/vickyg3
|
||||
[@wickerwaka]: https://github.com/wickerwaka
|
||||
[abode docs]: /components/abode/
|
||||
[alarm_control_panel.abode docs]: /components/alarm_control_panel.abode/
|
||||
[alarm_control_panel.manual docs]: /components/alarm_control_panel.manual/
|
||||
[alarm_control_panel.satel_integra docs]: /components/alarm_control_panel.satel_integra/
|
||||
[alarm_control_panel.spc docs]: /components/alarm_control_panel.spc/
|
||||
[alexa docs]: /components/alexa/
|
||||
[api docs]: /components/api/
|
||||
[apple_tv docs]: /components/apple_tv/
|
||||
[axis docs]: /components/axis/
|
||||
[binary_sensor.abode docs]: /components/binary_sensor.abode/
|
||||
[binary_sensor.bayesian docs]: /components/binary_sensor.bayesian/
|
||||
[binary_sensor.doorbird docs]: /components/binary_sensor.doorbird/
|
||||
[binary_sensor.knx docs]: /components/binary_sensor.knx/
|
||||
[binary_sensor.mqtt docs]: /components/binary_sensor.mqtt/
|
||||
[binary_sensor.satel_integra docs]: /components/binary_sensor.satel_integra/
|
||||
[binary_sensor.spc docs]: /components/binary_sensor.spc/
|
||||
[calendar.todoist docs]: /components/calendar.todoist/
|
||||
[camera.abode docs]: /components/camera.abode/
|
||||
[camera.axis docs]: /components/camera.axis/
|
||||
[camera.doorbird docs]: /components/camera.doorbird/
|
||||
[camera.uvc docs]: /components/camera.uvc/
|
||||
[climate.knx docs]: /components/climate.knx/
|
||||
[config.zwave docs]: /components/config.zwave/
|
||||
[cover.abode docs]: /components/cover.abode/
|
||||
[cover.knx docs]: /components/cover.knx/
|
||||
[device_tracker.aruba docs]: /components/device_tracker.aruba/
|
||||
[device_tracker.automatic docs]: /components/device_tracker.automatic/
|
||||
[device_tracker.keenetic_ndms2 docs]: /components/device_tracker.keenetic_ndms2/
|
||||
[device_tracker.owntracks docs]: /components/device_tracker.owntracks/
|
||||
[doorbird docs]: /components/doorbird/
|
||||
[emulated_hue docs]: /components/emulated_hue/
|
||||
[homematic docs]: /components/homematic/
|
||||
[input_boolean docs]: /components/input_boolean/
|
||||
[light.abode docs]: /components/light.abode/
|
||||
[light.knx docs]: /components/light.knx/
|
||||
[light.lifx docs]: /components/light.lifx/
|
||||
[light.template docs]: /components/light.template/
|
||||
[light.tradfri docs]: /components/light.tradfri/
|
||||
[light.xiaomi_philipslight docs]: /components/light.xiaomi_philipslight/
|
||||
[lock.abode docs]: /components/lock.abode/
|
||||
[media_player.apple_tv docs]: /components/media_player.apple_tv/
|
||||
[media_player.mpd docs]: /components/media_player.mpd/
|
||||
[media_player.russound_rio docs]: /components/media_player.russound_rio/
|
||||
[media_player.universal docs]: /components/media_player.universal/
|
||||
[mqtt_statestream docs]: /components/mqtt_statestream/
|
||||
[notify.html5 docs]: /components/notify.html5/
|
||||
[notify.xmpp docs]: /components/notify.xmpp/
|
||||
[python_script docs]: /components/python_script/
|
||||
[satel_integra docs]: /components/satel_integra/
|
||||
[sensor.airvisual docs]: /components/sensor.airvisual/
|
||||
[sensor.citybikes docs]: /components/sensor.citybikes/
|
||||
[sensor.coinmarketcap docs]: /components/sensor.coinmarketcap/
|
||||
[sensor.dte_energy_bridge docs]: /components/sensor.dte_energy_bridge/
|
||||
[sensor.fitbit docs]: /components/sensor.fitbit/
|
||||
[sensor.homematic docs]: /components/sensor.homematic/
|
||||
[sensor.knx docs]: /components/sensor.knx/
|
||||
[sensor.mopar docs]: /components/sensor.mopar/
|
||||
[sensor.onewire docs]: /components/sensor.onewire/
|
||||
[sensor.swiss_public_transport docs]: /components/sensor.swiss_public_transport/
|
||||
[sensor.systemmonitor docs]: /components/sensor.systemmonitor/
|
||||
[sensor.uber docs]: /components/sensor.uber/
|
||||
[sensor.worxlandroid docs]: /components/sensor.worxlandroid/
|
||||
[switch.abode docs]: /components/switch.abode/
|
||||
[switch.broadlink docs]: /components/switch.broadlink/
|
||||
[switch.doorbird docs]: /components/switch.doorbird/
|
||||
[switch.knx docs]: /components/switch.knx/
|
||||
[switch.rest docs]: /components/switch.rest/
|
||||
[switch.telnet docs]: /components/switch.telnet/
|
||||
[vacuum docs]: /components/vacuum/
|
||||
[vacuum.mqtt docs]: /components/vacuum.mqtt/
|
||||
[vacuum.xiaomi docs]: /components/vacuum.xiaomi/
|
||||
[xiaomi docs]: /components/xiaomi/
|
||||
[xiaomi_aqara docs]: /components/xiaomi_aqara/
|
||||
[zwave docs]: /components/zwave/
|
||||
[forum]: https://community.home-assistant.io/
|
||||
[issue]: https://github.com/home-assistant/home-assistant/issues
|
||||
[discord]: https://discord.gg/c5DvZ4e
|
||||
BIN
source/images/blog/2017-09-0.54/components.png
Normal file
BIN
source/images/blog/2017-09-0.54/components.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 100 KiB |
BIN
source/images/components/calendar/todoist-108x108.png
Executable file
BIN
source/images/components/calendar/todoist-108x108.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 8.1 KiB |
BIN
source/images/components/calendar/todoist-512x512.png
Executable file
BIN
source/images/components/calendar/todoist-512x512.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
BIN
source/images/supported_brands/doorbird.png
Normal file
BIN
source/images/supported_brands/doorbird.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
BIN
source/images/supported_brands/keenetic.png
Normal file
BIN
source/images/supported_brands/keenetic.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 2.8 KiB |
BIN
source/images/supported_brands/satel.jpg
Normal file
BIN
source/images/supported_brands/satel.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 26 KiB |
BIN
source/images/supported_brands/todoist.png
Executable file
BIN
source/images/supported_brands/todoist.png
Executable file
Binary file not shown.
|
After Width: | Height: | Size: 39 KiB |
Loading…
x
Reference in New Issue
Block a user