Merge branch 'rc' into current

CODEOWNERS

@@ -185,7 +185,6 @@ source/_integrations/lcn.markdown @alengwenus
 source/_integrations/life360.markdown @pnbruckner
 source/_integrations/linky.markdown @Quentame
 source/_integrations/linux_battery.markdown @fabaff
-source/_integrations/liveboxplaytv.markdown @pschmitt
 source/_integrations/local_ip.markdown @issacg
 source/_integrations/logger.markdown @home-assistant/core
 source/_integrations/logi_circle.markdown @evanjd

_config.yml

@@ -100,9 +100,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 0
-current_minor_version: 105
-current_patch_version: 5
-date_released: 2020-02-17
+current_minor_version: 106
+current_patch_version: 0
+date_released: 2020-02-26
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

source/_integrations/abode.markdown

@@ -31,7 +31,7 @@ There is currently support for the following device types within Home Assistant:
 - **Cover**: Reports on `Secure Barriers` and can be used to open and close the cover.
 - **Lock**: Reports on `Door Locks` and can be used to lock and unlock the door.
 - [**Light**](/integrations/abode/#light): Reports on `Dimmer` lights and can be used to dim or turn the light on and off.
-- [**Switch**](/integrations/abode/#switch): Reports on `Power Switch` devices and can be used to turn the power switch on and off. Also reports on `Automations` set up in the Abode system and allows you to activate or deactivate them (does not work with Abode's CUE automations).
+- [**Switch**](/integrations/abode/#switch): Reports on `Power Switch` and `Water Valve` devices which can be used to turn the devices on and off. Also reports on `Automations` set up in the Abode system and allows you to activate or deactivate them (does not currently work with Abode's CUE automations).
 - **Sensor**: Reports on `Temperature`, `Humidity`, and `Light` sensors.
 
 ## Configuration

source/_integrations/air_quality.xiaomi_miio.markdown

@@ -16,6 +16,8 @@ Currently, the supported features are:
 - Attributes
   - carbon_dioxide_equivalent
   - total_volatile_organic_compounds
+  - temperature
+  - humidity
 
 Please follow the instructions on [Retrieving the Access Token](/integrations/vacuum.xiaomi_miio/#retrieving-the-access-token) to get the API token.
 

source/_integrations/binary_sensor.modbus.markdown

@@ -18,20 +18,21 @@ To use your Modbus binary sensors in your installation, add the following to you
 # Example configuration.yaml entry
 binary_sensor:
   - platform: modbus
-    coils:
+    inputs:
       - name: Sensor1
         hub: hub1
         slave: 1
-        coil: 100
+        address: 100
       - name: Sensor2
         hub: hub1
         slave: 1
-        coil: 110
+        address: 110
+        input_type: discrete_input
 ```
 
 {% configuration %}
-coils:
-  description: The array contains a list of coils to read from.
+inputs:
+  description: The array contains a list of coils and discrete inputs to read from.
   required: true
   type: [map, list]
   keys:
@@ -48,10 +49,14 @@ coils:
       description: The number of the slave (Optional for TCP and UDP Modbus).
       required: true
       type: integer
-    coil:
-      description: Coil number.
+    address:
+      description: Coil or discrete input Modbus address.
       required: true
       type: integer
+    input_type:
+      description: Modbus input type (coil, discrete_input), default coil.
+      required: false
+      type: string
     device_class:
       description: The [type/class](/integrations/binary_sensor/#device-class) of the binary sensor to set the icon in the frontend.
       required: false

source/_integrations/blockchain.markdown

@@ -1,14 +1,14 @@
 ---
-title: Blockchain.info
-description: Instructions on how to integrate Blockchain.info data within Home Assistant.
+title: Blockchain.com
+description: Instructions on how to integrate Blockchain.com data within Home Assistant.
 logo: blockchain.png
 ha_category:
   - Finance
 ha_release: 0.47
 ha_iot_class: Cloud Polling
 ---
 
-The `Blockchain` sensor platform displays Bitcoin wallet balances from [blockchain.info](https://blockchain.info).
+The `Blockchain` sensor platform displays Bitcoin wallet balances from [blockchain.com](https://blockchain.com).
 
 To add the Blockchain sensor to your installation, specify a list of bitcoin addresses to watch in the `configuration.yaml` file. The sensor state will be the sum of the balances of all addresses listed.
 

source/_integrations/climate.modbus.markdown

@@ -56,6 +56,11 @@ current_temp_register:
   description: Register number for current temperature (Process value).
   required: true
   type: integer
+current_temp_register_type:
+  description: Modbus register type (holding, input) for current temperature, default holding.
+  required: false
+  type: string
+  default: holding
 data_type:
   description: Response representation (int, uint, float, custom). If float selected, value will converted to IEEE 754 floating point format.
   required: false

source/_integrations/cover.mqtt.markdown

@@ -12,8 +12,8 @@ The `mqtt` cover platform allows you to control an MQTT cover (such as blinds, a
 
 ## Configuration
 
-The device state (`open` or `closed`) will be updated only after a new message is published on `state_topic` matching `state_open` or `state_closed`. If these messages are published with the `retain` flag set, the cover will receive an instant state update after subscription and Home Assistant will display the correct state on startup. Otherwise, the initial state displayed in Home Assistant will be `unknown`.
-`state_topic` can only manage `state_open` and `state_closed`. No percentage positions etc.
+The device state (`open`, `opening`, `closed` or `closing`) will be updated only after a new message is published on `state_topic` matching `state_open`, `state_opening`, `state_closed` or `state_closing`. If these messages are published with the `retain` flag set, the cover will receive an instant state update after subscription and Home Assistant will display the correct state on startup. Otherwise, the initial state displayed in Home Assistant will be `unknown`.
+`state_topic` can only manage `state_open`, `state_opening`, `state_closed` and `state_closing`. No percentage positions etc.
 
 For this purpose is `position_topic` which can set state of the cover and position.
 Default setting are 0 means the device is `closed` and all other intermediate positions means the device is `open`.
@@ -70,11 +70,21 @@ state_open:
   required: false
   type: string
   default: open
+state_opening:
+  description: The payload that represents the opening state.
+  required: false
+  type: string
+  default: opening
 state_closed:
   description: The payload that represents the closed state.
   required: false
   type: string
   default: closed
+state_closing:
+  description: The payload that represents the closing state.
+  required: false
+  type: string
+  default: closing
 position_topic:
   description: The MQTT topic subscribed to receive cover position messages. If `position_topic` is set `state_topic` is ignored.
   required: false
@@ -242,7 +252,9 @@ cover:
     payload_close: "CLOSE"
     payload_stop: "STOP"
     state_open: "open"
+    state_opening: "opening"
     state_closed: "closed"
+    state_closing: "closing"
     payload_available: "online"
     payload_not_available: "offline"
     optimistic: false
@@ -297,7 +309,9 @@ cover:
     payload_close: "CLOSE"
     payload_stop: "STOP"
     state_open: "open"
+    state_opening: "opening"
     state_closed: "closed"
+    state_closing: "closing"
     payload_available: "online"
     payload_not_available: "offline"
     optimistic: false

source/_integrations/derivative.markdown

@@ -12,7 +12,8 @@ ha_codeowners:
   - '@afaucogney'
 ---
 
-The `derivative` platform provides the numerical derivative or numerical differentiation of the values provided by a source sensor. Derivative sensors are updated upon changes of the **source**. Fast sampling source sensors provide better results. 
+The `derivative` platform creates a sensor that estimates the derivative of the values provided by a source sensor.
+Derivative sensors are updated upon changes of the **source**.
 
 ## Configuration
 
@@ -41,7 +42,7 @@ round:
   default: 3
   type: integer
 unit_prefix:
-  description: Metric unit to prefix the derivative result. Available units are k, M, G, T.
+  description: Metric unit to prefix the derivative result ([Wikipedia](https://en.wikipedia.org/wiki/Unit_prefix)]). Available symbols are "n" (1e-9), "µ" (1e-6), "m" (1e-3), "k" (1e3), "M" (1e6), "G" (1e9), "T" (1e12).
   required: false
   default: None
   type: string
@@ -54,6 +55,27 @@ unit:
   description: Unit of Measurement to be used for the derivative.
   required: false
   type: string
+time_window:
+  description: The time window in which to calculate the derivative. This is useful for sensor that output discrete values. By default the derivative is calculated between two consecutive updates.
+  default: 0
+  required: false
+  type: time
 {% endconfiguration %}
 
-If 'unit' is set then 'unit_prefix' and 'unit_time' are ignored.
+## Temperature example
+
+For example, you have a temperature sensor `sensor.temperature` that outputs a value every few seconds, but rounds to the nearest half number.
+That means that two consecutive output values might be the same (so the derivative is `Δy/Δx=0` because `Δy=0` !)
+However, the temperature might actually be changing over time.
+In order to capture this, you should use a `time_window`, such that immediate jumps don't result in high derivatives and that after the next sensor update, the derivatives doesn't vanish to zero.
+An example configuration that uses `time_window` is
+
+```yaml
+sensor:
+  - platform: derivative
+    source: sensor.temperature
+    name: Temperature change per hour
+    round: 1
+    unit_time: h
+    time_window: "00:30:00"  # we look at the change over the last half hour
+```

source/_integrations/dsmr.markdown

@@ -10,7 +10,7 @@ ha_iot_class: Local Push
 
 A sensor platform for Dutch Smart Meters which comply to DSMR (Dutch Smart Meter Requirements), also known as 'Slimme meter' or 'P1 poort'.
 
-- Currently support DSMR V2.2, V3, V4 and V5 through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter.
+- Currently support DSMR V2.2, V3, V4, V5 and V5 Belgian through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter.
 - For official information about DSMR refer to: [DSMR Document](https://www.netbeheernederland.nl/dossiers/slimme-meter-15)
 - For official information about the P1 port refer to: <https://www.netbeheernederland.nl/_upload/Files/Slimme_meter_15_a727fce1f1.pdf>
 - For unofficial hardware connection examples refer to: [Domoticx](http://domoticx.com/p1-poort-slimme-meter-hardware/)
@@ -35,6 +35,7 @@ USB serial converters:
 - <https://sites.google.com/site/nta8130p1smartmeter/webshop>
 - <https://www.sossolutions.nl/slimme-meter-kabel>
 - <https://tweakers.net/gallery/269738/aanbod/>
+- <https://nl.aliexpress.com/item/32945187155.html>
 
 Serial to network proxies:
 
@@ -60,7 +61,7 @@ sensor:
     required: false
     type: string
   dsmr_version:
-    description: "Version of DSMR used by meter. Choices: 2.2, 4, 5. Defaults to 2.2."
+    description: "Version of DSMR used by meter. Choices: 2.2, 4, 5, 5B (For Belgian Meter). Defaults to 2.2."
     required: false
     type: string
   precision:
@@ -83,10 +84,10 @@ group:
   meter_readings:
     name: Meter readings
     entities:
-      - sensor.power_consumption_low
-      - sensor.power_consumption_normal
-      - sensor.power_production_low
-      - sensor.power_production_normal
+      - sensor.energy_consumption_tarif_1
+      - sensor.energy_consumption_tarif_2
+      - sensor.energy_production_tarif_1
+      - sensor.energy_production_tarif_2
       - sensor.gas_consumption
 ```
 
@@ -102,10 +103,10 @@ group:
   meter_readings:
     name: Meter readings
     entities:
-      - sensor.power_consumption_low
-      - sensor.power_consumption_normal
-      - sensor.power_production_low
-      - sensor.power_production_normal
+      - sensor.energy_consumption_tarif_1
+      - sensor.energy_consumption_tarif_2
+      - sensor.energy_production_tarif_1
+      - sensor.energy_production_tarif_2
       - sensor.gas_consumption
 ```