diff --git a/source/docs/assist/using_voice_assistants_overview.markdown b/source/docs/assist/using_voice_assistants_overview.markdown
new file mode 100644
index 00000000000..b0c164bf90a
--- /dev/null
+++ b/source/docs/assist/using_voice_assistants_overview.markdown
@@ -0,0 +1,19 @@
+---
+title: "Using voice assistants - overview"
+---
+
+We are in [chapter two](https://www.home-assistant.io/blog/2023/04/27/year-of-the-voice-chapter-2/) of Home Assistant's Year of the Voice.
+We can now turn speech into text and text back into speech. Wake word detection is not yet supported.
+
+The video below provides a good overview of what is currently possible with voice assistants. It shows you the following:
+
+* How to voice-control devices using the Assist button, an [analog phone](/projects/worlds-most-private-voice-assistant/), or an [ATOM Echo](/projects/thirteen-usd-voice-remote/).
+* How to [expose devices to Assist](/docs/assist/voice_remote_expose_devices/).
+* How to set up a [local voice assistant](/docs/assist/voice_remote_local_assistant/).
+* The video also shows the differences in processing speed. It compares:
+ * Home Assistant Cloud versus local processing,
+ * local processing on more or less powerful hardware.
+
+
+
+
From e9f5af55fa5257f73e1668dcee919ed59a9ab184 Mon Sep 17 00:00:00 2001
From: karwosts <32912880+karwosts@users.noreply.github.com>
Date: Tue, 16 May 2023 23:01:48 -0700
Subject: [PATCH 02/68] Mention `simple-entity` type in entities.markdown
(#27412)
* Mention `simple-entity` type in entities.markdown
Describe how `simple-entity` type can be used to get a read only version of a helper in an entities card.
I've seen this question for how to do this come up several times on discord, and the solution is currently undocumented.
* Update source/_dashboards/entities.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update entities.markdown
---------
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
---
source/_dashboards/entities.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_dashboards/entities.markdown b/source/_dashboards/entities.markdown
index cf7fb6ef867..7973839a311 100644
--- a/source/_dashboards/entities.markdown
+++ b/source/_dashboards/entities.markdown
@@ -65,7 +65,7 @@ entity:
type: string
type:
required: false
- description: "Sets a custom card type: `custom:my-custom-card`"
+ description: "Sets a custom card type: `custom:my-custom-card`. It also can be used to force entities with a default special row format to render as a simple state. You can do this by setting the type: `simple-entity`. This can be used, for example, to replace a helper with an editable control with a read-only value."
type: string
name:
required: false
From 76b2971c17839f3f14bd5884a8e652023c12b99d Mon Sep 17 00:00:00 2001
From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
Date: Wed, 17 May 2023 09:25:27 +0200
Subject: [PATCH 03/68] Installation ODROID M1: add affiliated links to HA
bundles (#27373)
---
.../installation/operating_system.md | 33 +++++++++++++++----
source/blue/index.html | 1 +
2 files changed, 27 insertions(+), 7 deletions(-)
diff --git a/source/_includes/installation/operating_system.md b/source/_includes/installation/operating_system.md
index 5ff4865fe19..b957c5961e2 100644
--- a/source/_includes/installation/operating_system.md
+++ b/source/_includes/installation/operating_system.md
@@ -12,15 +12,34 @@ Follow this guide if you want to get started with Home Assistant easily or if yo
We will need a few things to get started with installing Home Assistant. The links below lead to Ameridroid. If you’re not in the US, you should be able to find these items in web stores in your country.
-To get started we suggest the ODROID N2+, it's the most powerful ODROID. It's fast and with built-in eMMC one of the best boards to run Home Assistant. It's also the board that powers our [Home Assistant Blue](/blue/).
+To get started, we suggest the ODROID N2+, the board that powers our [Home Assistant Blue](/blue/), or the ODROID M1.
-- [ODROID N2+](https://ameridroid.com/products/odroid-n2-plus?ref=eeb6nfw07e)
-- [Power Supply](https://ameridroid.com/products/12v-2a-power-supply-plug?ref=eeb6nfw07e)
-- [CR2032 Coin Cell](https://ameridroid.com/products/rtc-bios-battery?ref=eeb6nfw07e)
-- [eMMC Module](https://ameridroid.com/products/emmc-module-n2-linux-red-dot?ref=eeb6nfw07e)
-- [Case](https://ameridroid.com/products/odroid-n2-case?ref=eeb6nfw07e)
+If unavailable, we also recommend the [ODROID C4](https://ameridroid.com/products/odroid-c4?ref=eeb6nfw07e).
-If unavailable, we also recommend the [ODROID C4](https://ameridroid.com/products/odroid-c4?ref=eeb6nfw07e) or [ODROID M1](https://ameridroid.com/products/odroid-M1?ref=eeb6nfw07e).
+
+Home Assistant bundles (US market):
+
+The bundles come with Home Assistant pre-installed.
+
+* [ODROID N2+: 2 GB RAM / 16 GB eMMC](https://ameridroid.com/products/odroid-n2-home-assistant-blue-bundle-limited-edition?variant=44748729286935?ref=eeb6nfw07e)
+* [ODROID N2+: 4 GB RAM / 64 GB eMMC](https://ameridroid.com/products/odroid-n2-home-assistant-blue-bundle-limited-edition?variant=44748729221399?ref=eeb6nfw07e)
+* ODROID M1: 4 GB RAM / 256 GB NVMe / [16 GB µSD](https://ameridroid.com/products/odroid-n2-home-assistant-blue-bundle-limited-edition?variant=44929573028119?ref=eeb6nfw07e) or [16 GB eMMC](https://ameridroid.com/products/odroid-n2-home-assistant-blue-bundle-limited-edition?variant=44994940567831?ref=eeb6nfw07e)
+* ODROID M1: 8 GB RAM / 256 GB NVMe / [16 GB µSD](https://ameridroid.com/products/odroid-n2-home-assistant-blue-bundle-limited-edition?variant=44929573093655?ref=eeb6nfw07e) or [16 GB eMMC](https://ameridroid.com/products/odroid-n2-home-assistant-blue-bundle-limited-edition?variant=44994940633367?ref=eeb6nfw07e)
+* [ODROID M1: 8 GB RAM / 1 TB NVMe / 64 GB eMMC ](https://ameridroid.com/products/odroid-n2-home-assistant-blue-bundle-limited-edition?variant=44994940698903?ref=eeb6nfw07e)
+* ODROID XU4: 2 GB RAM / [32 GB µSD](https://ameridroid.com/products/odroid-n2-home-assistant-blue-bundle-limited-edition?variant=44748729352471?ref=eeb6nfw07e) or [16 GB eMMC](https://ameridroid.com/products/odroid-n2-home-assistant-blue-bundle-limited-edition?variant=44748782305559?ref=eeb6nfw07e)
+
+Variants without pre-installed Home Assistant:
+
+* ODROID N2+, [2 GB RAM](https://ameridroid.com/products/odroid-n2-plus?variant=40371828719650?ref=eeb6nfw07e) or [4 GB RAM](https://ameridroid.com/products/odroid-n2-plus?variant=40371828752418?ref=eeb6nfw07e)
+* [ODROID C4](https://ameridroid.com/products/odroid-c4?ref=eeb6nfw07e)
+* [ODROID M1](https://ameridroid.com/products/odroid-M1?ref=eeb6nfw07e)
+
+* [Power Supply](https://ameridroid.com/products/12v-2a-power-supply-plug?ref=eeb6nfw07e)
+* [CR2032 Coin Cell](https://ameridroid.com/products/rtc-bios-battery?ref=eeb6nfw07e)
+* [eMMC Module](https://ameridroid.com/products/emmc-module-n2-linux-red-dot?ref=eeb6nfw07e)
+* [Case](https://ameridroid.com/products/odroid-n2-case?ref=eeb6nfw07e)
+
+* These are affiliated links. We get commissions for purchases made through links in this post.*
{% endif %}
diff --git a/source/blue/index.html b/source/blue/index.html
index 7925a686254..9b76f8d148b 100644
--- a/source/blue/index.html
+++ b/source/blue/index.html
@@ -37,6 +37,7 @@ frontpage_image: /images/frontpage/blue-frontpage.jpg
Discontinued! The edition of the Blue was — limited. We are out of stock, with no plans to relaunch this edition.
From bb07d07e8a67cd8fa1d2630a765b6dd2d852a02d Mon Sep 17 00:00:00 2001
From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
Date: Wed, 17 May 2023 09:25:41 +0200
Subject: [PATCH 04/68] Installtion w Etcher: add hint to use v1.10 (#27375)
- because there is an issue with the current version 1.18 of Balena Etcher
- https://github.com/balena-io/etcher/issues/4064
- add hint to use v1.10
---
source/_includes/installation/operating_system.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/source/_includes/installation/operating_system.md b/source/_includes/installation/operating_system.md
index b957c5961e2..ce635285b20 100644
--- a/source/_includes/installation/operating_system.md
+++ b/source/_includes/installation/operating_system.md
@@ -165,6 +165,7 @@ _Select and copy the URL or use the "copy" button that appear when you hover it.

1. When Balena Etcher has finished writing the image, you will see a confirmation.

+ * If you are having issues with Balena Etcher, try version [1.10](https://github.com/balena-io/etcher/releases/tag/v1.10.4).
### Start up your {{site.installation.types[page.installation_type].board}}
From 62ba946a78df3661e28a3597d76b55bb09c43189 Mon Sep 17 00:00:00 2001
From: Hedda
Date: Wed, 17 May 2023 10:03:27 +0200
Subject: [PATCH 05/68] Update ZHA sections about Zigbee channel and Adding
devices (#27423)
* Update zha.markdown
Rewrote the sections about "Defining Zigbee channel to use" and "Adding devices".
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
* Update source/_integrations/zha.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
---------
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
---
source/_integrations/zha.markdown | 41 ++++++++++++++++++++-----------
1 file changed, 26 insertions(+), 15 deletions(-)
diff --git a/source/_integrations/zha.markdown b/source/_integrations/zha.markdown
index 241b8495495..f7dc8cbdfef 100644
--- a/source/_integrations/zha.markdown
+++ b/source/_integrations/zha.markdown
@@ -272,6 +272,8 @@ Note: `cluster_id: 25` may also be `cluster_id: 0x0019`. The two are synonymous.
### Defining Zigbee channel to use
+Tip! Before considering to change to an other Zigbee channel on an existing Zigbee network, it is highly recommended that you read through the two segments under the [troubleshooting](#troubleshooting) section below about "*Best practices to avoid pairing/connection difficulties*" and "*Zigbee interference avoidance and network range/coverage optimization*". These sections provide prerequisite information and advice on how to achieve the best possible Zigbee network in your environment.
+
ZHA prefers to use Zigbee channel 15 by default. You can change this using YAML configuration, but this only works
if there's no existing network. To change the channel for an existing network, radio has to be factory reset and a new network to be formed. This requires re-pairing of all the devices.
@@ -283,13 +285,13 @@ zha:
channels: [15, 20, 25] # Channel mask
```
-This is a good reference for channel selection for [Zigbee and WiFi coexistance](https://support.metageek.com/hc/en-us/articles/203845040-ZigBee-and-WiFi-Coexistence).
+Note! The best practice is to not change the Zigbee channel from the ZHA default. Also, the related troubleshooting segments mentioned in the tip above will, among other things, inform that if you have issues with overlapping frequencies between Wi-Fi and Zigbee, then it is usually better to first only try changing and setting a static Wi-Fi channel on your Wi-Fi router or all your Wi-Fi access points (instead of just changing to another Zigbee channel).
-The Zigbee specification standards divide the 2.4Ghz ISM radio band into 16 Zigbee channels (i.e. distinct radio frequencies for Zigbee). For all Zigbee devices to be able to communicate, they must support the same Zigbee channel (i.e. Zigbee radio frequency) that is set on the Zigbee Coordinator as the channel to use for its Zigbee network. Not all Zigbee devices support all Zigbee channels, it will usually depend on the hardware and firmware age as well as devices power ratings.
+MetaGeek Support has a good reference article about channel selection for [Zigbee and WiFi coexistance]([https://support.metageek.com/hc/en-Ti](https://support.metageek.com/hc/en-us/articles/203845040-ZigBee-and-WiFi-Coexistence)).
-The general recommendation is to only use channels 15, 20, or 25 in order to avoid interoperability problems with Zigbee devices that are limited to only being compatible with the ZLL (Zigbee Light Link) channels as well as lessen the chance of Wi-Fi networks interfering too much with the Zigbee network. Note that especially using Zigbee channels 11, 24, 25, or 26 on your Zigbee Coordinator could mean it will probably not be accessible to older devices as those Zigbee channels are commonly only supported by relatively modern Zigbee hardware devices with newer Zigbee firmware.
+The Zigbee specification standards divide the 2.4 GHz ISM radio band into 16 Zigbee channels (i.e. distinct radio frequencies for Zigbee). For all Zigbee devices to be able to communicate, they must support the same Zigbee channel (i.e. Zigbee radio frequency) that is set on the Zigbee Coordinator as the channel to use for its Zigbee network. Not all Zigbee devices support all Zigbee channels. Channel support usually depends on the age of the hardware and firmware, as well as on the device's power ratings.
-Regardless, note that the best practice recommendation is, however, not to change the Zigbee channel from default as not all Zigbee devices support all channels. If you have issues with overlapping frequencies, then it will generally be a better idea to just change Wi-Fi channels on your Wi-Fi Router or all your Wi-Fi Access Points instead.
+The general recommendation is to only use channels 15, 20, or 25 in order to avoid interoperability problems with Zigbee devices. Not only because there is less chance of Wi-Fi networks interfering too much with the Zigbee network on other channels, but also because not all Zigbee devices support all channels. Some devices, for example, are limited to only being compatible with ZLL (Zigbee Light Link) channels. It is therefore especially not recommended to use Zigbee channels 11, 24, 25, or 26 on your Zigbee coordinator. These Zigbee channels are commonly only supported by relatively modern Zigbee hardware devices with newer Zigbee firmware. If using those channels, your coordinator may not be usable with older Zigbee devices.
### Modifying the device type
@@ -380,27 +382,36 @@ This service disables a lock code on a Zigbee lock.
## Adding devices
-To add a new device:
+Tip! It is highly recommended that you read through the two segments under the troubleshooting section below about "*Best practices to avoid pairing/connection difficulties*" and "*Zigbee interference avoidance and network range/coverage optimization*" for general prerequisite knowledge and advice on how to achieve the best possible Zigbee network in your environment.
+
+**To add a new Zigbee device:**
1. Go to the **Integrations** panel, find the **Zigbee Home Automation** integration that was added by the configuration steps above, and select **Configure**.
1. Click on the plus button at the bottom right corner to start a scan for new devices.
-1. Reset your Zigbee devices according to the device instructions provided by the manufacturer (e.g., turn on/off lights up to 10 times, switches usually have a reset button/pin). It might take a few seconds for the devices to appear. You can click on **Show logs** for more verbose output.
+1. Reset your Zigbee devices to factory default settings according to the device instructions provided by the manufacturer (e.g., turn on/off lights up to 10 times; switches usually have a reset button/pin). It might take a few seconds for the devices to appear. You can click on **Show logs** for more verbose output.
1. Once the device is found, it will appear on that page and will be automatically added to your devices. You can optionally change its name and add it to an area (you can change this later). You can search again to add another device, or you can go back to the list of added devices.
-### Using router devices
+### Using router devices to add more devices
-You use routers to increase the number of Zigbee devices that can be used in a network. The total number of Zigbee devices that you have on a Zigbee network depends on a few things, but you should know that Zigbee coordinator hardware and firmware only plays a larger role in Zigbee networks with a lot of devices. More important is how many directly connected devices ("direct children") versus how many routers are connected to your Zigbee coordinator. Zigpy library which ZHA uses has an upper limit. This is 32 direct children, but if your Zigbee coordinator hardware is powerful enough then you can still have hundreds of Zigbee devices connected through routers.
+Most mains-powered devices, e.g., many always-powered wall plugs or light bulbs in your Zigbee network will automatically act as a Zigbee router device (sometimes also referred to as a Zigbee "signal repeater" or "range extender").
-Even the least powerful Zigbee coordinator hardware supported by Zigpy is CC2530/2531 and its default firmware, only supports 20 devices connected directly to the coordinator. However, by having routers in your Zigbee network, the mesh network size can be extended. You can assume that most, if not all mains/AC-powered devices, e.g., wall-plugs and always powered-on lightbulbs in your Zigbee network can serve as a router. You can even use CC2530/CC2531 with router firmware, as additional routers (which in their turn have a limit of 21 devices).
+Because Zigbee should use a "[wireless mesh network]"(https://en.wikipedia.org/wiki/Wireless_mesh_network) to be effective, you will need to add Zigbee router devices to increase the number of Zigbee devices that can be used in your Zigbee network, both in the total number of devices that can be added as well as the total range and coverage of the network. Some Zigbee router devices do a much better job at routing and repeating Zigbee signals and messages than some other devices. You should not have a setup where Zigbee router devices (e.g. light bulbs) are often powered-off. Zigbee router devices are meant to be always available.
-An example using the default CC2531 coordinator firmware + two CC2531 routers; Your device limit will be:
+All Zigbee coordinator firmware will only allow you to directly connect a certain amount of devices. That limit is set for two reasons; firstly, to not overload the Zigbee coordinator, and secondly, to encourage your Zigbee network to quickly begin to utilize a "[mesh networking](https://en.wikipedia.org/wiki/Mesh_networking)" topology instead of only a "[star network](https://en.wikipedia.org/wiki/Star_network)" topology.
-- Coordinator: 15 devices - 2 routers = 13
-- Router one: + 21 devices
-- Router two: + 21 devices
-- Total device limit = **55 devices**
+The total number of Zigbee devices that you can have on a Zigbee network depends on a few things. The Zigbee coordinator hardware and its firmware only play a larger role in Zigbee networks with a lot of devices. More important is the number of directly connected devices ("direct children") versus the number of routers that are connected to your Zigbee coordinator. The Zigpy library, which the ZHA integration depends on, has an upper limit that is 32 direct children, but you can still have hundreds of Zigbee devices in total connected indirectly through routes via Zigbee router devices.
-### Binding and unbinding
+In this theoretical example, a CC2652-based Zigbee coordinator has three CC2530 Zigbee router devices for a total limit of 77 devices:
+
+- Coordinator: 32 Zigbee End devices - 3 routers = 29
+- Router one: + 16 devices
+- Router two: + 16 devices
+- Router three: + 16 devices
+- Total device limit = **77 devices**
+
+In practice, you will likely need to add a lot more Zigbee router devices than in this example in order to extend the coverage of the network to reach that many devices.
+
+## Binding and unbinding
ZHA support for binding and unbinding. Binding is an action in Zigbee which defines relations between two Zigbee devices, specific endpoints, and cluster id. It provides a mechanism for attaching an endpoint on one Zigbee node to one or more endpoints on another Zigbee node or Zigbee group (a group of Zigbee devices).
From cf33647d69022700f0f886a14426a56950525269 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Wed, 17 May 2023 10:58:15 +0200
Subject: [PATCH 06/68] Bump remark-lint from 9.1.1 to 9.1.2 (#27437)
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
package-lock.json | 8 ++++----
package.json | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/package-lock.json b/package-lock.json
index 7e8131ac68a..f999dba4d44 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -10,7 +10,7 @@
"devDependencies": {
"remark-cli": "^11.0.0",
"remark-frontmatter": "^4.0.1",
- "remark-lint": "^9.1.1",
+ "remark-lint": "^9.1.2",
"remark-lint-fenced-code-flag": "^3.1.1",
"remark-lint-no-shell-dollars": "^3.1.1",
"remark-stringify": "^10.0.2",
@@ -3481,9 +3481,9 @@
}
},
"node_modules/remark-lint": {
- "version": "9.1.1",
- "resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-9.1.1.tgz",
- "integrity": "sha512-zhe6twuqgkx/9KgZyNyaO0cceA4jQuJcyzMOBC+JZiAzMN6mFUmcssWZyY30ko8ut9vQDMX/pyQnolGn+Fg/Tw==",
+ "version": "9.1.2",
+ "resolved": "https://registry.npmjs.org/remark-lint/-/remark-lint-9.1.2.tgz",
+ "integrity": "sha512-m9e/aPlh7tsvfJfj8tPxrQzD6oEdb9Foko+Ya/6OwUP9EoGMfehv1Qtv26W1DoH58Wn8rT8CD+KuprTWscMmIA==",
"dev": true,
"dependencies": {
"@types/mdast": "^3.0.0",
diff --git a/package.json b/package.json
index 54136fae5cd..51516b01120 100644
--- a/package.json
+++ b/package.json
@@ -5,7 +5,7 @@
"devDependencies": {
"remark-cli": "^11.0.0",
"remark-frontmatter": "^4.0.1",
- "remark-lint": "^9.1.1",
+ "remark-lint": "^9.1.2",
"remark-lint-fenced-code-flag": "^3.1.1",
"remark-lint-no-shell-dollars": "^3.1.1",
"remark-stringify": "^10.0.2",
From c3c34f63685bf8ac791b09bd66e2e309c245aa05 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Wed, 17 May 2023 10:59:27 +0200
Subject: [PATCH 07/68] Bump google-protobuf from 3.23.0 to 3.23.1 (#27435)
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
Gemfile.lock | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Gemfile.lock b/Gemfile.lock
index c305520c31c..730069ed3c3 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -27,7 +27,7 @@ GEM
ffi (1.15.5)
ffi (1.15.5-x64-mingw32)
forwardable-extended (2.6.0)
- google-protobuf (3.23.0)
+ google-protobuf (3.23.1)
http_parser.rb (0.8.0)
i18n (1.13.0)
concurrent-ruby (~> 1.0)
From 0477f102feb85cd475960feb52aab833bf79a451 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Wed, 17 May 2023 12:55:12 +0200
Subject: [PATCH 08/68] Bump remark-lint-fenced-code-flag from 3.1.1 to 3.1.2
(#27434)
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
package-lock.json | 8 ++++----
package.json | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/package-lock.json b/package-lock.json
index f999dba4d44..299b0da3c64 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -11,7 +11,7 @@
"remark-cli": "^11.0.0",
"remark-frontmatter": "^4.0.1",
"remark-lint": "^9.1.2",
- "remark-lint-fenced-code-flag": "^3.1.1",
+ "remark-lint-fenced-code-flag": "^3.1.2",
"remark-lint-no-shell-dollars": "^3.1.1",
"remark-stringify": "^10.0.2",
"textlint": "^13.3.2",
@@ -3496,9 +3496,9 @@
}
},
"node_modules/remark-lint-fenced-code-flag": {
- "version": "3.1.1",
- "resolved": "https://registry.npmjs.org/remark-lint-fenced-code-flag/-/remark-lint-fenced-code-flag-3.1.1.tgz",
- "integrity": "sha512-FFVZmYsBccKIIEgOtgdZEpQdARtAat1LTLBydnIpyNIvcntzWwtrtlj9mtjL8ZoSRre8HtwmEnBFyOfmM/NWaA==",
+ "version": "3.1.2",
+ "resolved": "https://registry.npmjs.org/remark-lint-fenced-code-flag/-/remark-lint-fenced-code-flag-3.1.2.tgz",
+ "integrity": "sha512-yh4m3dlPmRsqM/BFhpqHYfrmBvFQ+D5dZZKDDYP2rf3YEoXlEVt8T8lWQueTTSxcq6yXAqL/XQL/iqqUHlLcHw==",
"dev": true,
"dependencies": {
"@types/mdast": "^3.0.0",
diff --git a/package.json b/package.json
index 51516b01120..130cba05cfc 100644
--- a/package.json
+++ b/package.json
@@ -6,7 +6,7 @@
"remark-cli": "^11.0.0",
"remark-frontmatter": "^4.0.1",
"remark-lint": "^9.1.2",
- "remark-lint-fenced-code-flag": "^3.1.1",
+ "remark-lint-fenced-code-flag": "^3.1.2",
"remark-lint-no-shell-dollars": "^3.1.1",
"remark-stringify": "^10.0.2",
"textlint": "^13.3.2",
From 9b7e748fc73c13539cce4e3b5b1f19a3cb6a6a1b Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Wed, 17 May 2023 12:58:41 +0200
Subject: [PATCH 09/68] Bump remark-lint-no-shell-dollars from 3.1.1 to 3.1.2
(#27433)
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
package-lock.json | 8 ++++----
package.json | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/package-lock.json b/package-lock.json
index 299b0da3c64..9ad0c999087 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -12,7 +12,7 @@
"remark-frontmatter": "^4.0.1",
"remark-lint": "^9.1.2",
"remark-lint-fenced-code-flag": "^3.1.2",
- "remark-lint-no-shell-dollars": "^3.1.1",
+ "remark-lint-no-shell-dollars": "^3.1.2",
"remark-stringify": "^10.0.2",
"textlint": "^13.3.2",
"textlint-filter-rule-comments": "^1.2.2",
@@ -3514,9 +3514,9 @@
}
},
"node_modules/remark-lint-no-shell-dollars": {
- "version": "3.1.1",
- "resolved": "https://registry.npmjs.org/remark-lint-no-shell-dollars/-/remark-lint-no-shell-dollars-3.1.1.tgz",
- "integrity": "sha512-Q3Ad1TaOPxbYog5+Of/quPG3Fy+dMKiHjT8KsU7NDiHG6YJOnAJ3f3w+y13CIlNIaKc/MrisgcthhrZ7NsgXfA==",
+ "version": "3.1.2",
+ "resolved": "https://registry.npmjs.org/remark-lint-no-shell-dollars/-/remark-lint-no-shell-dollars-3.1.2.tgz",
+ "integrity": "sha512-np2MDEhXHviXhbQFjnC1QYv5/fxCV1cIHfGMoJpqiW7Zcu/UGCOo5TE3XswZH4ukHZJ65c3X2A6qfLDW+ur3CQ==",
"dev": true,
"dependencies": {
"@types/mdast": "^3.0.0",
diff --git a/package.json b/package.json
index 130cba05cfc..b7bc0b6d4ea 100644
--- a/package.json
+++ b/package.json
@@ -7,7 +7,7 @@
"remark-frontmatter": "^4.0.1",
"remark-lint": "^9.1.2",
"remark-lint-fenced-code-flag": "^3.1.2",
- "remark-lint-no-shell-dollars": "^3.1.1",
+ "remark-lint-no-shell-dollars": "^3.1.2",
"remark-stringify": "^10.0.2",
"textlint": "^13.3.2",
"textlint-filter-rule-comments": "^1.2.2",
From 253ebcf3ef6e968c00e276a921ff9a98067d8c29 Mon Sep 17 00:00:00 2001
From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
Date: Wed, 17 May 2023 12:59:36 +0200
Subject: [PATCH 10/68] Google assistant: Add missing domains (#27411)
---
.../_integrations/google_assistant.markdown | 22 ++++++++++---------
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/source/_integrations/google_assistant.markdown b/source/_integrations/google_assistant.markdown
index 4d652ef5fd6..524bd77e605 100644
--- a/source/_integrations/google_assistant.markdown
+++ b/source/_integrations/google_assistant.markdown
@@ -271,21 +271,23 @@ Currently, the following domains are available to be used with Google Assistant,
- alarm_control_panel (arm/disarm)
- button (scene)
- camera (streaming, requires compatible camera)
-- group (on/off)
-- input_boolean (on/off)
-- input_select (option/setting/mode/value)
-- scene (on)
-- script (on)
-- switch (on/off)
+- climate (temperature setting, hvac_mode)
+- cover (on/off/set position)
- fan (on/off/speed percentage/preset mode)
+- group (on/off)
+- humidifier (humidity setting/on/off/mode)
+- input_boolean (on/off)
+- input_button
+- input_select (option/setting/mode/value)
- light (on/off/brightness/rgb color/color temp)
- lock
-- cover (on/off/set position)
- media_player (on/off/set volume (via set volume)/source (via set input source)/control playback)
-- climate (temperature setting, hvac_mode)
-- vacuum (dock/start/stop/pause)
+- scene (on)
+- script (on)
+- select
- sensor (temperature setting for temperature sensors and humidity setting for humidity sensors)
-- humidifier (humidity setting/on/off/mode)
+- switch (on/off)
+- vacuum (dock/start/stop/pause)
From 633dc7e041a5aedfa55da102297f2385ad4487f7 Mon Sep 17 00:00:00 2001
From: Smart Home Junkie <67226335+smarthomejunkie@users.noreply.github.com>
Date: Wed, 17 May 2023 15:57:42 +0200
Subject: [PATCH 13/68] Added Video Tutorial (#27427)
---
source/_integrations/proximity.markdown | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/source/_integrations/proximity.markdown b/source/_integrations/proximity.markdown
index 6824c5d428a..37b9c0a87ab 100644
--- a/source/_integrations/proximity.markdown
+++ b/source/_integrations/proximity.markdown
@@ -52,6 +52,11 @@ proximity:
unit_of_measurement: mi
```
+### Video Tutorial
+This video tutorial explains how to set up geofencing in Home Assistant using the proximity integration.
+
+
+
{% configuration %}
zone:
description: The zone to which this integration is measuring the distance to. Default is the home zone.
From 4c80df89b4ae09d0f1bc08dac776543ca8df6be0 Mon Sep 17 00:00:00 2001
From: Joost Lekkerkerker
Date: Wed, 17 May 2023 20:05:44 +0200
Subject: [PATCH 14/68] Update openuv.markdown (#27445)
---
source/_integrations/openuv.markdown | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/source/_integrations/openuv.markdown b/source/_integrations/openuv.markdown
index 24837fc29f1..19c104b0b8f 100644
--- a/source/_integrations/openuv.markdown
+++ b/source/_integrations/openuv.markdown
@@ -28,8 +28,7 @@ trained medical professional.
## Generating an API Key
-To generate an API key,
-[simply log in to the OpenUV website](https://www.openuv.io/auth/google).
+To generate an API key, simply log in at [the OpenUV website](https://www.openuv.io/).
{% include integrations/config_flow.md %}
From 577228c7d7970c3f00ba3e7bb6b240714732b462 Mon Sep 17 00:00:00 2001
From: Smart Home Junkie <67226335+smarthomejunkie@users.noreply.github.com>
Date: Thu, 18 May 2023 12:37:30 +0200
Subject: [PATCH 15/68] Added a video tutorial (#27453)
* Added a video tutorial
* Update source/_integrations/google_sheets.markdown
---------
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
---
source/_integrations/google_sheets.markdown | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/source/_integrations/google_sheets.markdown b/source/_integrations/google_sheets.markdown
index 29380f28e80..9d4beb968fb 100644
--- a/source/_integrations/google_sheets.markdown
+++ b/source/_integrations/google_sheets.markdown
@@ -72,6 +72,11 @@ The integration setup will next give you instructions to enter the [Application
If you have an error with your credentials you can delete them in the [Application Credentials](/integrations/application_credentials/) user interface.
+### Video Tutorial
+This video tutorial explains how to set up the Google Sheets integration and how you can add data from Home Assistant to a Google Sheet.
+
+
+
### Service `google_sheets.append_sheet`
You can use the service `google_sheets.append_sheet` to add a row of data to the Sheets document created at setup.
From fd9f0a526e1d74e9a262d90a9f6a016a890e5493 Mon Sep 17 00:00:00 2001
From: Sven Serlier <85389871+wrt54g@users.noreply.github.com>
Date: Thu, 18 May 2023 13:37:56 +0200
Subject: [PATCH 16/68] Small documentation improvements (#27440)
* Update light URLs
* Update light.markdown
* Update light.markdown
* Update URL
* Small improvements to blueprint documentation
* Fix
* Update source/_docs/automation/using_blueprints.markdown
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
---------
Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
---
source/_docs/automation/using_blueprints.markdown | 4 ++--
source/_integrations/light.markdown | 6 +++---
source/examples/index.markdown | 2 +-
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/source/_docs/automation/using_blueprints.markdown b/source/_docs/automation/using_blueprints.markdown
index 7bb8172c77c..1d9c86b97c2 100644
--- a/source/_docs/automation/using_blueprints.markdown
+++ b/source/_docs/automation/using_blueprints.markdown
@@ -13,11 +13,11 @@ Quick links:
Automations based on a blueprint only need to be configured to be used. What needs to be configured differs on each blueprint.
-To create your first automation based on a blueprint, go to **{% my config %}** -> **Automations & Scenes** -> **{% my blueprints %}**. Find the blueprint that you want to use and click on "Create Automation".
+To create your first automation based on a blueprint, go to **{% my blueprints title="Settings > Automations & Scenes > Blueprints" %}**. Find the blueprint that you want to use and select **Create Automation**.
This will open the automation editor with the blueprint selected. Give it a name and configure the blueprint and click on the blue button "Save Automation" in the bottom right.
-Done! If you want to revisit the configuration values, you can find it by going to **{% my config %}** and then **{% my automations %}**.
+Done! If you want to revisit the configuration values, you can find it by going to **Settings** and then **{% my blueprints %}**.
## Importing blueprints
diff --git a/source/_integrations/light.markdown b/source/_integrations/light.markdown
index ded61b41d64..51de2262b40 100644
--- a/source/_integrations/light.markdown
+++ b/source/_integrations/light.markdown
@@ -43,7 +43,7 @@ Most lights do not support all attributes. You can check the integration documen
| ---------------------- | -------- | ----------- |
| `entity_id` | no | String or list of strings that point at `entity_id`s of lights. To target all lights, set `entity_id` to `all`.
| `transition` | yes | Number that represents the time (in seconds) the light should take to transition to the new state.
-| `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define an xy color, brightness and a transition value (if no transition is desired, set to 0 or leave out the column entirely). If a profile is given, and a brightness is set, then the profile brightness will be overwritten.
+| `profile` | yes | String with the name of one of the [built-in profiles](https://github.com/home-assistant/core/blob/master/homeassistant/components/light/light_profiles.csv) (relax, energize, concentrate, reading) or one of the custom profiles defined in `light_profiles.csv` in the current working directory. Light profiles define an xy color, brightness and a transition value (if no transition is desired, set to 0 or leave out the column entirely). If a profile is given, and a brightness is set, then the profile brightness will be overwritten.
| `hs_color` | yes | A list containing two floats representing the hue and saturation of the color you want the light to be. Hue is scaled 0-360, and saturation is scaled 0-100.
| `xy_color` | yes | A list containing two floats representing the xy color you want the light to be. Two comma-separated floats that represent the color in XY.
| `rgb_color` | yes | A list containing three integers between 0 and 255 representing the RGB color you want the light to be. Three comma-separated integers that represent the color in RGB, within square brackets.
@@ -116,6 +116,6 @@ Turns one or multiple lights off.
### Service `light.toggle`
-Toggles the state of one or multiple lights. Takes the same arguments as [`turn_on`](#service-lightturn_on) service.
+Toggles the state of one or multiple lights. Takes the same arguments as the [`light.turn_on`](#service-lightturn_on) service.
-*Note*: If `light.toggle` is used for a group of lights, it will toggle the individual state of each light. If you want the lights to be treated as a single light, use [Light Groups](/integrations/light.group/) instead.
+*Note*: If `light.toggle` is used for a group of lights, it will toggle the individual state of each light. If you want the lights to be treated as a single light, use [Light Groups](/integrations/group#binary-sensor-light-and-switch-groups) instead.
diff --git a/source/examples/index.markdown b/source/examples/index.markdown
index 8190d71582d..ed4f75ad7dd 100644
--- a/source/examples/index.markdown
+++ b/source/examples/index.markdown
@@ -21,7 +21,7 @@ A great place to find popular configurations is on this
## Popular Blueprints
-This is a list of the most popular [blueprints](/integrations/blueprint) in the [Blueprint Exchange category on the forums](https://www.home-assistant.io/get-blueprints).
+This is a list of the most popular [blueprints](/docs/automation/using_blueprints/) in the [Blueprint Exchange category on the forums](https://www.home-assistant.io/get-blueprints).
{% for post in site.data.blueprint_exchange_data limit:25 %}
From ed295ee6ebb88334c0f01b75ded346b2995a1354 Mon Sep 17 00:00:00 2001
From: Michel van de Wetering
Date: Thu, 18 May 2023 22:17:13 +0200
Subject: [PATCH 17/68] Remove duplicated text and minor text fix (#27455)
---
source/_docs/blueprint/selectors.markdown | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/source/_docs/blueprint/selectors.markdown b/source/_docs/blueprint/selectors.markdown
index a47a614d0d7..7698fb824a7 100644
--- a/source/_docs/blueprint/selectors.markdown
+++ b/source/_docs/blueprint/selectors.markdown
@@ -561,8 +561,7 @@ include_entities:
filter:
description: >
When filter options are provided, the entities are limited by entities
- that at least match the given conditions. Can be either a object or a list of object.
- Can be either a object or a list of object.
+ that at least match the given conditions. Can be either an object or a list of objects.
type: list
required: false
keys:
From 653229e0e2dc097d8e72105b21809477c361cf53 Mon Sep 17 00:00:00 2001
From: Sven Serlier <85389871+wrt54g@users.noreply.github.com>
Date: Fri, 19 May 2023 15:17:41 +0200
Subject: [PATCH 18/68] Update wiz URLs (#27458)
* Update wiz URLs
* Update more URLs
---
source/_integrations/wiz.markdown | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/source/_integrations/wiz.markdown b/source/_integrations/wiz.markdown
index fcd79394edb..310903f511e 100644
--- a/source/_integrations/wiz.markdown
+++ b/source/_integrations/wiz.markdown
@@ -37,7 +37,7 @@ These devices have been sold under at least the following brands:
- [Atom Lighting](https://atomlighting.com.au/)
- [ATX LED](https://atxledinc.com/)
- [Brilliant](https://www.brilliantlightsource.com/)
-- [Designers Fountain](https://designersftn.com/default.dmx)
+- [Designers Fountain](https://designersfountain.com/)
- [Evoluziona](https://tecnolite.mx/)
- [Fischer & Honsel](https://fischer-honsel.com/)
- [Gauss](https://gauss.ru/smartlight/products/)
@@ -47,12 +47,12 @@ These devices have been sold under at least the following brands:
- [Lednify](https://lednify.com/)
- [Leyton](https://www.leyton-lighting.co.uk/)
- [Liteline](https://www.liteline.com/page/oncloud)
-- [Lutec](https://www.lutec.com/highlight/wiz)
+- [Lutec](https://www.lutec.com/segments/connected)
- [Philips Smart LED lights with WiZ Connected](https://www.usa.lighting.philips.com/consumer/smart-wifi-led)
- [Spex](https://spexlighting.com/pages/smart-lights)
- [SLV](https://www.slv.com/)
- [Trenz](https://trenzlighting.com/pages/smart-lights)
-- [Trio](https://wiz.trio-lighting.com/en/)
+- [Trio](https://wiz.trio-lighting.com/)
- [Wofi](https://wofi-wiz.com/)
The integration can report the state of occupancy sensors that have been linked to a device.
@@ -61,8 +61,8 @@ The integration can report the state of occupancy sensors that have been linked
## Connect WiZ devices to your network
-To connect a WiZ device to your Wi-Fi network, please follow the instructions in the [WiZ app](https://www.wizconnected.com/en/consumer/app/) (available for iOS and Android).
-If you have further questions, please have a look at the [WiZ Support Page](https://www.wizconnected.com/en/consumer/support/).
+To connect a WiZ device to your Wi-Fi network, please follow the instructions in the [WiZ app](https://www.wizconnected.com/en-us/explore-wiz/app) (available for iOS and Android).
+If you have further questions, please have a look at the [WiZ Support Page](https://www.wizconnected.com/en-us/support/faq).
### Enable local connectivity
From 166804fa7810898e0bfa577d28fe8f9eda6ab473 Mon Sep 17 00:00:00 2001
From: Sven Serlier <85389871+wrt54g@users.noreply.github.com>
Date: Sat, 20 May 2023 10:02:58 +0200
Subject: [PATCH 19/68] Update URLs (#27463)
* Update homekit.markdown
* Update network.markdown
* Update homekit.markdown
* Update URL
* Update URLs
* Update another URL
* Update URL
---
source/_integrations/homekit.markdown | 14 +++++++-------
source/_integrations/homekit_controller.markdown | 4 ++--
source/_integrations/network.markdown | 2 +-
source/help/index.markdown | 2 +-
4 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/source/_integrations/homekit.markdown b/source/_integrations/homekit.markdown
index e210a13274b..1d39e96b1a0 100644
--- a/source/_integrations/homekit.markdown
+++ b/source/_integrations/homekit.markdown
@@ -318,7 +318,7 @@ The HomeKit Accessory Protocol Specification only allows a maximum of 150 unique
### Multiple HomeKit instances
-If you create a HomeKit integration via the UI (i.e., **Settings** -> **Devices & Services**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port.
+If you create a HomeKit integration via the UI (i.e., **Settings** > **Devices & Services**), it must be configured via the UI **only**. While the UI only offers limited configuration options at the moment, any attempt to configure a HomeKit instance created in the UI via the `configuration.yaml` file will result in another instance of HomeKit running on a different port.
It is recommended to only edit a HomeKit instance in the UI that was created in the UI, and likewise, only edit a HomeKit instance in YAML that was created in YAML.
@@ -328,7 +328,7 @@ When exposing a Camera, Activity based remote (a `remote` that supports activiti
To quickly add all accessory mode entities in the UI:
-1. Create a new bridge via the UI (i.e., **{% my config_flow_start title="Settings >> Devices & Services" domain=page.ha_domain %}**).
+1. Create a new bridge via the UI (i.e., **{% my config_flow_start title="Settings > Devices & Services" domain=page.ha_domain %}**).
2. Select `media_player`, `remote`, `lock`, and `camera` domains.
3. Complete the flow as normal.
4. Additional HomeKit entries for each entity that must operate in accessory mode will be created for each entity that does not already have one.
@@ -337,7 +337,7 @@ To quickly add all accessory mode entities in the UI:
To add a single entity in accessory mode:
-1. Create a new bridge via the UI (i.e., **{% my config_flow_start title="Settings >> Devices & Services" domain=page.ha_domain %}**)
+1. Create a new bridge via the UI (i.e., **{% my config_flow_start title="Settings > Devices & Services" domain=page.ha_domain %}**)
2. Before pairing the bridge, access the options for the bridge.
3. Change the mode to `accessory`
4. Select the entity.
@@ -424,7 +424,7 @@ The following integrations are currently supported:
# Device Triggers
-Devices that support triggers can be added to the bridge by accessing options for the bridge in **{% my integrations title="Settings >> Devices & Services" %}**. To use this feature, Advanced Mode must be enabled in your user profile.
+Devices that support triggers can be added to the bridge by accessing options for the bridge in **{% my integrations title="Settings > Devices & Services" %}**. To use this feature, Advanced Mode must be enabled in your user profile.
Bridged device triggers are represented as a single press button on stateless programmable switches. This allows a HomeKit automation to run when a device trigger fires. Because the Apple Home app currently only shows the number of the button and not the name, users may find it easier to identify the name of the button in the `Eve for HomeKit` app.
@@ -549,7 +549,7 @@ Remember that the iOS device needs to be in the same local network as the Home A
#### `Home Assistant Bridge` doesn't appear in the Home App (for pairing) - Docker
-Set `network_mode: host` in your `docker-compose.yaml`. If you have further problems this [issue](https://github.com/home-assistant/home-assistant/issues/15692) might help.
+Set `network_mode: host` in your `docker-compose.yaml`. If you have further problems this [issue](https://github.com/home-assistant/core/issues/15692) might help.
You can also try to use `avahi-daemon` in reflector mode together with the option `advertise_ip`, see above.
@@ -592,7 +592,7 @@ To use the HomeKit integration with multiple different Home Assistant instances
#### Specific entity doesn't work
-Although we try our best, some entities don't work with the HomeKit integration yet. The result will be that either pairing fails completely or all Home Assistant accessories will stop working. Use the filter to identify which entity is causing the issue. It's best to try pairing and step by step including more entities. If it works, unpair and repeat until you find the one that is causing the issues. To help others and the developers, please open a new issue here: [home-assistant/issues/new](https://github.com/home-assistant/home-assistant/issues/new?labels=component:%20homekit)
+Although we try our best, some entities don't work with the HomeKit integration yet. The result will be that either pairing fails completely or all Home Assistant accessories will stop working. Use the filter to identify which entity is causing the issue. It's best to try pairing and step by step including more entities. If it works, unpair and repeat until you find the one that is causing the issues. To help others and the developers, please open a new issue here: [core/issues/new](https://github.com/home-assistant/core/issues/new)
If you have any iOS 12.x devices signed into your iCloud account, media player entities with `device_class: tv` may trigger this condition. Filtering the entity or signing the iOS 12.x device out of iCloud should resolve the issue after restarting other devices.
@@ -626,7 +626,7 @@ Ensure that the [`ffmpeg`](/integrations/ffmpeg) integration is configured corre
#### Camera streaming is unstable or slow
-If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Settings** -> **Devices & Services** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen.
+If your camera supports native H.264 streams, Home Assistant can avoid converting the video stream, which is an expensive operation. To enable native H.264 streaming when configured via YAML, change the `video_codec` to `copy`. To allow native H.264 streaming when setting up HomeKit via the UI, go to **Settings** > **Devices & Services** in the UI, click **Options** for your HomeKit Bridge, and check the box for your camera on the `Cameras that support native H.264 streams` screen.
#### Multiple camera streams
diff --git a/source/_integrations/homekit_controller.markdown b/source/_integrations/homekit_controller.markdown
index 8dffa6a9af4..fc4668590ad 100644
--- a/source/_integrations/homekit_controller.markdown
+++ b/source/_integrations/homekit_controller.markdown
@@ -43,7 +43,7 @@ ha_platforms:
ha_integration_type: integration
---
-The [HomeKit](https://developer.apple.com/homekit/) controller integration allows you to connect accessories with the "Works with HomeKit" logo to Home Assistant. This integration should not be confused with the [HomeKit](/integrations/homekit/) integration, which allows you to control Home Assistant devices via HomeKit.
+The [HomeKit](https://developer.apple.com/apple-home/) controller integration allows you to connect accessories with the "Works with HomeKit" logo to Home Assistant. This integration should not be confused with the [HomeKit](/integrations/homekit/) integration, which allows you to control Home Assistant devices via HomeKit.
The integration will automatically detect HomeKit compatible devices that are ready to pair if the [`zeroconf`](/integrations/zeroconf/) integration is enabled. This is enabled by default on new installations via the [`default_config`](/integrations/default_config/) component.
@@ -165,7 +165,7 @@ homekit:
`netdisco` is not used by Home Assistant to discover HomeKit devices, so if it can't see your device the problem is more likely to be environmental than with Home Assistant itself.
-Alternatively if you are less comfortable with the command line you could use Discovery for [Mac](https://apps.apple.com/us/app/discovery-dns-sd-browser/id1381004916?mt=12) or [iOS](https://apps.apple.com/us/app/discovery-dns-sd-browser/id305441017), Android [Service Browser](https://play.google.com/store/apps/details?id=com.druk.servicebrowser) or [All My Lan](https://www.microsoft.com/en-us/p/all-my-lan/9wzdncrdn19v). These are a less useful diagnostic as they aren't running from the same point on your network as Home Assistant. Even if it is visible in this tool it might still be a networking issue. They can give sometimes give clues.
+Alternatively if you are less comfortable with the command line you could use Discovery for [Mac](https://apps.apple.com/app/discovery-dns-sd-browser/id1381004916) or [iOS](https://apps.apple.com/app/discovery-dns-sd-browser/id305441017), Android [Service Browser](https://play.google.com/store/apps/details?id=com.druk.servicebrowser) or [All My Lan](https://apps.microsoft.com/store/detail/all-my-lan/9WZDNCRDN19V). These are a less useful diagnostic as they aren't running from the same point on your network as Home Assistant. Even if it is visible in this tool it might still be a networking issue. They can give sometimes give clues.
Where a discovery tool does give an IP, check it is what you expect (compare to DHCP leases in your router for example). Can you ping it? If not, you have a network problem.
diff --git a/source/_integrations/network.markdown b/source/_integrations/network.markdown
index 2fd4134e2e1..5b072d06246 100644
--- a/source/_integrations/network.markdown
+++ b/source/_integrations/network.markdown
@@ -12,7 +12,7 @@ ha_codeowners:
ha_integration_type: system
---
-This integration provides network configuration for integrations such as [Zeroconf](/integrations/zeroconf/). It is managed by going to **{% my network title="Settings >> System >> Network" %}** and is only available to users that have "Advanced Mode" enabled on their {% my profile title="user profile" %}.
+This integration provides network configuration for integrations such as [Zeroconf](/integrations/zeroconf/). It is managed by going to **{% my network title="Settings > System > Network" %}** and is only available to users that have "Advanced Mode" enabled on their {% my profile title="user profile" %}.
**{% my general badge %}**
diff --git a/source/help/index.markdown b/source/help/index.markdown
index 1d543e03304..67511627956 100644
--- a/source/help/index.markdown
+++ b/source/help/index.markdown
@@ -91,4 +91,4 @@ Don't miss the regular [Home Assistant podcasts](https://hasspodcast.io/).
[twitter]: https://twitter.com/home_assistant
[facebook]: https://www.facebook.com/homeassistantio
[reddit]: https://reddit.com/r/homeassistant
-[discord]: https://discord.gg/c5DvZ4e
+[discord]: /join-chat
From 1aa2a003a210ff71f31c0c3c9828df5e09622c43 Mon Sep 17 00:00:00 2001
From: Jan Bouwhuis
Date: Sat, 20 May 2023 19:53:15 +0200
Subject: [PATCH 20/68] Add notes on Nuki Smart Lock 3.0 Pro MQTT support
(#27467)
Co-authored-by: Franck Nijhof
---
source/_integrations/mqtt.markdown | 2 +-
source/_integrations/nuki.markdown | 5 +++++
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/source/_integrations/mqtt.markdown b/source/_integrations/mqtt.markdown
index ab89f6c9866..e286cf78b8d 100644
--- a/source/_integrations/mqtt.markdown
+++ b/source/_integrations/mqtt.markdown
@@ -536,7 +536,7 @@ The following software has built-in support for MQTT discovery:
- [IOTLink](https://iotlink.gitlab.io) (starting with 2.0.0)
- [MiFlora MQTT Daemon](https://github.com/ThomDietrich/miflora-mqtt-daemon)
- [Nuki Hub](https://github.com/technyon/nuki_hub)
-- [Nuki Smart Lock 3.0 Pro](https://support.nuki.io/hc/en-us/articles/12947926779409-MQTT-support)
+- [Nuki Smart Lock 3.0 Pro](https://support.nuki.io/hc/en-us/articles/12947926779409-MQTT-support), [more info](https://developer.nuki.io/t/mqtt-api-specification-v1-3/17626)
- [OpenMQTTGateway](https://github.com/1technophile/OpenMQTTGateway)
- [room-assistant](https://github.com/mKeRix/room-assistant) (starting with 1.1.0)
- [SmartHome](https://github.com/roncoa/SmartHome)
diff --git a/source/_integrations/nuki.markdown b/source/_integrations/nuki.markdown
index e9accbf5268..a7a714e3e37 100644
--- a/source/_integrations/nuki.markdown
+++ b/source/_integrations/nuki.markdown
@@ -68,3 +68,8 @@ Events generated by Nuki are sent as events of type `nuki_event` with the follow
| -------------------- | ------------------------------------------ |
| `type` | The type of the event. Values: `ring`
| `entity_id` | The ID of the entity generating the event.
+
+## MQTT support
+
+The Nuki Smart Lock 3.0 Pro also [supports MQTT](https://support.nuki.io/hc/en-us/articles/12947926779409-MQTT-support) and can directly integrate with Home Assistant through [MQTT discovery](/integrations/mqtt/#mqtt-discovery).
+Specific information can be found [here](https://developer.nuki.io/t/mqtt-api-specification-v1-3/17626).
From a507c67b2bd6a7f1a8c9a41d37a1967d7cf28e0b Mon Sep 17 00:00:00 2001
From: Ersin
Date: Sun, 21 May 2023 15:54:43 +0300
Subject: [PATCH 21/68] Update missing installation dependencies on core.md
(#26657)
---
source/_includes/installation/core.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_includes/installation/core.md b/source/_includes/installation/core.md
index a031f3f251c..fe693fe710b 100644
--- a/source/_includes/installation/core.md
+++ b/source/_includes/installation/core.md
@@ -33,7 +33,7 @@ sudo apt-get upgrade -y
Install the dependencies:
```bash
-sudo apt-get install -y python3 python3-dev python3-venv python3-pip bluez libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libopenjp2-7 libtiff5 libturbojpeg0-dev tzdata
+sudo apt-get install -y python3 python3-dev python3-venv python3-pip bluez libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libopenjp2-7 libtiff5 libturbojpeg0-dev tzdata ffmpeg liblapack3 liblapack-dev libatlas-base-dev
```
The above-listed dependencies might differ or missing, depending on your system or personal use of Home Assistant.
From 55d1025b17f41090e7ab0c9ad5d67999ef67e74a Mon Sep 17 00:00:00 2001
From: Nir Yeffet <1157065+niryeffet@users.noreply.github.com>
Date: Sun, 21 May 2023 07:51:06 -0700
Subject: [PATCH 22/68] Update temper.markdown (#27476)
---
source/_integrations/temper.markdown | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/source/_integrations/temper.markdown b/source/_integrations/temper.markdown
index b1d5b617243..1013684a707 100644
--- a/source/_integrations/temper.markdown
+++ b/source/_integrations/temper.markdown
@@ -35,10 +35,10 @@ scale:
type: integer
default: 1
name:
- description: The name to use when displaying this switch.
+ description: The name to use when displaying this sensor.
required: false
type: string
- default: myStrom Switch
+ default: Unnamed Device
{% endconfiguration %}
Since some of these sensors consistently show higher temperatures the scale and offset values can be used to fine-tune your sensor.
From 00d07643d8d846007ff9066830b4ee313e705523 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon, 22 May 2023 09:20:42 +0200
Subject: [PATCH 23/68] Bump nokogiri from 1.15.0 to 1.15.1 (#27480)
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
Gemfile | 2 +-
Gemfile.lock | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Gemfile b/Gemfile
index 6a78aea9229..41ccb5ea685 100644
--- a/Gemfile
+++ b/Gemfile
@@ -20,7 +20,7 @@ group :jekyll_plugins do
end
gem 'sinatra', '3.0.6'
-gem 'nokogiri', '1.15.0'
+gem 'nokogiri', '1.15.1'
# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
# and associated library
diff --git a/Gemfile.lock b/Gemfile.lock
index 730069ed3c3..8c66426287d 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -72,7 +72,7 @@ GEM
multi_json (1.15.0)
mustermann (3.0.0)
ruby2_keywords (~> 0.0.1)
- nokogiri (1.15.0)
+ nokogiri (1.15.1)
mini_portile2 (~> 2.8.2)
racc (~> 1.4)
pathutil (0.16.2)
@@ -129,7 +129,7 @@ DEPENDENCIES
jekyll-paginate (= 1.1.0)
jekyll-sitemap (= 1.4.0)
jekyll-toc (= 0.18.0)
- nokogiri (= 1.15.0)
+ nokogiri (= 1.15.1)
rake (= 13.0.6)
sass-globbing (= 1.1.5)
sassc (= 2.1.0)
From fb011ba0442ee00586f260cc4312d525bf147278 Mon Sep 17 00:00:00 2001
From: Smart Home Junkie <67226335+smarthomejunkie@users.noreply.github.com>
Date: Mon, 22 May 2023 10:15:38 +0200
Subject: [PATCH 24/68] Added a video tutorial (#27473)
---
source/_integrations/feedreader.markdown | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/source/_integrations/feedreader.markdown b/source/_integrations/feedreader.markdown
index dcc44b604d0..9052eaa6c05 100644
--- a/source/_integrations/feedreader.markdown
+++ b/source/_integrations/feedreader.markdown
@@ -89,6 +89,11 @@ automation:
Any field under the `` tag in the feed can be used for example `trigger.event.data.content` will get the body of the feed entry.
+### Video Tutorial
+This video tutorial explains how to set up the feedreader and show the latest news feed item on your dashboard in Home Assistant.
+
+
+
For more advanced use cases, a custom integration registering to the `feedreader` event type could be used instead:
```python
From 09bc5c2e11b85ae7977f4a3235623cb7b4c18a63 Mon Sep 17 00:00:00 2001
From: "J. Nick Koston"
Date: Mon, 22 May 2023 11:45:44 -0500
Subject: [PATCH 25/68] Update Yale Access Bluetooth with better
troubleshooting steps (#27484)
Co-authored-by: Franck Nijhof
---
source/_integrations/yalexs_ble.markdown | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/source/_integrations/yalexs_ble.markdown b/source/_integrations/yalexs_ble.markdown
index 8533280f507..8d3e06fde2f 100644
--- a/source/_integrations/yalexs_ble.markdown
+++ b/source/_integrations/yalexs_ble.markdown
@@ -50,6 +50,10 @@ These devices do not send updates, but can be locked and unlocked.
- MD-04I (Yale Conexis L1, Yale Conexis L2)
- YRCB-490 (Yale Smart Cabinet Lock)
+## Troubleshooting
+
+Lock operation requires setting up an encrypted connection highly sensitive to latency. It is recommended to use a [High-Performance Bluetooth adapter](/integrations/bluetooth/#known-working-high-performance-adapters) or [ESPHome Bluetooth proxy](/integrations/bluetooth/#remote-adapters-bluetooth-proxies) for stable operation.
+
## Push updates
Some locks only send push updates when they have an active HomeKit pairing. If your lock is not sending push updates, ensure it's paired with a HomeKit using an iOS device or the HomeKit controller integration. The lock cannot be paired via HomeKit Controller and the Yale Access Bluetooth integration on the same Home Assistant instance as they will both try to access the lock simultaneously and fail.
@@ -58,18 +62,19 @@ One easy way to fix this is to create a new/second home in the Apple Home app an
Alternatively, call the `homeassistant.update_entity` service to force the integration to update the lock state.
+If the lock does not support push updates via advertisements or you want lock operation to be more responsive, you can enable always connected mode. Always connected will cause the lock to stay connected to Home Assistant via Bluetooth, which will use more battery.
+
## Door Sensors
The lock must be calibrated in the Yale Access App for the door sensors to function correctly. If the door sensor has an unknown state or is not updating, try recalibrating the lock in the app.
-
## Obtaining the offline key
The offline key and slot number are required to operate the lock. These credentials can be found in multiple places depending on the lock brand and model.
-### Yale Access or August Cloud
+### Yale Access, Yale Home, or August Cloud
-The [August](/integrations/august) integration can automatically provision the offline key if the configured account has the key loaded. You may need to create or use a non-primary existing account with owner-level access to the lock, as not all accounts will have the key loaded.
+The [August](/integrations/august) integration can automatically provision the offline key if the configured account has the key loaded. You may need to create or use a non-primary existing account with owner-level access to the lock, as not all accounts will have the key loaded. If the lock was not discovered by Home Assistant when the cloud integration was loaded, reload the cloud integration once the lock has been discovered.
If the offline key can automatically be provisioned, you will not be asked to enter it and the integration should be automatically added, configured and running.
From f7385a2d31e1a576fb6370ffbaae8ff1073ee626 Mon Sep 17 00:00:00 2001
From: Erik Montnemery
Date: Tue, 23 May 2023 15:08:24 +0200
Subject: [PATCH 26/68] Improve template sensor documentation (#27492)
Co-authored-by: Franck Nijhof
---
source/_integrations/template.markdown | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/source/_integrations/template.markdown b/source/_integrations/template.markdown
index 9228e8ed5fc..5c929d280ea 100644
--- a/source/_integrations/template.markdown
+++ b/source/_integrations/template.markdown
@@ -113,7 +113,7 @@ sensor:
type: map
keys:
state:
- description: Defines a template to get the state of the sensor.
+ description: "Defines a template to get the state of the sensor. If the sensor is numeric, i.e. it has a `state_class` or a `unit_of_measurement`, the state template must render to a number or to `none`. The state template must not render to a string, including `unknown` or `unavailable`. An `availability` template may be defined to suppress rendering of the state template."
required: true
type: template
unit_of_measurement:
@@ -460,6 +460,8 @@ template:
### State based sensor changing the unit of measurement of another sensor
With a Template Sensor, it's easy to convert given values into others if the unit of measurement doesn't fit your needs.
+Because the sensors do math on the source sensor's state and need to render to a numeric value, an availability template is used
+to suppress rendering of the state template if the source sensor does not have a valid numeric state.
{% raw %}
@@ -469,10 +471,12 @@ template:
- name: "Transmission Down Speed"
unit_of_measurement: "kB/s"
state: "{{ states('sensor.transmission_down_speed')|float * 1024 }}"
+ availability: "{{ is_number(states('sensor.transmission_down_speed')) }}"
- name: "Transmission Up Speed"
unit_of_measurement: "kB/s"
state: "{{ states('sensor.transmission_up_speed')|float * 1024 }}"
+ availability: "{{ is_number(states('sensor.transmission_up_speed')) }}"
```
{% endraw %}
From 3ab89974a8102204e7202578912bc2922ec58ae1 Mon Sep 17 00:00:00 2001
From: Franck Nijhof
Date: Tue, 23 May 2023 23:53:23 +0200
Subject: [PATCH 27/68] 2023.5.4 (#27497)
---
_config.yml | 4 +-
.../_posts/2023-05-03-release-20235.markdown | 102 ++++++++++++++++++
2 files changed, 104 insertions(+), 2 deletions(-)
diff --git a/_config.yml b/_config.yml
index 32b628f3321..0556aa9adf2 100644
--- a/_config.yml
+++ b/_config.yml
@@ -110,8 +110,8 @@ social:
# Home Assistant release details
current_major_version: 2023
current_minor_version: 5
-current_patch_version: 3
-date_released: 2023-05-14
+current_patch_version: 4
+date_released: 2023-05-23
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.
diff --git a/source/_posts/2023-05-03-release-20235.markdown b/source/_posts/2023-05-03-release-20235.markdown
index 3aad0bb9006..92490ec22f2 100644
--- a/source/_posts/2023-05-03-release-20235.markdown
+++ b/source/_posts/2023-05-03-release-20235.markdown
@@ -50,6 +50,7 @@ Enjoy the release!
- [Release 2023.5.1 - May 4](#release-202351---may-4)
- [Release 2023.5.2 - May 5](#release-202352---may-5)
- [Release 2023.5.3 - May 14](#release-202353---may-14)
+- [Release 2023.5.4 - May 23](#release-202354---may-23)
- [Need help? Join the community!](#need-help-join-the-community)
- [Breaking Changes](#breaking-changes)
- [Farewell to the following](#farewell-to-the-following)
@@ -539,6 +540,107 @@ The following integrations are now available via the Home Assistant UI:
[zha docs]: /integrations/zha/
[zwave_js docs]: /integrations/zwave_js/
+## Release 2023.5.4 - May 23
+
+- Fix weather handling in zamg ([@killer0071234] - [#85635]) ([zamg docs])
+- Fix onvif cameras that cannot parse relative time ([@bdraco] - [#92711]) ([onvif docs]) (dependency)
+- Update solax state class for sensors with no units ([@MichaelMraka] - [#92914]) ([solax docs])
+- Fix NWS error with no observation ([@MatthewFlamm] - [#92997]) ([nws docs])
+- Increase timeout to 30 seconds for homeassistant_alerts integration ([@N3rdix] - [#93089]) ([homeassistant_alerts docs])
+- Fix ONVIF cameras that change the xaddr for the pull point service ([@bdraco] - [#93104]) ([onvif docs])
+- Bump pyunifiprotect to 4.9.0 ([@bdraco] - [#93106]) ([unifiprotect docs]) (dependency)
+- Fix last imap message is not reset on empty search ([@jbouwh] - [#93119]) ([imap docs])
+- Bump `accuweather` to version 0.5.2 ([@bieniu] - [#93130]) ([accuweather docs]) (dependency)
+- Better handling of source sensor unavailability in Riemman Integration ([@dgomes] - [#93137]) ([integration docs])
+- Bump `regenmaschine` to 2023.05.1 ([@bachya] - [#93139]) ([rainmachine docs]) (dependency)
+- Bump pyatv to 0.11.0 ([@bdraco] - [#93172]) ([apple_tv docs])
+- Fix china login for bmw_connected_drive ([@rikroe] - [#93180]) ([bmw_connected_drive docs])
+- Add Fan and Dry HVAC modes to Advantage Air MyTemp preset ([@Bre77] - [#93189]) ([advantage_air docs])
+- Disconnect yale access locks at the stop event ([@bdraco] - [#93192]) ([august docs]) ([yalexs_ble docs]) (dependency)
+- Add support for Yale Home brand to august ([@bdraco] - [#93214]) ([august docs])
+- Bump async-upnp-client to 0.33.2 ([@StevenLooman] - [#93329]) (dependency)
+- Bump `aionotion` to 2023.05.5 ([@bachya] - [#93334]) ([notion docs])
+- Bump zwave-js-server-python to 0.48.1 ([@raman325] - [#93342]) ([zwave_js docs]) (dependency)
+- Bump glances_api to 0.4.2 ([@freeDom-] - [#93352]) ([glances docs])
+- Fix august configuration url with Yale Home brand ([@bdraco] - [#93361]) ([august docs]) (dependency)
+- Bump httpx to 0.24.1 ([@epenet] - [#93396]) (dependency)
+- Fix non threadsafe call xiaomi_aqara ([@bdraco] - [#93405]) ([xiaomi_aqara docs])
+- Bump Matter server library to 3.4.1 and address changes ([@marcelveldt] - [#93411]) ([matter docs]) (dependency)
+- Fix race in tracking pending writes in recorder ([@bdraco] - [#93414]) ([recorder docs])
+
+[#85635]: https://github.com/home-assistant/core/pull/85635
+[#92422]: https://github.com/home-assistant/core/pull/92422
+[#92513]: https://github.com/home-assistant/core/pull/92513
+[#92610]: https://github.com/home-assistant/core/pull/92610
+[#92711]: https://github.com/home-assistant/core/pull/92711
+[#92914]: https://github.com/home-assistant/core/pull/92914
+[#92997]: https://github.com/home-assistant/core/pull/92997
+[#93066]: https://github.com/home-assistant/core/pull/93066
+[#93089]: https://github.com/home-assistant/core/pull/93089
+[#93104]: https://github.com/home-assistant/core/pull/93104
+[#93106]: https://github.com/home-assistant/core/pull/93106
+[#93119]: https://github.com/home-assistant/core/pull/93119
+[#93130]: https://github.com/home-assistant/core/pull/93130
+[#93137]: https://github.com/home-assistant/core/pull/93137
+[#93139]: https://github.com/home-assistant/core/pull/93139
+[#93172]: https://github.com/home-assistant/core/pull/93172
+[#93180]: https://github.com/home-assistant/core/pull/93180
+[#93189]: https://github.com/home-assistant/core/pull/93189
+[#93192]: https://github.com/home-assistant/core/pull/93192
+[#93214]: https://github.com/home-assistant/core/pull/93214
+[#93329]: https://github.com/home-assistant/core/pull/93329
+[#93334]: https://github.com/home-assistant/core/pull/93334
+[#93342]: https://github.com/home-assistant/core/pull/93342
+[#93352]: https://github.com/home-assistant/core/pull/93352
+[#93361]: https://github.com/home-assistant/core/pull/93361
+[#93396]: https://github.com/home-assistant/core/pull/93396
+[#93405]: https://github.com/home-assistant/core/pull/93405
+[#93411]: https://github.com/home-assistant/core/pull/93411
+[#93414]: https://github.com/home-assistant/core/pull/93414
+[@Bre77]: https://github.com/Bre77
+[@MatthewFlamm]: https://github.com/MatthewFlamm
+[@MichaelMraka]: https://github.com/MichaelMraka
+[@N3rdix]: https://github.com/N3rdix
+[@StevenLooman]: https://github.com/StevenLooman
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@bdraco]: https://github.com/bdraco
+[@bieniu]: https://github.com/bieniu
+[@dgomes]: https://github.com/dgomes
+[@epenet]: https://github.com/epenet
+[@freeDom-]: https://github.com/freeDom-
+[@frenck]: https://github.com/frenck
+[@jbouwh]: https://github.com/jbouwh
+[@killer0071234]: https://github.com/killer0071234
+[@marcelveldt]: https://github.com/marcelveldt
+[@raman325]: https://github.com/raman325
+[@rikroe]: https://github.com/rikroe
+[accuweather docs]: /integrations/accuweather/
+[advantage_air docs]: /integrations/advantage_air/
+[apple_tv docs]: /integrations/apple_tv/
+[august docs]: /integrations/august/
+[bluetooth docs]: /integrations/bluetooth/
+[bmw_connected_drive docs]: /integrations/bmw_connected_drive/
+[cloud docs]: /integrations/cloud/
+[frontend docs]: /integrations/frontend/
+[glances docs]: /integrations/glances/
+[homeassistant_alerts docs]: /integrations/homeassistant_alerts/
+[imap docs]: /integrations/imap/
+[integration docs]: /integrations/integration/
+[lifx docs]: /integrations/lifx/
+[matter docs]: /integrations/matter/
+[notion docs]: /integrations/notion/
+[nws docs]: /integrations/nws/
+[onvif docs]: /integrations/onvif/
+[rainmachine docs]: /integrations/rainmachine/
+[recorder docs]: /integrations/recorder/
+[solax docs]: /integrations/solax/
+[unifiprotect docs]: /integrations/unifiprotect/
+[xiaomi_aqara docs]: /integrations/xiaomi_aqara/
+[yalexs_ble docs]: /integrations/yalexs_ble/
+[zamg docs]: /integrations/zamg/
+[zwave_js docs]: /integrations/zwave_js/
+
## Need help? Join the community!
Home Assistant has a great community of users who are all more than willing
From bfe339726053e085c93ff33fd02b8ee4dc4a8c17 Mon Sep 17 00:00:00 2001
From: b-uwe <61052367+b-uwe@users.noreply.github.com>
Date: Wed, 24 May 2023 09:16:56 +0200
Subject: [PATCH 28/68] add SmarterHOME as a distributor (#27493)
---
source/skyconnect/index.html | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/source/skyconnect/index.html b/source/skyconnect/index.html
index e36da2cdb5d..3a0757cc8ac 100644
--- a/source/skyconnect/index.html
+++ b/source/skyconnect/index.html
@@ -399,6 +399,24 @@ frontpage_image: /images/skyconnect/skyconnect-cover.png