diff --git a/source/_integrations/geniushub.markdown b/source/_integrations/geniushub.markdown
index c1f61815c6e9..adb1779bfc57 100644
--- a/source/_integrations/geniushub.markdown
+++ b/source/_integrations/geniushub.markdown
@@ -10,7 +10,7 @@ ha_category:
ha_release: 0.92
ha_iot_class: Local Polling
ha_codeowners:
- - '@zxdavb'
+ - '@manzanotti'
ha_domain: geniushub
ha_platforms:
- binary_sensor
diff --git a/source/_integrations/geo_json_events.markdown b/source/_integrations/geo_json_events.markdown
index 58e138689a9f..5632cfefd0a2 100644
--- a/source/_integrations/geo_json_events.markdown
+++ b/source/_integrations/geo_json_events.markdown
@@ -10,7 +10,7 @@ ha_codeowners:
- '@exxamalte'
ha_platforms:
- geo_location
-ha_integration_type: integration
+ha_integration_type: service
---
The `geo_json_events` platform lets you integrate GeoJSON feeds. It retrieves events from a feed and shows information of those events filtered by distance to Home Assistant's location.
diff --git a/source/_integrations/google_assistant_sdk.markdown b/source/_integrations/google_assistant_sdk.markdown
index 96dfa3ac802c..787097796cb4 100644
--- a/source/_integrations/google_assistant_sdk.markdown
+++ b/source/_integrations/google_assistant_sdk.markdown
@@ -12,6 +12,7 @@ ha_codeowners:
ha_integration_type: service
ha_platforms:
- notify
+ha_quality_scale: platinum
---
The Google Assistant SDK integration allows Home Assistant to interact with Google Assistant. If you want to use Google Assistant (for example, from your phone or Google Home device) to interact with your Home Assistant managed devices, then you want the [Google Assistant](/integrations/google_assistant) integration.
diff --git a/source/_integrations/google_mail.markdown b/source/_integrations/google_mail.markdown
index e3ab58a9733c..ab133c30a091 100644
--- a/source/_integrations/google_mail.markdown
+++ b/source/_integrations/google_mail.markdown
@@ -21,7 +21,8 @@ The Google Mail integration allows you to connect your [Google Mail](https://mai
You need to configure developer credentials to allow Home Assistant to access your Google Account.
These credentials are the same as the ones for [Nest](/integrations/nest) and [Google Sheets](/integrations/google_sheets).
-If you have already set up credentials, you can do step 1 and then skip to step 13 on the below instructions.
+These are not the same as the one for [Google Calendar](/integrations/google).
+If you have already set up the correct credentials, you can do step 1 and then skip to step 13 on the below instructions.
{% details "Generate Client ID and Client Secret" %}
@@ -43,7 +44,7 @@ This section explains how to generate a Client ID and Client Secret on
13. Make sure **Publishing status** is set to production.
14. Click **Credentials** in the menu on the left-hand side of the screen, then click **Create credentials** (at the top of the screen), then select *OAuth client ID*.
15. Set the Application type to *Web application* and give this credential set a name (like "Home Assistant Credentials").
-16. Add https://my.home-assistant.io/redirect/oauth to *Authorized redirect URIs* then click **Create**.
+16. Add https://my.home-assistant.io/redirect/oauth to *Authorized redirect URIs* then click **Create**. This is not a placeholder and is the URI that must be used.
17. You will then be presented with a pop-up saying *OAuth client created* showing *Your Client ID* and *Your Client Secret*. Make a note of these (for example, copy and paste them into a text editor), as you will need these shortly. Once you have noted these strings, click **OK**. If you need to find these credentials again at any point, then navigate to *APIs & Services > Credentials*, and you will see *Home Assistant Credentials* (or whatever you named them in the previous step) under *OAuth 2.0 Client IDs*. To view both the *Client ID* and *Client secret*, click on the pencil icon; this will take you to the settings page for these credentials, and the information will be on the right-hand side of the page.
18. Double-check that the *Gmail API* has been automatically enabled. To do this, select **Library** from the menu, then search for *Gmail API*. If it is enabled you will see *API Enabled* with a green tick next to it. If it is not enabled, then enable it.
diff --git a/source/_integrations/google_sheets.markdown b/source/_integrations/google_sheets.markdown
index 149940c5a4b3..29380f28e80c 100644
--- a/source/_integrations/google_sheets.markdown
+++ b/source/_integrations/google_sheets.markdown
@@ -20,8 +20,9 @@ The integration currently only has access to that one document that is created d
## Prerequisites
You need to configure developer credentials to allow Home Assistant to access your Google Account.
-These credentials are the same as the ones for [Nest](/integrations/nest).
-If you have already set up credentials, you can do step 1 and then skip to step 13 on the below instructions.
+These credentials are the same as the ones for [Nest](/integrations/nest) and [Google Mail](/integrations/google_mail).
+These are not the same as the one for [Google Calendar](/integrations/google).
+If you have already set up the correct credentials, you can do step 1 and then skip to step 13 on the below instructions.
{% details "Generate Client ID and Client Secret" %}
@@ -43,7 +44,7 @@ This section explains how to generate a Client ID and Client Secret on
13. Make sure **Publishing status** is set to production.
14. Click **Credentials** in the menu on the left hand side of the screen, then click **Create credentials** (at the top of the screen), then select *OAuth client ID*.
15. Set the Application type to *Web application* and give this credential set a name (like "Home Assistant Credentials").
-16. Add https://my.home-assistant.io/redirect/oauth to *Authorized redirect URIs* then click **Create**.
+16. Add https://my.home-assistant.io/redirect/oauth to *Authorized redirect URIs* then click **Create**. This is not a placeholder and is the URI that must be used.
17. You will then be presented with a pop-up saying *OAuth client created* showing *Your Client ID* and *Your Client Secret*. Make a note of these (for example, copy and paste them into a text editor) as you will need these shortly. Once you have noted these strings, click **OK**. If you need to find these credentials again at any point then simply navigate to *APIs & Services > Credentials* and you will see *Home Assistant Credentials* (or whatever you named them in the previous step) under *OAuth 2.0 Client IDs*. To view both the *Client ID* and *Client secret*, click on the pencil icon, this will take you to the settings page for these credentials and the information will be on the right hand side of the page.
18. Double check that the *Google Drive API* has been automatically enabled. To do this, select **Library** from the menu, then search for *Google Drive API*. If it is enabled you will see *API Enabled* with a green tick next to it. If it is not enabled, then enable it.
diff --git a/source/_integrations/growatt_server.markdown b/source/_integrations/growatt_server.markdown
index 858b7f47a851..2b829ad7b0a5 100644
--- a/source/_integrations/growatt_server.markdown
+++ b/source/_integrations/growatt_server.markdown
@@ -7,9 +7,7 @@ ha_category:
ha_release: 0.99
ha_iot_class: Cloud Polling
ha_codeowners:
- - '@indykoning'
- '@muppet3000'
- - '@JasperPlant'
ha_domain: growatt_server
ha_platforms:
- sensor
diff --git a/source/_integrations/home_connect.markdown b/source/_integrations/home_connect.markdown
index 75b2eabe4fa4..457726e17eca 100644
--- a/source/_integrations/home_connect.markdown
+++ b/source/_integrations/home_connect.markdown
@@ -43,7 +43,10 @@ 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*: after performing the steps above **log out** of your Home Connect Developer account. If you don't so this, the configuration steps below will fail during OAuth authentication with the message `“error”: “unauthorized_client”`.
+*Important*:
+ - 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.
{% details "I have manually disabled My Home Assistant" %}
diff --git a/source/_integrations/honeywell.markdown b/source/_integrations/honeywell.markdown
index b058a6a6a849..62d59cea6026 100644
--- a/source/_integrations/honeywell.markdown
+++ b/source/_integrations/honeywell.markdown
@@ -19,14 +19,40 @@ ha_integration_type: integration
The Honeywell integration integrates Home Assistant with _US-based_ [Honeywell Total Connect Comfort (TCC)](https://mytotalconnectcomfort.com/portal/) climate systems.
-It uses the [somecomfort](https://github.com/kk7ds/somecomfort) client library. It does not support the home security functionality of TCC.
-
If your system is compatible with this integration, then you will be able access it via [https://mytotalconnectcomfort.com/portal/](https://mytotalconnectcomfort.com/portal/) (note the `/portal/`).
+- [Supported hardware](#supported-hardware)
+- [Climate](#climate)
+- [Sensor](#sensor)
+
+{% include integrations/config_flow.md %}
+
+## Supported hardware
+
+Home Assistant is integrated with the following devices through [https://mytotalconnectcomfort.com/portal/](https://mytotalconnectcomfort.com/portal/):
+
+- Thermostats
+ - Every thermostat is exposed as a climate entity
+ - Known working devices: TH6320R1004, RTH9585WF1004
+- Sensors
+ - A Temperature sensor entity.
+ - A Humidity sensor entity.
+ - Known working devices: C7089R1013
+
+Others devices like Security systems are not currently supported by this integration
+
+## Climate
+
+The climate platform integrates Honeywell US-based thermostats into Home Assistant, allowing control of the thermostat through the user interface. The current inside temperature, operating mode, and fan state are also displayed on the thermostat card.
+
+All [climate services](/integrations/climate) are supported except set_swing_mode
+
+## Sensor
+
+The sensor platform integrates outside temperature and outside humidity into Home Assistant as sensors for each device.
+
This integration will add Home Assistant sensors for the following:
|Sensor|Value|
--- | ---
|Outdoor temperature | Average temperature of all Honeywell Wireless Outdoor Sensors|
|Outdoor humidity | Average humidity of all Honeywell Wireless Outdoor Sensors|
-
-{% include integrations/config_flow.md %}
diff --git a/source/_integrations/jasco.markdown b/source/_integrations/jasco.markdown
new file mode 100644
index 000000000000..474134d852c3
--- /dev/null
+++ b/source/_integrations/jasco.markdown
@@ -0,0 +1,26 @@
+---
+title: Jasco
+description: Connect and control your Jasco Z-Wave devices using the Z-Wave integration
+ha_release: '2022.11'
+ha_iot_class: Local Push
+ha_category:
+ - Switch
+ - Plug
+ha_domain: jasco
+ha_integration_type: brand
+works_with:
+ - zwave
+ha_platforms:
+ - Switch
+ - Plug
+ha_iot_standard: zwave
+ha_brand: true
+---
+
+[Jasco](https://byjasco.com/) is a member of the Works with Home Assistant partner program for their Z-Wave products. Jasco is committed to making sure their products are up-to-date and ready to use in Home Assistant.
+
+Jasco Z-Wave devices work locally and integrate seamlessly with the Z-Wave integration in Home Assistant (Z-Wave stick required). As all connectivity is happening locally, status updates and controlling your devices happen instantly in Home Assistant.
+
+{% my add_zwave_device badge domain=page.ha_domain %}
+
+[Learn more about Z-Wave in Home Assistant.](/integrations/zwave_js/)
\ No newline at end of file
diff --git a/source/_integrations/marantz.markdown b/source/_integrations/marantz.markdown
index 23f1eed96d26..473504e74b4d 100644
--- a/source/_integrations/marantz.markdown
+++ b/source/_integrations/marantz.markdown
@@ -14,7 +14,7 @@ ha_codeowners:
ha_config_flow: true
ha_platforms:
- media_player
-ha_iot_class: Local Polling
+ha_iot_class: Local Push
ha_ssdp: true
---
diff --git a/source/_integrations/matter.markdown b/source/_integrations/matter.markdown
index 154fb765ff62..ea68e26abc46 100644
--- a/source/_integrations/matter.markdown
+++ b/source/_integrations/matter.markdown
@@ -1,5 +1,5 @@
---
-title: Matter
+title: Matter (BETA)
description: Instructions on how to integrate Matter with Home Assistant.
ha_category:
- Binary Sensor
@@ -10,11 +10,11 @@ ha_release: '2022.12'
ha_iot_class: Local Push
ha_config_flow: true
ha_codeowners:
- - '@marcelveldt'
- - '@MartinHjelmare'
+ - '@home-assistant/matter'
ha_domain: matter
ha_platforms:
- binary_sensor
+ - diagnostics
- light
- sensor
- switch
@@ -200,4 +200,3 @@ _This option is only available for Home Assistant OS (the recommended installati
This option is considered a very advanced setup and only for experienced users. You can find instructions on how to run the Matter Server in the [project repository](https://github.com/home-assistant-libs/python-matter-server).
_Disclaimer: Some links on this page are affiliate links._
-
diff --git a/source/_integrations/reolink.markdown b/source/_integrations/reolink.markdown
index 53fe393718f9..5b7e226a3757 100644
--- a/source/_integrations/reolink.markdown
+++ b/source/_integrations/reolink.markdown
@@ -3,6 +3,7 @@ title: Reolink IP NVR/camera
description: Instructions on how to integrate Reolink devices (NVR/cameras) into Home Assistant.
ha_category:
- Camera
+ - Update
ha_iot_class: Local Push
ha_release: 2023.1
ha_domain: reolink
@@ -12,6 +13,8 @@ ha_config_flow: true
ha_platforms:
- binary_sensor
- camera
+ - number
+ - update
ha_integration_type: integration
ha_dhcp: true
---
@@ -146,6 +149,7 @@ The following models have been tested and confirmed to work:
- C2 Pro
- E1 Zoom
- E1 Outdoor
+- RLC-410
- RLC-410W
- RLC-411
- RLC-420
@@ -170,6 +174,7 @@ Battery-powered cameras are not yet supported.
The following models are lacking the HTTP webserver API and can therfore not work with this integration:
- E1 Pro
+- E1
## Troubleshooting
diff --git a/source/_integrations/rympro.markdown b/source/_integrations/rympro.markdown
index 3e53b11ca292..8f2fe200bd86 100644
--- a/source/_integrations/rympro.markdown
+++ b/source/_integrations/rympro.markdown
@@ -8,6 +8,8 @@ ha_iot_class: Cloud Polling
ha_config_flow: true
ha_codeowners:
- '@OnFreund'
+ - '@elad-bar'
+ - '@maorcc'
ha_domain: rympro
ha_platforms:
- sensor
diff --git a/source/_integrations/scrape.markdown b/source/_integrations/scrape.markdown
index 7ea61e881f94..53834dd6ce71 100644
--- a/source/_integrations/scrape.markdown
+++ b/source/_integrations/scrape.markdown
@@ -145,15 +145,6 @@ sensor:
description: Defines a template for the entity picture of the sensor.
required: false
type: template
- attributes:
- description: Defines templates for attributes of the sensor.
- required: false
- type: map
- keys:
- "attribute: template":
- description: The attribute and corresponding template.
- required: true
- type: template
device_class:
description: Sets the class of the device, changing the device state and icon that is displayed on the UI (see below). It does not set the `unit_of_measurement`.
required: false
diff --git a/source/_integrations/screenlogic.markdown b/source/_integrations/screenlogic.markdown
index b204a24a2d24..809cbb10e268 100644
--- a/source/_integrations/screenlogic.markdown
+++ b/source/_integrations/screenlogic.markdown
@@ -8,7 +8,7 @@ ha_category:
- Hub
- Sensor
- Switch
-ha_iot_class: Local Polling
+ha_iot_class: Local Push
ha_config_flow: true
ha_dhcp: true
ha_codeowners:
diff --git a/source/_integrations/signal_messenger.markdown b/source/_integrations/signal_messenger.markdown
index 5a8ce36120b4..8855e0d0f741 100644
--- a/source/_integrations/signal_messenger.markdown
+++ b/source/_integrations/signal_messenger.markdown
@@ -65,6 +65,40 @@ recipients:
type: string
{% endconfiguration %}
+
+## Sending messages to Signal to trigger events
+
+You can use Signal Messenger REST API as a Home Assistant trigger. In this example, we will make a simple chatbot. If you write anything to your Signal account linked to Signal Messenger REST API, the automation gets triggered, with the condition that the number (attribute source) is correct, to take action by sending a Signal notification back with a "Message received!".
+
+To accomplish this, edit the configuration of Home Assistant, adding a [RESTful resource](/integrations/rest/) as follows:
+
+```yaml
+- resource: "http://127.0.0.1:8080/v1/receive/
"
+ headers:
+ Content-Type: application/json
+ sensor:
+ - name: "Signal message received"
+ value_template: "{{ value_json[0].envelope.dataMessage.message }}" #this will fetch the message
+ json_attributes_path: $[0].envelope
+ json_attributes:
+ - source #using attributes you can get additional information, in this case, the phone number.
+ ```
+You can create an automation as follows:
+
+```yaml
+...
+trigger:
+ - platform: state
+ entity_id:
+ - sensor.signal_message_received
+ attribute: source
+ to: ""
+action:
+ - service: notify.signal
+ data:
+ message: "Message received!"
+```
+
## Examples
A few examples on how to use this integration as actions in automations.
diff --git a/source/_integrations/thread.markdown b/source/_integrations/thread.markdown
index 118d689e06b4..d1a623f0c797 100644
--- a/source/_integrations/thread.markdown
+++ b/source/_integrations/thread.markdown
@@ -9,6 +9,9 @@ ha_domain: thread
ha_iot_class: Local Polling
ha_integration_type: service
ha_config_flow: true
+ha_platforms:
+ - diagnostics
+ha_zeroconf: true
---
The Thread integration helps you track the different Thread networks in your home and helps you manage their credentials. It is currently a work in progress.
@@ -19,4 +22,6 @@ To connect a Thread network to Home Assistant, Thread Border Routers (TBRs) are
Home Assistant communicates with TBRs over the local network. This means that TBRs do not have to be physically attached to Home Assistant to be used. You might already have a TBR as part of other products in your home, like a Google Nest Hub Gen 2 or Apple HomePod Mini. Each vendor forms their own network when you start using their products, so you can end up having a Home Assistant, an Apple, and a Google Thread network in your home. These are all separate networks using different credentials, which prevents devices to roam between TBRs.
-It is possible to align credentials for TBRs from different vendors and have them form a single network together. This allows you to freely move devices between rooms without losing connectivity. To do this, you need to make sure that all TBRs use the same credentials.
+It is possible to align credentials for TBRs from different vendors and have them form a single network together. This allows you to freely move devices between rooms without losing connectivity. To do this, you need to make sure that all TBRs use the same credentials. Sadly, this works differently for each TBR vendor.
+
+Home Assistant will sync the Thread credentials with Google when starting to commission a Matter device via the Home Assistant Companion app. For other vendors, if the vendor allows you to see the operational dataset in TLV format, you can import it to Home Assistant from the Thread panel.
diff --git a/source/_integrations/tplink_omada.markdown b/source/_integrations/tplink_omada.markdown
index 54303db13ce8..51ab344e5c98 100644
--- a/source/_integrations/tplink_omada.markdown
+++ b/source/_integrations/tplink_omada.markdown
@@ -1,5 +1,5 @@
---
-title: TP-Link Omada SDN Controller
+title: TP-Link Omada
description: Instructions on integrating TP-Link Omada SDN networking devices to Home Assistant.
ha_category:
- Hub
@@ -11,7 +11,7 @@ ha_codeowners:
ha_domain: tplink_omada
ha_platforms:
- switch
-ha_integration_type: integration
+ha_integration_type: hub
---
The TP-Link Omada SDN Controller integration allows you to control your [TP-Link Omada SDN Devices](https://www.tp-link.com/us/omada-sdn/) such as network switches, access points, and internet gateways. It requires a local Omada controller (software or hardware controllers) and does not currently support the paid-for TP-Link Omada Cloud Management SAAS Platform.
diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown
index 8efa95fe3d49..2f3a4b484229 100644
--- a/source/_integrations/xiaomi_miio.markdown
+++ b/source/_integrations/xiaomi_miio.markdown
@@ -372,6 +372,51 @@ Child Lock | Turn on/off the child lock
Learn Mode | Turn on/off the learn mode
LED | Turn on/off the LED
+
+### Air Purifier MA2 (zhimi.airpurifier.ma2)
+
+- Power (on, off)
+- Operation modes (Auto, Silent, Favorite)
+- Attributes (fan platform)
+ - `extra_features`
+ - `turbo_mode_supported`
+ - `button_pressed`
+ - `preset_modes`
+ - `preset_mode`
+ - `sleep_time`
+ - `sleep_mode_learn_count`
+ - `use_time`
+ - `sleep_mode`
+ - `friendly_name`
+ - `supported_features`
+
+Number | Description
+----------------------- | -----------------------
+Favorite Level | Set the favorite level
+
+- Sensor entities
+
+Sensor | Description | Enabled by default
+----------------------- | ----------------------- | -----------------------
+Filter Life Remaining | The remaining life of the filter | True
+Filter Use | Filter usage time in hours | True
+Humidity | The current humidity measured | True
+Motor Speed | The current motor speed measured in rpm | True
+PM2.5 | The current particulate matter 2.5 measured | True
+Temperature | The current temperature measured | True
+Illuminance | The current illuminance meassured on top of the device 0-200lux| True
+Use Time | The accumulative number of seconds the device has been in use | False
+
+- Switch entities
+
+Switch | Description
+----------------------- | -----------------------
+Buzzer | Turn on/off the buzzer
+Child Lock | Turn on/off the child lock
+Learn Mode | Turn on/off the learn mode
+LED | Turn on/off the LED
+
+
### Air Purifier 2S (zhimi.airpurifier.mc1)
- Power (on, off)
diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown
index a7852001cdf4..f07c261a616b 100644
--- a/source/_integrations/zwave_js.markdown
+++ b/source/_integrations/zwave_js.markdown
@@ -44,7 +44,7 @@ ha_integration_type: hub
ha_zeroconf: true
---
-This integration allows you to control a Z-Wave network via the [Z-Wave JS](https://zwave-js.github.io/node-zwave-js/#/) driver. This is our recommended Z-Wave integration for Home Assistant. If you're migrating from the legacy `zwave`, see [our migration instructions](#migrating-from-previous-z-wave-implementations).
+This integration allows you to control a Z-Wave network via the [Z-Wave JS](https://zwave-js.github.io/node-zwave-js/#/) driver.
To Run Z-Wave you will need a [Supported Z-Wave dongle](/docs/z-wave/controllers/#supported-z-wave-usb-sticks--hardware-modules), a running Z-Wave JS server (using only **one** of the add-ons or installation methods described below), and the Z-Wave integration.
@@ -575,65 +575,32 @@ 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. |
-## Migrating from previous Z-Wave implementations
+## Advanced Features (UI Only)
-If you are switching from the legacy `zwave` integration to the new Z-Wave integration, you will not need to recreate your entire network, as the network is **stored on your stick**. A few things, such as how you receive [central scene events](#events) will work differently than they did before.
+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.
-### Automatic migration wizard
+All of these features can be accessed either in the Z-Wave integration configuration panel or in a Z-Wave device's device panel.
-If you are using the legacy `zwave` integration, there is a migration wizard that will help you set up the Z-Wave integration, remove the legacy `zwave` integration and migrate the entities and devices that can be mapped from the legacy `zwave` integration to the Z-Wave integration. The migration wizard is available from the legacy `zwave` integration configuration panel in the GUI.
+### Integration Configuration Panel
-Some entities may not be able to migrate automatically and you will need to rename the corresponding available Z-Wave entities manually. Before completing the migration you will be shown a list of entities that could not be migrated automatically, and you'll have the option to abort or continue with the migration.
+The following features can be accessed from the integration configuration panel:
-### Manual migration path from legacy `zwave` or OpenZWave
+- **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 zwave-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.
-1) Make a **backup** of your Home Assistant configuration. You should do this so you'll be able to quickly revert if you encounter unexpected problems.
+### Device Panel
- Write down/copy your Z-Wave network key somewhere, you are going to need it later.
+The following features can be accessed from the device panel of a Z-Wave device:
- Make a list of what node ID belongs to each device. Your network (Nodes and their config etc) is stored on the stick but the names you gave your devices and entities are not. This step is optional but will save you a lot of time later.
-
-2) Remove the legacy `zwave` or OpenZWave integration from Home Assistant: Settings --> Devices & Services --> Z-Wave (or OpenZWave) --> Press the three dots and click Delete.
-
-
-
- If you have configured the legacy `zwave` manually, make sure to also remove the `zwave:` section from your `configuration.yaml`.
-
-
-
-3) If you were running the OpenZWave beta, make sure to stop (or even remove) the OpenZWave add-on, also make sure it doesn't start automatically at startup.
-
-4) Restart your Home Assistant host. This step is important to make sure that your Z-Wave stick is released by the operating system.
-
-5) Install the Z-Wave JS Server of your choice. If you run the supervisor and you'd like to run the standard add-on, you can skip this step if you want. The add-on is installed automatically for you when you choose so in the integration set-up. Remember to fill in the network key you've saved before.
-
-6) Set up the Z-Wave integration and connect it to the server. You should see your nodes being detected by Home Assistant. Carefully watch if the status of the node is "ready". This means it's been fully interviewed (and those details cached) by the Z-Wave JS driver. Battery-powered nodes will only be interviewed when they wake up (at scheduled intervals) or if you manually wakeup the device (refer to the device's manual for instructions).
-
-
-
- Activating a battery powered sensor, such as opening a door sensor, is *not* the same as waking up the device.
-
-
-
-7) Once a node is ready, the entities will be created. Only at this point, is it safe to rename the device (and so its entities). This is actually the only real hard part of the migration as you will need to name all your devices again.
-
-8) Enjoy your super fast up-to-date Z-Wave network in Home Assistant with support for all modern devices!
-
-#### Need more help with your migration to Z-Wave?
-
-Please see our [Frequently Asked Questions](#frequently-asked-questions).
-
-There are also a few topics created on the forums that might be helpful:
-
-- [OpenZwave (beta) -> Z-Wave JS Official add-on](https://community.home-assistant.io/t/switching-from-openzwave-beta-to-zwave-js/276723)
-
-- [OpenZwave (beta) -> ZwaveJS2MQTT](https://community.home-assistant.io/t/switching-from-openzwave-beta-to-zwavejs2mqtt/276724)
-
-- [Z-Wave legacy (1.4) -> Z-Wave JS Official add-on](https://community.home-assistant.io/t/switching-from-zwave-1-4-to-zwave-js/276718/2)
-
-- [Z-Wave legacy (1.4) -> ZwaveJS2MQTT](https://community.home-assistant.io/t/switching-from-zwave-1-4-to-zwavejs2mqtt/276721)
-
-You can also visit the `#zwave` channel on [our discord](/join-chat/).
+- **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
@@ -679,8 +646,6 @@ This is considered a very advanced use case. In this case you run the Z-Wave JS
For new installations, unique default keys will be auto-generated for you by the Z-Wave JS add-on. You can also generate those network keys in the Settings section of Z-Wave JS UI.
-If migrating from the legacy `zwave` integration, your network key from those integration should be entered as the S0 network key. Those integrations did not support S2 security, so you will not yet have S2 network keys to configure.
-
Make sure that you keep a backup of these keys in a safe place. You will need to enter the same keys to be able to access securely paired devices.
@@ -724,23 +689,6 @@ Some Z-Wave USB sticks can be auto-discovered, which can simplify the Z-Wave set
Additional devices may be discoverable, however only devices that have been confirmed discoverable are listed above.
-#### Is there a way to easily export a dump of all my current Z-Wave nodes before I migrate?
-
-You can run the script below in the Developer Tools to get a full oversight of your nodes and their entities.
-
-{% raw %}
-
-```yaml
-{%- for node, zstates in states | selectattr('attributes.node_id', 'in', range(1000)) | groupby('attributes.node_id') %}
-
-{%- for s in zstates %}
-Node {{ node }};{{ s.name }};{{ s.entity_id }}{% endfor %}
-
-{%- endfor %}
-```
-
-{% endraw %}
-
#### What happened to Zwavejs2Mqtt or the Z-Wave JS to MQTT add-on?
Zwavejs2Mqtt was renamed Z-Wave JS UI in September 2022. They are synonymous with no difference between their capabilities.
@@ -779,11 +727,6 @@ Correct, the Z-Wave JS UI project existed before Home Assistant had plans to mov
Sure, in the settings of Z-Wave JS UI, make sure to enable "WS Server" and disable "Gateway".
-#### How do I use my OZW network key in Z-Wave JS UI?
-
-You can use your existing network key in Z-Wave JS UI but you need to slightly adjust it.
-The OZW looks like this: `0x01, 0x02, 0x03 etc.` while the network key format accepted in Z-Wave JS UI looks like this `0102030405 etc.`. You can simply edit your existing key and remove the `"0x"` part and the `", "` part so it becomes one large string of numbers.
-
#### Should I name my devices in Home Assistant, or in Z-Wave JS UI?
Ultimately, this is a personal decision. If you provide a name or location for a device in the Z-Wave JS UI, that name will be imported into Home Assistant when the integration is reloaded or Home Assistant is restarted. Any entity names, however, will not change if the device has already been set up by Home Assistant. Names set in Z-Wave JS UI _will not_ overwrite changes that have already been made in Home Assistant.
@@ -828,7 +771,7 @@ S2 security does not impose additional network traffic and provides additional b
#### I'm having a problem, what should I do first?
-_Many_ reported issues result from RF interference caused by the system's USB ports. This can manifest in many ways, including devices that won't include at all, devices that won't include securely, sensors with erroneous values (packets corrupted), delayed control of devices, or no ability to control devices. These problems can be intermittent, and they may be newly apparent after switching from `ozw`, though they existed before, as Z-Wave interviews devices and reports errors differently.
+_Many_ reported issues result from RF interference caused by the system's USB ports. This can manifest in many ways, including devices that won't include at all, devices that won't include securely, sensors with erroneous values (packets corrupted), delayed control of devices, or no ability to control devices.
**All users are encouraged to use a USB extension cable to prevent such interference.** Please try such a cable before opening an issue or requesting support on Discord. It will nearly always be the first troubleshooting step that we ask you to take anyway.
diff --git a/source/_posts/2023-03-01-release-20233.markdown b/source/_posts/2023-03-01-release-20233.markdown
new file mode 100644
index 000000000000..9b6a6e557fe6
--- /dev/null
+++ b/source/_posts/2023-03-01-release-20233.markdown
@@ -0,0 +1,686 @@
+---
+layout: post
+title: "2023.3: Dialogs!"
+description: "A brand new restart dialog, ask Assist about the state of your home, amazing new dialogs for lights and switches, Thread & Matter updates, control the precision of your sensors, and Python 3.11 support."
+date: 2023-03-01 00:00:00
+date_formatted: "March 1, 2023"
+author: Franck Nijhof
+author_twitter: frenck
+comments: true
+categories:
+ - Release-Notes
+ - Core
+og_image: /images/blog/2023-03/social.png
+---
+
+