@@ -297,7 +298,7 @@ source /srv/homeassistant/bin/activate
pip3 install pyodbc
```
-You will also need to install an ODBC Driver. Microsoft ODBC drivers are recommended, however FreeTDS is available for systems that are not supported by Microsoft. Instrucitons for installing the Microsoft ODBC drivers can be found [here](https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server).
+You will also need to install an ODBC Driver. Microsoft ODBC drivers are recommended, however FreeTDS is available for systems that are not supported by Microsoft. Instructions for installing the Microsoft ODBC drivers can be found [here](https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server).
diff --git a/source/_integrations/recswitch.markdown b/source/_integrations/recswitch.markdown
index 24baa51b8ac..6fb3507f046 100644
--- a/source/_integrations/recswitch.markdown
+++ b/source/_integrations/recswitch.markdown
@@ -1,7 +1,6 @@
---
title: Ankuoo REC Switch
description: Instructions on how to integrate Ankuoo REC Switch into Home Assistant.
-logo: ankuoo_recswitch.png
ha_release: 0.81
ha_category:
- Switch
diff --git a/source/_integrations/sendgrid.markdown b/source/_integrations/sendgrid.markdown
index 1f0db84fc57..24e498e2e16 100644
--- a/source/_integrations/sendgrid.markdown
+++ b/source/_integrations/sendgrid.markdown
@@ -1,7 +1,6 @@
---
title: SendGrid
description: Instructions on how to add email notifications via SendGrid to Home Assistant.
-logo: sendgrid.png
ha_category:
- Notifications
ha_release: 0.14
diff --git a/source/_integrations/sesame.markdown b/source/_integrations/sesame.markdown
index 8ec2919733c..63808979852 100644
--- a/source/_integrations/sesame.markdown
+++ b/source/_integrations/sesame.markdown
@@ -1,7 +1,6 @@
---
title: Sesame Smart Lock
description: Instructions on how to integrate Sesame by CANDY HOUSE into Home Assistant.
-logo: sesame.png
ha_category:
- Lock
ha_iot_class: Cloud Polling
diff --git a/source/_integrations/shodan.markdown b/source/_integrations/shodan.markdown
index f939242e866..b9b78d89a1a 100644
--- a/source/_integrations/shodan.markdown
+++ b/source/_integrations/shodan.markdown
@@ -4,7 +4,6 @@ description: Instructions on how to integrate Shodan sensors into Home Assistant
ha_category:
- Sensor
ha_iot_class: Cloud Polling
-logo: shodan.png
ha_release: 0.51
ha_codeowners:
- '@fabaff'
diff --git a/source/_integrations/sigfox.markdown b/source/_integrations/sigfox.markdown
index 4b76b45825c..47d07adb26c 100644
--- a/source/_integrations/sigfox.markdown
+++ b/source/_integrations/sigfox.markdown
@@ -1,7 +1,6 @@
---
title: Sigfox
description: Display messages from Sigfox devices in Home Assistant.
-logo: sigfox.png
ha_category:
- Sensor
ha_iot_class: Cloud Polling
diff --git a/source/_integrations/slide.markdown b/source/_integrations/slide.markdown
index d60705c47a7..72a30a2300a 100644
--- a/source/_integrations/slide.markdown
+++ b/source/_integrations/slide.markdown
@@ -1,7 +1,6 @@
---
title: Slide
description: Instructions on how to integrate the Innovation in Motion Slide covers with Home Assistant.
-logo: slide.png
ha_category:
- Hub
- Cover
diff --git a/source/_integrations/sma.markdown b/source/_integrations/sma.markdown
index f3932e472ec..d7299b9c562 100644
--- a/source/_integrations/sma.markdown
+++ b/source/_integrations/sma.markdown
@@ -3,7 +3,6 @@ title: SMA Solar
description: Instructions on how to connect your SMA Solar Inverter to Home Assistant.
ha_category:
- Energy
-logo: sma.png
ha_iot_class: Local Polling
ha_release: 0.36
ha_codeowners:
diff --git a/source/_integrations/snapcast.markdown b/source/_integrations/snapcast.markdown
index 1b393ef0795..fded380fb19 100644
--- a/source/_integrations/snapcast.markdown
+++ b/source/_integrations/snapcast.markdown
@@ -1,7 +1,6 @@
---
title: Snapcast
description: Instructions on how to integrate Snapcast into Home Assistant.
-logo: snapcast.png
ha_category:
- Media Player
ha_release: 0.13
diff --git a/source/_integrations/snips.markdown b/source/_integrations/snips.markdown
index b401005a4fa..76b26ed094b 100644
--- a/source/_integrations/snips.markdown
+++ b/source/_integrations/snips.markdown
@@ -1,7 +1,6 @@
---
title: Snips
description: Instructions on how to integrate Snips within Home Assistant.
-logo: snips.png
ha_category:
- Voice
ha_release: 0.48
diff --git a/source/_integrations/socialblade.markdown b/source/_integrations/socialblade.markdown
index 73cf67594c2..2f281bde3c1 100644
--- a/source/_integrations/socialblade.markdown
+++ b/source/_integrations/socialblade.markdown
@@ -1,7 +1,6 @@
---
title: Social Blade
description: Instructions on how to set up Social Blade Sensor within Home Assistant.
-logo: socialblade.png
ha_category:
- Multimedia
ha_release: 0.69
diff --git a/source/_integrations/somfy_mylink.markdown b/source/_integrations/somfy_mylink.markdown
index 586fa5d767c..05cd22c9d45 100644
--- a/source/_integrations/somfy_mylink.markdown
+++ b/source/_integrations/somfy_mylink.markdown
@@ -1,7 +1,6 @@
---
title: Somfy MyLink
description: Instructions on how to integrate Somfy MyLink devices with Home Assistant.
-logo: tahoma.png
ha_category:
- Hub
- Cover
diff --git a/source/_integrations/sony_projector.markdown b/source/_integrations/sony_projector.markdown
index 9ca5efa21ba..b8b354f03af 100644
--- a/source/_integrations/sony_projector.markdown
+++ b/source/_integrations/sony_projector.markdown
@@ -1,7 +1,6 @@
---
title: Sony Projector
description: Instructions on how to integrate Sony Projector switches into Home Assistant.
-logo: sony.png
ha_category:
- Multimedia
ha_iot_class: Local Polling
diff --git a/source/_integrations/spc.markdown b/source/_integrations/spc.markdown
index a9410db6b34..4640f749d89 100644
--- a/source/_integrations/spc.markdown
+++ b/source/_integrations/spc.markdown
@@ -6,7 +6,6 @@ ha_category:
- Alarm
- Binary Sensor
ha_release: 0.47
-logo: vanderbilt_spc.png
ha_iot_class: Local Push
ha_domain: spc
---
diff --git a/source/_integrations/speedtestdotnet.markdown b/source/_integrations/speedtestdotnet.markdown
index 87c79c7728b..feb344549ba 100644
--- a/source/_integrations/speedtestdotnet.markdown
+++ b/source/_integrations/speedtestdotnet.markdown
@@ -21,7 +21,7 @@ Most Speedtest.net servers require TCP port 8080 outbound to function. Without t
## Configuration
-For the `server_id` check the list of [available servers](http://www.speedtestserver.com).
+For the `server_id` check the list of [available servers](https://speedtest.net/speedtest-servers.php).
To add Speedtest.net sensors to your installation, add the following to your `configuration.yaml` file:
diff --git a/source/_integrations/spotify.markdown b/source/_integrations/spotify.markdown
index c42b8a43764..fb7936ca364 100644
--- a/source/_integrations/spotify.markdown
+++ b/source/_integrations/spotify.markdown
@@ -31,8 +31,8 @@ To create the required Spotify application:
- Select **Create An App**. Enter any name and description.
- Once your application is created, view it and copy your **Client ID** and **Client Secret**, which are used in the Home Assistant configuration file.
- Add a **Redirect URI** in one of the following forms:
- - If you are not using SSL: `http://
/auth/external/callback`
- - If you are using SSL: `https:///auth/external/callback`
+ - If you are not using SSL: `http://:/auth/external/callback`
+ - If you are using SSL: `https://:/auth/external/callback`
- Click **Save** after adding the URI.
If you are using an externally accessible address, you will likely also need to set the `base_url` attribute of the [HTTP Integration](/integrations/http/). This should be set using the same base URL as the redirect URI, e.g., if you used a domain name (not local IP) in the redirect, then use the same domain name in your `base_url`.
diff --git a/source/_integrations/ssdp.markdown b/source/_integrations/ssdp.markdown
index 3d7d5d2c12e..1b35eaf014b 100644
--- a/source/_integrations/ssdp.markdown
+++ b/source/_integrations/ssdp.markdown
@@ -28,4 +28,5 @@ The following integrations are automatically discovered by the SSDP integration:
- [DirecTV](/integrations/directv/)
- [Huawei LTE](../huawei_lte/)
- [Philips Hue](../hue/)
+ - [Roku](/integrations/roku/)
- [Samsung TV](../samsungtv/)
diff --git a/source/_integrations/startca.markdown b/source/_integrations/startca.markdown
index 0f7f77437f0..9b77092a6a8 100644
--- a/source/_integrations/startca.markdown
+++ b/source/_integrations/startca.markdown
@@ -1,7 +1,6 @@
---
title: Start.ca
description: Instructions on how to integrate Start.ca data usage within Home Assistant.
-logo: startca.png
ha_category:
- Network
ha_release: 0.64
diff --git a/source/_integrations/supervisord.markdown b/source/_integrations/supervisord.markdown
index d304456b01f..7ece0e19100 100644
--- a/source/_integrations/supervisord.markdown
+++ b/source/_integrations/supervisord.markdown
@@ -1,7 +1,6 @@
---
title: Supervisord
description: Instructions on how to integrate Supervisord within Home Assistant.
-logo: supervisord.png
ha_category:
- System Monitor
ha_release: '0.20'
diff --git a/source/_integrations/swisscom.markdown b/source/_integrations/swisscom.markdown
index 82a35ee8836..dc6c370a64a 100644
--- a/source/_integrations/swisscom.markdown
+++ b/source/_integrations/swisscom.markdown
@@ -1,7 +1,6 @@
---
title: Swisscom Internet-Box
description: Instructions on how to integrate Swisscom Internet-Box into Home Assistant.
-logo: swisscom.png
ha_category:
- Presence Detection
ha_release: 0.32
diff --git a/source/_integrations/tahoma.markdown b/source/_integrations/tahoma.markdown
index 1f519361f69..0ae93c45438 100644
--- a/source/_integrations/tahoma.markdown
+++ b/source/_integrations/tahoma.markdown
@@ -1,7 +1,6 @@
---
title: Tahoma
description: Instructions on how to integrate Somfy Tahoma devices with Home Assistant.
-logo: tahoma.png
ha_category:
- Hub
- Binary Sensor
diff --git a/source/_integrations/tank_utility.markdown b/source/_integrations/tank_utility.markdown
index 7a473175799..ea2f0cf9a84 100644
--- a/source/_integrations/tank_utility.markdown
+++ b/source/_integrations/tank_utility.markdown
@@ -1,7 +1,6 @@
---
title: Tank Utility
description: How to integrate Tank Utility sensors within Home Assistant.
-logo: tank_utility.png
ha_category:
- Energy
ha_release: 0.53
diff --git a/source/_integrations/tapsaff.markdown b/source/_integrations/tapsaff.markdown
index 3c9eb0d7323..455d1daf046 100644
--- a/source/_integrations/tapsaff.markdown
+++ b/source/_integrations/tapsaff.markdown
@@ -1,7 +1,6 @@
---
title: Taps Aff
description: Instructions on how to use the Taps Aff binary sensor in Home Assistant.
-logo: tapsaff.png
ha_category:
- Weather
ha_release: 0.47
diff --git a/source/_integrations/ted5000.markdown b/source/_integrations/ted5000.markdown
index 1736d429bd8..5f6ac7960a5 100644
--- a/source/_integrations/ted5000.markdown
+++ b/source/_integrations/ted5000.markdown
@@ -1,7 +1,6 @@
---
title: The Energy Detective TED5000
description: How to add a TED5000 to Home Assistant.
-logo: ted.png
ha_category:
- Energy
ha_release: '0.30'
diff --git a/source/_integrations/teksavvy.markdown b/source/_integrations/teksavvy.markdown
index cc1dc2b54a1..f5166d5456e 100644
--- a/source/_integrations/teksavvy.markdown
+++ b/source/_integrations/teksavvy.markdown
@@ -1,7 +1,6 @@
---
title: TekSavvy
description: Instructions on how to integrate TekSavvy data usage within Home Assistant.
-logo: teksavvy.png
ha_category:
- Network
ha_release: 0.62
diff --git a/source/_integrations/tellstick.markdown b/source/_integrations/tellstick.markdown
index ac421a253cb..8a197af9625 100644
--- a/source/_integrations/tellstick.markdown
+++ b/source/_integrations/tellstick.markdown
@@ -1,7 +1,6 @@
---
title: TellStick
description: Instructions on how to integrate your TellStick into Home Assistant.
-logo: telldus_tellstick.png
ha_release: pre 0.7
ha_category:
- Hub
diff --git a/source/_integrations/thermoworks_smoke.markdown b/source/_integrations/thermoworks_smoke.markdown
index af147f0fe79..751b7bcfafc 100644
--- a/source/_integrations/thermoworks_smoke.markdown
+++ b/source/_integrations/thermoworks_smoke.markdown
@@ -1,7 +1,6 @@
---
title: ThermoWorks Smoke
description: Pulls temperature data for a ThermoWorks Smoke Thermometer connected with Smoke Gateway.
-logo: thermoworks.png
ha_category:
- Sensor
ha_release: 0.81
diff --git a/source/_integrations/thingspeak.markdown b/source/_integrations/thingspeak.markdown
index 552ca382464..07b362f543f 100644
--- a/source/_integrations/thingspeak.markdown
+++ b/source/_integrations/thingspeak.markdown
@@ -1,7 +1,6 @@
---
title: ThingSpeak
description: Record one entity in ThingSpeak
-logo: thingspeak.png
ha_category:
- History
ha_release: 0.32
diff --git a/source/_integrations/thomson.markdown b/source/_integrations/thomson.markdown
index f35594df439..2b445ad7f38 100644
--- a/source/_integrations/thomson.markdown
+++ b/source/_integrations/thomson.markdown
@@ -1,7 +1,6 @@
---
title: Thomson
description: Instructions on how to integrate Thomson routers into Home Assistant.
-logo: technicolor.png
ha_category:
- Presence Detection
ha_release: 0.7
diff --git a/source/_integrations/tibber.markdown b/source/_integrations/tibber.markdown
index 27d99b63bce..2676dec5f50 100644
--- a/source/_integrations/tibber.markdown
+++ b/source/_integrations/tibber.markdown
@@ -1,7 +1,6 @@
---
title: Tibber
description: Instructions on how to integrate Tibber within Home Assistant.
-logo: tibber.png
ha_category:
- Energy
- Sensor
diff --git a/source/_integrations/tikteck.markdown b/source/_integrations/tikteck.markdown
index 90b5253671a..1816f156001 100644
--- a/source/_integrations/tikteck.markdown
+++ b/source/_integrations/tikteck.markdown
@@ -4,7 +4,6 @@ description: Instructions on how to setup Tikteck LED bulbs within Home Assistan
ha_category:
- Light
ha_iot_class: Local Polling
-logo: tikteck.png
ha_release: 0.36
ha_domain: tikteck
---
diff --git a/source/_integrations/tomato.markdown b/source/_integrations/tomato.markdown
index 9cbaabdc816..4927bfa9a60 100644
--- a/source/_integrations/tomato.markdown
+++ b/source/_integrations/tomato.markdown
@@ -7,13 +7,22 @@ ha_release: pre 0.7
ha_domain: tomato
---
-The `tomato` platform requires an extra configuration variable called `http_id`. The
-value can be obtained by logging in to the Tomato admin interface and search for
-`http_id` in the page source code.
+The `tomato` device tracker integration allows one to tracker devices which are
+connected to a wireless router that is running [Tomato](https://tomato.groov.pl/)
+as firmware.
-Because of a limitation in Tomato's API, this platform will only track wireless devices.
-If tracking wired devices like a Philips Hue Hub is necessary,
-it is possible to use another platform like [Nmap](/integrations/nmap_tracker).
+Because of a limitation in Tomato's API, this integration will only track wireless devices.
+
+It could be that the integration is also working with [AdvancedTomato](https://advancedtomato.com/)
+but this was never tested.
+
+## Setup
+
+The integration requires an extra configuration variable called `http_id`. The
+value can be obtained by logging in to the Tomato admin interface and search for
+`http_id` in the page's source code.
+
+## Configuration
To use this device tracker in your installation,
add the following to your `configuration.yaml` file:
@@ -57,7 +66,7 @@ password:
required: true
type: string
http_id:
- description: "The value can be obtained by logging in to the Tomato admin interface and search for `http_id` in the page source code."
+ description: "The value of `http_id`."
required: true
type: string
{% endconfiguration %}
@@ -65,14 +74,11 @@ http_id:
See the [device tracker integration page](/integrations/device_tracker/) for
instructions how to configure the people to be tracked.
-A description of the API s available in this
-[Tomato API](https://paulusschoutsen.nl/blog/2013/10/tomato-api-documentation/)
-blog post.
-
-SSL Certificate:
+## SSL Certificate
Gathering the SSL Certificate of your router can be accomplished with this (or
a similar) command:
+
```bash
openssl s_client -showcerts -connect 172.10.10.1:443 /dev/null | openssl x509 -outform PEM > router_cert.pem
```
diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown
index f661cea6cd7..e2e74dd6ad4 100644
--- a/source/_integrations/tplink.markdown
+++ b/source/_integrations/tplink.markdown
@@ -35,12 +35,12 @@ Plugs are type `switch` when autodiscovery has been disabled.
- HS100
- HS103
- HS105
-- HS110 (This device is capable or reporting energy usage data to template sensors)
+- HS110 (This device is capable of reporting energy usage data to template sensors)
### Strip (Multi-Plug)
- HS107 (indoor 2-outlet)
-- HS300 (powerstrip 6-outlet) (This device is capable or reporting energy usage data to template sensors)
+- HS300 (powerstrip 6-outlet) (This device is capable of reporting energy usage data to template sensors)
- KP303 (powerstrip 3-outlet)
- KP400 (outdoor 2-outlet)
- KP200 (indoor 2-outlet)
diff --git a/source/_integrations/trend.markdown b/source/_integrations/trend.markdown
index 83ffcda9d65..dbac93eacea 100644
--- a/source/_integrations/trend.markdown
+++ b/source/_integrations/trend.markdown
@@ -87,8 +87,7 @@ sensors:
If the optional `sample_duration` and `max_samples` parameters are specified
then multiple samples can be stored and used to detect long-term trends.
-Each time the state changes, a new sample is stored along with the sample time.
-Samples older than `sample_duration` seconds will be discarded.
+Each time the state changes, a new sample is stored along with the sample time. Samples older than `sample_duration` seconds will be discarded. The `max_samples` parameter must be large enough to store sensor updates over the requested duration. If you want to trend over two hours and your sensor updates every 120s then then `max_samples` must be at least 60, i.e., 7200/120 = 60.
A trend line is then fitted to the available samples, and the gradient of this
line is compared to `min_gradient` to determine the state of the trend sensor.
@@ -124,12 +123,14 @@ binary_sensor:
temp_falling:
entity_id: sensor.outside_temperature
sample_duration: 7200
+ max_samples: 120
min_gradient: -0.0008
device_class: cold
temp_rising:
entity_id: sensor.outside_temperature
sample_duration: 7200
+ max_samples: 120
min_gradient: 0.0008
device_class: heat
```
diff --git a/source/_integrations/w800rf32.markdown b/source/_integrations/w800rf32.markdown
index 011855030a7..68cdad1c627 100644
--- a/source/_integrations/w800rf32.markdown
+++ b/source/_integrations/w800rf32.markdown
@@ -1,7 +1,6 @@
---
title: WGL Designs W800RF32
description: Instructions on how to integrate a W800rf32(a) into Home Assistant.
-logo: w800rf32.png
ha_category:
- Hub
- Binary Sensor
diff --git a/source/_lovelace/picture.markdown b/source/_lovelace/picture.markdown
index c38959d6ca0..e6e94eb2773 100644
--- a/source/_lovelace/picture.markdown
+++ b/source/_lovelace/picture.markdown
@@ -18,7 +18,7 @@ type:
type: string
image:
required: true
- description: The URL of an image.
+ description: The URL of an image. When you want to store images in your Home Assistant installation use the [hosting files documentation](/integrations/http/#hosting-files). After storing your files, use the /local path, for example /local/filename.jpg .
type: string
theme:
required: false
diff --git a/source/_posts/2020-04-08-release-108.markdown b/source/_posts/2020-04-08-release-108.markdown
index ce2274a4596..336103f1ca7 100644
--- a/source/_posts/2020-04-08-release-108.markdown
+++ b/source/_posts/2020-04-08-release-108.markdown
@@ -441,6 +441,108 @@ These integrations have been removed. The websites for both have changed, causin
[powerwall docs]: /integrations/powerwall/
[zha docs]: /integrations/zha/
+## Release 0.108.4 - April 13
+
+- Fix #33995 Use "now" if departure is None ([@eifinger] - [#34017]) ([here_travel_time docs])
+- Fix nexia fan and hold modes for XL824 thermostats ([@bdraco] - [#34042]) ([nexia docs])
+- Handle all zero serial numbers in NUT ([@bdraco] - [#34045]) ([nut docs])
+- UniFi - Fix unit of measurement from B to MB ([@Kane610] - [#34091]) ([unifi docs])
+- Fix Daikin sensor temperature_unit & cleanup ([@fredrike] - [#34116]) ([daikin docs])
+- Bump pyIntesisHome to 1.7.3 ([@jnimmo] - [#34125]) ([intesishome docs])
+- Fix deprecated icon/username logic in Slack ([@bachya] - [#34156]) ([slack docs])
+- Improve rounding the light level conversion in Lutron Caseta ([@swails] - [#34167]) ([lutron_caseta docs])
+- Fix z-wave brightness off by one ([@bdraco] - [#34170]) ([zwave docs])
+- Increase timeout and log the url of the elkm1 system that time… ([@bdraco] - [#34172]) ([elkm1 docs])
+- Convert sense to use DataUpdateCoordinator for trends data ([@bdraco] - [#34160]) ([sense docs])
+
+[#34017]: https://github.com/home-assistant/core/pull/34017
+[#34042]: https://github.com/home-assistant/core/pull/34042
+[#34045]: https://github.com/home-assistant/core/pull/34045
+[#34091]: https://github.com/home-assistant/core/pull/34091
+[#34116]: https://github.com/home-assistant/core/pull/34116
+[#34125]: https://github.com/home-assistant/core/pull/34125
+[#34156]: https://github.com/home-assistant/core/pull/34156
+[#34160]: https://github.com/home-assistant/core/pull/34160
+[#34167]: https://github.com/home-assistant/core/pull/34167
+[#34170]: https://github.com/home-assistant/core/pull/34170
+[#34172]: https://github.com/home-assistant/core/pull/34172
+[@Kane610]: https://github.com/Kane610
+[@bachya]: https://github.com/bachya
+[@bdraco]: https://github.com/bdraco
+[@eifinger]: https://github.com/eifinger
+[@fredrike]: https://github.com/fredrike
+[@jnimmo]: https://github.com/jnimmo
+[@swails]: https://github.com/swails
+[daikin docs]: /integrations/daikin/
+[elkm1 docs]: /integrations/elkm1/
+[here_travel_time docs]: /integrations/here_travel_time/
+[intesishome docs]: /integrations/intesishome/
+[lutron_caseta docs]: /integrations/lutron_caseta/
+[nexia docs]: /integrations/nexia/
+[nut docs]: /integrations/nut/
+[sense docs]: /integrations/sense/
+[slack docs]: /integrations/slack/
+[unifi docs]: /integrations/unifi/
+[zwave docs]: /integrations/zwave/
+
+## Release 0.108.5 - April 15
+
+- Temporary transition Docker init ([@frenck] - [#34135])
+- Catch IPPVersionNotSupportedError in IPP ([@ctalkington] - [#34184]) ([ipp docs])
+- Fix websocket connection bug/errant logic in Ambient PWS ([@bachya] - [#34217]) ([ambient_station docs])
+- Fix Cloud UI bug preventing managing Google 2FA ([@balloob] - [#34241]) ([cloud docs]) ([google_assistant docs])
+- Add daikin update_before_add ([@fredrike] - [#34248]) ([daikin docs])
+- Fix various Daikin issues ([@fredrike] - [#34249]) ([daikin docs])
+
+[#34135]: https://github.com/home-assistant/core/pull/34135
+[#34184]: https://github.com/home-assistant/core/pull/34184
+[#34217]: https://github.com/home-assistant/core/pull/34217
+[#34241]: https://github.com/home-assistant/core/pull/34241
+[#34248]: https://github.com/home-assistant/core/pull/34248
+[#34249]: https://github.com/home-assistant/core/pull/34249
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@ctalkington]: https://github.com/ctalkington
+[@fredrike]: https://github.com/fredrike
+[@frenck]: https://github.com/frenck
+[ambient_station docs]: /integrations/ambient_station/
+[cloud docs]: /integrations/cloud/
+[daikin docs]: /integrations/daikin/
+[google_assistant docs]: /integrations/google_assistant/
+[ipp docs]: /integrations/ipp/
+
+## Release 0.108.6 - April 16
+
+- Use config entry id for unique id if serial number is missing ([@bdraco] - [#34154]) ([nut docs])
+- Fix default elkm1 temp units ([@bdraco] - [#34274]) ([elkm1 docs])
+- Skip ignored hosts when checking existing config entries in config flow ([@raman325] - [#34280]) ([vizio docs])
+- Upgrade broadlink lib to 0.13.1 ([@Danielhiversen] - [#34290]) ([broadlink docs])
+- Pass an argument to kef.update_dsp for async_track_time_interval ([@basnijholt] - [#34310]) ([kef docs])
+- Fixes for Sonos media titles ([@amelchio] - [#34311]) ([sonos docs])
+- Abort vizio zeroconf config flow if unique ID is already configured ([@raman325] - [#34313]) ([vizio docs])
+- Update Coordinator: Only schedule a refresh if listenerrs ([@balloob] - [#34317])
+
+[#34154]: https://github.com/home-assistant/core/pull/34154
+[#34274]: https://github.com/home-assistant/core/pull/34274
+[#34280]: https://github.com/home-assistant/core/pull/34280
+[#34290]: https://github.com/home-assistant/core/pull/34290
+[#34310]: https://github.com/home-assistant/core/pull/34310
+[#34311]: https://github.com/home-assistant/core/pull/34311
+[#34313]: https://github.com/home-assistant/core/pull/34313
+[#34317]: https://github.com/home-assistant/core/pull/34317
+[@Danielhiversen]: https://github.com/Danielhiversen
+[@amelchio]: https://github.com/amelchio
+[@balloob]: https://github.com/balloob
+[@basnijholt]: https://github.com/basnijholt
+[@bdraco]: https://github.com/bdraco
+[@raman325]: https://github.com/raman325
+[broadlink docs]: /integrations/broadlink/
+[elkm1 docs]: /integrations/elkm1/
+[kef docs]: /integrations/kef/
+[nut docs]: /integrations/nut/
+[sonos docs]: /integrations/sonos/
+[vizio docs]: /integrations/vizio/
+
## All changes
diff --git a/source/_posts/2020-04-14-the-future-of-yaml.markdown b/source/_posts/2020-04-14-the-future-of-yaml.markdown
new file mode 100644
index 00000000000..72e1595dd66
--- /dev/null
+++ b/source/_posts/2020-04-14-the-future-of-yaml.markdown
@@ -0,0 +1,234 @@
+---
+title: The future of YAML
+description: "A blog post answering the 'Is YAML going away?' question."
+date: 2020-04-14 00:00:00
+date_formatted: "April 14, 2020"
+author: Franck Nijhof
+author_twitter: frenck
+categories: Announcements
+og_image: /images/blog/2020-04-14-the-future-of-yaml/social.png
+---
+
+Recently, comments and questions in the community have been posted, about the
+announcement of integrations becoming available via the frontend and the removal
+of YAML support from some of them.
+
+This raises questions and opinions that need addressing. It mainly comes down to
+this single question:
+
+> _“Is YAML going away?”_
+
+The answer to this question is: _“**No!**, but…”_
+
+Realizing you may not like that loose answer and, in that case, you are possibly
+looking for a hard and simple “NO” answer to this question. However, things are
+a bit more complicated.
+
+This blog post aims to bring more clarity to this question, so everybody knows
+why things are the way they are right now and what to expect for the future of
+configuring Home Assistant.
+
+## Enabling configuration via the UI
+
+Before talking about YAML, let’s explain the reasoning behind all the UI
+features introduced.
+
+The Home Assistant project has grown at a ludicrous rate in the last few years.
+Being one of the few solutions to provide a local home automation platform,
+that puts privacy first, has gathered interest from all kinds of people on this
+planet.
+
+In the beginning, Home Assistant was a small project; aimed at developers and
+the tech-savvy. With the growth of privacy concerns, but also the growth in the
+availability of IoT devices in our homes in general, the project gained
+traction; attracting lots of new community members that are not always the
+tech-savvy types.
+
+This is great, but that also means we need to adjust, to make it usable for
+everybody. We want everybody to enjoy what we all have been enjoying already.
+No matter your level of experience.
+
+Considering that, enabling and empowering people with managing their
+Home Assistant instance via the user interface is needed. Not just for the
+lesser tech-savvy, since it also brings convenience, that even many technically
+capable users enjoy and prefer.
+
+Goal: _**Making things easier.**_
+
+The goal of making it easier is currently the main focus.
+
+## Breaking changes
+
+We all dislike them, those breaking changes when a new release is published.
+We all scan the release notes hoping you are not affected by any of them in
+that release.
+
+There is a big upside on using configuration via the UI: Home Assistant manages
+that configuration part for you and handles the upgrades and migrations.
+Virtually removing the chances of hitting a breaking change,
+we all hate just as much.
+
+## Shareability & Security
+
+This is a screenshot of one of the slides,
+[showed during the State of the Union 2019][yt]:
+
+
+
+ Presentation slide showed during the State of the Union 2019.
+
+
+We all like to share our experiences, and thus parts of our configurations.
+GitHub is [full of repositories][gh] that shares people’s homes.
+
+This is great! Sharing ideas, providing inspiration for all of us!
+
+There is a great downside to this, which is privacy and security. There are a
+lot of things we don’t want to share. For example, our passwords,
+sensitive (personal) information or (historical) data.
+
+A bit more technical, but integrations using OAuth2 as the authentication method
+to integrate with, for example, a service like Somfy don’t need to store the
+username/password at all.
+
+## Both YAML & UI
+
+Home Assistant is moving towards a better separation of YAML configuration
+versus configuration done in the UI. This is already partly showing in things
+like zones, Lovelace and the recently introduced “Helpers”
+(also known as the `input_*` integrations in YAML).
+
+Zones can be configured via the UI and via YAML (even at the same time!).
+Both configuration sources will be loaded by Home Assistant when considering
+the configured zones and both can be changed on the fly without restarting
+Home Assistant.
+
+For the future, Home Assistant will be moving towards that concept more
+and more. This allows anybody to use the method they prefer.
+
+In these cases, YAML support has been extended and improved by adding features
+like reloading and by removing parts that mess with your YAML files.
+
+## We are still an open-source project
+
+Home Assistant is an open-source project and relies on contributors adding
+those amazing integrations, maintaining them and extending their functionality
+to make them even more capable.
+
+Those contributors do this in their free spare time, for which we all are
+eternally grateful. It is their work that enables Home Assistant to do what it
+can right now. It is what automates your home.
+
+So what about integrations that remove YAML support?
+
+Some contributors have decided to remove the YAML support to reduce their
+maintenance and support burden. The amount of energy that needs to be put in
+(to maintain both capabilities) can be too much and is complex. We have to
+understand and accept that. If we do not do that, a contributor could simply
+stop contributing.
+
+Unfortunately, such a move creates breaking changes and often leads to a few
+pretty de-motivating comments, towards the contributor and the project in
+general. This is harmful to everybody, as the contributors get demotivated or,
+even worse, don’t want to implement new features or create a breaking change.
+
+This halts our project goals, slows down innovation and induces the risk of
+losing contributors and maintainers. In the end, leads to a greater loss for
+everybody.
+
+## The future of YAML
+
+So, with all of the above set context: What is the future of YAML?
+
+As of today, [ADR-0010][adr] (Architectural Decision Record) has been approved
+that states:
+
+- Any new integration that communicates with devices and/or services, must use
+ configuration via the UI. Configuration via YAML is only allowed in very rare
+ cases, which will be determined on a case by case basis.
+- Existing integrations that communicate with devices and/or services, are
+ allowed and encouraged to implement configuration via the UI
+ and remove YAML support.
+- We will no longer accept any changes to the YAML configuration for existing
+ integrations that communicate with devices and/or services.
+
+So what stays available in YAML in the end?
+
+All other integrations that do not communicate with a device and/or service,
+are configured via YAML or via Storage Collections (these enable both YAML and
+UI capabilities used by, e.g., Lovelace and zones).
+Examples of these other integrations:
+
+- Integrations that integrate transports. These integrations allow users to
+ define their own protocol, e.g., MQTT, serial, GPIO.
+- Integrations that process Home Assistant data and make this available to
+ other integrations, e.g., template, stats, derivative, utility meter.
+- Integrations that provide automations, e.g., automation,
+ device_sun_light_trigger, alert.
+- Integrations that help controlling devices and services, e.g., script, scene.
+- Integrations that expose Home Assistant data to other services, e.g.,
+ Google Assistant, HomeKit.
+
+This ADR is set to remove confusion and questions for everybody, builds upon the
+goals that have been set out (as presented during the State of the Union),
+and sets the guidelines for our contributors to work with.
+This ADR brings clarity for us all.
+
+## Myth-busting
+
+In the raised concerns and comments across the community, some comments have
+been found multiple times. Please note, these are not exact quotes, as we don’t
+want to address anybody personally.
+
+- _“Making backups became harder!”_
+
+ Using the Home Assistant snapshot feature, this is not an issue. However,
+ if you do manual backups on a system that runs just Core, you need to make
+ sure to back up the `.storage` folder as well
+ (which hopefully you're already doing). Otherwise, there is no difference.
+
+- _“It is harder to test my configuration if integration does not support YAML”._
+
+ YAML configuration testing is often done to see if a specific YAML
+ configuration is still valid against (newer versions of) Home Assistant.
+ With integrations set up via the UI, this is not a concern,
+ since Home Assistant ensures the data structure is compatible between
+ versions and migrates it for you.
+
+- _“I like to use a private git repository where I store all my data in,
+ including my sensitive data, since it is not public.
+ Without YAML this is not possible.”_
+
+ This is actually not true, the `.storage` folder contains all Home Assistant
+ managed configuration files in JSON format, which in those cases,
+ can be stored and versioned in a git repository.
+
+## Is YAML going away?
+
+**No**!
+
+Not for the things we like to share publicly. It will also remain available for
+the advanced features we currently cannot provide a UI for. The goal is not
+phasing out YAML, the goal is to make the best home automation platform in the
+world that is easy to use for everybody. Enabling users of all experience
+levels, to enjoy this wonderful hobby we all share and allowing everyone to
+focus on what matters most: automating our homes.
+
+Closing with the YouTube recording of the State of the Union 2019,
+starting at the part discussing this.
+
+
+
+
+
+[adr]: https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md
+[yt]: https://youtu.be/tc17q1Zn0Xs?t=1809
+[gh]: https://github.com/topics/home-assistant-config
diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown
index 0033be38ec5..3b10900220c 100644
--- a/source/hassio/installation.markdown
+++ b/source/hassio/installation.markdown
@@ -51,8 +51,6 @@ The following will take you through the steps required to install Home Assistant
6. You will be able to reach your installation at `http://homeassistant.local:8123` (if your router supports mDNS, otherwise see below).
-7. It is important to provide yourself proper access, including the Home Assistant CLI tools. Both the [Samba add-on][samba] and the [SSH add-on][ssh] should be the first add-ons you should install, before making changes to the configuration in the `/config/` folder. From the UI choose **Supervisor**, which is located in the sidebar and then the add-on store.
-
We used `hassio.local` in the past, if you have a system that is installed before this naming change, you might need to use `hassio.local` instead of `homeassistant.local`.
@@ -85,7 +83,12 @@ Best practice for updating a Home Assistant installation:
## Run a specific version on Home Assistant
-SSH to your Home Assistant system, or connect to the console, and run:
+For this you would need to install the [Terminal & SSH add-on][ssh] or use the console
+that is available on your device by connecting a keyboard and screen.
+
+To install the Terminal & SSH add-on, choose **Supervisor**, which is located in the sidebar and then the add-on store.
+
+Use the web-based terminal or SSH to your Home Assistant system, or connect to the console, and run:
```bash
ha core update --version=0.XX.X
@@ -192,21 +195,21 @@ If you can not find your machine type in the list, you should pick the `qemu` re
[balenaEtcher]: https://www.balena.io/etcher
[Virtual Appliance]: https://github.com/home-assistant/operating-system/blob/dev/Documentation/boards/ova.md
[hassos-network]: https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md
-[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi0-w-3.12.img.gz
-[pi1]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi-3.12.img.gz
-[pi2]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi2-3.12.img.gz
-[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi3-3.12.img.gz
-[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi3-64-3.12.img.gz
-[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi4-3.12.img.gz
-[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi4-64-3.12.img.gz
-[tinker]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_tinker-3.12.img.gz
-[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_odroid-c2-3.12.img.gz
+[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_rpi0-w-3.13.img.gz
+[pi1]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_rpi-3.13.img.gz
+[pi2]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_rpi2-3.13.img.gz
+[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_rpi3-3.13.img.gz
+[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_rpi3-64-3.13.img.gz
+[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_rpi4-3.13.img.gz
+[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_rpi4-64-3.13.img.gz
+[tinker]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_tinker-3.13.img.gz
+[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_odroid-c2-3.13.img.gz
[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.4/hassos_odroid-n2-4.4.img.gz
-[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_odroid-xu4-3.12.img.gz
-[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_intel-nuc-3.12.img.gz
-[vmdk]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_ova-3.12.vmdk.gz
-[vhdx]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_ova-3.12.vhdx.gz
-[vdi]: https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_ova-3.12.vdi.gz
+[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_odroid-xu4-3.13.img.gz
+[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_intel-nuc-3.13.img.gz
+[vmdk]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_ova-3.13.vmdk.gz
+[vhdx]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_ova-3.13.vhdx.gz
+[vdi]: https://github.com/home-assistant/operating-system/releases/download/3.13/hassos_ova-3.13.vdi.gz
[linux]: https://github.com/home-assistant/supervised-installer
[local]: http://homeassistant.local:8123
[samba]: /addons/samba/
diff --git a/source/images/blog/2020-04-14-the-future-of-yaml/sharing.png b/source/images/blog/2020-04-14-the-future-of-yaml/sharing.png
new file mode 100644
index 00000000000..6c9e7fda248
Binary files /dev/null and b/source/images/blog/2020-04-14-the-future-of-yaml/sharing.png differ
diff --git a/source/images/blog/2020-04-14-the-future-of-yaml/social.png b/source/images/blog/2020-04-14-the-future-of-yaml/social.png
new file mode 100644
index 00000000000..043b4034c52
Binary files /dev/null and b/source/images/blog/2020-04-14-the-future-of-yaml/social.png differ
diff --git a/source/lovelace/dashboards-and-views.markdown b/source/lovelace/dashboards-and-views.markdown
index f56b25a3063..354b926f2f8 100644
--- a/source/lovelace/dashboards-and-views.markdown
+++ b/source/lovelace/dashboards-and-views.markdown
@@ -6,6 +6,7 @@ description: "The Lovelace UI is a powerful and configurable interface for Home
### Dashboards
You can define multiple dashboards that all have their own YAML file, and add custom resources that are shared by all dashboards.
+To create new or manage existing (with `mode: storage` only) dashboards, click on `Configuration` in the sidebar and then on `Lovelace Dashboards`.
The key of the dashboard is used as the URL, this needs to contain a hyphen (`-`).
@@ -34,7 +35,7 @@ lovelace:
filename: hidden.yaml
```
-You can also add YAML dashboards when your main dashboard is UI configurated:
+You can also add YAML dashboards when your main dashboard is UI configured:
```yaml
lovelace:
mode: storage