mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 15:26:59 +00:00
Remove zwave js GUI node configuration limitation (#17203)
This commit is contained in:
parent
17072f3ee4
commit
b6db2602db
@ -31,7 +31,7 @@ ha_platforms:
|
||||
|
||||
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.
|
||||
|
||||
Please review the limitations [below](/integrations/zwave_js/#current-limitations) before you get started as a few devices still may not work or only work partially.
|
||||
Please review the limitations [below](/integrations/zwave_js/#current-limitations) before you get started as a few devices still may not work or only work partially.
|
||||
|
||||
## Quick start (Home Assistant including Supervisor)
|
||||
|
||||
@ -100,7 +100,7 @@ Example 3:
|
||||
```yaml
|
||||
service: zwave_js.set_config_parameter
|
||||
target:
|
||||
entity_id: switch.fan
|
||||
entity_id: switch.fan
|
||||
data:
|
||||
entity_id: switch.fan
|
||||
parameter: "LED 1 Blink Status (bottom)"
|
||||
@ -120,7 +120,7 @@ This service will bulk set multiple partial configuration parameters. Be warned
|
||||
|
||||
#### Examples of bulk setting partial parameter values
|
||||
|
||||
Let's use parameter 21 for [this device](https://devices.zwave-js.io/?jumpTo=0x031e:0x000a:0x0001:0.0) as an example to show how partial parameters can be bulk set. In this case, we want to set `0xff` to `127`, `0x7f00` to `10`, and `0x8000` to `1` (or the raw value of `4735`).
|
||||
Let's use parameter 21 for [this device](https://devices.zwave-js.io/?jumpTo=0x031e:0x000a:0x0001:0.0) as an example to show how partial parameters can be bulk set. In this case, we want to set `0xff` to `127`, `0x7f00` to `10`, and `0x8000` to `1` (or the raw value of `4735`).
|
||||
|
||||
<div class='note'>
|
||||
|
||||
@ -288,7 +288,6 @@ Value Notification example:
|
||||
As this integration is still in the early stages there are some important limitations to be aware of.
|
||||
|
||||
- While support for the most common devices is working, 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).
|
||||
- Configuration of Z-Wave nodes within the Home Assistant UI is not yet implemented, but a [service](#service-zwave_js.set_config_parameter) is available with limited configuration capabilities. If the service doesn't meet your needs, you will need to use another tool, such as [zwavejs2mqtt](https://github.com/zwave-js/zwavejs2mqtt), to manage device configuration.
|
||||
- There currently is no migration path available from any of the other Z-Wave implementations in Home Assistant. Your Z-Wave network is however stored on your stick so migrating will only require you to redo your device and entity naming.
|
||||
|
||||
You can keep track of the Roadmap for the Z-Wave JS integration [here](https://github.com/home-assistant-libs/zwave-js-server-python/issues/56).
|
||||
|
Loading…
x
Reference in New Issue
Block a user