diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
index 140a23be5cb..3922c4e2cb0 100644
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -8,7 +8,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- name: Check out files from GitHub
- uses: actions/checkout@v3.5.0
+ uses: actions/checkout@v3.5.2
- name: Setting up Node.js
uses: actions/setup-node@v3.6.0
with:
@@ -25,7 +25,7 @@ jobs:
runs-on: ubuntu-latest
steps:
- name: Check out files from GitHub
- uses: actions/checkout@v3.5.0
+ uses: actions/checkout@v3.5.2
- name: Setting up Node.js
uses: actions/setup-node@v3.6.0
with:
diff --git a/Gemfile b/Gemfile
index ac33e7b7c38..a30ba89780c 100644
--- a/Gemfile
+++ b/Gemfile
@@ -19,8 +19,8 @@ group :jekyll_plugins do
gem 'jekyll-toc', '0.18.0'
end
-gem 'sinatra', '3.0.5'
-gem 'nokogiri', '1.14.2'
+gem 'sinatra', '3.0.6'
+gem 'nokogiri', '1.14.3'
# 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 0020d5fa662..7311e330423 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -1,11 +1,11 @@
GEM
remote: https://rubygems.org/
specs:
- addressable (2.8.3)
+ addressable (2.8.4)
public_suffix (>= 2.0.2, < 6.0)
chunky_png (1.4.0)
colorator (1.1.0)
- commonmarker (0.23.8)
+ commonmarker (0.23.9)
compass (1.0.3)
chunky_png (~> 1.2)
compass-core (~> 1.0.2)
@@ -27,7 +27,7 @@ GEM
ffi (1.15.5)
ffi (1.15.5-x64-mingw32)
forwardable-extended (2.6.0)
- google-protobuf (3.22.2)
+ google-protobuf (3.22.3)
http_parser.rb (0.8.0)
i18n (1.12.0)
concurrent-ruby (~> 1.0)
@@ -72,17 +72,15 @@ GEM
multi_json (1.15.0)
mustermann (3.0.0)
ruby2_keywords (~> 0.0.1)
- nokogiri (1.14.2)
+ nokogiri (1.14.3)
mini_portile2 (~> 2.8.0)
racc (~> 1.4)
- nokogiri (1.14.2-x64-mingw32)
- racc (~> 1.4)
pathutil (0.16.2)
forwardable-extended (~> 2.6)
public_suffix (5.0.1)
racc (1.6.2)
rack (2.2.6.4)
- rack-protection (3.0.5)
+ rack-protection (3.0.6)
rack
rake (13.0.6)
rb-fsevent (0.11.2)
@@ -93,10 +91,10 @@ GEM
ruby2_keywords (0.0.5)
safe_yaml (1.0.5)
sass (3.4.25)
- sass-embedded (1.60.0)
+ sass-embedded (1.62.0)
google-protobuf (~> 3.21)
rake (>= 10.0.0)
- sass-embedded (1.60.0-x64-mingw32)
+ sass-embedded (1.62.0-x64-mingw32)
google-protobuf (~> 3.21)
sass-globbing (1.1.5)
sass (>= 3.1)
@@ -104,10 +102,10 @@ GEM
ffi (~> 1.9)
sassc (2.1.0-x64-mingw32)
ffi (~> 1.9)
- sinatra (3.0.5)
+ sinatra (3.0.6)
mustermann (~> 3.0)
rack (~> 2.2, >= 2.2.4)
- rack-protection (= 3.0.5)
+ rack-protection (= 3.0.6)
tilt (~> 2.0)
stringex (2.8.5)
terminal-table (3.0.2)
@@ -131,11 +129,11 @@ DEPENDENCIES
jekyll-paginate (= 1.1.0)
jekyll-sitemap (= 1.4.0)
jekyll-toc (= 0.18.0)
- nokogiri (= 1.14.2)
+ nokogiri (= 1.14.3)
rake (= 13.0.6)
sass-globbing (= 1.1.5)
sassc (= 2.1.0)
- sinatra (= 3.0.5)
+ sinatra (= 3.0.6)
stringex (= 2.8.5)
tzinfo (~> 2.0)
tzinfo-data
diff --git a/_config.yml b/_config.yml
index c86f15642e1..2d6fa991958 100644
--- a/_config.yml
+++ b/_config.yml
@@ -110,8 +110,8 @@ social:
# Home Assistant release details
current_major_version: 2023
current_minor_version: 4
-current_patch_version: 0
-date_released: 2023-04-05
+current_patch_version: 4
+date_released: 2023-04-13
# 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/_data/glossary.yml b/source/_data/glossary.yml
index 852963b503e..fd551c82230 100644
--- a/source/_data/glossary.yml
+++ b/source/_data/glossary.yml
@@ -26,6 +26,16 @@
Add-ons are additional standalone third-party software packages that can be
installed on Home Assistant OS.
+- term: Area
+ definition: >-
+ Locations within your home such as living room, dance floor, etc.
+ Devices can be associated to an area for easier sorting and automatically
+ generated cards, such as the [Area card](/dashboards/area/).
+ excerpt: >-
+ Places within your home such as rooms, spaces, etc.
+ aliases:
+ - areas
+
- term: Automation
definition: >-
Automations connect one or more triggers to one or more actions in a
diff --git a/source/_docs/configuration/templating.markdown b/source/_docs/configuration/templating.markdown
index 14bd0c1420c..c3bbe7874c1 100644
--- a/source/_docs/configuration/templating.markdown
+++ b/source/_docs/configuration/templating.markdown
@@ -150,6 +150,8 @@ Print out a list of all the sensor states:
{% endfor %}
```
+{% endraw %}
+
Print out a list of all the sensor states sorted by `entity_id`:
{% raw %}
diff --git a/source/_integrations/amcrest.markdown b/source/_integrations/amcrest.markdown
index eb4913d7be4..457fab8a8ed 100644
--- a/source/_integrations/amcrest.markdown
+++ b/source/_integrations/amcrest.markdown
@@ -289,7 +289,7 @@ elements:
tap_action:
action: call-service
service: amcrest.ptz_control
- data:
+ service_data:
entity_id: camera.lakehouse
movement: up
- type: icon
@@ -301,7 +301,7 @@ elements:
tap_action:
action: call-service
service: amcrest.ptz_control
- data:
+ service_data:
entity_id: camera.lakehouse
movement: down
- type: icon
@@ -313,7 +313,7 @@ elements:
tap_action:
action: call-service
service: amcrest.ptz_control
- data:
+ service_data:
entity_id: camera.lakehouse
movement: left
- type: icon
@@ -325,7 +325,7 @@ elements:
tap_action:
action: call-service
service: amcrest.ptz_control
- data:
+ service_data:
entity_id: camera.lakehouse
movement: right
- type: icon
@@ -337,7 +337,7 @@ elements:
tap_action:
action: call-service
service: amcrest.ptz_control
- data:
+ service_data:
entity_id: camera.lakehouse
movement: left_up
- type: icon
@@ -349,7 +349,7 @@ elements:
tap_action:
action: call-service
service: amcrest.ptz_control
- data:
+ service_data:
entity_id: camera.lakehouse
movement: right_up
- type: icon
@@ -361,7 +361,7 @@ elements:
tap_action:
action: call-service
service: amcrest.ptz_control
- data:
+ service_data:
entity_id: camera.lakehouse
movement: left_down
- type: icon
@@ -373,7 +373,7 @@ elements:
tap_action:
action: call-service
service: amcrest.ptz_control
- data:
+ service_data:
entity_id: camera.lakehouse
movement: right_down
- type: icon
@@ -385,7 +385,7 @@ elements:
tap_action:
action: call-service
service: amcrest.ptz_control
- data:
+ service_data:
entity_id: camera.lakehouse
movement: zoom_in
hold_action:
diff --git a/source/_integrations/arcam_fmj.markdown b/source/_integrations/arcam_fmj.markdown
index 2ef55077dd7..cb806b8da87 100644
--- a/source/_integrations/arcam_fmj.markdown
+++ b/source/_integrations/arcam_fmj.markdown
@@ -41,6 +41,10 @@ Supported devices:
- SA 30
- SR 250
+This integration may also work with JBL and AudioControl receivers and processors as they share the same firmware as Arcam.
+
+- SDP-55/58
+
{% include integrations/config_flow.md %}
## Power state
diff --git a/source/_integrations/epsonworkforce.markdown b/source/_integrations/epsonworkforce.markdown
index c1122ffc6fd..e47b5f4682b 100644
--- a/source/_integrations/epsonworkforce.markdown
+++ b/source/_integrations/epsonworkforce.markdown
@@ -72,6 +72,7 @@ Tested devices:
- Epson ET-2650
- Epson ET-4750
- Epson EcoTank ET-5150 (51x0)
+- Epson Expression Home XP-2100
- Epson Expression Home XP-2105
To make this module work you need to connect your printer to your LAN.
diff --git a/source/_integrations/fixer.markdown b/source/_integrations/fixer.markdown
index db1c3cbd77c..f79916115d6 100644
--- a/source/_integrations/fixer.markdown
+++ b/source/_integrations/fixer.markdown
@@ -17,7 +17,7 @@ To get an overview about the available [currencies](https://fixer.io/symbols).
## Setup
-You need to create an [API key](https://fixer.io/product). The free account is limited to only EUR as a base currency, allows 250 requests per month, and updates every hour.
+You need to create an [API key](https://fixer.io/product). The free account is limited to only EUR as a base currency, allows 100 requests per month, and updates every hour.
## Configuration
diff --git a/source/_integrations/flux_led.markdown b/source/_integrations/flux_led.markdown
index e29e3204ab0..afb9a83edb5 100644
--- a/source/_integrations/flux_led.markdown
+++ b/source/_integrations/flux_led.markdown
@@ -83,7 +83,7 @@ These devices have been sold under at least the following brands:
- [Diode Dynamics](https://www.diodedynamics.com/)
- [Flux LED](https://www.fluxsmartlighting.com/)
- [FVTLED](https://fvtled.com/)
-- [GEV LIG](https://www.gev.de/)
+- GEV LIG
- GEYUEYA Home
- GIDEALED
- [GIDERWEL](https://giderwel.com/)
@@ -98,7 +98,7 @@ These devices have been sold under at least the following brands:
- INDARUN
- iNextStation
- [Koopower](https://www.koopower.com/)
-- [Lallumer](https://www.lapuretes.cn/)
+- Lallumer
- LEDENET
- [LiteWRX](https://litewrx.com/)
- Lytworx
diff --git a/source/_integrations/home_connect.markdown b/source/_integrations/home_connect.markdown
index 457726e17ec..21cc2ee5d53 100644
--- a/source/_integrations/home_connect.markdown
+++ b/source/_integrations/home_connect.markdown
@@ -43,7 +43,9 @@ Note that it depends on the appliance and on API permissions which of the featur
- OAuth Flow: Authorization Code Grant Flow
- Redirect URI: `https://my.home-assistant.io/redirect/oauth`
-*Important*:
+*Important*:
+ - **Power on** all your appliances during the integration configuration process; otherwise appliance programs list will be empty.
+ - To update the appliance programs list, you can reload the Home Connect integration when an appliance is turned on. If the re-initialization process is not triggered by reload, restart the Home Assistant when an appliance is turned on.
- After performing the steps above **log out** of your Home Connect Developer account. If you don't do this, the configuration steps below will fail during OAuth authentication with the message `“error”: “unauthorized_client”`.
- The provided Home Connect User Account email address **must** be all lowercase otherwise it will result in authentication failures.
- All changes in the developer portal take 15 minutes before the change is implemented.
diff --git a/source/_integrations/insteon.markdown b/source/_integrations/insteon.markdown
index f25292806a8..ce459b1eea8 100644
--- a/source/_integrations/insteon.markdown
+++ b/source/_integrations/insteon.markdown
@@ -186,6 +186,6 @@ Many users tried to factory reset their Insteon Hub when the Insteon app stopped
- If you have a Hub v2 you will need the default username and password which are printed on the bottom of the Hub
-3. Add devices to the Hub using the instructions for adding devices to the INSTEON integration using the [Insteon Panel]](#insteon-panel)
+3. Add devices to the Hub using the instructions for adding devices to the Insteon integration using the [Insteon Panel](#insteon-panel)
Once your devices are linked to the Hub again they will appear in Home Assistant automatically.
diff --git a/source/_integrations/mailgun.markdown b/source/_integrations/mailgun.markdown
index be485a7bfe2..654fd8562a2 100644
--- a/source/_integrations/mailgun.markdown
+++ b/source/_integrations/mailgun.markdown
@@ -12,7 +12,7 @@ ha_platforms:
ha_integration_type: integration
---
-To be able to receive webhooks from Mailgun, your Home Assistant instance needs to be accessible from the web and you need to have the extern URL [configured](/docs/configuration/basic)).
+To be able to receive webhooks from Mailgun, your Home Assistant instance needs to be accessible from the web and you need to have the external URL [configured](/docs/configuration/basic)).
To set it up, go to the integrations page in the configuration screen and find Mailgun. Click on configure. Follow the instructions on the screen to configure Mailgun.
diff --git a/source/_integrations/nest.markdown b/source/_integrations/nest.markdown
index af56bcda814..0c8e997e414 100644
--- a/source/_integrations/nest.markdown
+++ b/source/_integrations/nest.markdown
@@ -259,7 +259,7 @@ This feature is enabled by the following permissions:
-Additional Nest Temperature Sensors are not supported by the SDM API.
+Additional Nest Temperature Sensors are not supported by the SDM API. The Temperature reported by the API will be pulled from whichever device is currently configured as the Active Sensor, which can be adjusted via manual selection or the schedule offered in the Nest App.
diff --git a/source/_integrations/sql.markdown b/source/_integrations/sql.markdown
index 7b88c29e33e..75be3c56843 100644
--- a/source/_integrations/sql.markdown
+++ b/source/_integrations/sql.markdown
@@ -68,7 +68,7 @@ sql:
db_url:
description: The URL which points to your database. See [supported engines](/integrations/recorder/#custom-database-engines).
required: false
- default: "Defaults to the default recorder `db_url` (not the current `db_url` of recorder)."
+ default: "Defaults to the recorder `db_url`."
type: string
name:
description: The name of the sensor.
diff --git a/source/_integrations/subaru.markdown b/source/_integrations/subaru.markdown
index 3f60a70e588..2061d966d12 100644
--- a/source/_integrations/subaru.markdown
+++ b/source/_integrations/subaru.markdown
@@ -18,7 +18,7 @@ ha_platforms:
ha_integration_type: integration
---
-This integration retrieves vehicle information and actuates remote services provided by [Subaru STARLINK](https://www.subaru.com/engineering/starlink/safety-security.html) (currently only available in USA and Canada).
+This integration retrieves vehicle information and actuates remote services provided by [Subaru STARLINK](https://www.subaru.com/subaru-starlink/starlink-safety-and-security.html) (currently only available in USA and Canada).
This integration requires a telematics equipped Subaru and an active vehicle subscription to the Subaru STARLINK service. Before using this integration, you must first register and have login credentials to [MySubaru](https://www.mysubaru.com).
diff --git a/source/_integrations/ultraloq.markdown b/source/_integrations/ultraloq.markdown
index 11c2a37a5cb..e2bdff1ebb0 100644
--- a/source/_integrations/ultraloq.markdown
+++ b/source/_integrations/ultraloq.markdown
@@ -11,6 +11,11 @@ works_with:
ha_iot_standard: zwave
---
+
+There is a
bug in the firmware of Ultraloq devices that causes the door state sensor to not be updated and the latch to always be reported as "OPEN".
+We are fully aware that this is not what you expect from a
Works With Home Assistant brand and we are in contact Ultraloq to get this resolved!
+
While your Z-Wave mesh is permanently stored on your dongle, the additional metadata is not. When the Z-Wave integration starts up the first time, it will interview your entire Z-Wave network. Depending on the number of devices paired with the Z-Wave dongle, this can take a while. You can speed up this process by manually waking up your battery-powered devices. Most of the time, this is a button press on those devices (see their manual). It is not necessary to exclude and re-include devices from the mesh.
+### Adding a new device to the Z-Wave network
+
+1. In Home Assistant, go to {% my integrations title="**Settings** > **Devices & Services**" %}.
+1. In the Z-Wave integration, select **Configure**.
+1. Select **Add device**.
+ * The Z-Wave controller is now in inclusion mode.
+1. If your device supports SmartStart, select **Scan QR code** and scan the QR code on your device.
+1. If your device does not support SmartStart, set the device in inclusion mode. Refer to the device manual to see how this is done.
+ * If your device is included using S2 security, you may be prompted to enter a PIN number provided with your device. Often, this PIN is provided with the documentation _and_ is also printed on the device itself. For more information on secure inclusion, refer to [this section](/integrations/zwave_js/#should-i-use-secure-inclusion).
+1. The UI should confirm that the device was added. After a short while (seconds to minutes), the entities should also be created.
+1. If the controller fails to add/find your device, cancel the inclusion process.
+ * In some cases, it might help to first [remove](/integrations/zwave_js/#removing-a-device-from-the-z-wave-network) a device (exclusion) before you add it, even when the device has not been added to this Z-Wave network yet.
+ * Another approach would be to factory reset the device. Refer to the device manual to see how this is done.
+
+**Important:**
+
+1. **Do not move your Z-Wave stick to include devices.** This is no longer necessary and leads to broken routes.
+1. **Do not initiate device inclusion from the Z-Wave stick itself.** This is no longer supported.
+
+### Removing a device from the Z-Wave network
+
+1. In Home Assistant, go to {% my integrations title="**Settings** > **Devices & Services**" %}.
+1. In the Z-Wave integration, select **Configure**.
+1. Select **Remove device**, then **Start exclusion**.
+ * The Z-Wave controller is now in exclusion mode.
+1. Put the device you want to remove in exclusion mode. Refer to its manual how this is done.
+1. The UI should confirm that the device was removed and the device and entities will be removed from Home Assistant.
+
+## Using advanced features (UI only)
+
+While the integration aims to provide as much functionality as possible through existing Home Assistant constructs (entities, states, automations, services, etc.), there are some features that are only available through the UI.
+
+All of these features can be accessed either in the Z-Wave integration configuration panel or in a Z-Wave device's device panel.
+
+### Integration configuration panel
+
+The following features can be accessed from the integration configuration panel:
+
+
+
+* **Add device:** Allows you to pre-provision a SmartStart device or start the inclusion process for adding a new device to your network.
+* **Remove device:** Starts the exclusion process for removing a device from your network.
+* **Heal network:** Forces your network to rediscover routes to the controller from each device. This is useful when devices or the controller have moved to a new location, or if you are having significant problems with your network, but it also generates a lot of network traffic and should be used sparingly.
+* **[Controller statistics](https://zwave-js.github.io/node-zwave-js/#/api/controller?id=quotstatistics-updatedquot):** Provides statistics about communication between the controller and other devices, allowing you to troubleshoot your network's RF quality.
+* **Third-party data opt-in/out:** Allows you to opt-in or out of telemetry that the Z-Wave JS project collects to help inform development decisions, influence manufacturers, etc. This telemetry is disabled by default and has to be opted in to be activated.
+
+### Integration menu
+
+Some features can be accessed from the menu of integration itself. As they are not specific to Z-Wave, they are not described here in detail.
+
+
+* **[Download diagnostics](/docs/configuration/troubleshooting/#download-diagnostics):** Exports a JSON file describing the entities of all devices registered with this integration.
+
+### Device panel
+
+The following features can be accessed from the device panel of a Z-Wave device:
+
+
+
+* **Configure:** Provides an easy way to look up and update configuration parameters for the device. While there is an existing service for setting configuration parameter values, this UI may sometimes be quicker to use for one-off changes.
+* **Re-interview:** Forces the device to go through the interview process again so that Z-Wave-JS can discover all of its capabilities. Can be helpful if you don't see all the expected entities for your device.
+* **Heal:** Forces the device to rediscover its optimal route back to the controller. Use this if you think you are experiencing unexpected delays or RF issues with your device. Your device may be less responsive during this process.
+* **Remove failed:** Forces the controller to remove the device from the controller. Can be used when a device has failed and it can't go through the normal exclusion process.
+* **[Statistics](https://zwave-js.github.io/node-zwave-js/#/api/node?id=quotstatistics-updatedquot):** Provides statistics about communication between this device and the controller, allowing you to troubleshoot RF issues with the device.
+* **Update:** Updates a device's firmware using a manually uploaded firmware file. Only some devices support this feature (controllers and devices with the Firmware Update Metadata Command Class).
+* **Download diagnostics:** Exports a JSON file describing the entities of this specific device.
+
## Services
### Service `zwave_js.set_config_parameter`
@@ -587,33 +654,6 @@ In addition to the [standard automation trigger data](/docs/automation/templatin
| `trigger.event` | Name of event. |
| `trigger.event_data` | Any data included in the event. |
-## Advanced Features (UI Only)
-
-While the integration aims to provide as much functionality as possible through existing Home Assistant constructs (entities, states, automations, services, etc.), there are some features that are only available through the UI.
-
-All of these features can be accessed either in the Z-Wave integration configuration panel or in a Z-Wave device's device panel.
-
-### Integration Configuration Panel
-
-The following features can be accessed from the integration configuration panel:
-
-* **Add device:** Allows you to pre-provision a SmartStart device or start the inclusion process for adding a new device to your network.
-* **Remove device:** Starts the exclusion process for removing a device from your network.
-* **Heal network:** Forces your network to rediscover routes to the controller from each device. This is useful when devices or the controller have moved to a new location, or if you are having significant problems with your network, but it also generates a lot of network traffic and should be used sparingly.
-* **Third-party data opt-in/out:** Allows you to opt-in or out of telemetry that the Z-Wave JS project collects to help inform development decisions, influence manufacturers, etc. This telemetry is disabled by default and has to be opted in to be activated.
-* **[Controller statistics](https://zwave-js.github.io/node-zwave-js/#/api/controller?id=quotstatistics-updatedquot):** Provides statistics about communication between the controller and other devices, allowing you to troubleshoot your network's RF quality.
-
-### Device Panel
-
-The following features can be accessed from the device panel of a Z-Wave device:
-
-* **Configure:** Provides an easy way to look up and update configuration parameters for the device. While there is an existing service for setting configuration parameter values, this UI may sometimes be quicker to use for one off changes.
-* **Re-interview:** Forces the device to go through the interview process again so that zwave-js can discover all of its capabilities. Can be helpful if you don't see all the expected entities for your device.
-* **Heal:** Forces the device to rediscover its optimal route back to the controller. Use this if you think you are experiencing unexpected delays or RF issues with your device. Your device may be less responsive during this process.
-* **Remove failed:** Forces the controller to remove the device from the controller. Can be used when a device has failed and it can't go through the normal exclusion process.
-* **[Statistics](https://zwave-js.github.io/node-zwave-js/#/api/node?id=quotstatistics-updatedquot):** Provides statistics about communication between this device and the controller, allowing you to troubleshoot RF issues with the device.
-* **Update firmware:** Updates a device's firmware using a manually uploaded firmware file. Only some devices support this feature (controllers and devices with the Firmware Update Metadata Command Class).
-
## Advanced installation instructions
If you are using Home Assistant Container, Home Assistant Core, or you don't want to use the built-in Z-Wave JS Server add-on, you will need to run the Z-Wave JS server yourself, to which the Z-Wave integration will connect.
@@ -623,12 +663,15 @@ If you are using Home Assistant Container, Home Assistant Core, or you don't wan
This application provides the connection between your Z-Wave USB stick and Home Assistant. The Home Assistant Z-Wave integration connects to this server via a websocket connection. You need to run this Z-Wave JS server before you can use the integration.
There are multiple ways to run this server:
+The chart below illustrates Options 1 and 2, which are available for Home Assistant OS only.
+
+
**Option 1: The official Z-Wave JS add-on, as described above**
_This option is only available for Home Assistant OS (the recommended installation type) and Home Assistant Supervised installations._
-This add-on can only be configured via the built-in Z-Wave control panel in Home Assistant.
+This add-on can only be configured via the built-in Z-Wave control panel in Home Assistant. If you followed the standard [installation procedure](#setting-up-a-z-wave-js-server), this is how you are running the Z-Wave JS server.
**Option 2: The Z-Wave JS UI add-on installed from the community add-on store**
@@ -678,7 +721,7 @@ See the [Z-Wave JS device database](https://devices.zwave-js.io/).
While there is support for the most common devices, some command classes are not yet (fully) implemented in Z-Wave JS. You can track the status [here](https://github.com/zwave-js/node-zwave-js/issues/6).
-You can also keep track of the roadmap for the Z-Wave integration [here](https://github.com/home-assistant-libs/zwave-js-server-python/issues/56).
+You can also keep track of the road map for the Z-Wave integration [here](https://github.com/home-assistant-libs/zwave-js-server-python/issues/56).
### Installation and Configuration
@@ -725,7 +768,7 @@ Switching does not require renaming your devices.
6. Enable the Z-Wave integration.
-#### What's the benefit of using Z-Wave JS UI add-on over the official Add-On?
+#### What's the benefit of using Z-Wave JS UI add-on over the official add-on?
The official add-on provides the Z-Wave Server in its bare minimum variant, just enough to serve the Home Assistant integration.
@@ -745,24 +788,6 @@ Ultimately, this is a personal decision. If you provide a name or location for a
Names set in Home Assistant will not import into Z-Wave JS UI.
-### Using Z-Wave
-
-#### How can I add (include) a new device to my Z-Wave network?
-
-1. In Home Assistant: open Settings -> Devices & Services -> Z-Wave -> Configure.
-2. Press `+ ADD DEVICE`.
-3. The Z-Wave controller is now in inclusion mode and will not respond to other commands.
-4. Put the device you want to add in inclusion mode. Refer to its manual how this is done.
-5. The UI should confirm that the node was added and it will be immediately visible in Home Assistant. After a short while (seconds to minutes) the entities should also be created.
-6. If the controller fails to add/find your device, cancel the inclusion process (to unblock your network again). In some cases it might help to first remove a node (exclusion) before you add it, even when the device has not been added to this Z-Wave network yet. Another approach would be to factory reset the device. Info about that is in the manual of your device.
-
-If your device is included using S2 security, you may be prompted to enter a PIN number provided with your device. Often, this PIN is provided with the documentation _and_ is also printed on the device itself.
-
-**Warning:**
-
-1. **Do not move your Z-Wave stick to include devices.** This is no longer necessary and leads to broken routes.
-2. **Do not initiate device inclusion from the Z-Wave stick itself.** This is no longer supported.
-
#### Should I use `Secure Inclusion`?
That depends. There are two generations of Z-Wave security, S0, and S2.
@@ -771,13 +796,9 @@ S0 security imposes significant additional traffic on your mesh and is recommend
S2 security does not impose additional network traffic and provides additional benefits, such as detecting packet corruption. By default, Z-Wave attempts S2 security during inclusion if supported, falling back to S0 security only when necessary.
-#### How do I remove (exclude) a device from my Z-Wave network?
+#### Where can I see the security keys in the Z-Wave JS add-on?
-1. In Home Assistant: open Settings -> Devices & Services -> Z-Wave -> Configure.
-2. Press `REMOVE DEVICE`.
-3. Press `START EXCLUSION`. The Z-Wave controller is now in exclusion mode and will not respond to other commands.
-4. Put the device you want to remove in exclusion mode. Refer to its manual how this is done.
-5. The UI should confirm that the node was removed and the device and entities will be removed from Home Assistant.
+After the initial setup of the Z-Wave controller, you can view the security keys in the Z-Wave JS add-on. Go to {% my supervisor_addon addon="core_zwave_js" title="**Settings** > **Add-ons** > **Z-Wave JS**" %} and open the **Configuration** tab. You can now see the three S2 keys and the S0 key. The network security key is a legacy configuration setting, identical to the S0 key.
### Troubleshooting
diff --git a/source/_posts/2022-10-25-ultraloq-partner.markdown b/source/_posts/2022-10-25-ultraloq-partner.markdown
index 13774b28d93..bfb62d7ae1d 100644
--- a/source/_posts/2022-10-25-ultraloq-partner.markdown
+++ b/source/_posts/2022-10-25-ultraloq-partner.markdown
@@ -12,6 +12,11 @@ categories:
og_image: /images/blog/2022-10-25-ultraloq-partner/social.png
---
+
+There is a
bug in the firmware of Ultraloq devices that causes the door state sensor to not be updated and the latch to always be reported as "OPEN".
+We are fully aware that this is not what you expect from a
Works With Home Assistant brand and we are in contact Ultraloq to get this resolved!
+
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.
diff --git a/source/_posts/2023-04-05-release-20234.markdown b/source/_posts/2023-04-05-release-20234.markdown
index a822ab34653..3474a42018b 100644
--- a/source/_posts/2023-04-05-release-20234.markdown
+++ b/source/_posts/2023-04-05-release-20234.markdown
@@ -44,12 +44,16 @@ Happy Easter! 🐣 and enjoy the release!
- [Other noteworthy changes](#other-noteworthy-changes)
- [New Integrations](#new-integrations)
- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
+- [Release 2023.4.1 - April 6](#release-202341---april-6)
+- [Release 2023.4.2 - April 8](#release-202342---april-8)
+- [Release 2023.4.3 - April 12](#release-202343---april-12)
+- [Release 2023.4.4 - April 13](#release-202344---april-13)
- [Need help? Join the community!](#need-help-join-the-community)
- [Breaking Changes](#breaking-changes)
- [Farewell to the following](#farewell-to-the-following)
- [All changes](#all-changes)
-Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=IGnCGDaXR0M)
+Don't forget to [join our release party live stream on YouTube](https://www.youtube.com/watch?v=IGnCGDaXR0M)
5 April 2023, at 12:00 PDT / 21:00 CEST!
@@ -485,6 +489,303 @@ The following integrations are now available via the Home Assistant UI:
[nextcloud]: /integrations/nextcloud
[obihai]: /integrations/obihai
+## Release 2023.4.1 - April 6
+
+- Handle Uncaught exceptions in async_update Honeywell ([@mkmer] - [#90746]) ([honeywell docs])
+- Bump fritzconnection to 1.12.0 ([@saschaabraham] - [#90799]) ([fritz docs]) ([fritzbox_callmonitor docs])
+- Fix issue with Insteon All-Link Database loading ([@teharris1] - [#90858]) ([insteon docs])
+- Generate a seperate log message per dumped object for profiler.dump_log_objects ([@bdraco] - [#90867]) ([profiler docs])
+- Add constraint for websockets to <11.0 ([@bdraco] - [#90868])
+- Add MariaDB deadlock retry wrapper to database timestamp column migrations ([@bdraco] - [#90880]) ([recorder docs])
+- Migrate entity unique ids in PI-Hole ([@mib1185] - [#90883]) ([pi_hole docs])
+- Fix missing bluetooth client wrapper in bleak_retry_connector ([@bdraco] - [#90885]) ([bluetooth docs])
+- Bump ulid-transform 0.6.0 ([@bdraco] - [#90888])
+- Guard against invalid ULIDs in contexts while recording events ([@bdraco] - [#90889]) ([recorder docs])
+- Fix entity_id migration query failing with MySQL 8.0.30 ([@bdraco] - [#90895]) ([recorder docs])
+- Bump `simplisafe-python` to 2023.04.0 ([@bachya] - [#90896]) ([simplisafe docs])
+- Bump aiodiscover to 1.4.16 ([@bdraco] - [#90903]) ([dhcp docs])
+- Return empty available programs list if an appliance is off during initial configuration ([@stickpin] - [#90905]) ([home_connect docs])
+- Handle NoURLAvailableError in Nuki component ([@pree] - [#90927]) ([nuki docs])
+- Update frontend to 20230406.1 ([@bramkragten] - [#90951]) ([frontend docs])
+- Fix flaky test in vesync ([@epenet] - [#90921]) ([vesync docs])
+- Bump `aioambient` to 2022.10.0 ([@bachya] - [#90940]) ([ambient_station docs])
+- Bump reolink-aio to 0.5.10 ([@starkillerOG] - [#90963]) ([reolink docs])
+- Avoid writing state to all esphome entities at shutdown ([@bdraco] - [#90555]) ([esphome docs])
+- Fix state being cleared on disconnect with deep sleep esphome devices ([@bdraco] - [#90925]) ([esphome docs])
+- Coerce previously persisted local calendars to have valid durations ([@allenporter] - [#90970]) ([local_calendar docs])
+- Bump gcal_sync to 4.1.3 ([@allenporter] - [#90968]) ([google docs])
+- Fix error after losing an imap connection ([@jbouwh] - [#90966]) ([imap docs])
+- Fix command_template sensor value_template not being used if json_attributes set ([@gadgetchnnel] - [#90603]) ([command_line docs])
+- Fix verisure autolock ([@heiparta] - [#90960]) ([verisure docs])
+
+[#90555]: https://github.com/home-assistant/core/pull/90555
+[#90603]: https://github.com/home-assistant/core/pull/90603
+[#90855]: https://github.com/home-assistant/core/pull/90855
+[#90925]: https://github.com/home-assistant/core/pull/90925
+[#90956]: https://github.com/home-assistant/core/pull/90956
+[#90960]: https://github.com/home-assistant/core/pull/90960
+[#90966]: https://github.com/home-assistant/core/pull/90966
+[#90968]: https://github.com/home-assistant/core/pull/90968
+[#90970]: https://github.com/home-assistant/core/pull/90970
+[@allenporter]: https://github.com/allenporter
+[@balloob]: https://github.com/balloob
+[@bdraco]: https://github.com/bdraco
+[@frenck]: https://github.com/frenck
+[@gadgetchnnel]: https://github.com/gadgetchnnel
+[@heiparta]: https://github.com/heiparta
+[@jbouwh]: https://github.com/jbouwh
+[actiontec docs]: /integrations/actiontec/
+[advantage_air docs]: /integrations/advantage_air/
+[airly docs]: /integrations/airly/
+[command_line docs]: /integrations/command_line/
+[esphome docs]: /integrations/esphome/
+[google docs]: /integrations/google/
+[imap docs]: /integrations/imap/
+[local_calendar docs]: /integrations/local_calendar/
+[verisure docs]: /integrations/verisure/
+[#90921]: https://github.com/home-assistant/core/pull/90921
+[@epenet]: https://github.com/epenet
+[ambient_station docs]: /integrations/ambient_station/
+[reolink docs]: /integrations/reolink/
+[@bachya]: https://github.com/bachya
+[@starkillerOG]: https://github.com/starkillerOG
+[#90746]: https://github.com/home-assistant/core/pull/90746
+[#90799]: https://github.com/home-assistant/core/pull/90799
+[#90855]: https://github.com/home-assistant/core/pull/90855
+[#90858]: https://github.com/home-assistant/core/pull/90858
+[#90867]: https://github.com/home-assistant/core/pull/90867
+[#90868]: https://github.com/home-assistant/core/pull/90868
+[#90880]: https://github.com/home-assistant/core/pull/90880
+[#90883]: https://github.com/home-assistant/core/pull/90883
+[#90885]: https://github.com/home-assistant/core/pull/90885
+[#90888]: https://github.com/home-assistant/core/pull/90888
+[#90889]: https://github.com/home-assistant/core/pull/90889
+[#90895]: https://github.com/home-assistant/core/pull/90895
+[#90896]: https://github.com/home-assistant/core/pull/90896
+[#90903]: https://github.com/home-assistant/core/pull/90903
+[#90905]: https://github.com/home-assistant/core/pull/90905
+[#90927]: https://github.com/home-assistant/core/pull/90927
+[#90951]: https://github.com/home-assistant/core/pull/90951
+[@bachya]: https://github.com/bachya
+[@bdraco]: https://github.com/bdraco
+[@bramkragten]: https://github.com/bramkragten
+[@frenck]: https://github.com/frenck
+[@mib1185]: https://github.com/mib1185
+[@mkmer]: https://github.com/mkmer
+[@pree]: https://github.com/pree
+[@saschaabraham]: https://github.com/saschaabraham
+[@stickpin]: https://github.com/stickpin
+[@teharris1]: https://github.com/teharris1
+[actiontec docs]: /integrations/actiontec/
+[advantage_air docs]: /integrations/advantage_air/
+[airly docs]: /integrations/airly/
+[bluetooth docs]: /integrations/bluetooth/
+[dhcp docs]: /integrations/dhcp/
+[fritz docs]: /integrations/fritz/
+[fritzbox_callmonitor docs]: /integrations/fritzbox_callmonitor/
+[frontend docs]: /integrations/frontend/
+[home_connect docs]: /integrations/home_connect/
+[honeywell docs]: /integrations/honeywell/
+[insteon docs]: /integrations/insteon/
+[nuki docs]: /integrations/nuki/
+[pi_hole docs]: /integrations/pi_hole/
+[profiler docs]: /integrations/profiler/
+[recorder docs]: /integrations/recorder/
+[simplisafe docs]: /integrations/simplisafe/
+
+## Release 2023.4.2 - April 8
+
+- Fix NMBS AttributeError ([@PatrickGlesner] - [#90525]) ([nmbs docs])
+- Bump websockets constraint to 11.0.1+ ([@bdraco] - [#90901]) ([ambient_station docs]) ([vallox docs])
+- Raise an issue for legacy SQL queries that will cause full table scans ([@bdraco] - [#90971]) ([sql docs])
+- Resume entity id post migration after a restart ([@bdraco] - [#90973]) ([recorder docs])
+- Bump vallox-websocket-api to 3.2.1 ([@bdraco] - [#90980]) ([vallox docs])
+- Bump `aioambient` to 2023.04.0 ([@bachya] - [#90991]) ([ambient_station docs])
+- Bump roombapy to 1.6.8 ([@joostlek] - [#91012]) ([roomba docs])
+- Delay utility_meter until HA has started ([@dgomes] - [#91017]) ([utility_meter docs])
+- Make sure upnp-router is also initialized when first seen through an advertisement ([@StevenLooman] - [#91037]) ([upnp docs])
+- Bump ZHA quirks lib ([@dmulcahey] - [#91054]) ([zha docs])
+- Fix Smartthings acceleration sensor in ZHA ([@dmulcahey] - [#91056]) ([zha docs])
+- Bump zeroconf to 0.55.0 ([@bdraco] - [#90987]) ([zeroconf docs])
+- Bump zeroconf to 0.56.0 ([@bdraco] - [#91060]) ([zeroconf docs])
+- Make location optional in google calendar create service ([@allenporter] - [#91061]) ([google docs])
+- Bump gcal_sync to 4.1.4 ([@allenporter] - [#91062]) ([google docs])
+- Bump subarulink to 0.7.6 ([@G-Two] - [#91064]) ([subaru docs])
+- Bump env_canada to v0.5.31 ([@michaeldavie] - [#91094]) ([environment_canada docs])
+- Fix context_user_id round trip when calling to_native ([@bdraco] - [#91098]) ([recorder docs])
+- Bump flux_led to 0.28.37 ([@bdraco] - [#91099]) ([flux_led docs])
+- Make the device_tracker more forgiving when passed an empty ip address string ([@bdraco] - [#91101]) ([device_tracker docs])
+
+[#90525]: https://github.com/home-assistant/core/pull/90525
+[#90855]: https://github.com/home-assistant/core/pull/90855
+[#90901]: https://github.com/home-assistant/core/pull/90901
+[#90956]: https://github.com/home-assistant/core/pull/90956
+[#90971]: https://github.com/home-assistant/core/pull/90971
+[#90973]: https://github.com/home-assistant/core/pull/90973
+[#90980]: https://github.com/home-assistant/core/pull/90980
+[#90987]: https://github.com/home-assistant/core/pull/90987
+[#90991]: https://github.com/home-assistant/core/pull/90991
+[#91012]: https://github.com/home-assistant/core/pull/91012
+[#91017]: https://github.com/home-assistant/core/pull/91017
+[#91037]: https://github.com/home-assistant/core/pull/91037
+[#91054]: https://github.com/home-assistant/core/pull/91054
+[#91056]: https://github.com/home-assistant/core/pull/91056
+[#91060]: https://github.com/home-assistant/core/pull/91060
+[#91061]: https://github.com/home-assistant/core/pull/91061
+[#91062]: https://github.com/home-assistant/core/pull/91062
+[#91064]: https://github.com/home-assistant/core/pull/91064
+[#91094]: https://github.com/home-assistant/core/pull/91094
+[#91098]: https://github.com/home-assistant/core/pull/91098
+[#91099]: https://github.com/home-assistant/core/pull/91099
+[#91101]: https://github.com/home-assistant/core/pull/91101
+[@G-Two]: https://github.com/G-Two
+[@PatrickGlesner]: https://github.com/PatrickGlesner
+[@StevenLooman]: https://github.com/StevenLooman
+[@allenporter]: https://github.com/allenporter
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@bdraco]: https://github.com/bdraco
+[@dgomes]: https://github.com/dgomes
+[@dmulcahey]: https://github.com/dmulcahey
+[@frenck]: https://github.com/frenck
+[@joostlek]: https://github.com/joostlek
+[@michaeldavie]: https://github.com/michaeldavie
+[actiontec docs]: /integrations/actiontec/
+[advantage_air docs]: /integrations/advantage_air/
+[airly docs]: /integrations/airly/
+[ambient_station docs]: /integrations/ambient_station/
+[device_tracker docs]: /integrations/device_tracker/
+[environment_canada docs]: /integrations/environment_canada/
+[flux_led docs]: /integrations/flux_led/
+[google docs]: /integrations/google/
+[nmbs docs]: /integrations/nmbs/
+[recorder docs]: /integrations/recorder/
+[roomba docs]: /integrations/roomba/
+[sql docs]: /integrations/sql/
+[subaru docs]: /integrations/subaru/
+[upnp docs]: /integrations/upnp/
+[utility_meter docs]: /integrations/utility_meter/
+[vallox docs]: /integrations/vallox/
+[zeroconf docs]: /integrations/zeroconf/
+[zha docs]: /integrations/zha/
+
+## Release 2023.4.3 - April 12
+
+- Fix configuring Flo instances ([@amattas] - [#90990]) ([flo docs])
+- Fall back to polling if webhook cannot be registered on Nuki ([@pree] - [#91013]) ([nuki docs])
+- Track availability of source sensor in utility meter ([@dgomes] - [#91035]) ([utility_meter docs])
+- Bump aiopyarr to 23.4.0 ([@tkdrob] - [#91110]) ([sonarr docs]) ([radarr docs]) ([lidarr docs])
+- Bump env_canada to 0.5.32 ([@michaeldavie] - [#91126]) ([environment_canada docs])
+- Relax calendar event validation to allow existing zero duration events ([@allenporter] - [#91129]) ([google docs]) ([calendar docs]) ([caldav docs])
+- Bump ulid-transform to 0.6.3 ([@bdraco] - [#91133])
+- Fix false positive in SQL sensor full table scan check ([@bdraco] - [#91134]) ([sql docs])
+- Reolink config flow fix custom port when USE_HTTPS not selected ([@starkillerOG] - [#91137]) ([reolink docs])
+- Fix all day event coercion logic ([@allenporter] - [#91169]) ([calendar docs]) ([local_calendar docs])
+- Reduce startup time for System Bridge integration ([@timmo001] - [#91171]) ([system_bridge docs])
+- Cleanup ZHA from Zigpy deprecated property removal ([@dmulcahey] - [#91180]) ([zha docs])
+- Bump `pytile` to 2023.04.0 ([@bachya] - [#91191]) ([tile docs])
+- Flush conversation name cache when an entity is renamed ([@emontnemery] - [#91214]) ([conversation docs])
+- Update frontend to 20230411.0 ([@bramkragten] - [#91219]) ([frontend docs])
+- Fix switch_as_x name ([@emontnemery] - [#91232]) ([switch_as_x docs])
+- Update Inovelli Blue Series switch support in ZHA ([@codyhackw] - [#91254]) ([zha docs])
+- Bump ZHA dependencies ([@puddly] - [#91291]) ([zha docs])
+- Restore use of local timezone for MariaDB/MySQL in SQL integration ([@bdraco] - [#91313]) ([recorder docs]) ([sql docs])
+- Google Assistant SDK: Fix broadcast command for Portuguese ([@tronikos] - [#91293]) ([google_assistant_sdk docs])
+- Remove codecov from Python test requirements ([@frenck] - [#91295])
+
+[#91293]: https://github.com/home-assistant/core/pull/91293
+[#91295]: https://github.com/home-assistant/core/pull/91295
+[@frenck]: https://github.com/frenck
+[@tronikos]: https://github.com/tronikos
+[google_assistant_sdk docs]: /integrations/google_assistant_sdk/
+[#90855]: https://github.com/home-assistant/core/pull/90855
+[#90956]: https://github.com/home-assistant/core/pull/90956
+[#90990]: https://github.com/home-assistant/core/pull/90990
+[#91013]: https://github.com/home-assistant/core/pull/91013
+[#91035]: https://github.com/home-assistant/core/pull/91035
+[#91110]: https://github.com/home-assistant/core/pull/91110
+[#91111]: https://github.com/home-assistant/core/pull/91111
+[#91126]: https://github.com/home-assistant/core/pull/91126
+[#91129]: https://github.com/home-assistant/core/pull/91129
+[#91133]: https://github.com/home-assistant/core/pull/91133
+[#91134]: https://github.com/home-assistant/core/pull/91134
+[#91137]: https://github.com/home-assistant/core/pull/91137
+[#91169]: https://github.com/home-assistant/core/pull/91169
+[#91171]: https://github.com/home-assistant/core/pull/91171
+[#91180]: https://github.com/home-assistant/core/pull/91180
+[#91191]: https://github.com/home-assistant/core/pull/91191
+[#91214]: https://github.com/home-assistant/core/pull/91214
+[#91219]: https://github.com/home-assistant/core/pull/91219
+[#91232]: https://github.com/home-assistant/core/pull/91232
+[#91254]: https://github.com/home-assistant/core/pull/91254
+[#91291]: https://github.com/home-assistant/core/pull/91291
+[#91313]: https://github.com/home-assistant/core/pull/91313
+[@allenporter]: https://github.com/allenporter
+[@amattas]: https://github.com/amattas
+[@bachya]: https://github.com/bachya
+[@balloob]: https://github.com/balloob
+[@bdraco]: https://github.com/bdraco
+[@bramkragten]: https://github.com/bramkragten
+[@codyhackw]: https://github.com/codyhackw
+[@dgomes]: https://github.com/dgomes
+[@dmulcahey]: https://github.com/dmulcahey
+[@emontnemery]: https://github.com/emontnemery
+[@frenck]: https://github.com/frenck
+[@michaeldavie]: https://github.com/michaeldavie
+[@pree]: https://github.com/pree
+[@puddly]: https://github.com/puddly
+[@starkillerOG]: https://github.com/starkillerOG
+[@timmo001]: https://github.com/timmo001
+[@tkdrob]: https://github.com/tkdrob
+[actiontec docs]: /integrations/actiontec/
+[advantage_air docs]: /integrations/advantage_air/
+[airly docs]: /integrations/airly/
+[caldav docs]: /integrations/caldav/
+[calendar docs]: /integrations/calendar/
+[conversation docs]: /integrations/conversation/
+[environment_canada docs]: /integrations/environment_canada/
+[flo docs]: /integrations/flo/
+[frontend docs]: /integrations/frontend/
+[google docs]: /integrations/google/
+[lidarr docs]: /integrations/lidarr/
+[local_calendar docs]: /integrations/local_calendar/
+[nuki docs]: /integrations/nuki/
+[radarr docs]: /integrations/radarr/
+[recorder docs]: /integrations/recorder/
+[reolink docs]: /integrations/reolink/
+[sonarr docs]: /integrations/sonarr/
+[sql docs]: /integrations/sql/
+[switch_as_x docs]: /integrations/switch_as_x/
+[system_bridge docs]: /integrations/system_bridge/
+[tile docs]: /integrations/tile/
+[utility_meter docs]: /integrations/utility_meter/
+[zha docs]: /integrations/zha/
+
+## Release 2023.4.4 - April 13
+
+- Bump python-homewizard-energy to 2.0.1 ([@DCSBL] - [#91097]) ([homewizard docs]) (dependency)
+- Bump aiolifx to 0.8.10 ([@bdraco] - [#91324]) ([lifx docs]) (dependency)
+- Update frontend to 20230411.1 ([@bramkragten] - [#91344]) ([frontend docs])
+
+[#90855]: https://github.com/home-assistant/core/pull/90855
+[#90956]: https://github.com/home-assistant/core/pull/90956
+[#91097]: https://github.com/home-assistant/core/pull/91097
+[#91111]: https://github.com/home-assistant/core/pull/91111
+[#91316]: https://github.com/home-assistant/core/pull/91316
+[#91324]: https://github.com/home-assistant/core/pull/91324
+[#91344]: https://github.com/home-assistant/core/pull/91344
+[@DCSBL]: https://github.com/DCSBL
+[@balloob]: https://github.com/balloob
+[@bdraco]: https://github.com/bdraco
+[@bramkragten]: https://github.com/bramkragten
+[@frenck]: https://github.com/frenck
+[actiontec docs]: /integrations/actiontec/
+[advantage_air docs]: /integrations/advantage_air/
+[airly docs]: /integrations/airly/
+[frontend docs]: /integrations/frontend/
+[homewizard docs]: /integrations/homewizard/
+[lifx docs]: /integrations/lifx/
+
## Need help? Join the community!
Home Assistant has a great community of users who are all more than willing
diff --git a/source/_posts/2023-04-11-homeseer-partner.markdown b/source/_posts/2023-04-11-homeseer-partner.markdown
new file mode 100644
index 00000000000..c1e99db7426
--- /dev/null
+++ b/source/_posts/2023-04-11-homeseer-partner.markdown
@@ -0,0 +1,34 @@
+---
+layout: post
+title: "HomeSeer joins Works with Home Assistant"
+description: "HomeSeer join the Works with Home Assistant partner program as a Z-Wave partner."
+date: 2023-04-11 00:00:00
+date_formatted: "April 11, 2023"
+author: Uwe Bernitt
+comments: true
+categories:
+ - Announcements
+og_image: /images/blog/2023-04-11-homeseer-partner/social.png
+---
+
+
+
+
+HomeSeer is now a member of the Works with Home Assistant partner program and they are committed to ensuring that their Z-Wave smart products are up to date and ready to use in Home Assistant.
+
+HomeSeer products are all Z-Wave Plus certified. Their smart dimmer/switches offer convenient RGB LEDs that may be programmed with automations to glow or blink 7 different colors when things happen in your home. The switches also support multi-tap actions for triggering automations and scenes.
+
+
+
+
+HomeSeer offers an AC powered Z-Wave multi-sensor that also includes an RGB LED for status updates. Additional Z-Wave products include a motion sensor, leak sensor, door/window sensor, floodlight sensor, and motorized water valve.
+
+HomeSeer Z-Wave devices work locally and integrate seamlessly with the Z-Wave integration in Home Assistant (Z-Wave interface required). As all connectivity is happening locally, status updates and control of your devices happen instantly in Home Assistant.
+
+With automatic firmware updates via Home Assistant we will continue to provide the best user experience for their devices.
+
+To learn more about HomeSeer products, have a look at their [website](https://shop.homeseer.com/collections/z-wave-products).
+
+PS: We’re actively working on easing the integration of the HomeSeer [Z-NET G3](https://shop.homeseer.com/collections/z-wave-products/products/z-net-g3-remote-z-wave-interface) into Home Assistant
+
+_[Learn more about the Works with Home Assistant partner program.](/blog/2022/07/12/partner-program/)_
diff --git a/source/help/reporting_issues.markdown b/source/help/reporting_issues.markdown
index 28829b8e969..9b6a60d1813 100644
--- a/source/help/reporting_issues.markdown
+++ b/source/help/reporting_issues.markdown
@@ -6,9 +6,9 @@ sidebar: false
If you have an installation, a setup or a configuration issue please use our [Forum](https://community.home-assistant.io/) to get help. We have a big community which will help you if they can.
-If you found a bug then please report it in one of our [trackers](/help/#bugs-feature-requests-and-alike). To help you and our developers to identify the issue quickly, please fill out the provided template. The "weird" content you will see is there to render your entry in a nice format after submitting. It's just [markdown](https://guides.github.com/features/mastering-markdown/).
+If you found a bug then please report it in one of our [trackers](/help/#bugs-feature-requests-and-alike). To help you and our developers to identify the issue quickly, please fill out the provided template. The "weird" content you will see is there to render your entry in a nice format after submitting. It's just [markdown](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax).
-Please refer to the **Settings** -> **About** page, which is accessible inside the Home Assistant frontend.
+Please refer to the [**Settings** -> **About**](https://my.home-assistant.io/redirect/info/) page, which is accessible inside the Home Assistant frontend.
## First Home Assistant release with the issue
@@ -26,8 +26,8 @@ There are many different ways to run Home Assistant. In this section please ment
Please add the link to the documentation of the integration in question. E.g.,
-- issue with the `random` sensor: [/integrations/random#sensor](/integrations/random#sensor)
-- issue with the `hue` integration: [/integrations/hue/](/integrations/hue/)
+- Issue with the `random` sensor: [/integrations/random#sensor](/integrations/random#sensor).
+- Issue with the `hue` integration: [/integrations/hue/](/integrations/hue/).
### Description of problem
diff --git a/source/images/blog/2023-04-11-homeseer-partner/homeseer_top.png b/source/images/blog/2023-04-11-homeseer-partner/homeseer_top.png
new file mode 100644
index 00000000000..95e3e840a5b
Binary files /dev/null and b/source/images/blog/2023-04-11-homeseer-partner/homeseer_top.png differ
diff --git a/source/images/blog/2023-04-11-homeseer-partner/marketing.jpg b/source/images/blog/2023-04-11-homeseer-partner/marketing.jpg
new file mode 100644
index 00000000000..ee9e49f2206
Binary files /dev/null and b/source/images/blog/2023-04-11-homeseer-partner/marketing.jpg differ
diff --git a/source/images/blog/2023-04-11-homeseer-partner/social.png b/source/images/blog/2023-04-11-homeseer-partner/social.png
new file mode 100644
index 00000000000..747b08c340a
Binary files /dev/null and b/source/images/blog/2023-04-11-homeseer-partner/social.png differ
diff --git a/source/images/frontpage/year-of-the-voice-chapter-2.png b/source/images/frontpage/year-of-the-voice-chapter-2.png
new file mode 100644
index 00000000000..1bd862359ba
Binary files /dev/null and b/source/images/frontpage/year-of-the-voice-chapter-2.png differ
diff --git a/source/images/integrations/z-wave/z-wave-device-info.png b/source/images/integrations/z-wave/z-wave-device-info.png
new file mode 100644
index 00000000000..2138c26241f
Binary files /dev/null and b/source/images/integrations/z-wave/z-wave-device-info.png differ
diff --git a/source/images/integrations/z-wave/z-wave-integration-config-panel.png b/source/images/integrations/z-wave/z-wave-integration-config-panel.png
new file mode 100644
index 00000000000..ddbf67fed11
Binary files /dev/null and b/source/images/integrations/z-wave/z-wave-integration-config-panel.png differ
diff --git a/source/images/integrations/z-wave/z-wave-integration-menu.png b/source/images/integrations/z-wave/z-wave-integration-menu.png
new file mode 100644
index 00000000000..55295e6efea
Binary files /dev/null and b/source/images/integrations/z-wave/z-wave-integration-menu.png differ
diff --git a/source/images/integrations/z-wave/z-wave-server-install-options-1-2.png b/source/images/integrations/z-wave/z-wave-server-install-options-1-2.png
new file mode 100644
index 00000000000..d99b16180d0
Binary files /dev/null and b/source/images/integrations/z-wave/z-wave-server-install-options-1-2.png differ
diff --git a/source/index.html b/source/index.html
index 1d341c6d87a..6f3b6c90f56 100644
--- a/source/index.html
+++ b/source/index.html
@@ -90,6 +90,17 @@ feedback: false