jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Z-Wave integrations deprecation and migration status (#19856)

Browse Source
This commit is contained in:
Martin Hjelmare 2021-10-19 12:06:32 +02:00 committed by GitHub
parent 73b7851ab8
commit 6fc44eac1b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
source/_integrations/ozw.markdown
View File

@ -1,5 +1,5 @@
---
title: OpenZWave (beta)
title: OpenZWave (deprecated)
description: Instructions on how to integrate OpenZWave with Home Assistant.
ha_category:
- Switch
@ -22,14 +22,15 @@ ha_platforms:
- switch
---
This integration allows you to utilize OpenZWave's ozwdaemon to control a Z-Wave network over MQTT.
<div class='note warning'>
As of mid-2021 this integration, as well as the upstream ozwdaemon project, are not currently maintained. If you're starting out with Z-Wave in Home Assistant, we recommend that you use [the Z-Wave JS integration](/integrations/zwave_js).
This integration is deprecated. We recommend using [the Z-Wave JS integration](/integrations/zwave_js).
The OpenZWave integration will no longer receive any updates. The technical dependencies may render this integration unusable in the future, at which time it may be removed.
</div>
This integration allows you to utilize OpenZWave's ozwdaemon to control a Z-Wave network over MQTT.
## Requirements

2
source/_integrations/zwave.markdown
View File

@ -33,7 +33,7 @@ ha_platforms:
This integration is deprecated. We recommend using [the Z-Wave JS integration](/integrations/zwave_js).
The Z-Wave integration will no longer receive any updates. It will not be removed unless it becomes incompatible with a future version of Python.
The Z-Wave integration will no longer receive any updates. The technical dependencies may render this integration unusable in the future at which time it may be removed.
</div>

6
source/_integrations/zwave_js.markdown
View File

@ -493,16 +493,18 @@ You can keep track of the Roadmap for the Z-Wave JS integration [here](https://g
If you're new to Home Assistant, use Z-Wave JS.
The `zwave` integration has been marked as deprecated and will no longer receive any updates like new device files. The `ozw` integration will receive new device files if they are provided by upstream.
The `zwave` and `ozw` integrations have been marked as deprecated and will no longer receive any updates.
It is perfectly doable to switch over from one of the above mentioned previous integrations to the new Z-Wave JS integration. The good news is that your entire Z-Wave network is **stored on your stick** so you will not have to run through your house to recreate your network.
If you are currently running the [`zwave`](/integrations/zwave/) or [`ozw`](/integrations/ozw/) Z-Wave integration and it works fine, there is **no need to switch over at this time** to Z-Wave JS. What is important to know is that all development focus currently goes to Z-Wave JS. The previous implementations are provided as-is. They will **NOT be removed** without proper notice but in time there *might* come technical dependencies that render one or both of those integrations unusable.
If you are currently running the [`zwave`](/integrations/zwave/) or [`ozw`](/integrations/ozw/) Z-Wave integration we recommend you to migrate to Z-Wave JS. All development focus now goes to Z-Wave JS. The previous implementations are provided as-is. They will not be removed without proper notice but in time there might come technical dependencies that render one or both of those integrations unusable.
### Automatic migration wizard
For the `zwave` integration there is a migration wizard that will help you set up the Z-Wave JS integration, remove the `zwave` integration and migrate the entities and devices that can be mapped from the `zwave` integration to the Z-Wave JS integration. Some entities may not be able to migrate automatically and you will need to rename the corresponding available Z-Wave JS entities manually, after the migration. 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 migration wizard is available from the `zwave` integration configuration panel in the GUI.
There is no automatic migration wizard for the `ozw` integration. Please follow the manual migration path below if you want to migrate from `ozw` to Z-Wave JS.
### In a nutshell this is what the migration path looks like
1) Make a **backup** of your Home Assistant configuration. If you're running the supervisor this is very easy to do by creating a backup. You should do this so you'll be able to quickly revert if you may run into unexpected problems.