Merge branch 'current' into next

_config.yml

@@ -107,8 +107,8 @@ social:
 # Home Assistant release details
 current_major_version: 2022
 current_minor_version: 10
-current_patch_version: 4
-date_released: 2022-10-14
+current_patch_version: 5
+date_released: 2022-10-20
 
 # 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/_dashboards/button.markdown

@@ -101,6 +101,11 @@ theme:
   required: false
   description: Override the used theme for this card with any loaded theme. For more information about themes, see the [frontend documentation](/integrations/frontend/).
   type: string
+action_name:
+  required: false
+  description: Override the default action name for a button row.
+  type: string
+  default: Run
 {% endconfiguration %}
 
 Example:

source/_integrations/balboa.markdown

@@ -23,6 +23,12 @@ There is currently support for the following device types within Home Assistant:
 - Binary Sensor (Filter cycles and circulation pumps)
 - Climate
 
+## Compatible hardware
+
+Balboa Spa Client integration support local control of hot tub spas equipped with a Balboa BP system and a bwa™ Wi-Fi Module (50350).
+
+Balboa Spa Client integration is not compatible with ControlMySpa™ cloud API used by Balboa ControlMySpa Gateway Ultra (59303).
+
 {% include integrations/config_flow.md %}
 
 {% configuration_basic %}

source/_integrations/broadlink.markdown

@@ -28,7 +28,7 @@ The Broadlink integration allows you to control and monitor Broadlink universal
 - Power Strips: `MP1-1K3S2U` and `MP1-1K4S`
 - Sensors: `e-Sensor`
 - Smart Plugs: `SP mini`, `SP mini+`, `SP mini 3`, `SP1`, `SP2`, `SP2-CL`, `SP2-UK/BR/IN`, `SP3`, `SP3-EU`, `SP3S-EU`, `SP3S-US`, `SP4L-EU` and `SP4M-US`
-- Universal Remotes: `RM mini`, `RM mini 3`, `RM pro`, `RM pro+`, `RM plus`, `RM4 mini`, `RM4 pro` and `RM4C mini`
+- Universal Remotes: `RM mini`, `RM mini 3`, `RM pro`, `RM pro+`, `RM plus`, `RM4 mini`, `RM4 pro`, `RM4C mini` and `RM4 TV mate`
 - Wi-Fi Controlled Switches: `BG1`, `SC1`
 - Smart Light Bulbs: `LB1`,`LB2`
 

source/_integrations/device_tracker.mqtt.markdown

@@ -276,7 +276,7 @@ mosquitto_pub -h 127.0.0.1 -t homeassistant/device_tracker/a4567d663eaf/config -
 To set the state of the device tracker to specific coordinates:
 
 ```bash
-mosquitto_pub -h 127.0.0.1 -t a4567d663eaf/state -m '{"latitude": 32.87336, "longitude": -117.22743, "gps_accuracy": 1.2}'
+mosquitto_pub -h 127.0.0.1 -t a4567d663eaf/attributes -m '{"latitude": 32.87336, "longitude": -117.22743, "gps_accuracy": 1.2}'
 ```
 
 

source/_integrations/ecovacs.markdown

@@ -52,7 +52,7 @@ continent:
   type: string
 {% endconfiguration %}
 
-Note: For some countries, you will need to set `continent` to `ww` (meaning worldwide.) There is unfortunately no way to know the correct settings other than guessing and checking. See the [sucks library protocol documentation](https://github.com/wpietri/sucks/blob/master/protocol.md) for more information about what has been figured out about the Ecovacs servers.
+Note: For some countries, you will need to set `continent` to `ww` (meaning worldwide.) There is unfortunately no way to know the correct settings other than guessing and checking. See the [py-sucks library protocol documentation](https://github.com/mib1185/py-sucks/blob/master/protocol.md) for more information about what has been figured out about the Ecovacs servers.
 
 Additional note: There are some issues during the password encoding. Using some special characters (e.g., `-`) in your password does not work.
 
@@ -60,7 +60,7 @@ Additional note: There are some issues during the password encoding. Using some
 
 The library that talks to the Ecovacs servers is in a very early state and still under development. As such, it is likely that not all regions and devices will work at the current time.
 
-Please see the [sucks library documentation](https://github.com/wpietri/sucks) for some more information about what has been tested, and check out the GitHub issues to see if the issue you're having is known or being worked on.
+Please see the [py-sucks library documentation](https://github.com/mib1185/py-sucks) for some more information about what has been tested, and check out the GitHub issues to see if the issue you're having is known or being worked on.
 
 If you have an issue with the Ecovacs component, please file a [GitHub Issue](https://github.com/home-assistant/home-assistant/issues) and include your Home Assistant logs in the report. To get full debug output from both the Ecovacs integration and the underlying `sucks` library, place this in your `configuration.yaml` file:
 

source/_integrations/hangouts.markdown

@@ -25,24 +25,22 @@ There is currently support for the following device types within Home Assistant:
 
 If you are sure your email and password are correct, but the integration says the login is invalid then you would need to use the manual authentication method.
 
-To use the manual method, first you would need to obtain an authorization code (see <a href="#steps-to-obtain-authorization-code">instructions below</a> for details).
-
-Once the code is obtained fill in the form with your email, password and the authorization code to complete authentication.
+To use the manual method, first, you would need to obtain an authorization code (see [instructions below](#steps-to-obtain-authorization-code) for details). Once the code is obtained, fill in the form with your email, password, and authorization code to complete authentication.
 
 ### Steps to obtain Authorization Code:
 
-1. To obtain your authorization code, open [this URL](https://accounts.google.com/o/oauth2/programmatic_auth?scope=https%3A%2F%2Fwww.google.com%2Faccounts%2FOAuthLogin+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email&client_id=936475272427.apps.googleusercontent.com&device_name=hangups) in your browser.
+1. Open [this URL](https://accounts.google.com/o/oauth2/programmatic_auth?scope=https%3A%2F%2Fwww.google.com%2Faccounts%2FOAuthLogin+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email&client_id=936475272427.apps.googleusercontent.com&device_name=hangups) in your browser.
 2. Log into your Google account normally.
-3. You should be redirected to a loading screen. Copy the `oauth_code` cookie value set by this page and paste it here.
+3. You should be redirected to a loading screen that continues loading indefinitely.
 
-To obtain the `oauth_code` cookie value, follow the steps below:
+The authorization code is stored as `oauth_code` cookie value on this page. To obtain this value, continue with the steps below:
 
 *Note:* If the `oauth_code` cookie is not showing in Chrome, try Firefox.
 
-* Press F12 to open developer tools.
-* Select the "Application" (Chrome) or "Storage" (Firefox) tab.
-* In the sidebar, expand "Cookies" and select `https://accounts.google.com`
-* In the cookie list, double click on the value for the `oauth_code` cookie to select it, and copy the value. This is the authorization code
+4. Press F12 to open developer tools.
+5. Select the "Application" (Chrome) or "Storage" (Firefox) tab.
+6. In the sidebar, expand "Cookies" and select `https://accounts.google.com`
+7. In the cookie list, double click on the value for the `oauth_code` cookie to select it, and copy the value (this is the authorization code).
 
 <div class='note'>
 You can't write messages to yourself or get notifications in a group, if "you" write the message. The best way is to create a new Google Chat account for this integration.<br>

source/_integrations/rfxtrx.markdown

@@ -158,7 +158,7 @@ Copy the event code from the state attribute of the switch, which shows up on th
 710030e4102 **01** 50<br>
 710030e4102 **02** 50
 
-### Protocols {#protocols}
+### Protocols
 
 When no protocols are selected in the device configuration, the RFXtrx device will use the protocols enabled in its non-volatile memory. You can set these using [RFXmgmr](http://www.rfxcom.com/epages/78165469.sf/en_GB/?ViewObjectPath=%2FShops%2F78165469%2FCategories%2FDownloads).
 

source/_integrations/third_reality.markdown

@@ -3,7 +3,6 @@ title: Third Reality
 description: Connect and control your Third Reality Zigbee devices using the Zigbee integration
 ha_release: '2022.10'
 ha_iot_class: Local Push
-ha_config_flow: true
 ha_category:
   - Cover
   - Switch
@@ -32,4 +31,4 @@ To add Third Reality products, pair them as Zigbee devices:
 
 {% my config_zha badge %}
 
-[Learn more about Zigbee in Home Assistant.](/integrations/zha)
+[Learn more about Zigbee in Home Assistant.](/integrations/zha/)

source/_integrations/tuya.markdown

@@ -149,6 +149,9 @@ Click the created project to enter the `Project Overview` page and get the `Auth
 
     - IoT Data Analytics
 
+"28841002: No permissions. Your subscription to cloud development plan has expired":
+  description: Your subscription to Tuya cloud development **IoT Core Service** resources has expired, please [extend it](https://iot.tuya.com/cloud/products/detail?abilityId=1442730014117204014) in `Cloud` > `Cloud Services` > `IoT Core` > `My Subscriptions` tab > `Subscribed Resources` > `IoT Core` > `Extend Trial Period`. 
+
 {% endconfiguration_basic %}
 
 ## Scenes

source/_integrations/ultraloq.markdown

@@ -0,0 +1,25 @@
+---
+title: Ultraloq
+description: Connect and control your Ultraloq Z-Wave series devices using the Z-Wave integration
+ha_release: '2022.11'
+ha_iot_class: Local Push
+ha_category:
+  - Lock
+ha_domain: ultraloq
+ha_integration_type: virtual
+works_with:
+  - zwave
+ha_platforms:
+  - lock
+ha_iot_standard: zwave
+---
+
+Ultraloq smart locks allow users to enter their homes without a key. The lock can be controlled remotely using the Ultraloq app or by using Home Assistant. U-tec, their parent company, is a member of the Works with Home Assistant partner program. This means they are committed to making sure the Ultraloq Z-Wave products are up-to-date and ready to use with Home Assistant.
+
+Ultraloq Z-Wave Series smart locks work locally and integrate seamlessly with the Z-Wave integration in Home Assistant (Z-Wave stick required).
+
+To add Ultraloq Z-Wave products, pair them as Z-Wave devices:
+
+{% my config_zwave_js badge %}
+
+[Learn more about Z-Wave in Home Assistant.](/integrations/zwave_js/)

source/_posts/2022-10-25-ultraloq-partner.markdown

@@ -0,0 +1,26 @@
+---
+layout: post
+title: "Ultraloq joins Works with Home Assistant"
+description: "Ultraloq Z-Wave Series join the Works with Home Assistant partner program as a Z-Wave partner."
+date: 2022-10-25 00:00:00
+date_formatted: "October 25, 2022"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories:
+- Announcements
+og_image: /images/blog/2022-10-25-ultraloq-partner/social.png
+---
+
+<img src='/images/works_with/works-with-zwave.png' width="256" align="right" alt="Works via Zigbee with Home Assistant" class='no-shadow'>
+
+Today we are excited to announce that [Ultraloq by U-tec](https://u-tec.com) has joined the Works with Home Assistant program as a Z-Wave partner.
+
+As a partner, U-tec and Nabu Casa will be working together to ensure the best experience for connecting Ultraloq Z-Wave smart locks to Home Assistant, including testing the actual products in the Nabu Casa labs.
+
+<img src='/images/blog/2022-10-25-ultraloq-partner/devices.jpg' alt="Ultraloq devices" class='no-shadow'>
+<br><br>
+
+Ultraloq smart locks connect and integrate into Home Assistant using the Z-Wave integration (Z-Wave stick required). This means that connected locks work completely local, and updates coming from the device are instantaneously reflected in Home Assistant. This allows for the best user experience when building your smart home.
+
+_[Learn more about the Works with Home Assistant partner program.](/blog/2022/07/12/partner-program/)_