jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-23 09:17:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2020-05-25 15:24:27 +02:00
commit d838b8b9ec
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
21 changed files with 201 additions and 76 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
_config.yml
View File

@ -101,8 +101,8 @@ social:
# Home Assistant release details
current_major_version: 0
current_minor_version: 110
current_patch_version: 0
date_released: 2020-05-20
current_patch_version: 2
date_released: 2020-05-24
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

10
source/_docs/automation/editor.markdown
View File

@ -33,6 +33,16 @@ As "Service Data" we want a simple text that is shown as part of the notificatio
}
```
The Automation Editor does not currently support **data_template** as a "Service Data" entry. For these actions, it will be necessary to edit as YAML. This can be achieved by clicking the menu (3 vertical dots) and selecting "Edit as YAML"
```yaml
# Example of how to use data_template in the Automation Editor, using "Edit as YAML"
data_template:
message: >
Paulus just changed from {{ trigger.from_state.state }}
to {{ trigger.to_state.state }}
```
Don't forget to save your new automation rule. For your saved automation rule to come into effect, you will need to go to the **Configuration** page and click on **Reload Automation**.
## Updating your configuration to use the editor

2
source/_docs/configuration/basic.markdown
View File

@ -23,6 +23,8 @@ homeassistant:
- /tmp
```
NOTE: You will not be able to edit anything in Configuration -> General in the UI if you are using YAML configuration for any of the following: name, latitude, longitute, elevation, unit_system, temperature_unit, time_zone, external_url, internal_url.
{% configuration %}
name:
description: Name of the location where Home Assistant is running.

7
source/_docs/installation/docker.markdown
View File

@ -246,6 +246,13 @@ To restart Home Assistant when you have changed configuration:
docker-compose restart
```
To update your docker-compose image to the latest version and restart:
```bash
docker-compose pull
docker-compose up -d --build homeassistant
```
## Exposing Devices
In order to use Z-Wave, Zigbee or other integrations that require access to devices, you need to map the appropriate device into the container. Ensure the user that is running the container has the correct privileges to access the `/dev/tty*` file, then add the device mapping to your Docker command:

8
source/_docs/installation/updating.markdown
View File

@ -24,16 +24,16 @@ The default way to update Home Assistant to the latest release, when available,
pip3 install --upgrade homeassistant
```
For a Docker container, simply pull the latest one:
For a Docker container, simply pull the latest stable one:
```bash
sudo docker pull homeassistant/home-assistant:latest
sudo docker pull homeassistant/home-assistant:stable
```
For a Raspberry Pi Docker container, simply pull the latest one:
For a Raspberry Pi Docker container, simply pull the latest stable one:
```bash
sudo docker pull homeassistant/raspberrypi3-homeassistant:latest
sudo docker pull homeassistant/raspberrypi3-homeassistant:stable
```
After updating, you must start/restart Home Assistant for the changes to take effect. This means that you will have to restart `hass` itself or the [autostarting](/docs/autostart/) daemon (if applicable). Startup can take a considerable amount of time (i.e., minutes) depending on your device. This is because all requirements are updated as well.

3
source/_integrations/alarm_control_panel.xiaomi_miio.markdown
View File

@ -1,11 +1,10 @@
---
title: "Xiaomi Gateway Alarm"
description: "Instructions on how to integrate your Xiaomi Gateway Alarm within Home Assistant."
logo: xiaomi.png
ha_category:
- Alarm
ha_iot_class: Local Polling
ha_release: 0.110
ha_release: '0.110'
ha_domain: xiaomi_miio
---

2
source/_integrations/ampio.markdown
View File

@ -9,7 +9,7 @@ ha_iot_class: Cloud Polling
ha_domain: ampio
---
The `ampio` air quality platform will query the open data API of [ampio.pl](http://smog1.ampio.pl:3050/) to monitor air quality sensor station.
The `ampio` air quality platform will query the open data API of [ampio.pl](http://smog.ampio.pl/) to monitor air quality sensor station.
## Setup

7
source/_integrations/broadlink.markdown
View File

@ -363,11 +363,6 @@ timeout:
description: Timeout in seconds for the connection to the device.
required: false
type: integer
retry:
description: Retry times for fetch data if failed.
required: false
type: integer
default: 2
friendly_name:
description: The name used to display the switch in the frontend.
required: false
@ -435,7 +430,6 @@ switch:
host: 192.168.1.2
mac: 'B4:43:0D:CC:0F:58'
timeout: 15
retry: 5
switches:
# Will work on most Phillips TVs:
tv_phillips:
@ -483,7 +477,6 @@ switch:
host: IP_ADDRESS
mac: 'MAC_ADDRESS'
type: sp2
retry: 5
friendly_name: 'Humidifier'
```

18
source/_integrations/bsblan.markdown
View File

@ -3,19 +3,19 @@ title: BSB-Lan
description: Instructions on how to integrate BSBLan device into Home Assistant.
logo: bsblan.png
ha_category: Climate
ha_release: '0.110'
ha_release: "0.110"
ha_iot_class: Local Polling
ha_config_flow: true
ha_codeowners:
- '@liudger'
- "@liudger"
ha_domain: bsblan
---
This integration integrates [BSBLan](https://github.com/fredlcore/bsb_lan) device into Home Assistant.
BSBLan is a device that is made by `Frederik Holst` and `Ulf Diekmann` for documentation and with
BSBLan is a device that is made by `Frederik Holst` and `Ulf Dieckmann` for documentation and with
the help of many other contributors.
The board is designed for an Arduino Mega 2560 with an Ethernet-Shield for web-based controlling
The new board v3 is designed for an Arduino Due with an Ethernet-Shield for web-based controlling
of heating systems such as `Elco Thision`, `Brötje` and similar systems.
It can interface with the heating system over Boiler-System-Bus, Local Process Bus and PPS (Punkt-zu-Punkt Schnittstelle)
@ -38,7 +38,11 @@ After completing the configuration flow, the BSBLan Climate integration will be
available.
For more documentation of the BSBLan device, check the [manual](https://1coderookie.github.io/BSB-LPB-LAN_EN/).
The device support quite a few controllers from different manufacturers.
[list of supported models](https://1coderookie.github.io/BSB-LPB-LAN_EN/chap03.html#313-other-manufacturers)
The integration is tested with firmware latest stable version `v0.43`.
To see a more detailed listing of the reported systems which are successfully used with BSB-LAN please follow the corresponding link:
- [`Brötje`](https://1coderookie.github.io/BSB-LPB-LAN_EN/chap03.html#311-broetje)
- [`Elco`](https://1coderookie.github.io/BSB-LPB-LAN_EN/chap03.html#312-elco)
- [`Other Manufacturers (e.g. Fujitsu, Atlantic, Weishaupt)`](https://1coderookie.github.io/BSB-LPB-LAN_EN/chap03.html#313-other-manufacturers)
The integration is tested with firmware the stable version `v0.43`.

1
source/_integrations/deconz.markdown
View File

@ -156,6 +156,7 @@ Currently supported devices as device triggers:
- Aqara Round Switch
- Aqara Square Switch
- Aqara Magic Cube
- Aqara Opple 2/4/6 button Switches
#### Requesting support for new device trigger

6
source/_integrations/denonavr.markdown
View File

@ -11,10 +11,11 @@ ha_codeowners:
- '@starkillerOG'
---
The `denonavr` platform allows you to control [Denon Network Receivers](https://www.denon.co.uk/chg/product/compactsystems/networkmusicsystems/ceolpiccolo) from Home Assistant. It might be that your device is supported by the [Denon] platform.
The `denonavr` platform allows you to control [Denon Network Receivers](https://www.denon.com/en-gb/shop/networkmusicsystem/ceolpiccolon4) from Home Assistant. It might be that your device is supported by the [Denon] platform.
Known supported devices:
- Denon AVR-X1000
- Denon AVR-X1200W
- Denon AVR-X1300W
- Denon AVR-X1500H
@ -109,7 +110,8 @@ A few notes:
#### Service `denonavr.get_command`
Generic commands are supported, in particular, any command supported by the telnet protocol can be sent to `/goform/formiPhoneAppDirect.xml`, e.g., `/goform/formiPhoneAppDirect.xml?VSMONI2` to switch HDMI outputs on supported receivers. IR remote codes can also be sent to this endpoint, e.g., "/goform/formiPhoneAppDirect.xml?RCKSK0410370" as a mute toggle. A comprehensive list of telnet protocol commands is available at <https://ca.denon.com/ca/product/hometheater/receivers/avrx4400h?docname=AVR-X6400H_X4400H_X3400H_X2400H_X1400H_S930H_S730H_PROTOCOL_V01.xlsx> and a full list of IR codes at <http://www.denon-hifi.nl/uk/product/hometheater/avreceivers/avr3313?docname=AVR3313_IR_CODE_V01.pdf>
Generic commands are supported, in particular, any command supported by the telnet protocol can be sent to `/goform/formiPhoneAppDirect.xml`, e.g., `/goform/formiPhoneAppDirect.xml?VSMONI2` to switch HDMI outputs on supported receivers. IR remote codes can also be sent to this endpoint, e.g., "/goform/formiPhoneAppDirect.xml?RCKSK0410370" as a mute toggle.
A comprehensive list of telnet protocol commands is [also available](http://assets.denon.com/_layouts/15/xlviewer.aspx?id=/DocumentMaster/us/AVR-X6400H_X4400H_X3400H_X2400H_X1400H_S930H_S730H_PROTOCOL_V01.xlsx) and so is a [full list of IR codes](http://assets.denon.com/DocumentMaster/UK/AVR3313_IR_CODE_V01.pdf)
| Service data attribute | Optional | Description |
| ---------------------- | -------- | ---------------------------------------------------- |

42
source/_integrations/ecobee.markdown
View File

@ -72,15 +72,7 @@ api_key:
<img src='{{site_root}}/images/screenshots/ecobee-thermostat-card.png' />
</p>
[Restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. In the **Configuration** > **Integrations** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the App per the Integration menu instructions above.
The first time you (re)run Home Assistant with this integration it will give you a PIN code that you need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by clicking **Add Application** in the **My Apps** section in the sidebar.
The PIN can be found in the Home Assistant portal on the ecobee card or from the `configurator.ecobee` entity in the States developer tool.
- If you do not have an ecobee card, you may be using groups with `default_view` that don't show the card. To get around this, you can temporarily comment out the `default_view` section or add the `configurator.ecobee` integration to your `default_view` and restart Home Assistant.
Once you enter the PIN on the ecobee site, wait approximately 5 minutes, and then click on the **I have authorized the app** link at the bottom of the ecobee pop-up window. If everything worked correctly, you should now be able to restart Home Assistant again to see the full ecobee card with all of the sensors populated or see the list of sensors in the developer tools. Now you can re-enable your `default_view` (if you had to disable it) and add the ecobee sensors to a group and/or view.
[Restart Home Assistant](/docs/configuration/#reloading-changes) for the changes to take effect. In the **Configuration** > **Integrations** menu, hit **Configure** next to the discovered `ecobee` entry, and continue to authorize the App per the Integration menu instructions above, starting at step 2.
## Notifications
@ -111,37 +103,17 @@ To use notifications, please see the [getting started with automation page](/get
The ecobee thermostat supports the following key concepts.
The _target temperature_ is the temperature that the device attempts
to achieve. The target temperature is either determined by the
currently active climate or it may be overridden by a hold. When the
thermostat is not in auto mode, there is a single target
temperature. When the thermostat is in auto HVAC mode, there is a
pair of target temperatures: the lower target temperature determines
the lowest desired temperature, while the higher target temperature
determines the highest desired temperature (the thermostat will switch
between heating and cooling to keep the temperature within these
limits).
The _target temperature_ is the temperature that the device attempts to achieve. The target temperature is either determined by the currently active climate or it may be overridden by a hold. When the
thermostat is not in auto mode, there is a single target temperature. When the thermostat is in auto HVAC mode, there is a pair of target temperatures: the lower target temperature determines the lowest desired temperature, while the higher target temperature determines the highest desired temperature (the thermostat will switch between heating and cooling to keep the temperature within these limits).
A _climate_ is a predefined or user-defined set of presets that the
thermostat aims to achieve. The ecobee thermostat provides three predefined
climates: Home, Away, and Sleep. Ecobee refers to these as _comfort settings_. The user can define additional climates.
A _climate_ is a predefined or user-defined set of presets that the thermostat aims to achieve. The ecobee thermostat provides three predefined climates: Home, Away, and Sleep. Ecobee refers to these as _comfort settings_. The user can define additional climates.
A _preset_ is an override of the target temperature defined in the
currently active climate. The temperature targeted in the preset mode may be
explicitly set (temperature preset), it may be derived from a reference
climate (home, away, sleep, etc.), or it may be derived from a vacation
defined by the thermostat. All holds are temporary. Temperature and
climate holds expire when the thermostat transitions to the next climate
defined in its program. A vacation hold starts at the beginning of the
A _preset_ is an override of the target temperature defined in the currently active climate. The temperature targeted in the preset mode may be explicitly set (temperature preset), it may be derived from a reference climate (home, away, sleep, etc.), or it may be derived from a vacation defined by the thermostat. All holds are temporary. Temperature and climate holds expire when the thermostat transitions to the next climate defined in its program. A vacation hold starts at the beginning of the
defined vacation period and expires when the vacation period ends.
When in _away preset_, the target temperature is permanently overridden by
the target temperature defined for the away climate. The away preset is a
simple way to emulate a vacation mode.
When in _away preset_, the target temperature is permanently overridden by the target temperature defined for the away climate. The away preset is a simple way to emulate a vacation mode.
The _HVAC mode_ of the device is the currently active operational
modes that the ecobee thermostat provides: heat, auxHeatOnly, cool,
auto, and off.
The _HVAC mode_ of the device is the currently active operational modes that the ecobee thermostat provides: heat, auxHeatOnly, cool, auto, and off.
## Attributes

3
source/_integrations/manual.markdown
View File

@ -74,7 +74,7 @@ armed_custom_bypass/armed_home/armed_away/armed_night/disarmed/triggered:
required: false
type: integer
arming_time:
description: State specific setting for **arming_time** (all states except **disarmed**)
description: State specific setting for **arming_time** (all states except **disarmed** and **triggered**)
required: false
type: integer
trigger_time:
@ -134,7 +134,6 @@ alarm_control_panel:
- platform: manual
name: Home Alarm
code: '1234'
pending_time: 30
arming_time: 30
delay_time: 20
trigger_time: 4

2
source/_integrations/mqtt.markdown
View File

@ -29,7 +29,7 @@ mqtt:
broker: IP_ADDRESS_BROKER
```
You can also use the [embedded MQTT broker](/docs/mqtt/broker#embedded-broker). A separate broker is advised for more stability.
You can also use the [embedded MQTT broker](/docs/mqtt/broker#embedded-broker-deprecated). A separate broker is advised for more stability.
<div class='note warning'>
As of release 0.92, the embedded broker has been marked as deprecated. This means bugs may not be fixed, and the broker functionality will be removed in a future release.

4
source/_integrations/onvif.markdown
View File

@ -20,6 +20,10 @@ Home Assistant offers ONVIF integration through **Configuration** -> **Integrati
It is recommended that you create a user on your device specifically for Home Assistant. For all current functionality, it is enough to create a standard user.
</div>
<div class='note'>
If running Home Asssistant Core in a venv, ensure that libxml2 and libxslt python interfaces are installed via your package manager.
</div>
### Configuration Notes
Most of the ONVIF devices support more than one audio/video profile. Each profile provides different image quality, or in the case of an NVR, separate connected cameras. This integration will add entities for all compatible profiles with the video encoding set to H254. Usually, the first profile has the highest quality and it is the profile used by default. However, you may want to use a lower quality image. You may disable unwanted entities through the Home Assistant UI.

2
source/_integrations/ozw.markdown
View File

@ -19,7 +19,7 @@ This integration allows you to utilize OpenZWave's ozwdaemon to control a Z-Wave
- MQTT server and the [MQTT integration](/integrations/mqtt/) set up in Home Assistant.
- The [ozwdaemon](https://github.com/OpenZWave/qt-openzwave) installed and running in your network.
For Home Assistant Supervisor there's a [custom add-on](https://github.com/marcelveldt/hassio-addons-repo/tree/master/ozwdaemon).
For Home Assistant Supervisor there's an official add-on named OpenZWave available from the add-on store.
- Supported Z-Wave dongle compatible with OpenZWave 1.6. See this [list](/docs/z-wave/controllers/#supported-z-wave-usb-sticks--hardware-modules) of controllers. The Z-Wave controller dongle should be connected to the same host as where the ozwdaemon is running.
## Configuration

8
source/_integrations/synology_dsm.markdown
View File

@ -74,18 +74,14 @@ This sensor will wake up your Synology NAS if it's in hibernation mode.
</div>
You can change the scan interal within the configuration options (default is 15 min).
## Separate User Configuration
Due to the nature of the Synology DSM API, it is required to grant the user admin rights. This is related to the fact that utilization information is stored in the core module.
When creating the user, it is possible to deny access to all locations and applications. By doing this, the user will not be able to login to the web interface or view any of the files on the Synology NAS. It is still able to read the utilization and storage information using the API.
<div class='note warning'>
The Home Assistant integration doesn't support two-factor authentication for Synology DSM accounts. Use a strong, randomly generated password to improve security.
</div>
## Created sensors

4
source/_integrations/ubus.markdown
View File

@ -21,7 +21,7 @@ For OpenWrt version 18.06.x the package uhttpd-mod-ubus should also be installed
opkg install uhttpd-mod-ubus
```
And create a read-only user to be used by setting up the ACL file `/usr/share/rpcd/acl.d/user.json`.
And create on your OpenWrt device a read-only user to be used by setting up the ACL file `/usr/share/rpcd/acl.d/user.json`.
```json
{
@ -38,7 +38,7 @@ And create a read-only user to be used by setting up the ACL file `/usr/share/rp
}
```
Restart the services.
Restart the services. This ACL file needs to be recreated after updating/upgrading your OpenWrt firmware.
```bash
# /etc/init.d/rpcd restart && /etc/init.d/uhttpd restart

11
source/_lovelace/picture-elements.markdown
View File

@ -19,9 +19,18 @@ type:
description: picture-elements
type: string
image:
required: true
required: false
description: The URL of an image.<br/>To use a locally hosted image, see [Hosting](/integrations/http#hosting-files).
type: string
camera_image:
required: false
description: A camera entity.
type: string
camera_view:
required: false
description: '"live" will show the live view if `stream` is enabled.'
default: auto
type: string
elements:
required: true
description: List of elements

131
source/_posts/2020-05-20-release-110.markdown
View File

@ -463,7 +463,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
- **HTTP** - `base_url` is deprecated and replaced by an `internal_url` and
`external_url` core configuration setting. -
([@frenck] - [#35224]) ([config docs]) ([http docs])
([@frenck] - [#35224]) ([basic config docs]) ([http docs])
- **Kodi** - Kodi previously reported the media content type for all PVR
channels as "channel", no matter if it was a TV or a radio channel.
@ -499,7 +499,11 @@ Experiencing issues introduced by this release? Please report them in our [issue
but the only supported entries are `username`, `password`, and `scan_interval`.
All other entries must be removed; otherwise, the integration will not be
configured. - ([@fronzbot] - [#35396]) ([blink docs])
- **Emulated Hue** - Emulated Hue was updated for better compatibility with newer
systems. Existing users may find that they will need to re-pair their system with
emulated hue to reconnect devices. - ([@Tho85] - [#35148]) ([emulated_hue docs])
- **Universal Devices ISY994** - This migrates ISY994 to PyISY v2 and is now
available to be added from the Integrations UI. PyISY Version 2 is a
significant update to the original module used to communicate with the ISY.
@ -583,6 +587,128 @@ Experiencing issues introduced by this release? Please report them in our [issue
</details>
## Release 0.110.1 - May 21
- Fix Delijn sensor naming ([@Emilv2] - [#35789]) ([delijn docs])
- Handle None received from pyforked-daapd ([@uvjustin] - [#35830]) ([forked_daapd docs])
- Fix Daikin duplicate entries ([@fredrike] - [#35833]) ([daikin docs])
- Homekit should skip devices that are missing in device registry ([@bdraco] - [#35857]) ([homekit docs])
- Updated frontend to 20200519.1 ([@bramkragten] - [#35877]) ([frontend docs])
- Fix light profiles for HomeMatic lights ([@danielperna84] - [#35882]) ([homematic docs])
- fix mjpeg issue along with some cameras not returning event capabilities properly ([@hunterjm] - [#35885]) ([onvif docs])
- Ensure http can startup if homekit fails to load ([@bdraco] - [#35888]) ([logbook docs])
- Ensure storage write consume the data under the lock ([@bdraco] - [#35889])
- Fix legacy Hunter Douglas PowerView devices ([@bdraco] - [#35895]) ([hunterdouglas_powerview docs])
[#35789]: https://github.com/home-assistant/core/pull/35789
[#35830]: https://github.com/home-assistant/core/pull/35830
[#35833]: https://github.com/home-assistant/core/pull/35833
[#35857]: https://github.com/home-assistant/core/pull/35857
[#35877]: https://github.com/home-assistant/core/pull/35877
[#35882]: https://github.com/home-assistant/core/pull/35882
[#35885]: https://github.com/home-assistant/core/pull/35885
[#35888]: https://github.com/home-assistant/core/pull/35888
[#35889]: https://github.com/home-assistant/core/pull/35889
[#35895]: https://github.com/home-assistant/core/pull/35895
[@Emilv2]: https://github.com/Emilv2
[@bdraco]: https://github.com/bdraco
[@bramkragten]: https://github.com/bramkragten
[@danielperna84]: https://github.com/danielperna84
[@fredrike]: https://github.com/fredrike
[@hunterjm]: https://github.com/hunterjm
[@uvjustin]: https://github.com/uvjustin
[daikin docs]: /integrations/daikin/
[delijn docs]: /integrations/delijn/
[forked_daapd docs]: /integrations/forked_daapd/
[frontend docs]: /integrations/frontend/
[homekit docs]: /integrations/homekit/
[homematic docs]: /integrations/homematic/
[hunterdouglas_powerview docs]: /integrations/hunterdouglas_powerview/
[logbook docs]: /integrations/logbook/
[onvif docs]: /integrations/onvif/
## Release 0.110.2 - May 24
- Auto-level AirVisual API calls ([@bachya] - [#34903]) ([airvisual docs])
- Fix service registration supported features check ([@chmielowiec] - [#35718])
- Fix Prezzibenzina doing I/O in the event loop ([@bachya] - [#35881]) ([prezzibenzina docs])
- Update rokuecp to 0.4.1 ([@ctalkington] - [#35899]) ([roku docs])
- Update frontend to 20200519.3 ([@bramkragten] - [#35925]) ([frontend docs])
- Ensure homekit functions if numpy is unavailable ([@bdraco] - [#35931]) ([homekit docs])
- Fix ONVIF Transport ([@hunterjm] - [#35932]) ([onvif docs])
- Fix typo in conf[CONF_SSL] ([@Wohlraj] - [#35946]) ([zabbix docs])
- Fix Daikin AC integration for AirBase units ([@fredrike] - [#35952]) ([daikin docs])
- Improve ipp unique id parsing ([@ctalkington] - [#35959]) ([ipp docs])
- Bump pyAV and close unclosed outputs ([@hunterjm] - [#35960]) ([stream docs])
- Fix lutron_caseta setup options ([@MartinHjelmare] - [#35974]) ([lutron_caseta docs])
- Fix device_registry cleanup behavior ([@alengwenus] - [#35977])
- Bump python-openzwave-mqtt to 1.0.2 ([@MartinHjelmare] - [#35980]) ([ozw docs])
- Handle StorageError in the Broadlink integration ([@felipediel] - [#35986]) ([broadlink docs])
- Update frontend to 20200519.4 ([@bramkragten] - [#35987]) ([frontend docs])
- Fix ONVIF PTZ and profile encoding issues ([@hunterjm] - [#36006]) ([onvif docs])
- Upgrade hass-nabucasa to 0.34.3 ([@frenck] - [#36025]) ([cloud docs])
- Migrate rpi_gpio_pwm to extend LightEntity instead of Light ([@soldag] - [#36028]) ([rpi_gpio_pwm docs])
- Fix shade compatibility with hunter douglas powerview 1.0 hubs ([@bdraco] - [#36040]) ([hunterdouglas_powerview docs])
- Bump aiohomekit ([@Jc2k] - [#36041]) ([homekit_controller docs])
- Bump tellduslive version ([@fredrike] - [#36048]) ([tellduslive docs])
- Fix roku play/pause support ([@ctalkington] - [#35991]) ([roku docs])
[#34903]: https://github.com/home-assistant/core/pull/34903
[#35718]: https://github.com/home-assistant/core/pull/35718
[#35881]: https://github.com/home-assistant/core/pull/35881
[#35899]: https://github.com/home-assistant/core/pull/35899
[#35925]: https://github.com/home-assistant/core/pull/35925
[#35931]: https://github.com/home-assistant/core/pull/35931
[#35932]: https://github.com/home-assistant/core/pull/35932
[#35946]: https://github.com/home-assistant/core/pull/35946
[#35952]: https://github.com/home-assistant/core/pull/35952
[#35959]: https://github.com/home-assistant/core/pull/35959
[#35960]: https://github.com/home-assistant/core/pull/35960
[#35974]: https://github.com/home-assistant/core/pull/35974
[#35977]: https://github.com/home-assistant/core/pull/35977
[#35980]: https://github.com/home-assistant/core/pull/35980
[#35986]: https://github.com/home-assistant/core/pull/35986
[#35987]: https://github.com/home-assistant/core/pull/35987
[#35991]: https://github.com/home-assistant/core/pull/35991
[#36006]: https://github.com/home-assistant/core/pull/36006
[#36025]: https://github.com/home-assistant/core/pull/36025
[#36028]: https://github.com/home-assistant/core/pull/36028
[#36040]: https://github.com/home-assistant/core/pull/36040
[#36041]: https://github.com/home-assistant/core/pull/36041
[#36048]: https://github.com/home-assistant/core/pull/36048
[@Jc2k]: https://github.com/Jc2k
[@MartinHjelmare]: https://github.com/MartinHjelmare
[@Wohlraj]: https://github.com/Wohlraj
[@alengwenus]: https://github.com/alengwenus
[@bachya]: https://github.com/bachya
[@bdraco]: https://github.com/bdraco
[@bramkragten]: https://github.com/bramkragten
[@chmielowiec]: https://github.com/chmielowiec
[@ctalkington]: https://github.com/ctalkington
[@felipediel]: https://github.com/felipediel
[@fredrike]: https://github.com/fredrike
[@frenck]: https://github.com/frenck
[@hunterjm]: https://github.com/hunterjm
[@soldag]: https://github.com/soldag
[airvisual docs]: /integrations/airvisual/
[broadlink docs]: /integrations/broadlink/
[cloud docs]: /integrations/cloud/
[daikin docs]: /integrations/daikin/
[frontend docs]: /integrations/frontend/
[homekit docs]: /integrations/homekit/
[homekit_controller docs]: /integrations/homekit_controller/
[hunterdouglas_powerview docs]: /integrations/hunterdouglas_powerview/
[ipp docs]: /integrations/ipp/
[lutron_caseta docs]: /integrations/lutron_caseta/
[onvif docs]: /integrations/onvif/
[ozw docs]: /integrations/ozw/
[prezzibenzina docs]: /integrations/prezzibenzina/
[roku docs]: /integrations/roku/
[rpi_gpio_pwm docs]: /integrations/rpi_gpio_pwm/
[stream docs]: /integrations/stream/
[tellduslive docs]: /integrations/tellduslive/
[zabbix docs]: /integrations/zabbix/
## All changes
<details>
@ -1473,6 +1599,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[automatic docs]: /integrations/automatic/
[automation docs]: /integrations/automation/
[axis docs]: /integrations/axis/
[basic config docs]: /docs/configuration/basic/
[blebox docs]: /integrations/blebox/
[blink docs]: /integrations/blink/
[bluetooth_le_tracker docs]: /integrations/bluetooth_le_tracker/

2
source/help/index.markdown
View File

@ -62,7 +62,7 @@ Don't miss the regular [Home Assistant podcasts](https://hasspodcast.io/).
- [The winners of the Thomas-Krenn-Awards 2018](https://www.thomas-krenn.com/de/tkmag/allgemein/die-gewinner-des-thomas-krenn-awards-2018-stehen-fest/) - March 2018
- [Best of Open Source Smart Home: Home Assistant vs OpenHAB](https://smarthome.university/your-smart-home-platform-home-assistant-vs-openhab/) - February 2018
- [Hausautomations-Schaltzentrale Home Assistant auf Python-Basis](https://www.heise.de/ct/ausgabe/2017-26-Hausautomations-Schaltzentrale-Home-Assistant-3909532.html) - December 2017
- [Using Home Assistant the ARTIK Cloud](https://developer.artik.io/documentation/developer-guide/wireless-iot/hass.html) - September 2017
- [Using Home Assistant the ARTIK Cloud](http://web.archive.org/web/20191028191303/https://developer.artik.io/documentation/developer-guide/wireless-iot/hass.html) - September 2017
- [Control home automation hardware with Home Assistant](http://www.linux-magazine.com/Issues/2017/203/Home-Assistant) - August 2017
- [Smart Home Home Assistant KNX Alexa Sprachsteuerung](https://onesmarthome.de/smart-home-home-assistant-knx-alexa-sprachsteuerung/) - August 2017
- [Episode #122: Home Assistant: Pythonic Home Automation](https://talkpython.fm/episodes/show/122/home-assistant-pythonic-home-automation) - July 2017