Merge branch 'current' into next

source/_integrations/alexa.intent.markdown

@@ -25,12 +25,10 @@ The built-in Alexa integration allows you to integrate Home Assistant into Alexa
 
 - Log in to the [Amazon developer console][amazon-dev-console]
 - Click the Alexa button at the top of the console
-- Click the yellow "Add a new skill" button in the top right
-  - Skill Type: Custom Interaction Model (default)
-  - Name: Home Assistant
-  - Invocation name: `home assistant` (or be creative, up to you)
-  - Version: 1.0
-  - Endpoint: This will be the ARN for the Lambda Function you will create next.
+- Click the blue "Create Skill" button in the top right
+  - Model to add: Custom
+  - Name: HomeAssistantIntentsSkill (or whatever you want to call this skill)
+  - Method to host: Provision your own
  
 You can use this [specially sized Home Assistant logo][large-icon] as the large icon and [this one][small-icon] as the small one.
 
@@ -66,7 +64,7 @@ Next you need to create a Lambda function.
   - **US West (Oregon)** region for Japanese and English (AU) skills.
 - Click `Functions` in the left navigation bar, display list of your Lambda functions.
 - Click `Create function`, select `Author from scratch`, then input a `Function name`.
-- Select *Python 3.6* or *Python 3.7* as `Runtime`.
+- Select *Python 3.* as `Runtime` (Python 3.9 was available at this time).
 - Select *Use an existing role* as `Execution role`, then select the role you just created from the `Existing role` list.
 - Click `Create function`, then you can configure the details of the Lambda function.
 - Under the `Configuration` tab, expand `Designer`, then click on `+ Add trigger` in the left part of the panel and select `Alexa Skills Kit` from the dropdown list to add an Alexa Skills Kit trigger to your Lambda function.
@@ -80,7 +78,9 @@ Next you need to create a Lambda function.
   - DEBUG *(optional)*: set to *True* to log debugging messages.
   - LONG_LIVED_ACCESS_TOKEN *(optional, not recommended)*: you will connect your Alexa Custom skill with your Home Assistant user account in the later steps, so that you don't need to use long-lived access token here. However, the access token you got from login flow is only valid for 30 minutes. It will be hard for you to test lambda function with the access token in test data. So for your convenience, you can remove the access token from the test data, [generate a long-lived access token][generate-long-lived-access-token] to put here, then the function will fall back to reading the token from environment variables. (tips: You did not enable the security storage for your environment variables, so your token saved here is not that safe. You should only use it for debugging and testing purpose. You should remove and delete the long-lived access token after you finish the debugging.)
 - Save your environmental variables by clicking the `Save` button.
-- Next, copy the ARN displayed in the top of the page, which is the identify of this Lambda function. Set the end point of the custom Alexa Skill you created earlier to this value.
+- Next, copy the ARN displayed at the top of the page, which is the identity of this Lambda function. 
+  - Go back to your Alexa skill and go to the Custom->Endpoint menu option on the left.
+  - Paste the ARN value in the "Default Region". Note: you will not be able to do this until you have completed the step above adding the Alexa Skills Kit trigger (done in the previous step) to the AWS Lambda Function.
 
 ### Account Linking
 

source/_integrations/compensation.markdown

@@ -33,7 +33,7 @@ compensation:
 
 {% configuration %}
 source:
-  description: The entity to monitor.
+  description: The entity to monitor/compensate.
   required: true
   type: string
 data_points:
@@ -45,7 +45,7 @@ unique_id:
   required: false
   type: string
 attribute:
-  description: Attribute to monitor.
+  description: Attribute from the source to monitor/compensate. When omitted the state value of the source will be used.
   required: false
   type: string
 degree:

source/_integrations/cover.mysensors.markdown

@@ -149,3 +149,9 @@ void receive(const MyMessage &message) {
   }
 }
 ```
+
+## Sketch example with position measurement based on motor running time
+
+This sketch is ideally for star topology wiring. You can run up to 12 covers with a single Arduino Mega board and some relays. All you need to set is one line of parameters for one Cover. However, you can also use it for a single cover based on an Arduino Nano or even an ESP8266 board.
+
+[Check out the code on GitHub.](https://github.com/gryzli133/RollerShutterSplit)

source/_integrations/enocean.markdown

@@ -233,6 +233,7 @@ The following [EnOcean Equipment Profiles](https://www.enocean-alliance.org/what
 - **A5-10-01** to **A5-10-14** - Room Operating Panels
 - **A5-04-01** - Temp. and Humidity Sensor, Range 0°C to +40°C and 0% to 100%
 - **A5-04-02** - Temp. and Humidity Sensor, Range -20°C to +60°C and 0% to 100%
+- **A5-10-03** - Temp. Sensor, Set point control
 - **A5-10-10** - Temp. and Humidity Sensor and Set Point
 - **A5-10-12** - Temp. and Humidity Sensor, Set Point and Occupancy Control
 
@@ -281,6 +282,7 @@ However, some EEPs have a different, inverted range, which goes from 0 to 250. T
 - **A5-04-01**
 - **A5-04-02**
 - **A5-10-10** to **A5-10-14**
+- **A5-20-01** - Battery powered actuator (bi-dir)
 
 Adapt the `configuration.yaml` for those sensors:
 

source/_integrations/mfi.markdown

@@ -28,7 +28,7 @@ To add this platform to your installation, add the following to your `configurat
 # Example configuration.yaml entry
 sensor:
   - platform: mfi
-    host: IP_ADDRESS_OF_SENSOR
+    host: IP_ADDRESS_OF_CONTROLLER
     username: YOUR_USERNAME
     password: YOUR_PASSWORD
 ```
@@ -73,7 +73,7 @@ To add this platform to your installation, add the following to your `configurat
 # Example configuration.yaml entry
 switch:
   - platform: mfi
-    host: IP_ADDRESS_OF_SWITCH
+    host: IP_ADDRESS_OF_CONTROLLER
     username: YOUR_USERNAME
     password: YOUR_PASSWORD
 ```