mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-15 13:26:54 +00:00
Merge branch 'rc' into current
This commit is contained in:
Paulus Schoutsen
commit
7a958b0b99
@ -139,14 +139,14 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 69
|
||||
current_patch_version: 1
|
||||
date_released: 2018-05-12
|
||||
current_minor_version: 70
|
||||
current_patch_version: 0
|
||||
date_released: 2018-05-27
|
||||
|
||||
# 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-0691---may-12"
|
||||
patch_version_notes: "#"
|
||||
# Minor release (Example #release-0431---april-25):
|
||||
|
||||
# Date we moved to Discourse for comments
|
||||
|
||||
21
source/_components/binary_sensor.homematicip_cloud.markdown
Normal file
21
source/_components/binary_sensor.homematicip_cloud.markdown
Normal file
@ -0,0 +1,21 @@
|
||||
---
|
||||
layout: page
|
||||
title: "HomematicIP Cloud Binary Sensor"
|
||||
description: "Instructions on how to integrate HomematicIP binary sensors within Home Assistant."
|
||||
date: 2018-04-02 13:40
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: homematic.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.70
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `homematicip_cloud` binary_switch platform allows you to control
|
||||
[HomematicIP](http://www.homematic-ip.com) binary sensors through Home Assistant.
|
||||
|
||||
Devices will be configured automatically. Please refer to the
|
||||
[component](/components/homematicip_cloud/) configuration on how to setup
|
||||
HomematicIP Cloud.
|
||||
21
source/_components/binary_sensor.konnected.markdown
Normal file
21
source/_components/binary_sensor.konnected.markdown
Normal file
@ -0,0 +1,21 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Konnected Binary Sensor"
|
||||
description: "Connect wired open/close sensors to Home Assistant with Konnected and a NodeMCU ESP8266"
|
||||
date: 2018-04-03 12:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: konnected.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: "0.70"
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `konnected` binary sensor allows you to monitor wired door sensors, window sensors, motion sensors, smoke detectors, CO detectors, glass-break sensors, water leak sensors or any other simple wired open/close circuit attached to a NodeMCU ESP8266 WiFi module running the [open source Konnected software](https://github.com/konnected-io/konnected-security).
|
||||
|
||||
See the [`konnected`](/components/konnected/) component for configuration and setup instructions.
|
||||
|
||||
This component supports all of the built-in device classes of the generic [Binary Sensor](/components/binary_sensor/) component.
|
||||
|
||||
16
source/_components/binary_sensor.mychevy.markdown
Normal file
16
source/_components/binary_sensor.mychevy.markdown
Normal file
@ -0,0 +1,16 @@
|
||||
---
|
||||
layout: page
|
||||
title: "MyChevy Binary Sensors"
|
||||
description: "Instructions on how to integrate Chevy Bolt binary sensors car into Home Assistant."
|
||||
date: 2017-08-28 17:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: chevy.png
|
||||
ha_category: Binary Sensor
|
||||
ha_release: 0.62
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
For configuration instructions, see [main component config](/components/mychecvy/).
|
||||
34
source/_components/camera.familyhub.markdown
Normal file
34
source/_components/camera.familyhub.markdown
Normal file
@ -0,0 +1,34 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Family Hub Camera"
|
||||
description: "Instructions on how to integrate Samsung Family Hub refrigerator cameras within Home Assistant."
|
||||
date: 2018-05-04 09:44
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: familyhub.png
|
||||
ha_category: Camera
|
||||
ha_release: "0.70"
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `familyhub` platform allows you to get images of the inside of your [Samsung Family Hub refrigerator](https://www.samsung.com/us/explore/family-hub-refrigerator/connected-hub/) in Home Assistant.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To enable your Family Hub camera in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
camera:
|
||||
- platform: familyhub
|
||||
ip_address: 'IP_ADDRESS'
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
ip_address:
|
||||
description: The IP address of your refrigerator.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
@ -36,6 +36,7 @@ Configuration variables:
|
||||
- **authentication** (*Optional*): Type for authenticating the requests `basic` (default) or `digest`.
|
||||
- **limit_refetch_to_url_change** (*Optional*): True/false value (default: false). Limits re-fetching of the remote image to when the URL changes. Only relevant if using a template to fetch the remote image.
|
||||
- **content_type** (*Optional*): Set the content type for the IP camera if it is not a jpg file (default: `image/jpeg`). Use `image/svg+xml` to add a dynamic svg file.
|
||||
- **framerate** (*Optional*): The number of frames-per-second (FPS) of the stream (setting this too high may cause too much traffic on the network or be heavy on the camera).
|
||||
|
||||
<p class='img'>
|
||||
<a href='/cookbook/google_maps_card/'>
|
||||
|
||||
@ -25,7 +25,13 @@ Currently supported functionality:
|
||||
- Setting heat/cool temperature when the thermostat is in the appropriate mode.
|
||||
- Changing the operation mode of the thermostat (heat/cool/off/auto)
|
||||
- Turning the fan on/off
|
||||
- Setting the humidity level
|
||||
- Reading and setting the humidity level and limits
|
||||
- Turning away mode on/off
|
||||
- Turning hold mode on/off
|
||||
|
||||
The following values are supported for the hold_mode state attribute:
|
||||
- `off`: *Enables* the scheduling functionality.
|
||||
- `temperature`: *Disables* the schedule and holds the set temperature indefinitely.
|
||||
|
||||
Note - Please ensure you update your thermostat to the latest firmware. Currently tested on firmware 5.10.
|
||||
|
||||
@ -61,6 +67,11 @@ timeout:
|
||||
required: false
|
||||
type: int
|
||||
default: 5
|
||||
humidifier:
|
||||
description: Report humidity and expose humidifier setpoints.
|
||||
required: false
|
||||
type: boolean
|
||||
default: true
|
||||
{% endconfiguration %}
|
||||
|
||||
## {% linkable_title Full configuration sample %}
|
||||
@ -74,4 +85,5 @@ climate:
|
||||
username: OPTIONAL_AUTH_USER_HERE
|
||||
password: OPTIONAL_AUTH_PASS_HERE
|
||||
timeout: 5
|
||||
humidifier: False
|
||||
```
|
||||
|
||||
@ -13,7 +13,7 @@ ha_release: 0.58
|
||||
---
|
||||
|
||||
This component offers presence detection by examining devices connected to a [Rogers Hitron CODA](https://www.rogers.com/customer/support/article/wi-fi-password-hitron-coda4582-cgn3amr-cgnm3552-cgn3acr-cgn3)
|
||||
Router.
|
||||
or [Shaw Hitron CGNM](https://community.shaw.ca/docs/DOC-4066) Router.
|
||||
|
||||
To use a Hitron router in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -24,6 +24,7 @@ device_tracker:
|
||||
host: !secret router_ip
|
||||
username: !secret router_username
|
||||
password: !secret router_password
|
||||
type: rogers
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
@ -39,6 +40,10 @@ password:
|
||||
description: The password for the specified username. Usually your WiFi password.
|
||||
required: true
|
||||
type: string
|
||||
type:
|
||||
description: The internet provider for the modem; "rogers" or "shaw". Defaults to "rogers".
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
See the [device tracker component page](/components/device_tracker/) for instructions how to configure the people to be tracked.
|
||||
|
||||
@ -33,9 +33,11 @@ Configuration variables:
|
||||
- **username** (*Required*): The username for the iCloud account.
|
||||
- **password** (*Required*): The password for your given username.
|
||||
- **account_name** (*Optional*): The friendly name for the account_name. If this isn't given, it will use the account_name of the username (so the part before the `@` in the email address).
|
||||
- **max_interval** (*Optional*): Maximum interval in minutes between subsequent location upates. This tracker uses dynamic intervals for requesting location updates. When iphone is stationary, interval will eventually be set to `max_interval` to save battery. When iphone starts moving again interval will be dynamically updated to 1 min. Note that updating interval to 1 min might be delayed by maximum `max_interval` minutes. Default is 30 min. Minimum value is 1 min.
|
||||
- **gps_accuracy_threshold** (*Optional*): iCloud location updates come with some gps_accuracy varying from 10 to 5000 meters. This setting defines the accuracy threshold in meters for a location update. Less accurate updates will be discarded by this tracker. This allows more precise location monitoring and fewer false positive zone changes. Default is 1000 meters.
|
||||
|
||||
<p class='note warning'>
|
||||
This may cause battery drainage as it wakes up your device to get the current location.
|
||||
Low `max_interval` may cause battery drainage as it wakes up your device to get the current location.
|
||||
</p>
|
||||
|
||||
<p class='note warning'>
|
||||
@ -48,7 +50,7 @@ To disable the drainage of the battery, a dynamic interval is being used for eac
|
||||
2 Factor Authentication is the improved version of 2 Steps Authentication, this is still not supported by the pyicloud library. Therefore it's not possible to use it with the device_tracker yet.
|
||||
|
||||
4 services are available for this component:
|
||||
- **icloud_update**: This service can be used to ask for an update of a certain iDevice. The `account_name` and `device_name` are optional.
|
||||
- **icloud_update**: This service can be used to ask for an update of a certain iDevice. The `account_name` and `device_name` are optional. Request will result in new Home Assistant [state_changed](/docs/configuration/events/#event-state_changed) event describing current iphone location. Can be used in automations when manual location update is needed, e.g. to check if anyone is home when door's been opened.
|
||||
- **icloud_lost_iphone**: This service will play the Lost iPhone sound on a certain iDevice. The `account_name` and `device_name` are optional.
|
||||
- **icloud_set_interval**: This service will change the dynamic interval of an iDevice. The `account_name` and `device_name` are optional. If `interval` is used in the service_data, the iDevice will be updated with that new interval. That interval will be fixed until the iDevice changes zone or if this service is called again. If `interval` isn't used in the service_data, the interval for that iDevice will revert back to its default dynamic interval based on its current zone, its distance towards home and its battery level.
|
||||
- **icloud_reset_account**: This service can be used to reset an iCloud account. This is helpful when not all devices are being found by the component or if you have added a new iDevice to your account. The `account_name` is optional.
|
||||
|
||||
@ -14,8 +14,8 @@ logo: home-assistant.png
|
||||
---
|
||||
|
||||
The `template` platform creates fans that combine components and provides the
|
||||
ability to run scripts or invoke services for each of the turn_on, turn_off, set_speed, and
|
||||
set_oscillating commands of a fan.
|
||||
ability to run scripts or invoke services for each of the turn_on, turn_off, set_speed,
|
||||
set_oscillating, and set_direction commands of a fan.
|
||||
|
||||
To enable Template Fans in your installation, add the following to your
|
||||
`configuration.yaml` file:
|
||||
@ -31,6 +31,7 @@ fan:
|
||||
value_template: "{{ states('input_boolean.state') }}"
|
||||
speed_template: "{{ states('input_select.speed') }}"
|
||||
oscillating_template: "{{ states('input_select.osc') }}"
|
||||
direction_template: "{{ states('input_select.direction') }}"
|
||||
turn_on:
|
||||
service: script.fan_on
|
||||
turn_off:
|
||||
@ -43,6 +44,10 @@ fan:
|
||||
service: script.fan_oscillating
|
||||
data_template:
|
||||
oscillating: "{{ oscillating }}"
|
||||
set_direction:
|
||||
service: script.fan_direction
|
||||
data_template:
|
||||
direction: "{{ direction }}"
|
||||
speeds:
|
||||
- '1'
|
||||
- '2'
|
||||
@ -72,6 +77,10 @@ fan:
|
||||
description: "Defines a template to get the osc state of the fan. Valid value: True/False"
|
||||
required: false
|
||||
type: template
|
||||
direction_template:
|
||||
description: "Defines a template to get the direction of the fan. Valid value: 'forward'/'reverse'"
|
||||
required: false
|
||||
type: template
|
||||
turn_on:
|
||||
description: Defines an action to run when the fan is turned on.
|
||||
required: true
|
||||
@ -88,6 +97,10 @@ fan:
|
||||
description: Defines an action to run when the fan is given a osc state command.
|
||||
required: false
|
||||
type: action
|
||||
set_direction:
|
||||
description: Defines an action to run when the fan is given a direction command.
|
||||
required: false
|
||||
type: action
|
||||
speeds:
|
||||
description: List of speeds the fan is capable of running at.
|
||||
required: false
|
||||
|
||||
@ -25,9 +25,36 @@ feedreader:
|
||||
- https://hasspodcast.io/feed/podcast
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
{% configuration %}
|
||||
urls:
|
||||
description: List of URLS for your feeds.
|
||||
required: true
|
||||
type: list
|
||||
scan_interval:
|
||||
description: Defines the update interval of the feeds.
|
||||
required: false
|
||||
default: 1 hour
|
||||
type: interval
|
||||
max_entries:
|
||||
description: The maximum number of entries to extract from each feed.
|
||||
required: false
|
||||
default: 20
|
||||
type: int
|
||||
{% endconfiguration %}
|
||||
|
||||
- **urls** (*Required*): List of URLS for your feeds.
|
||||
The following configuration example shows how to configure update interval and maximum number of entries:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry with optional parameters
|
||||
feedreader:
|
||||
urls:
|
||||
- https://www.home-assistant.io/atom.xml
|
||||
- https://github.com/blog.atom
|
||||
- https://hasspodcast.io/feed/podcast
|
||||
scan_interval:
|
||||
minutes: 30
|
||||
max_entries: 5
|
||||
```
|
||||
|
||||
Feedreader events can be used out of the box to trigger automation actions, e.g.:
|
||||
|
||||
|
||||
@ -86,11 +86,15 @@ homekit:
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
code:
|
||||
description: Code to arm or disarm the alarm in the frontend. Only applicable for `alarm_control_panel` entities.
|
||||
name:
|
||||
description: Name of entity to show in HomeKit. HomeKit will cache the name on the first run so a device must be removed and then re-added for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
default: ''
|
||||
code:
|
||||
description: Code to `arm / disarm` an alarm or `lock / unlock` a lock. Only applicable for `alarm_control_panel` or `lock` entities.
|
||||
required: false
|
||||
type: string
|
||||
default: '`<No code>`'
|
||||
{% endconfiguration %}
|
||||
|
||||
<p class='note'>
|
||||
@ -222,6 +226,7 @@ The following components are currently supported:
|
||||
| cover | WindowCovering | All covers that support `open_cover` and `close_cover` through value mapping. (`open` -> `>=50`; `close` -> `<50`) |
|
||||
| cover | WindowCovering | All covers that support `open_cover`, `stop_cover` and `close_cover` through value mapping. (`open` -> `>70`; `close` -> `<30`; `stop` -> every value in between) |
|
||||
| device_tracker | Sensor | Support for `occupancy` device class. |
|
||||
| fan | Fan | Support for `on / off`, `direction` and `oscillating`. |
|
||||
| light | Light | Support for `on / off`, `brightness` and `rgb_color`. |
|
||||
| lock | DoorLock | Support for `lock / unlock`. |
|
||||
| sensor | TemperatureSensor | All sensors that have `Celsius` or `Fahrenheit` as their `unit_of_measurement` or `temperature` as their `device_class`. |
|
||||
|
||||
@ -24,12 +24,13 @@ generate_auth_token.py
|
||||
```
|
||||
|
||||
- add the information to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
homematicip_cloud:
|
||||
- name: NAME
|
||||
accesspoint: IDENTIFIER
|
||||
- accesspoint: IDENTIFIER
|
||||
authtoken: AUTHTOKEN
|
||||
- name: Location2
|
||||
accesspoint: IDENTIFIER2
|
||||
authtoken: AUTHTOKEN2
|
||||
```
|
||||
|
||||
Configuration variables (global):
|
||||
|
||||
60
source/_components/image_processing.facebox.markdown
Normal file
60
source/_components/image_processing.facebox.markdown
Normal file
@ -0,0 +1,60 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Facebox"
|
||||
description: "Detect and recognise faces with Facebox."
|
||||
date: 2018-05-03 00:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: machine-box.png
|
||||
ha_category: Image Processing
|
||||
featured: false
|
||||
ha_release: 0.70
|
||||
---
|
||||
|
||||
The `facebox` image processing platform allows you to detect and recognise faces in a camera image using [Facebox](https://machinebox.io/docs/facebox). The state of the entity is the number of faces detected, and recognised faces are listed in the `matched_faces` attribute. Facebox runs in a Docker container, and it is recommended that you run this container on a machine with a minimum of 2 GB RAM. On your machine with Docker, run the Facebox container with:
|
||||
```
|
||||
MB_KEY="INSERT-YOUR-KEY-HERE"
|
||||
|
||||
sudo docker run --name=facebox --restart=always 8080:8080 -e "MB_KEY=$MB_KEY" machinebox/facebox
|
||||
```
|
||||
|
||||
If you only require face detection (number of faces) you can disable face recognition by adding ```-e "MB_FACEBOX_DISABLE_RECOGNITION=true"``` to the `docker run` command.
|
||||
|
||||
To enable this platform in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
image_processing:
|
||||
- platform: facebox
|
||||
ip_address: 192.168.0.1
|
||||
port: 8080
|
||||
source:
|
||||
- entity_id: camera.local_file
|
||||
name: my_custom_name
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
ip_address:
|
||||
description: The IP address of your machine hosting Facebox.
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
description: The port which Facebox is exposed on.
|
||||
required: true
|
||||
type: string
|
||||
source:
|
||||
description: The list of image sources.
|
||||
required: true
|
||||
type: map
|
||||
keys:
|
||||
entity_id:
|
||||
description: A camera entity id to get picture from.
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: This parameter allows you to override the name of your `image_processing` entity.
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
151
source/_components/konnected.markdown
Normal file
151
source/_components/konnected.markdown
Normal file
@ -0,0 +1,151 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Konnected"
|
||||
description: "Connect wired alarm sensors and siren using the NodeMCU based Konnected Alarm Panel"
|
||||
date: 2018-04-03 12:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: konnected.png
|
||||
ha_category: Alarm
|
||||
ha_release: "0.70"
|
||||
---
|
||||
|
||||
The `konnected` component lets you connect wired sensors and switches to a NodeMCU ESP8226 based device running the [open source Konnected software](https://github.com/konnected-io/konnected-security). Reuse the wired sensors and siren from an old or pre-wired alarm system installation and integrate them directly into Home Assistant.
|
||||
|
||||
Visit the [Konnected.io website](https://konnected.io) for more information about the Konnected Alarm Panel board and compatible hardware.
|
||||
|
||||
The component currently supports the following device types in Home Assistant:
|
||||
|
||||
- [Binary Sensor](/components/binary_sensor.konnected/): Wired door and window sensors, motion detectors, glass-break detectors, leak sensors, smoke & CO detectors or any open/close switch.
|
||||
- [Switch](/components/switch.konnected/): Actuate a siren, strobe, buzzer or relay module.
|
||||
|
||||
This component requires the [`discovery`](https://www.home-assistant.io/components/discovery) component to be enabled.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
A `konnected` section must be present in the `configuration.yml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
konnected:
|
||||
access_token: REPLACE_ME_WITH_A_RANDOM_STRING
|
||||
devices:
|
||||
- id: 8bcd53
|
||||
binary_sensors:
|
||||
- zone: 1
|
||||
type: door
|
||||
switches:
|
||||
- zone: out
|
||||
- id: 438a38
|
||||
binary_sensors:
|
||||
- pin: 2
|
||||
type: door
|
||||
switches:
|
||||
- pin: 5
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
access_token:
|
||||
description: Any random string. This is used to ensure that only those devices which you have configured can authenticate to Home Assistant to change a device state.
|
||||
required: true
|
||||
type: string
|
||||
devices:
|
||||
description: A list of Konnected devices that you have on your network.
|
||||
required: true
|
||||
type: list
|
||||
keys:
|
||||
id:
|
||||
description: The MAC address of the WiFi module with colons/punctuation removed. You can either use the full 12-character MAC address or only the last 6 characters. This is visible in the device's WiFi SSID and hostname.
|
||||
required: true
|
||||
type: string
|
||||
binary_sensors:
|
||||
description: A list of binary sensors connected to the device. See [Konnected Binary Sensor](/components/binary_sensor.konnected/) for configuration variables.
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
pin:
|
||||
description: The number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values are 1, 2, 5, 6, 7 and 9.
|
||||
required: exclusive
|
||||
zone:
|
||||
description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board. Valid values are 1, 2, 3, 4, 5 and 6.
|
||||
required: exclusive
|
||||
type:
|
||||
description: Any [binary sensor](/components/binary_sensor/) class, typically `door`, `window`, `motion` or `smoke`.
|
||||
required: true
|
||||
name:
|
||||
description: The name of the device used in the front end.
|
||||
required: false
|
||||
default: automatically generated
|
||||
switches:
|
||||
description: A list of actuators (on/off switches) connected to the device. See [Konnected Switch](/components/switch.konnected/) for configuration variables.
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
pin:
|
||||
description: The number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values are 1, 2, 5, 6, 7 and 8.
|
||||
required: exclusive
|
||||
zone:
|
||||
description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board or the word `out` to specify the dedicated ALARM/OUT terminal on the Konnected board. Valid values are 1, 2, 3, 4, 5 and out.
|
||||
required: exclusive
|
||||
name:
|
||||
description: The name of the device used in the front end.
|
||||
required: false
|
||||
default: automatically generated
|
||||
activation:
|
||||
description: Either "low" or "high" to specify the state when the switch is turned on.
|
||||
default: high
|
||||
required: false
|
||||
{% endconfiguration%}
|
||||
|
||||
#### Configuration Notes
|
||||
|
||||
- Either **pin** or **zone** is required for each actuator or sensor. Do not use both in the same definition.
|
||||
- Pin `D8` or the `out` zone will only work when activation is set to high (the default).
|
||||
|
||||
## {% linkable_title Full configuration %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
konnected:
|
||||
access_token: REPLACE_ME_WITH_A_RANDOM_STRING
|
||||
devices:
|
||||
- id: 8bcd53
|
||||
binary_sensors:
|
||||
- zone: 1
|
||||
type: door
|
||||
name: 'Front Door'
|
||||
- zone: 3
|
||||
type: motion
|
||||
name: 'Test Motion'
|
||||
switches:
|
||||
- zone: out
|
||||
name: siren
|
||||
- id: 438a38
|
||||
binary_sensors:
|
||||
- pin: 1
|
||||
type: motion
|
||||
name: 'Office Motion'
|
||||
- pin: 2
|
||||
type: door
|
||||
name: 'Office Door'
|
||||
switches:
|
||||
- pin: 5
|
||||
name: 'Garage Door'
|
||||
activation: low
|
||||
```
|
||||
|
||||
### {% linkable_title Pin Mapping %}
|
||||
|
||||
Konnected runs on an ESP8266 board with the NodeMCU firmware. It is commonly used with the NodeMCU dev kit WiFi module and optionally Konnected's Alarm Panel hardware. The following table shows the pin mapping between the Konnected hardware labeled zones, the NodeMCU labeled pins and the ESP8266 GPIO pins.
|
||||
|
||||
| Konnected Alarm Panel Zone | NodeMCU pin | IO Index | ESP8266 GPIO |
|
||||
|---|---|---|---|
|
||||
| 1 | D1 | 1 | GPIO5 |
|
||||
| 2 | D2 | 2 | GPIO4 |
|
||||
| 3 | D5 | 5 | GPIO14 |
|
||||
| 4 | D6 | 6 | GPIO12 |
|
||||
| 5 | D7 | 7 | GPIO13 |
|
||||
| 6 | RX | 9 | GPIO3 |
|
||||
| ALARM or OUT | D8 | 8 | GPIO15 |
|
||||
21
source/_components/light.homematicip_cloud.markdown
Normal file
21
source/_components/light.homematicip_cloud.markdown
Normal file
@ -0,0 +1,21 @@
|
||||
---
|
||||
layout: page
|
||||
title: "HomematicIP Cloud Light"
|
||||
description: "Instructions on how to integrate HomematicIP light switches within Home Assistant."
|
||||
date: 2018-04-02 13:40
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: homematic.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.70
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `homematicip_cloud` light platform allows you to control
|
||||
[HomematicIP](http://www.homematic-ip.com) light switches through Home Assistant.
|
||||
|
||||
Devices will be configured automatically. Please refer to the
|
||||
[component](/components/homematicip_cloud/) configuration on how to setup
|
||||
HomematicIP Cloud.
|
||||
@ -58,4 +58,9 @@ maxcube:
|
||||
required: false
|
||||
type: int
|
||||
default: 62910
|
||||
scan_interval:
|
||||
description: The update interval in seconds
|
||||
required: false
|
||||
type: int
|
||||
default: 300
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -30,6 +30,8 @@ media_player:
|
||||
pc: 'HTPC'
|
||||
```
|
||||
|
||||
If your receiver has second or third zone’s available, they are displayed as additional media players with the same functionality as the main zone.
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: IP address of the device. Example:`192.168.1.2`. If not specified, the platform will load any discovered receivers.
|
||||
@ -39,14 +41,14 @@ name:
|
||||
description: Name of the device. (*Required if host is specified*)
|
||||
required: false
|
||||
type: string
|
||||
max_volume:
|
||||
description: Maximum volume. Defaults to 80.
|
||||
required: false
|
||||
type: number
|
||||
sources:
|
||||
description: A list of mappings from source to source name. Valid sources can be found below. A default list will be used if no source mapping is specified.
|
||||
required: false
|
||||
type: list
|
||||
zone2:
|
||||
description: Enables control for the receiver's second zone.
|
||||
required: false
|
||||
type: bool
|
||||
{% endconfiguration %}
|
||||
|
||||
List of source names:
|
||||
|
||||
@ -24,27 +24,6 @@ Integrate your Serial, Ethernet or MQTT Client MySensors Gateway by adding the f
|
||||
mysensors:
|
||||
gateways:
|
||||
- device: '/dev/ttyUSB0'
|
||||
persistence_file: 'path/mysensors.json'
|
||||
baud_rate: 38400
|
||||
nodes:
|
||||
1:
|
||||
name: 'kitchen'
|
||||
3:
|
||||
name: 'living_room'
|
||||
- device: '/dev/ttyACM0'
|
||||
persistence_file: 'path/mysensors2.json'
|
||||
baud_rate: 115200
|
||||
- device: '192.168.1.18'
|
||||
persistence_file: 'path/mysensors3.json'
|
||||
tcp_port: 5003
|
||||
- device: mqtt
|
||||
persistence_file: 'path/mysensors4.json'
|
||||
topic_in_prefix: 'mygateway1-out'
|
||||
topic_out_prefix: 'mygateway1-in'
|
||||
optimistic: false
|
||||
persistence: true
|
||||
retain: true
|
||||
version: '2.0'
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
@ -62,6 +41,11 @@ mysensors:
|
||||
required: false
|
||||
type: int
|
||||
default: 115200
|
||||
persistence_file:
|
||||
description: The path to a file to save sensor information. The file extension determines the file type. Currently supported file types are 'pickle' and 'json'.
|
||||
required: false
|
||||
type: string
|
||||
default: path/to/config/directory/mysensors.pickle
|
||||
tcp_port:
|
||||
description: Specifies the port of the connected TCP Ethernet gateway.
|
||||
required: false
|
||||
@ -83,23 +67,14 @@ mysensors:
|
||||
type: map
|
||||
keys:
|
||||
name:
|
||||
description: The name the node will be renamed to. This nodename becomes part of the entity_id. Default entity_id is [sketch_name]\_[node_id]\_[child_id] and when this name is set, the entity_id becomes [name]\_[child_id].
|
||||
description: The name the node will be renamed to. This node name becomes part of the entity_id. Default entity_id is [sketch_name]\_[node_id]\_[child_id] and when this name is set, the entity_id becomes [name]\_[child_id].
|
||||
required: true
|
||||
type: string
|
||||
debug:
|
||||
description: This option has been deprecated. Please remove this from your config if you have it included. Use the [logger component](/components/logger/) to filter log messages on log level.
|
||||
required: false
|
||||
type: int
|
||||
persistence:
|
||||
description: Enable or disable local persistence of sensor information. If this is disabled, then each sensor will need to send presentation messages after Home Assistant starts.
|
||||
required: false
|
||||
type: int
|
||||
default: true
|
||||
persistence_file:
|
||||
description: The path to a file to save sensor information. The file extension determines the file type. Currently supported file types are 'pickle' and 'json'.
|
||||
required: false
|
||||
type: string
|
||||
default: path/to/config/directory/mysensors.pickle
|
||||
version:
|
||||
description: Specifies the MySensors protocol version to use. Supports 1.4, 1.5 and 2.0.
|
||||
required: false
|
||||
@ -138,17 +113,47 @@ mqtt:
|
||||
The MQTT gateway requires MySensors version 2.0 and only the MQTT client gateway is supported.
|
||||
</p>
|
||||
|
||||
### {% linkable_title Extended configuration example %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
mysensors:
|
||||
gateways:
|
||||
- device: '/dev/ttyUSB0'
|
||||
persistence_file: 'path/mysensors.json'
|
||||
baud_rate: 38400
|
||||
nodes:
|
||||
1:
|
||||
name: 'kitchen'
|
||||
3:
|
||||
name: 'living_room'
|
||||
- device: '/dev/ttyACM0'
|
||||
persistence_file: 'path/mysensors2.json'
|
||||
baud_rate: 115200
|
||||
- device: '192.168.1.18'
|
||||
persistence_file: 'path/mysensors3.json'
|
||||
tcp_port: 5003
|
||||
- device: mqtt
|
||||
persistence_file: 'path/mysensors4.json'
|
||||
topic_in_prefix: 'mygateway1-out'
|
||||
topic_out_prefix: 'mygateway1-in'
|
||||
optimistic: false
|
||||
persistence: true
|
||||
retain: true
|
||||
version: '2.0'
|
||||
```
|
||||
|
||||
### {% linkable_title Presentation %}
|
||||
|
||||
Present a MySensors sensor or actuator, by following these steps:
|
||||
|
||||
1. Connect the serial gateway to your computer or the Ethernet or MQTT gateway to your network.
|
||||
2. Configure the MySensors component in `configuration.yaml`.
|
||||
3. Start hass.
|
||||
3. Start Home Assistant.
|
||||
4. Write and upload your MySensors sketch to the sensor. Make sure you:
|
||||
- Send sketch name.
|
||||
- Present the sensor's S_TYPE.
|
||||
- Send at least one initial value per V_TYPE. In version 2.0 of MySensors this has to be done in the loop function. See below for an example in 2.0 of how to make sure the initial value has been received by the controller.
|
||||
- Send at least one initial value per V_TYPE. In version 2.0 of MySensors, this has to be done in the loop function. See below for an example in 2.0 of how to make sure the initial value has been received by the controller.
|
||||
5. Start the sensor.
|
||||
|
||||
```cpp
|
||||
@ -231,9 +236,11 @@ void receive(const MyMessage &message) {
|
||||
}
|
||||
```
|
||||
|
||||
### {% linkable_title Heartbeats %}
|
||||
### {% linkable_title SmartSleep %}
|
||||
|
||||
Sending a heartbeat from the MySensors device to Home Assistant activates the SmartSleep functionality in Home Assistant. This means that messages are buffered and only sent to the device upon receiving a heartbeat from the device. State changes are stored so that only the last requested state change is sent to the device. Other types of messages are queued in a FIFO queue. SmartSleep is useful for battery powered actuators that are waiting for commands. See the MySensors library API for information on how to send heartbeats and sleep device.
|
||||
Sending a heartbeat, `I_HEARTBEAT_RESPONSE`, from the MySensors device to Home Assistant, using MySensors version 2.0 - 2.1, activates the SmartSleep functionality in Home Assistant. This means that messages are buffered and only sent to the device upon receiving a heartbeat from the device. State changes are stored so that only the last requested state change is sent to the device. Other types of messages are queued in a FIFO queue. SmartSleep is useful for battery powered actuators that are waiting for commands. See the MySensors library API for information on how to send heartbeats and sleep the device.
|
||||
|
||||
In MySensors version 2.2 the serial API changed from using `I_HEARTBEAT_RESPONSE` to signal SmartSleep, to using `I_PRE_SLEEP_NOTIFICATION` and `I_POST_SLEEP_NOTIFICATION`. Home Assistant has been upgraded to support the new message types and will activate SmartSleep when receiving a message of type `I_PRE_SLEEP_NOTIFICATION`, if using MySensors version 2.2.x or higher. If Home Assistant is configured to use MySensors version 2.0 - 2.1 the old SmartSleep behavior is retained.
|
||||
|
||||
### {% linkable_title Message validation %}
|
||||
|
||||
@ -247,7 +254,7 @@ logger:
|
||||
homeassistant.components.mysensors: debug
|
||||
mysensors: debug
|
||||
```
|
||||
The log should inform you of messages that failed validation or if a child value is missing that is required for a certain child type. Note that the log will log all possible combinations of platforms for a child type that failed validation. It is normal to see some platforms fail validation if the child type supports multiple platforms and your sketch doesn't send all corresponding value types. Eg. the S_BARO child type supports both V_PRESSURE and V_FORECAST value types. If you only send a V_PRESSURE value, an S_BARO entity with V_PRESSURE value will be set up for the sensor platform. But the log will inform of a sensor platform that failed validation due to missing V_FORECAST value type for the S_BARO child. Home Assistant will log failed validations of child values at warning level if one required value type for a platform has been received, but other required value types are missing. Most failed validations are logged at debug level.
|
||||
The log should inform you of messages that failed validation or if a child value is missing that is required for a certain child type. Note that the log will log all possible combinations of platforms for a child type that failed validation. It is normal to see some platforms fail validation if the child type supports multiple platforms and your sketch doesn't send all corresponding value types. Eg. the S_BARO child type supports both V_PRESSURE and V_FORECAST value types. If you only send a V_PRESSURE value, an S_BARO entity with V_PRESSURE value will be set up for the sensor platform. However, the log will inform of a sensor platform that failed validation due to missing V_FORECAST value type for the S_BARO child. Home Assistant will log failed validations of child values at warning level if one required value type for a platform has been received, but other required value types are missing. Most failed validations are logged at debug level.
|
||||
|
||||
Message validation was introduced in version 0.52 of Home Assistant.
|
||||
|
||||
|
||||
@ -43,6 +43,11 @@ cycles:
|
||||
required: false
|
||||
type: int
|
||||
default: 1
|
||||
priority:
|
||||
description: Defines the priority of the notification.
|
||||
required: False
|
||||
type: string
|
||||
default: warning
|
||||
{% endconfiguration %}
|
||||
|
||||
Check out the list of all icons at [https://developer.lametric.com/icons](https://developer.lametric.com/icons). Note that icons always begin with "i" while animations begin with "a". This is part of the name, you can't just use the number!
|
||||
@ -59,11 +64,12 @@ notify:
|
||||
lifetime: 20
|
||||
icon: a7956
|
||||
cycles: 3
|
||||
priority: info
|
||||
```
|
||||
|
||||
### {% linkable_title Changing sounds and icons %}
|
||||
|
||||
To add a notification sound or an icon override, it has to be done via service data.
|
||||
To add a notification sound, icon, cycles, or priority override, it has to be done via service data.
|
||||
|
||||
```yaml
|
||||
- alias: "Send notification on arrival at school"
|
||||
@ -79,6 +85,8 @@ To add a notification sound or an icon override, it has to be done via service d
|
||||
data:
|
||||
sound: 'notification'
|
||||
icon: 'i51'
|
||||
cycles: 0
|
||||
priority: 'critical'
|
||||
```
|
||||
|
||||
### {% linkable_title Only notify specific device %}
|
||||
|
||||
@ -1,57 +0,0 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Simplepush"
|
||||
description: "Instructions on how to add Simplepush notifications to Home Assistant."
|
||||
date: 2016-09-11 18:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: simplepush.png
|
||||
ha_category: Notifications
|
||||
ha_release: 0.29
|
||||
---
|
||||
|
||||
|
||||
The `simplepush` platform uses [Simplepush](https://simplepush.io/) to delivery notifications from Home Assistant to your Android device. Unlike similar apps the Simplepush app requires no registration.
|
||||
|
||||
To add Simplepush to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
notify:
|
||||
- name: NOTIFIER_NAME
|
||||
platform: simplepush
|
||||
device_key: ABCDE
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: Setting the optional parameter `name` allows multiple notifiers to be created. The default value is `notify`. The notifier will bind to the service `notify.NOTIFIER_NAME`.
|
||||
required: false
|
||||
type: string
|
||||
device_key:
|
||||
description: The device key of your device.
|
||||
required: true
|
||||
type: string
|
||||
event:
|
||||
description: The event for the events.
|
||||
required: false
|
||||
type: string
|
||||
password:
|
||||
description: The password of the encryption used by your device.
|
||||
required: inclusive
|
||||
type: string
|
||||
salt:
|
||||
description: The salt used by your device.
|
||||
required: inclusive
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
To test if the service works, just send a message with `curl` from the command-line.
|
||||
|
||||
```bash
|
||||
$ curl 'https://api.simplepush.io/send/device_key/title/message'
|
||||
```
|
||||
|
||||
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
|
||||
117
source/_components/sabnzbd.markdown
Normal file
117
source/_components/sabnzbd.markdown
Normal file
@ -0,0 +1,117 @@
|
||||
---
|
||||
layout: page
|
||||
title: "SABnzbd"
|
||||
description: "Instructions on how to integrate SABnzbd with Home Assistant."
|
||||
date: 2018-03-03 19:09
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: sabnzbd.png
|
||||
ha_category: Downloading
|
||||
ha_release: 0.70
|
||||
ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
The `sabnzbd` component will allow you to monitor and control your downloads with [SABnzbd](https://sabnzbd.org) from
|
||||
within Home Assistant and setup automations based on the information.
|
||||
|
||||
If SABnzbd is discovered on your network, you can enter your API Key in the Configurator. Press "CONFIGURE" to do it.
|
||||
|
||||
<p class='img'>
|
||||
<img src='{{site_root}}/images/screenshots/sabnzbd-configure.png' />
|
||||
</p>
|
||||
|
||||
This will create services for interacting with SABnzbd in scripts and automations, but no sensors will be created.
|
||||
|
||||
|
||||
To configure SABnzbd, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sabnzbd:
|
||||
api_key: YOUR_SABNZBD_API_KEY
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
api_key:
|
||||
description: The API key used to interact with your SABnzbd instance
|
||||
required: true
|
||||
type: string
|
||||
host:
|
||||
description: The hostname of your SABnzbd instance, e.g., 192.168.1.32.
|
||||
required: false
|
||||
default: localhost
|
||||
type: string
|
||||
name:
|
||||
description: The name of your SABnzbd instance (this will be the prefix for all created sensors).
|
||||
required: false
|
||||
default: SABnzbd
|
||||
type: string
|
||||
port:
|
||||
description: The port on which your SABnzbd instance is listening.
|
||||
required: false
|
||||
default: 8080
|
||||
type: integer
|
||||
sensors:
|
||||
description: List of variables for which to create sensor entities.
|
||||
required: false
|
||||
type: list
|
||||
ssl:
|
||||
description: Set to true to use SSL (https) to access SABnzbd.
|
||||
required: false
|
||||
default: false
|
||||
type: boolean
|
||||
{% endconfiguration %}
|
||||
|
||||
Available sensors are:
|
||||
|
||||
* `current_status`: The current status of SABnzbd (Idle, Paused, etc.)
|
||||
* `speed`: The current download speed
|
||||
* `queue_size`: The total size of the download queue
|
||||
* `queue_remaining`: The remaining size of the download queue
|
||||
* `disk_size`: The total disk size at SABnzbd's download location
|
||||
* `disk_free`: The available disk space at SABnzbd's download location
|
||||
* `queue_count`: The number of items in the download queue
|
||||
* `day_size`: GB downloaded today
|
||||
* `week_size`: GB downloaded this week
|
||||
* `month_size`: GB downloaded this month
|
||||
* `total_size`: Total GB downloaded
|
||||
|
||||
## {% linkable_title Full examples %}
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sabnzbd:
|
||||
api_key: YOUR_SABNZBD_API_KEY
|
||||
host: 192.168.1.32
|
||||
name: sab
|
||||
port: 9090
|
||||
ssl: true
|
||||
sensors:
|
||||
- current_status
|
||||
- speed
|
||||
- queue_size
|
||||
- queue_remaining
|
||||
- disk_size
|
||||
- disk_free
|
||||
- queue_count
|
||||
- day_size
|
||||
- week_size
|
||||
- month_size
|
||||
- total_size
|
||||
```
|
||||
This will attempt to access your SABnzbd instance at https://192.168.1.32:9090 and will create sensors named
|
||||
`sensor.sab_status`, `sensor.sab_speed`, etc.
|
||||
|
||||
## {% linkable_title Services %}
|
||||
|
||||
### {% linkable_title Media control services %}
|
||||
Available services: `pause`, `resume`, `set_speed`.
|
||||
|
||||
#### {% linkable_title Service `sabnzbd/set_speed` %}
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| `speed` | yes | Sets the download speed limit. If specified as a number with no units, will be interpreted as a percent. If units are provided (e.g., 500K) will be interpreted absolutely. Defaults to 100 |
|
||||
|
||||
@ -102,10 +102,10 @@ Configuration variables:
|
||||
- **minutely_summary**: A human-readable text summary for the next hour.
|
||||
- **hourly_summary**: A human-readable text summary for the next 24 hours.
|
||||
- **daily_summary**: A human-readable text summary for the next 7 days.
|
||||
- **temperature_max**: Today's expected high temperature.
|
||||
- **temperature_min**: Today's expected low temperature.
|
||||
- **apparent_temperature_max**: Today's expected apparent high temperature.
|
||||
- **apparent_temperature_min**: Today's expected apparent low temperature.
|
||||
- **temperature_high**: Today's daytime expected high temperature.
|
||||
- **temperature_low**: Today's overnight expected low temperature.
|
||||
- **apparent_temperature_high**: Today's daytime expected apparent high temperature.
|
||||
- **apparent_temperature_low**: Today's overnight expected apparent low temperature.
|
||||
- **precip_intensity_max**: Today's expected maximum intensity of precipitation.
|
||||
- **uv_index**: The current UV index.
|
||||
- **units** (*Optional*): Specify the unit system. Default to `si` or `us` based on the temperature preference in Home Assistant. Other options are `auto`, `us`, `si`, `ca`, `uk` and `uk2`.
|
||||
|
||||
74
source/_components/sensor.fints.markdown
Normal file
74
source/_components/sensor.fints.markdown
Normal file
@ -0,0 +1,74 @@
|
||||
---
|
||||
layout: page
|
||||
title: "FinTS Sensor"
|
||||
description: "Instructions on how to use the FinTS sensor."
|
||||
date: 2018-03-25 13:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
ha_category: Sensor
|
||||
ha_release: 0.70
|
||||
ha_iot_class: "Local Push"
|
||||
logo: home-assistant.png
|
||||
---
|
||||
|
||||
With the FinTS sensor, you can fetch your account information from your bank. This only works with banks that support the FinTS (aka. HBCI) standard. The FinTS standard used by many German banks. So if you do not have a German bank account, this will most likely not work for you. To find out if your bank supports FinTS, check the bank's website or call their hotline.
|
||||
|
||||
For each account you have with the bank, a separate sensor is created. If you have several accounts with a bank, you can select which ones you want to have, and you can also give the accounts a name.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: fints
|
||||
bank_identification_number: <for your bank>
|
||||
username: <your FinTS user name>
|
||||
pin: <your FinTS pin>
|
||||
url: <FinTS url of your bank>
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
To find out the configuration for your bank, check their website or call their hotline. Do not use random information you find on the Internet! As you're storing your bank account information in the Home Assistant configuration: make sure that this configuration is not accessible to anyone.
|
||||
|
||||
{% configuration %}
|
||||
sensors:
|
||||
description: List of your sensors.
|
||||
required: true
|
||||
type: map
|
||||
keys:
|
||||
name:
|
||||
description: (optional) name of the bank.
|
||||
required: false
|
||||
type: string
|
||||
bank_identification_number:
|
||||
description: Bank identification number, in most cases the "Bankleitzahl".
|
||||
required: true
|
||||
type: string
|
||||
username:
|
||||
description: Your FinTS username.
|
||||
required: true
|
||||
type: string
|
||||
pin:
|
||||
description: Your FinTS PIN or password.
|
||||
required: true
|
||||
type: string
|
||||
url:
|
||||
description: URL of your bank's FinTS server.
|
||||
required: true
|
||||
type: string
|
||||
accounts:
|
||||
description: (optional) You can configure with of the accounts of your bank shall be shown in Home Assistant. If this attribute is set, only the accounts listed here are shown.
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
account:
|
||||
description: For balance accounts use the IBAN of the account for holdings accounts use the classic account number.
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: (optional) Use this field to give the account a meaningful name.
|
||||
required: false
|
||||
type: string
|
||||
|
||||
{% endconfiguration %}
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: page
|
||||
title: "HomematicIP Cloud Sensor"
|
||||
description: "Instructions on how to integrate HomematIP sensors within Home Assistant."
|
||||
description: "Instructions on how to integrate HomematicIP sensors within Home Assistant."
|
||||
date: 2018-04-02 13:40
|
||||
sidebar: true
|
||||
comments: false
|
||||
|
||||
16
source/_components/sensor.mychevy.markdown
Normal file
16
source/_components/sensor.mychevy.markdown
Normal file
@ -0,0 +1,16 @@
|
||||
---
|
||||
layout: page
|
||||
title: "MyChevy Sensors"
|
||||
description: "Instructions on how to integrate Chevy Bolt sensors car into Home Assistant."
|
||||
date: 2017-08-28 17:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: chevy.png
|
||||
ha_category: Sensor
|
||||
ha_release: 0.62
|
||||
ha_iot_class: "Cloud Polling"
|
||||
---
|
||||
|
||||
For configuration instructions, see [main component config](/components/mychecvy/).
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: page
|
||||
title: "SABnzbd"
|
||||
description: "Instructions on how to integrate SABnzbd within Home Assistant."
|
||||
title: "SABnzbd Sensor"
|
||||
description: "Instructions on how to integrate SABnzbd with Home Assistant."
|
||||
date: 2015-03-23 19:59
|
||||
sidebar: true
|
||||
comments: false
|
||||
@ -14,61 +14,6 @@ ha_iot_class: "Local Polling"
|
||||
---
|
||||
|
||||
|
||||
The `sabnzbd` platform will allow you to monitor your downloads with [SABnzbd](http://sabnzbd.org) from within Home Assistant and setup automation based on the information.
|
||||
The `sabnzbd` sensor platform will allow you to monitor your downloads with [SABnzbd](http://sabnzbd.org) from within Home Assistant.
|
||||
|
||||
If SABnzbd is discovered on your network you can enter your API Key in the Configurator Press "CONFIGURE" to do it.
|
||||
|
||||
<p class='img'>
|
||||
<img src='{{site_root}}/images/screenshots/sabnzbd-configure.png' />
|
||||
</p>
|
||||
|
||||
This will enable a minimal setup where `sensor.sabnzbd_status` is enabled.
|
||||
|
||||
|
||||
For more advanced usage, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
platform: sabnzbd
|
||||
host: YOUR_SABNZBD_HOST
|
||||
api_key: YOUR_API_KEY
|
||||
monitored_variables:
|
||||
- 'current_status'
|
||||
- 'speed'
|
||||
- 'queue_size'
|
||||
- 'queue_remaining'
|
||||
- 'disk_size'
|
||||
- 'disk_free'
|
||||
- 'queue_count'
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **host** (*Required*): The host where your SABnzbd instance is running, eg. 192.168.1.32
|
||||
- **port** (*Optional*): The port to use with SABnzbd instance. Defaults to `8080`.
|
||||
- **api_key** (*Required*): Name that will be used in the frontend for the pin.
|
||||
- **name** (*Optional*): The name to use when displaying this SABnzbd instance.
|
||||
- **ssl** (*Optional*): Use `https` instead of `http` to connect. Defaults to False.
|
||||
- **monitored_variables** array (*Required*): List of the monitored variables.
|
||||
- **current_status**: Current status of the SABnzbd instance
|
||||
- **speed**: Current speed.
|
||||
- **queue_size**: Size of the queue
|
||||
- **queue_remaining**: Remaining elements in the queue
|
||||
- **disk_size**: Disk size of the storage location
|
||||
- **disk_free**: Free disk space at the storage location
|
||||
- **queue_count**: Number of items in the queue
|
||||
|
||||
Note that this will create the following sensors:
|
||||
|
||||
```
|
||||
- sensor.sabnzbd_status
|
||||
- sensor.sabnzbd_speed
|
||||
- sensor.sabnzbd_queue
|
||||
- sensor.sabnzbd_left
|
||||
- sensor.sabnzbd_disk
|
||||
- sensor.sabnzbd_disk_free
|
||||
- sensor.sabnzbd_queue_count
|
||||
```
|
||||
|
||||
As always, you can determine the names of sensors by looking at the dev-state page `< >` in the web interface.
|
||||
To add SABnzbd sensors, please follow the instructions for the [SABnzbd component](/components/sabnzbd).
|
||||
|
||||
@ -14,6 +14,8 @@ ha_iot_class: "Local Polling"
|
||||
|
||||
The `skybeacon` sensor platform supports [CR2477](http://cnsky9.en.alibaba.com)-powered [iBeacon](https://en.wikipedia.org/wiki/IBeacon)/eddystone sensors that come with temperature/sensor module.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To use your Skybeacon sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
@ -26,8 +28,24 @@ sensor:
|
||||
- humidity
|
||||
```
|
||||
|
||||
- **mac** (*Required*): The MAC address of your sensor. You can find this be running `hcitool lescan` from command line.
|
||||
- **monitored_conditions** array (*Required*): The parameters that should be monitored.
|
||||
- **temperature**: Temperature at the sensor's location.
|
||||
- **humidity**: Humidity at the sensor's location.
|
||||
{% configuration %}
|
||||
mac:
|
||||
description: "The MAC address of your sensor. You can find this be running `hcitool lescan` from command line."
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: The name of the Skybeacon sensor.
|
||||
required: false
|
||||
type: string
|
||||
default: Skybeacon
|
||||
monitored_conditions:
|
||||
description: The parameters that should be monitored.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
temperature:
|
||||
description: Temperature at the sensor's location.
|
||||
humidity:
|
||||
description: Humidity at the sensor's location.
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
@ -48,4 +48,12 @@ name:
|
||||
required: false
|
||||
default: "Waze Travel Time"
|
||||
type: string
|
||||
incl_filter:
|
||||
description: A substring that has to be present in the description of the selected route (a simple case-insensitive matching).
|
||||
required: false
|
||||
type: string
|
||||
excl_filter:
|
||||
description: A substring that has to be NOT present in the description of the selected route (a simple case-insensitive matching).
|
||||
required: false
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
149
source/_components/spaceapi.markdown
Normal file
149
source/_components/spaceapi.markdown
Normal file
@ -0,0 +1,149 @@
|
||||
---
|
||||
layout: page
|
||||
title: "SpaceAPI"
|
||||
description: "Instructions on how to configure the SpaceAPI for Home Assistant."
|
||||
date: 2018-05-08 09:00
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: spaceapi.png
|
||||
ha_category: Other
|
||||
ha_release: "0.70"
|
||||
---
|
||||
|
||||
The `spaceapi` component allow Hackerspaces to expose information to web apps or any other application with the [SpaceAPI](http://spaceapi.net/).
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To setup the `spaceapi` component in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
spaceapi:
|
||||
space: HACKERSPACE_NAME
|
||||
logo: URL_FOR_LOGO
|
||||
url: URL
|
||||
location:
|
||||
address: ADDRESS
|
||||
contact:
|
||||
email: EMAIL_ADDRESS
|
||||
issue_report_channels:
|
||||
- email
|
||||
state:
|
||||
entity_id: binary_sensor.front_door
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
space:
|
||||
description: Name of the Hackerspace.
|
||||
required: true
|
||||
type: string
|
||||
logo:
|
||||
description: URL which is publicly accessible of the logo.
|
||||
required: true
|
||||
type: URL
|
||||
logo:
|
||||
description: URL of the hackerspace's web site.
|
||||
required: true
|
||||
type: URL
|
||||
location:
|
||||
description: Location of the Hackerspace.
|
||||
required: true
|
||||
type: map
|
||||
keys:
|
||||
address:
|
||||
description: The physical address of the Hackerspace.
|
||||
required: true
|
||||
type: String
|
||||
contact:
|
||||
description: Contact information of the Hackerspace.
|
||||
required: true
|
||||
type: map
|
||||
keys:
|
||||
email:
|
||||
description: The email address of the Hackerspace.
|
||||
required: true
|
||||
type: String
|
||||
irc:
|
||||
description: The IRC channel of the Hackerspace
|
||||
required: false
|
||||
type: String
|
||||
mailing_list:
|
||||
description: The mailing list of the Hackerspace.
|
||||
required: false
|
||||
type: String
|
||||
twitter:
|
||||
description: The Twitter account of the Hackerspace.
|
||||
required: false
|
||||
type: String
|
||||
issue_report_channels:
|
||||
description: "The reporting channel for issues. Pick an entity from `contact:`."
|
||||
required: true
|
||||
type: List
|
||||
state:
|
||||
description: The current state of the Hackerspace.
|
||||
required: true
|
||||
type: list
|
||||
keys:
|
||||
entity_id:
|
||||
description: "The `entity_id` of a binary sensor that represents the current state."
|
||||
required: true
|
||||
type: entity_id
|
||||
icon_open:
|
||||
description: The URL which is publicly accessible of the icon for the open Hackerspace.
|
||||
required: false
|
||||
type: URL
|
||||
icon_closed:
|
||||
description: The URL which is publicly accessible of the icon for the closed Hackerspace.
|
||||
required: false
|
||||
type: URL
|
||||
sensors:
|
||||
description: List of sensors to expose.
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
temperature:
|
||||
description: List of temperature sensors.
|
||||
required: true
|
||||
type: entity_id
|
||||
humidity:
|
||||
description: The Twitter account of the Hackerspace.
|
||||
required: true
|
||||
type: entity_id
|
||||
{% endconfiguration %}
|
||||
|
||||
## {% linkable_title Examples %}
|
||||
|
||||
In this section you find some real life examples of how to use this component.
|
||||
|
||||
### {% linkable_title Eastermundigen %}
|
||||
|
||||
A possible configuration entry for [Eastermundigen](http://www.eastermundigen.ch/), a Hackerspace in Switzerland, could look like this.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
spaceapi:
|
||||
space: Eastermundigen
|
||||
logo: https://eastermundigen.ch/logo.png
|
||||
url: https://eastermundigen.ch
|
||||
location:
|
||||
address: "Steinbruchweg 16, 3072 Ostermundigen, Schweiz"
|
||||
contact:
|
||||
phone: "+41311111111"
|
||||
twitter: "@eastermundigen"
|
||||
email: "info@eastermundigen.ch"
|
||||
issue_report_channels:
|
||||
- email
|
||||
state:
|
||||
entity_id: binary_sensor.front_door"
|
||||
icon_open: https://eastermundigen.ch/open.png
|
||||
icon_closed: https://eastermundigen.ch/close.png
|
||||
sensors:
|
||||
temperature:
|
||||
- "sensor.temperature_in"
|
||||
- "sensor.temperature_out"
|
||||
humidity:
|
||||
- "sensor.humidity_in"
|
||||
- "sensor.humidity_out"
|
||||
```
|
||||
@ -13,7 +13,7 @@ ha_iot_class: "Local Polling"
|
||||
ha_release: 0.16
|
||||
---
|
||||
|
||||
The `arest` switch platform allows you to toggle pins of your devices (like Arduino boards with a Ethernet/Wifi connection, ESP8266 based devices, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework.
|
||||
The `arest` switch platform allows you to toggle pins of your devices (like Arduino boards with an Ethernet/Wifi connection, ESP8266 based devices, and the Raspberry Pi) running the [aREST](http://arest.io/) RESTful framework.
|
||||
|
||||
To use your aREST enabled device with pins in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -25,6 +25,9 @@ switch:
|
||||
pins:
|
||||
11:
|
||||
name: Fan
|
||||
13:
|
||||
name: Switch
|
||||
invert: True
|
||||
```
|
||||
|
||||
If you want to use custom functions, then add the following to your `configuration.yaml` file:
|
||||
@ -39,18 +42,39 @@ switch:
|
||||
function1:
|
||||
name: Light Desk
|
||||
```
|
||||
|
||||
Configuration variables:
|
||||
|
||||
- **resource** (*Required*): IP address and schema of the device that is exposing an aREST API, eg. http://192.168.1.10 (no-trailing slash)
|
||||
- **name** (*Optional*): Let you overwrite the name of the device. By default *name* from the device is used.
|
||||
- **pins** array (*Optional*): An array with all used pins.
|
||||
- **name** (*Required*): The name of the pin to use in the frontend.
|
||||
|
||||
or
|
||||
|
||||
- **functions** array (*Optional*): An array with all used functions.
|
||||
- **name** (*Required*): The name to use in the frontend.
|
||||
{% configuration %}
|
||||
resource:
|
||||
description: IP address and schema of the device that is exposing an aREST API, e.g., http://192.168.1.10 (no-trailing slash)
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: Let you overwrite the name of the device. By default *name* from the device is used.
|
||||
required: optional
|
||||
type: string
|
||||
pins:
|
||||
description: An array with all used pins.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
name:
|
||||
description: The name of the pin to use in the frontend.
|
||||
required: true
|
||||
type: string
|
||||
invert:
|
||||
description: If the logic for on/off should be inverted.
|
||||
required: false
|
||||
type: boolean
|
||||
default: false
|
||||
functions:
|
||||
description: An array with all used functions.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
name:
|
||||
description: The name to use in the frontend.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
You can still switch your pins with a web browser or a command line tool. Use the URL http://192.168.1.10/digital/8/1 to set pin 8 to high/on, the JSON response will give you the feedback.
|
||||
|
||||
|
||||
21
source/_components/switch.homematicip_cloud.markdown
Normal file
21
source/_components/switch.homematicip_cloud.markdown
Normal file
@ -0,0 +1,21 @@
|
||||
---
|
||||
layout: page
|
||||
title: "HomematicIP Cloud Switch"
|
||||
description: "Instructions on how to integrate HomematicIP switches within Home Assistant."
|
||||
date: 2018-04-02 13:40
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: homematic.png
|
||||
ha_category: Switch
|
||||
ha_release: 0.70
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `homematicip_cloud` switch platform allows you to control
|
||||
[HomematicIP](http://www.homematic-ip.com) switches through Home Assistant.
|
||||
|
||||
Devices will be configured automatically. Please refer to the
|
||||
[component](/components/homematicip_cloud/) configuration on how to setup
|
||||
HomematicIP Cloud.
|
||||
19
source/_components/switch.konnected.markdown
Normal file
19
source/_components/switch.konnected.markdown
Normal file
@ -0,0 +1,19 @@
|
||||
---
|
||||
layout: page
|
||||
title: "Konnected Switch"
|
||||
description: "Connect wired actuators to Home Assistant with Konnected and a NodeMCU ESP8266"
|
||||
date: 2018-04-03 12:30
|
||||
sidebar: true
|
||||
comments: false
|
||||
sharing: true
|
||||
footer: true
|
||||
logo: konnected.png
|
||||
ha_category: Switch
|
||||
ha_release: "0.70"
|
||||
ha_iot_class: "Local Push"
|
||||
---
|
||||
|
||||
The `konnected` switch platform allows you to actuate an alarm system siren, strobe light, buzzer or any other wired device using a [Konnected Alarm Panel board](https://konnected.io) or relay module and a NodeMCU ESP8266 WiFi module running the [open source Konnected software](https://github.com/konnected-io/konnected-security).
|
||||
|
||||
See the [`konnected`](/components/konnected/) component for configuration and setup instructions.
|
||||
|
||||
@ -10,13 +10,33 @@ footer: true
|
||||
redirect_from: /ecosystem/synology/
|
||||
---
|
||||
|
||||
Synology NAS are the perfect companion to running Home Assistant.
|
||||
Synology NAS are the perfect companion to running Home Assistant. But by default, the DSM Reverse Proxy does not configure its NGINX settings to allow WebSocket, and some extra configuration will be required to get the Home Assistant frontend working with the DSM.
|
||||
|
||||
### {% linkable_title HTTP Configuration %}
|
||||
### {% linkable_title Template change %}
|
||||
|
||||
Synology will require some extra configuration to get the Home Assistant frontend working.
|
||||
To allow WebSocket by default for all service exposed by NGINX, you can enable it in the template file located in `/usr/syno/share/nginx/Portal.mustache`. Please be really careful in editing this file since you may break access to the DSM UI. Please backup this file before any edition.
|
||||
|
||||
- Copy the Home Assistant specific Reverse Proxy settings from the existing `/etc/nginx/app.d/server.ReverseProxy.conf` to `/usr/local/etc/nginx/conf.d/http.HomeAssistant.conf`
|
||||
Open `/usr/syno/share/nginx/Portal.mustache` and add the followings in the `Location` section:
|
||||
|
||||
```
|
||||
proxy_set_header Upgrade $http_upgrade;
|
||||
proxy_set_header Connection "upgrade";
|
||||
proxy_read_timeout 86400;
|
||||
```
|
||||
|
||||
Then restart the NGINX daemon:
|
||||
|
||||
```bash
|
||||
sudo synoservicecfg --restart nginx
|
||||
```
|
||||
|
||||
This will restart the running HTTP service, not only reverse proxy, as a single instance of NGINX runs everything.
|
||||
|
||||
You can find more information [here](https://github.com/orobardet/dsm-reverse-proxy-websocket).
|
||||
|
||||
#### {% linkable_title HTTP Configuration %}
|
||||
|
||||
- Copy the Home Assistant specific Reverse Proxy settings from the existing `/etc/nginx/app.d/server.ReverseProxy.conf` file to `/usr/local/etc/nginx/conf.d/http.HomeAssistant.conf`.
|
||||
- Include these lines in the location declaration:
|
||||
|
||||
```
|
||||
|
||||
435
source/_posts/2018-05-18-release-70.markdown
Normal file
435
source/_posts/2018-05-18-release-70.markdown
Normal file
@ -0,0 +1,435 @@
|
||||
---
|
||||
layout: post
|
||||
title: "0.70: Facebox, SpaceAPI, Konnected Alarm System"
|
||||
description: "Complete overhaul of our new frontend. "
|
||||
date: 2018-05-27 00:01:00
|
||||
date_formatted: "May 27, 2018"
|
||||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Release-Notes
|
||||
---
|
||||
|
||||
It's time for release 0.70. It's a little later than expected because of a major overhaul of how our frontend is build. It should not have any impact on how the frontend looks or behaves. Thanks to all the people running the beta who helped test this. Right now it looks like Firefox is still having some issues running the Hass.io panel. We're working on releasing a fix for that soon.
|
||||
|
||||
If you're using custom UI or Panels, some changes have been made. Make sure you run the latest version. More info on our [developer blog](https://developers.home-assistant.io/blog/2018/05/22/custom-ui-panels-api.html).
|
||||
|
||||
Talking about our developer blog, this is a new blog with accompanying [Twitter account](https://twitter.com/hass_devs). This is part of our ongoing effort of splitting content and interaction for users and developers of Home Assistant.
|
||||
|
||||
One cool new component in this release is [Konnected][konnected docs] ([product page](https://konnected.io/)). It allows you to connect your existing wired alarm systen and plug it … straigt into Home Assistant!
|
||||
|
||||
Another cool one this release is [Facebox][image_processing.facebox docs]. It will allow you to do local face detection on your camera feeds. Can't wait to hear the cool things people will do with this.
|
||||
|
||||
## {% linkable_title New Platforms %}
|
||||
|
||||
- Converted SABnzbd to a component ([@jeradM] - [#12915]) ([sabnzbd docs]) ([sensor.sabnzbd docs]) (breaking change) (new-platform)
|
||||
- Add more homematicip cloud components ([@mxworm] - [#14084]) ([homematicip_cloud docs]) ([binary_sensor.homematicip_cloud docs]) ([light.homematicip_cloud docs]) ([switch.homematicip_cloud docs]) (new-platform)
|
||||
- Adds facebox ([@robmarkcole] - [#14356]) ([image_processing.facebox docs]) (new-platform)
|
||||
- Add SpaceAPI support ([@fabaff] - [#14204]) ([spaceapi docs]) (new-platform)
|
||||
- Samsung Family hub camera component ([@Klathmon] - [#14458]) ([camera.familyhub docs]) (new-platform)
|
||||
- Add Konnected component with support for discovery, binary sensor and switch ([@heythisisnate] - [#13670]) ([konnected docs]) ([binary_sensor.konnected docs]) ([switch.konnected docs]) (new-platform)
|
||||
- New Sensor FinTS ([@ChristianKuehnel] - [#14334]) ([sensor.fints docs]) (new-platform)
|
||||
|
||||
## {% linkable_title New Features %}
|
||||
|
||||
- Allow HomeKit name to be customized ([@schmittx] - [#14159]) ([homekit docs]) (new-feature)
|
||||
- Add HomeKit support for fans ([@schmittx] - [#14351]) ([homekit docs]) (new-feature)
|
||||
|
||||
## {% linkable_title If you need help... %}
|
||||
|
||||
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e). 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](https://github.com/home-assistant/home-assistant/issues). Make sure to fill in all fields of the issue template.
|
||||
|
||||
<!--more-->
|
||||
## {% linkable_title Breaking Changes %}
|
||||
|
||||
- Converted SABnzbd to a component. Set it up using the new config:
|
||||
```yaml
|
||||
sabnzbd:
|
||||
api_key: YOUR_SABNZBD_API_KEY
|
||||
```
|
||||
([@jeradM] - [#12915]) ([sabnzbd docs]) ([sensor.sabnzbd docs]) (breaking change) (new-platform)
|
||||
- For BMW electric cars: The current sensor `remaining_range_fuel` is replaced by `remaining_range_total` for cars with a combustion engine. ([@gerard33] - [#14293]) ([bmw_connected_drive docs]) ([binary_sensor.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs]) (breaking change)
|
||||
- Removed simplepush.io becayse website is offline and apps are no longer available. ([@c727] - [#14358]) ([notify docs]) (breaking change)
|
||||
- DarkSky sensor: Added temperature (apparent) high/low, deprecated max/min ([@nordlead2005] - [#12233]) ([sensor.darksky docs]) (breaking change)
|
||||
|
||||
## {% linkable_title Beta Fixes %}
|
||||
|
||||
- Wait for future mysensors gateway ready ([@MartinHjelmare] - [#14398]) ([mysensors docs]) (beta fix)
|
||||
- Homekit style cleanup ([@cdce8p] - [#14556]) ([homekit docs]) (beta fix)
|
||||
- fix nanoleaf aurora lights min and max temperature ([@Oro] - [#14571]) ([light.nanoleaf_aurora docs]) (beta fix)
|
||||
- Fix ISY moisure sensors showing unknown until a leak is detected ([@OverloadUT] - [#14496]) ([binary_sensor.isy994 docs]) (beta fix)
|
||||
- Bump insteonplm version to fix device hanging ([@teharris1] - [#14582]) ([insteon_plm docs]) (beta fix)
|
||||
- Fix hue discovery popping up ([@balloob] - [#14614]) (beta fix)
|
||||
- Use libsodium18 ([@balloob] - [#14624]) (beta fix)
|
||||
- No longer use backports for ffmpeg ([@balloob] - [#14626]) (beta fix)
|
||||
- Allow Hass.io panel dir ([@balloob] - [#14655]) ([hassio docs]) (beta fix)
|
||||
|
||||
## {% linkable_title All changes %}
|
||||
|
||||
- Add unique_id to MQTT switch ([@thepotoo] - [#13719]) ([switch.mqtt docs])
|
||||
- zha: Bump to zigpy 0.1.0 ([@rcloran] - [#14305]) ([zha docs])
|
||||
- Converted SABnzbd to a component ([@jeradM] - [#12915]) ([sabnzbd docs]) ([sensor.sabnzbd docs]) (breaking change) (new-platform)
|
||||
- Adds unique ID to Roku for entity registry inclusion ([@bachya] - [#14325]) ([media_player.roku docs])
|
||||
- Update hitron_coda.py to fix login for Shaw modems ([@mikedm139] - [#14306]) ([device_tracker docs])
|
||||
- Add sensors for BMW electric cars ([@gerard33] - [#14293]) ([bmw_connected_drive docs]) ([binary_sensor.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs]) (breaking change)
|
||||
- Add more homematicip cloud components ([@mxworm] - [#14084]) ([homematicip_cloud docs]) ([binary_sensor.homematicip_cloud docs]) ([light.homematicip_cloud docs]) ([switch.homematicip_cloud docs]) (new-platform)
|
||||
- add 2 devices ([@m4dmin] - [#14321]) ([tahoma docs]) ([cover.tahoma docs])
|
||||
- Gogogate2 0.1.1 ([@dlbroadfoot] - [#14294]) ([cover.gogogate2 docs])
|
||||
- Snips: Added slot values for siteId and probability ([@tschmidty69] - [#14315]) ([snips docs])
|
||||
- Add help for conversation/process service ([@stephanerosi] - [#14323])
|
||||
- Fix BOM weather '-' value ([@nickw444] - [#14042]) ([sensor.bom docs]) ([weather.bom docs])
|
||||
- Make sure zwave nodes/entities enter the registry is proper state. ([@andrey-git] - [#14251]) ([zwave docs])
|
||||
- Improving icloud device tracker ([@evgeniy-khatko] - [#14078]) ([device_tracker docs])
|
||||
- Adds useful attributes to RainMachine programs and zones ([@bachya] - [#14087]) ([switch.rainmachine docs])
|
||||
- Waze Travel Time: optional inclusive/exclusive filters ([@diraimondo] - [#14000]) ([sensor.waze_travel_time docs])
|
||||
- Add zone 3 for Onkyo media player ([@snikch] - [#14295]) ([media_player.onkyo docs])
|
||||
- Support control of away mode and hold mode in Venstar component. Correctly detect humidifiers. ([@nkaminski] - [#14256]) ([climate.venstar docs])
|
||||
- Upgrade keyring to 12.2.0 and keyrings.alt to 3.1 ([@fabaff] - [#14355])
|
||||
- debug++ for multiple volume controls ([@rytilahti] - [#14349]) ([media_player.songpal docs])
|
||||
- Backend tweaks to make authorization work ([@balloob] - [#14339]) ([api docs]) ([frontend docs]) ([http docs]) ([websocket_api docs])
|
||||
- script/lint: Ensure there are files to test with pylint ([@cdce8p] - [#14363])
|
||||
- Update .coveragerc ([@pvizeli] - [#14368])
|
||||
- Fix binary_sensor async_update ([@damarco] - [#14376]) ([zha docs]) ([binary_sensor.zha docs])
|
||||
- Add local auth provider ([@balloob] - [#14365])
|
||||
- Update to sensibo 1.0.3 with better error reporting ([@andrey-git] - [#14380]) ([climate.sensibo docs])
|
||||
- Fix binary_sensor device_state_attributes ([@damarco] - [#14375]) ([binary_sensor.zha docs])
|
||||
- Add support for pressure sensors ([@damarco] - [#14361]) ([zha docs]) ([sensor.zha docs])
|
||||
- Add "framerate" parameter to generic camera ([@abmantis] - [#14079]) ([camera docs]) ([camera.generic docs])
|
||||
- Rewritten HomeKit tests ([@cdce8p] - [#14377]) ([homekit docs])
|
||||
- Update sensor state before adding device ([@damarco] - [#14357]) ([sensor.zha docs])
|
||||
- Make mysensors component async ([@MartinHjelmare] - [#13641]) ([mysensors docs]) ([notify docs]) ([climate.mysensors docs]) ([cover.mysensors docs]) ([light.mysensors docs]) ([switch.mysensors docs])
|
||||
- Adds facebox ([@robmarkcole] - [#14356]) ([image_processing.facebox docs]) (new-platform)
|
||||
- more detailed error message ([@exxamalte] - [#14385]) ([sensor.rest docs])
|
||||
- Allow HomeKit name to be customized ([@schmittx] - [#14159]) ([homekit docs]) (new-feature)
|
||||
- Xiaomi Aqara: Add new cube model (sensor_cube.aqgl01) ([@syssi] - [#14393]) ([binary_sensor.xiaomi_aqara docs])
|
||||
- Bump pycmus version ([@mtreinish] - [#14395]) ([media_player.cmus docs])
|
||||
- Fix name of tox pylint env ([@MartinHjelmare] - [#14402])
|
||||
- Use None as initial state in zha component ([@damarco] - [#14389]) ([sensor.zha docs])
|
||||
- Bump PyXiaomiGateway version ([@syssi] - [#14412]) ([xiaomi_aqara docs])
|
||||
- Homekit test cleanup ([@cdce8p] - [#14416]) ([homekit docs])
|
||||
- Update pylint to 1.8.4 ([@scop] - [#14421])
|
||||
- Bring back typing check. Meanwhile just for homeassistant/*.py ([@andrey-git] - [#14410])
|
||||
- Look at registry before pulling zwave config values ([@andrey-git] - [#14408]) ([zwave docs])
|
||||
- Add Bulgarian to Google TTS ([@Chariyski] - [#14422]) ([tts docs])
|
||||
- Remove extra quotes from docstrings ([@scop] - [#14431]) ([folder_watcher docs]) ([sensor.sigfox docs]) ([sensor.simulated docs])
|
||||
- Spelling, grammar etc fixes ([@scop] - [#14432]) ([hassio docs]) ([homekit docs]) ([media_player.yamaha docs]) ([sensor.buienradar docs]) ([sensor.hive docs]) ([sensor.statistics docs]) ([switch.tahoma docs])
|
||||
- Invoke pytest instead of py.test per upstream recommendation, #dropthedot ([@scop] - [#14434])
|
||||
- Fix fan service description ([@cdce8p] - [#14423])
|
||||
- Clean up some Python 3.4 remnants ([@scop] - [#14433]) ([system_log docs])
|
||||
- Remove universal wheel setting ([@MartinHjelmare] - [#14445])
|
||||
- Upgrade requests_mock to 1.5 ([@fabaff] - [#14444])
|
||||
- Upgrade pyota to 2.0.5 ([@fabaff] - [#14442]) ([iota docs]) ([sensor.iota docs])
|
||||
- Upgrade python-telegram-bot to 10.1.0 ([@fabaff] - [#14441]) ([telegram_bot docs])
|
||||
- Upgrade Sphinx to 1.7.4 ([@fabaff] - [#14439])
|
||||
- Upgrade youtube_dl to 2018.05.09 ([@fabaff] - [#14438]) ([media_extractor docs])
|
||||
- Upgrade distro to 1.3.0 ([@fabaff] - [#14436]) ([updater docs])
|
||||
- Add priority and cycles to LaMetric ([@PhilRW] - [#14414]) ([notify docs])
|
||||
- Allow qwikswitch sensors as part of devices ([@kellerza] - [#14454]) ([qwikswitch docs])
|
||||
- Bump requirement to pydeconz v38 ([@Kane610] - [#14452]) ([deconz docs])
|
||||
- Add SpaceAPI support ([@fabaff] - [#14204]) ([spaceapi docs]) (new-platform)
|
||||
- Use ATTR_NAME from const.py ([@fabaff] - [#14450])
|
||||
- zha: Fix cluster class check in single-cluster device type ([@rcloran] - [#14303]) ([zha docs])
|
||||
- Upgrade pygatt to 3.2.0 ([@fabaff] - [#14447]) ([sensor.skybeacon docs])
|
||||
- Add support for direction to fan template ([@schmittx] - [#14371]) ([fan.template docs])
|
||||
- Samsung Family hub camera component ([@Klathmon] - [#14458]) ([camera.familyhub docs]) (new-platform)
|
||||
- Fix key error upon missing node ([@MartinHjelmare] - [#14460]) ([mysensors docs])
|
||||
- Bump lakeside version ([@mjg59] - [#14471]) ([eufy docs])
|
||||
- Minor Wink fixes ([@w1ll1am23] - [#14468]) ([climate.wink docs]) ([light.wink docs])
|
||||
- Don't poll the Samsung Family hub camera ([@syssi] - [#14473]) ([camera.familyhub docs])
|
||||
- Optimistic MQTT light ([@dgomes] - [#14401]) ([light.mqtt docs])
|
||||
- Remove simplepush.io ([@c727] - [#14358]) ([notify docs]) (breaking change)
|
||||
- Add Konnected component with support for discovery, binary sensor and switch ([@heythisisnate] - [#13670]) ([konnected docs]) ([binary_sensor.konnected docs]) ([switch.konnected docs]) (new-platform)
|
||||
- Make Feedreader component more extendable ([@exxamalte] - [#14342]) ([feedreader docs])
|
||||
- BMW code cleanup ([@gerard33] - [#14424]) ([binary_sensor.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs])
|
||||
- Don't add a url to built-in panels ([@balloob] - [#14456]) ([frontend docs])
|
||||
- Added temperature (apparent) high/low, deprecated max/min ([@nordlead2005] - [#12233]) ([sensor.darksky docs]) (breaking change)
|
||||
- Improve handling of offline Sonos devices ([@amelchio] - [#14479]) ([media_player.sonos docs])
|
||||
- "unavailable" Media players should be considered off in Universal player ([@OverloadUT] - [#14466]) ([media_player.universal docs])
|
||||
- Added option to invert aREST pin switch logic for active low relays ([@w1ll1am23] - [#14467]) ([switch.arest docs])
|
||||
- Use "Returns" consistently to avoid being treated as section ([@scop] - [#14448])
|
||||
- Add HomeKit support for fans ([@schmittx] - [#14351]) ([homekit docs]) (new-feature)
|
||||
- Add stdout and stderr to debug output for shell_command ([@n8henrie] - [#14465]) ([shell_command docs])
|
||||
- New Sensor FinTS ([@ChristianKuehnel] - [#14334]) ([sensor.fints docs]) (new-platform)
|
||||
- Update hitron_coda.py ([@mikedm139] - [#14506]) ([device_tracker docs])
|
||||
- Konnected component follow up ([@heythisisnate] - [#14491]) ([konnected docs])
|
||||
- Adjust LimitlessLED properties for running effects ([@amelchio] - [#14481]) ([light.limitlessled docs])
|
||||
- Bump locationsharinglib to 2.0.2 ([@thelittlefireman] - [#14359]) ([device_tracker docs])
|
||||
- Update frontend to 20180518.0 ([@balloob] - [#14510]) ([frontend docs])
|
||||
- Feedreader configurable update interval and max entries ([@exxamalte] - [#14487]) ([feedreader docs])
|
||||
- Flux bug fix ([@oblogic7] - [#14476]) ([light.flux_led docs]) ([switch.flux docs])
|
||||
- Show warning if no locations are shared (fixes #14177) ([@fabaff] - [#14511]) ([device_tracker docs])
|
||||
- Add code to HomeKit lock ([@cdce8p] - [#14524]) ([homekit docs])
|
||||
- Set pytz to >=2018.04 ([@fabaff] - [#14520])
|
||||
- Add Homematic IP RotaryHandleSensor support ([@hanzoh] - [#14522]) ([homematic docs])
|
||||
- Update HAP-python to 2.1.0 ([@cdce8p] - [#14528]) ([homekit docs])
|
||||
- Fix some ISY sensors not getting detected as binary sensors ([@OverloadUT] - [#14497]) ([isy994 docs])
|
||||
- Update mychevy to 0.4.0 ([@sdague] - [#14372]) ([mychevy docs]) ([binary_sensor.mychevy docs]) ([sensor.mychevy docs])
|
||||
- Set certifi to >=2018.04.16 ([@fabaff] - [#14536])
|
||||
- Wait for future mysensors gateway ready ([@MartinHjelmare] - [#14398]) ([mysensors docs]) (beta fix)
|
||||
- Homekit style cleanup ([@cdce8p] - [#14556]) ([homekit docs]) (beta fix)
|
||||
- fix nanoleaf aurora lights min and max temperature ([@Oro] - [#14571]) ([light.nanoleaf_aurora docs]) (beta fix)
|
||||
- Fix ISY moisure sensors showing unknown until a leak is detected ([@OverloadUT] - [#14496]) ([binary_sensor.isy994 docs]) (beta fix)
|
||||
- Bump insteonplm version to fix device hanging ([@teharris1] - [#14582]) ([insteon_plm docs]) (beta fix)
|
||||
- Fix hue discovery popping up ([@balloob] - [#14614]) (beta fix)
|
||||
- Use libsodium18 ([@balloob] - [#14624]) (beta fix)
|
||||
- No longer use backports for ffmpeg ([@balloob] - [#14626]) (beta fix)
|
||||
- Allow Hass.io panel dir ([@balloob] - [#14655]) ([hassio docs]) (beta fix)
|
||||
|
||||
[#12233]: https://github.com/home-assistant/home-assistant/pull/12233
|
||||
[#12915]: https://github.com/home-assistant/home-assistant/pull/12915
|
||||
[#13641]: https://github.com/home-assistant/home-assistant/pull/13641
|
||||
[#13670]: https://github.com/home-assistant/home-assistant/pull/13670
|
||||
[#13719]: https://github.com/home-assistant/home-assistant/pull/13719
|
||||
[#14000]: https://github.com/home-assistant/home-assistant/pull/14000
|
||||
[#14042]: https://github.com/home-assistant/home-assistant/pull/14042
|
||||
[#14078]: https://github.com/home-assistant/home-assistant/pull/14078
|
||||
[#14079]: https://github.com/home-assistant/home-assistant/pull/14079
|
||||
[#14084]: https://github.com/home-assistant/home-assistant/pull/14084
|
||||
[#14087]: https://github.com/home-assistant/home-assistant/pull/14087
|
||||
[#14159]: https://github.com/home-assistant/home-assistant/pull/14159
|
||||
[#14204]: https://github.com/home-assistant/home-assistant/pull/14204
|
||||
[#14251]: https://github.com/home-assistant/home-assistant/pull/14251
|
||||
[#14256]: https://github.com/home-assistant/home-assistant/pull/14256
|
||||
[#14293]: https://github.com/home-assistant/home-assistant/pull/14293
|
||||
[#14294]: https://github.com/home-assistant/home-assistant/pull/14294
|
||||
[#14295]: https://github.com/home-assistant/home-assistant/pull/14295
|
||||
[#14303]: https://github.com/home-assistant/home-assistant/pull/14303
|
||||
[#14305]: https://github.com/home-assistant/home-assistant/pull/14305
|
||||
[#14306]: https://github.com/home-assistant/home-assistant/pull/14306
|
||||
[#14315]: https://github.com/home-assistant/home-assistant/pull/14315
|
||||
[#14321]: https://github.com/home-assistant/home-assistant/pull/14321
|
||||
[#14323]: https://github.com/home-assistant/home-assistant/pull/14323
|
||||
[#14325]: https://github.com/home-assistant/home-assistant/pull/14325
|
||||
[#14334]: https://github.com/home-assistant/home-assistant/pull/14334
|
||||
[#14339]: https://github.com/home-assistant/home-assistant/pull/14339
|
||||
[#14342]: https://github.com/home-assistant/home-assistant/pull/14342
|
||||
[#14349]: https://github.com/home-assistant/home-assistant/pull/14349
|
||||
[#14351]: https://github.com/home-assistant/home-assistant/pull/14351
|
||||
[#14355]: https://github.com/home-assistant/home-assistant/pull/14355
|
||||
[#14356]: https://github.com/home-assistant/home-assistant/pull/14356
|
||||
[#14357]: https://github.com/home-assistant/home-assistant/pull/14357
|
||||
[#14358]: https://github.com/home-assistant/home-assistant/pull/14358
|
||||
[#14359]: https://github.com/home-assistant/home-assistant/pull/14359
|
||||
[#14361]: https://github.com/home-assistant/home-assistant/pull/14361
|
||||
[#14363]: https://github.com/home-assistant/home-assistant/pull/14363
|
||||
[#14365]: https://github.com/home-assistant/home-assistant/pull/14365
|
||||
[#14368]: https://github.com/home-assistant/home-assistant/pull/14368
|
||||
[#14371]: https://github.com/home-assistant/home-assistant/pull/14371
|
||||
[#14372]: https://github.com/home-assistant/home-assistant/pull/14372
|
||||
[#14375]: https://github.com/home-assistant/home-assistant/pull/14375
|
||||
[#14376]: https://github.com/home-assistant/home-assistant/pull/14376
|
||||
[#14377]: https://github.com/home-assistant/home-assistant/pull/14377
|
||||
[#14380]: https://github.com/home-assistant/home-assistant/pull/14380
|
||||
[#14385]: https://github.com/home-assistant/home-assistant/pull/14385
|
||||
[#14389]: https://github.com/home-assistant/home-assistant/pull/14389
|
||||
[#14393]: https://github.com/home-assistant/home-assistant/pull/14393
|
||||
[#14395]: https://github.com/home-assistant/home-assistant/pull/14395
|
||||
[#14398]: https://github.com/home-assistant/home-assistant/pull/14398
|
||||
[#14401]: https://github.com/home-assistant/home-assistant/pull/14401
|
||||
[#14402]: https://github.com/home-assistant/home-assistant/pull/14402
|
||||
[#14408]: https://github.com/home-assistant/home-assistant/pull/14408
|
||||
[#14410]: https://github.com/home-assistant/home-assistant/pull/14410
|
||||
[#14412]: https://github.com/home-assistant/home-assistant/pull/14412
|
||||
[#14414]: https://github.com/home-assistant/home-assistant/pull/14414
|
||||
[#14416]: https://github.com/home-assistant/home-assistant/pull/14416
|
||||
[#14421]: https://github.com/home-assistant/home-assistant/pull/14421
|
||||
[#14422]: https://github.com/home-assistant/home-assistant/pull/14422
|
||||
[#14423]: https://github.com/home-assistant/home-assistant/pull/14423
|
||||
[#14424]: https://github.com/home-assistant/home-assistant/pull/14424
|
||||
[#14431]: https://github.com/home-assistant/home-assistant/pull/14431
|
||||
[#14432]: https://github.com/home-assistant/home-assistant/pull/14432
|
||||
[#14433]: https://github.com/home-assistant/home-assistant/pull/14433
|
||||
[#14434]: https://github.com/home-assistant/home-assistant/pull/14434
|
||||
[#14436]: https://github.com/home-assistant/home-assistant/pull/14436
|
||||
[#14438]: https://github.com/home-assistant/home-assistant/pull/14438
|
||||
[#14439]: https://github.com/home-assistant/home-assistant/pull/14439
|
||||
[#14441]: https://github.com/home-assistant/home-assistant/pull/14441
|
||||
[#14442]: https://github.com/home-assistant/home-assistant/pull/14442
|
||||
[#14444]: https://github.com/home-assistant/home-assistant/pull/14444
|
||||
[#14445]: https://github.com/home-assistant/home-assistant/pull/14445
|
||||
[#14447]: https://github.com/home-assistant/home-assistant/pull/14447
|
||||
[#14448]: https://github.com/home-assistant/home-assistant/pull/14448
|
||||
[#14450]: https://github.com/home-assistant/home-assistant/pull/14450
|
||||
[#14452]: https://github.com/home-assistant/home-assistant/pull/14452
|
||||
[#14454]: https://github.com/home-assistant/home-assistant/pull/14454
|
||||
[#14456]: https://github.com/home-assistant/home-assistant/pull/14456
|
||||
[#14458]: https://github.com/home-assistant/home-assistant/pull/14458
|
||||
[#14460]: https://github.com/home-assistant/home-assistant/pull/14460
|
||||
[#14465]: https://github.com/home-assistant/home-assistant/pull/14465
|
||||
[#14466]: https://github.com/home-assistant/home-assistant/pull/14466
|
||||
[#14467]: https://github.com/home-assistant/home-assistant/pull/14467
|
||||
[#14468]: https://github.com/home-assistant/home-assistant/pull/14468
|
||||
[#14471]: https://github.com/home-assistant/home-assistant/pull/14471
|
||||
[#14473]: https://github.com/home-assistant/home-assistant/pull/14473
|
||||
[#14476]: https://github.com/home-assistant/home-assistant/pull/14476
|
||||
[#14479]: https://github.com/home-assistant/home-assistant/pull/14479
|
||||
[#14481]: https://github.com/home-assistant/home-assistant/pull/14481
|
||||
[#14487]: https://github.com/home-assistant/home-assistant/pull/14487
|
||||
[#14491]: https://github.com/home-assistant/home-assistant/pull/14491
|
||||
[#14496]: https://github.com/home-assistant/home-assistant/pull/14496
|
||||
[#14497]: https://github.com/home-assistant/home-assistant/pull/14497
|
||||
[#14506]: https://github.com/home-assistant/home-assistant/pull/14506
|
||||
[#14510]: https://github.com/home-assistant/home-assistant/pull/14510
|
||||
[#14511]: https://github.com/home-assistant/home-assistant/pull/14511
|
||||
[#14520]: https://github.com/home-assistant/home-assistant/pull/14520
|
||||
[#14522]: https://github.com/home-assistant/home-assistant/pull/14522
|
||||
[#14524]: https://github.com/home-assistant/home-assistant/pull/14524
|
||||
[#14528]: https://github.com/home-assistant/home-assistant/pull/14528
|
||||
[#14536]: https://github.com/home-assistant/home-assistant/pull/14536
|
||||
[#14556]: https://github.com/home-assistant/home-assistant/pull/14556
|
||||
[#14571]: https://github.com/home-assistant/home-assistant/pull/14571
|
||||
[#14582]: https://github.com/home-assistant/home-assistant/pull/14582
|
||||
[#14614]: https://github.com/home-assistant/home-assistant/pull/14614
|
||||
[#14624]: https://github.com/home-assistant/home-assistant/pull/14624
|
||||
[#14626]: https://github.com/home-assistant/home-assistant/pull/14626
|
||||
[#14655]: https://github.com/home-assistant/home-assistant/pull/14655
|
||||
[@Chariyski]: https://github.com/Chariyski
|
||||
[@ChristianKuehnel]: https://github.com/ChristianKuehnel
|
||||
[@Kane610]: https://github.com/Kane610
|
||||
[@Klathmon]: https://github.com/Klathmon
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[@Oro]: https://github.com/Oro
|
||||
[@OverloadUT]: https://github.com/OverloadUT
|
||||
[@PhilRW]: https://github.com/PhilRW
|
||||
[@abmantis]: https://github.com/abmantis
|
||||
[@amelchio]: https://github.com/amelchio
|
||||
[@andrey-git]: https://github.com/andrey-git
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@c727]: https://github.com/c727
|
||||
[@cdce8p]: https://github.com/cdce8p
|
||||
[@damarco]: https://github.com/damarco
|
||||
[@dgomes]: https://github.com/dgomes
|
||||
[@diraimondo]: https://github.com/diraimondo
|
||||
[@dlbroadfoot]: https://github.com/dlbroadfoot
|
||||
[@evgeniy-khatko]: https://github.com/evgeniy-khatko
|
||||
[@exxamalte]: https://github.com/exxamalte
|
||||
[@fabaff]: https://github.com/fabaff
|
||||
[@gerard33]: https://github.com/gerard33
|
||||
[@hanzoh]: https://github.com/hanzoh
|
||||
[@heythisisnate]: https://github.com/heythisisnate
|
||||
[@jeradM]: https://github.com/jeradM
|
||||
[@kellerza]: https://github.com/kellerza
|
||||
[@m4dmin]: https://github.com/m4dmin
|
||||
[@mikedm139]: https://github.com/mikedm139
|
||||
[@mjg59]: https://github.com/mjg59
|
||||
[@mtreinish]: https://github.com/mtreinish
|
||||
[@mxworm]: https://github.com/mxworm
|
||||
[@n8henrie]: https://github.com/n8henrie
|
||||
[@nickw444]: https://github.com/nickw444
|
||||
[@nkaminski]: https://github.com/nkaminski
|
||||
[@nordlead2005]: https://github.com/nordlead2005
|
||||
[@oblogic7]: https://github.com/oblogic7
|
||||
[@pvizeli]: https://github.com/pvizeli
|
||||
[@rcloran]: https://github.com/rcloran
|
||||
[@robmarkcole]: https://github.com/robmarkcole
|
||||
[@rytilahti]: https://github.com/rytilahti
|
||||
[@schmittx]: https://github.com/schmittx
|
||||
[@scop]: https://github.com/scop
|
||||
[@sdague]: https://github.com/sdague
|
||||
[@snikch]: https://github.com/snikch
|
||||
[@stephanerosi]: https://github.com/stephanerosi
|
||||
[@syssi]: https://github.com/syssi
|
||||
[@teharris1]: https://github.com/teharris1
|
||||
[@thelittlefireman]: https://github.com/thelittlefireman
|
||||
[@thepotoo]: https://github.com/thepotoo
|
||||
[@tschmidty69]: https://github.com/tschmidty69
|
||||
[@w1ll1am23]: https://github.com/w1ll1am23
|
||||
[api docs]: /components/api/
|
||||
[auth docs]: /components/auth/
|
||||
[binary_sensor.bmw_connected_drive docs]: /components/binary_sensor.bmw_connected_drive/
|
||||
[binary_sensor.homematicip_cloud docs]: /components/binary_sensor.homematicip_cloud/
|
||||
[binary_sensor.isy994 docs]: /components/binary_sensor.isy994/
|
||||
[binary_sensor.konnected docs]: /components/binary_sensor.konnected/
|
||||
[binary_sensor.mychevy docs]: /components/binary_sensor.mychevy/
|
||||
[binary_sensor.xiaomi_aqara docs]: /components/binary_sensor.xiaomi_aqara/
|
||||
[binary_sensor.zha docs]: /components/binary_sensor.zha/
|
||||
[bmw_connected_drive docs]: /components/bmw_connected_drive/
|
||||
[camera docs]: /components/camera/
|
||||
[camera.familyhub docs]: /components/camera.familyhub/
|
||||
[camera.generic docs]: /components/camera.generic/
|
||||
[climate.mysensors docs]: /components/climate.mysensors/
|
||||
[climate.sensibo docs]: /components/climate.sensibo/
|
||||
[climate.venstar docs]: /components/climate.venstar/
|
||||
[climate.wink docs]: /components/climate.wink/
|
||||
[cover.gogogate2 docs]: /components/cover.gogogate2/
|
||||
[cover.mysensors docs]: /components/cover.mysensors/
|
||||
[cover.tahoma docs]: /components/cover.tahoma/
|
||||
[deconz docs]: /components/deconz/
|
||||
[device_tracker docs]: /components/device_tracker/
|
||||
[eufy docs]: /components/eufy/
|
||||
[fan.template docs]: /components/fan.template/
|
||||
[feedreader docs]: /components/feedreader/
|
||||
[folder_watcher docs]: /components/folder_watcher/
|
||||
[frontend docs]: /components/frontend/
|
||||
[hassio docs]: /components/hassio/
|
||||
[homekit docs]: /components/homekit/
|
||||
[homematic docs]: /components/homematic/
|
||||
[homematicip_cloud docs]: /components/homematicip_cloud/
|
||||
[http docs]: /components/http/
|
||||
[image_processing.facebox docs]: /components/image_processing.facebox/
|
||||
[insteon_plm docs]: /components/insteon_plm/
|
||||
[iota docs]: /components/iota/
|
||||
[isy994 docs]: /components/isy994/
|
||||
[konnected docs]: /components/konnected/
|
||||
[light.flux_led docs]: /components/light.flux_led/
|
||||
[light.homematicip_cloud docs]: /components/light.homematicip_cloud/
|
||||
[light.limitlessled docs]: /components/light.limitlessled/
|
||||
[light.mqtt docs]: /components/light.mqtt/
|
||||
[light.mysensors docs]: /components/light.mysensors/
|
||||
[light.nanoleaf_aurora docs]: /components/light.nanoleaf_aurora/
|
||||
[light.wink docs]: /components/light.wink/
|
||||
[media_extractor docs]: /components/media_extractor/
|
||||
[media_player.cmus docs]: /components/media_player.cmus/
|
||||
[media_player.onkyo docs]: /components/media_player.onkyo/
|
||||
[media_player.roku docs]: /components/media_player.roku/
|
||||
[media_player.songpal docs]: /components/media_player.songpal/
|
||||
[media_player.sonos docs]: /components/media_player.sonos/
|
||||
[media_player.universal docs]: /components/media_player.universal/
|
||||
[media_player.yamaha docs]: /components/media_player.yamaha/
|
||||
[mychevy docs]: /components/mychevy/
|
||||
[mysensors docs]: /components/mysensors/
|
||||
[notify docs]: /components/notify/
|
||||
[qwikswitch docs]: /components/qwikswitch/
|
||||
[sabnzbd docs]: /components/sabnzbd/
|
||||
[sensor.bmw_connected_drive docs]: /components/sensor.bmw_connected_drive/
|
||||
[sensor.bom docs]: /components/sensor.bom/
|
||||
[sensor.buienradar docs]: /components/sensor.buienradar/
|
||||
[sensor.darksky docs]: /components/sensor.darksky/
|
||||
[sensor.fints docs]: /components/sensor.fints/
|
||||
[sensor.hive docs]: /components/sensor.hive/
|
||||
[sensor.iota docs]: /components/sensor.iota/
|
||||
[sensor.mychevy docs]: /components/sensor.mychevy/
|
||||
[sensor.rest docs]: /components/sensor.rest/
|
||||
[sensor.sabnzbd docs]: /components/sensor.sabnzbd/
|
||||
[sensor.sigfox docs]: /components/sensor.sigfox/
|
||||
[sensor.simulated docs]: /components/sensor.simulated/
|
||||
[sensor.skybeacon docs]: /components/sensor.skybeacon/
|
||||
[sensor.statistics docs]: /components/sensor.statistics/
|
||||
[sensor.waze_travel_time docs]: /components/sensor.waze_travel_time/
|
||||
[sensor.zha docs]: /components/sensor.zha/
|
||||
[shell_command docs]: /components/shell_command/
|
||||
[snips docs]: /components/snips/
|
||||
[spaceapi docs]: /components/spaceapi/
|
||||
[switch.arest docs]: /components/switch.arest/
|
||||
[switch.flux docs]: /components/switch.flux/
|
||||
[switch.homematicip_cloud docs]: /components/switch.homematicip_cloud/
|
||||
[switch.konnected docs]: /components/switch.konnected/
|
||||
[switch.mqtt docs]: /components/switch.mqtt/
|
||||
[switch.mysensors docs]: /components/switch.mysensors/
|
||||
[switch.rainmachine docs]: /components/switch.rainmachine/
|
||||
[switch.tahoma docs]: /components/switch.tahoma/
|
||||
[system_log docs]: /components/system_log/
|
||||
[tahoma docs]: /components/tahoma/
|
||||
[telegram_bot docs]: /components/telegram_bot/
|
||||
[tts docs]: /components/tts/
|
||||
[updater docs]: /components/updater/
|
||||
[weather.bom docs]: /components/weather.bom/
|
||||
[websocket_api docs]: /components/websocket_api/
|
||||
[xiaomi_aqara docs]: /components/xiaomi_aqara/
|
||||
[zha docs]: /components/zha/
|
||||
[zwave docs]: /components/zwave/
|
||||
@ -31,6 +31,7 @@ Have you found an issue in your Home Assistant installation? Please report it. R
|
||||
|
||||
### {% linkable_title Videos, talks, workshops and alike %}
|
||||
|
||||
- [Automate your home with Home Assistant](https://www.youtube.com/watch?v=SSrgi4iHGbs) at [foss-north 2018](http://foss-north.se/2018/speakers-and-talks.html#jparadies) - March 2018
|
||||
- [Home Assistant](https://github.com/home-assistant/home-assistant-assets/tree/master/english/2017-qecampX) at QECampX 2017 - October 2017
|
||||
- [Open Source Heimautomation mit Home Assistant](https://github.com/home-assistant/home-assistant-assets/tree/master/german/2017-maker-faire-zurich) at [Mini Maker Faire Zurich 2017](https://www.makerfairezurich.ch/en/) - September 2017
|
||||
- [Why we can't have the Internet of Nice Things: A home automation primer](https://www.openwest.org/custom/description.php?id=92) at [OpenWest 2017](https://www.openwest.org) - July 2017
|
||||
|
||||
BIN
source/images/supported_brands/familyhub.png
Normal file
BIN
source/images/supported_brands/familyhub.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 28 KiB |
BIN
source/images/supported_brands/konnected.png
Normal file
BIN
source/images/supported_brands/konnected.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
source/images/supported_brands/machine-box.png
Normal file
BIN
source/images/supported_brands/machine-box.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.3 KiB |
BIN
source/images/supported_brands/spaceapi.png
Normal file
BIN
source/images/supported_brands/spaceapi.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 8.8 KiB |
Loading…
x
Reference in New Issue
Block a user