Z-Wave JS UI, and Z-Wave JS

Configuration Z-Wave
1

I’ve been using Z-Wave JS addon for a while to manage zwave devices. I now want to try using Z-Wave JS UI to set a parameter that is not yet supported by the official Z-Wave JS addon.

I just installed the Z-Wave JS UI addon, and I think it is connected to Z-Wave JS. I’m a little confused, is there any more configuration I need to do before it will work? As none of my devices are showing up in the Z-Wave JS UI. I thought I only needed to setup my USB device/etc if I was using MQTT gateway (Which I don’t think I need).

Thanks!

2

You can also set unsupported config parameters in HA using the zwave_js.invoke_cc_api service call.

service: zwave_js.invoke_cc_api
data:
  command_class: "112"
  method_name: set
  parameters:
    - parameter: 7
      value: 1
      valueSize: 1

Where parameter is the parameter number, value is the value to set, and valueSize is the size of the parameter in bytes (1, 2, or 4).

You need to carefully follow the instructions in the docs to switch add-ons, otherwise Z-Wave JS UI won’t work properly and you’ll have major problems. https://www.home-assistant.io/integrations/zwave_js/#how-do-i-switch-between-the-official-z-wave-js-add-on-and-the-z-wave-js-ui-add-on

The add-on has its own documentation you should be following for configuration. Every add-on has documentation on a separate tab of the add-on’s page, so the same instructions are available there.

2 Likes
3

Thank you @freshcoast ! The api call is exactly what I am looking for.

4

Does this look correct @freshcoast? I’m trying to override minimum dimmness value on the new inovelli red series firmware. It is supposed to be able to go above 45.

alias: Inovelli - 05 - minimum dimmer level
description: ""
trigger:
  - platform: sun
    event: sunrise
    offset: "+00:00:00"
condition: []
action:
  - service: zwave_js.invoke_cc_api
    data:
      command_class: "112"
      method_name: set
      parameters:
        - parameter: 5
          value: 50
          valueSize: 1
    target:
      device_id: f5a1593343f660341a242f6e6fe8b48d
5

That looks correct to me. Is it not working? If this is the LZW31-SN, where do you see that the minimum dim level has been relaxed to values > 45? I checked the firmware change log and couldn’t find anything.

6

According to these posts, they have relaxed the setting in recent firmware versions:

Ya, it’s still not working for me. I’ll try with another light I just upgraded to 1.61 firmware.

7

Double check that the firmware was updated properly. The firmware update currently doesn’t work in HA, using the update entities. The updates were also pulled (yesterday) from the update service until this problem can be addressed.

Oh, and 1.61 is a beta firmware so it’s not exposed via the update service. Presumably you updated manually then… I’d still confirm the version is correct.

8

Ya, i’m definitely updating the firmware correctly. Both targets. I’m following the instructions here, and flashing both targets: https://support.inovelli.com/portal/en/kb/articles/how-to-s-general-how-to-update-firmware-z-stick-z-wave-pc-controller
and this: https://support.inovelli.com/portal/en/kb/articles/firmware-change-log-lzw31-sn-dimmer-switch-red-series

9

You can confirm the command is sent via the debug driver logs. https://www.home-assistant.io/integrations/zwave_js/#how-to-access-the-z-wave-logs

If it’s being sent but not sticking, then it’s a device problem.

10

I just set it by the api, on this light. And it works. So thanks! There is also a patch on github to allow this: LZW31-SN -allow higher minimum dim level up to 98 for FW 1.57+ by kreene1987 · Pull Request #5181 · zwave-js/node-zwave-js · GitHub

11

If you want to use that config file, then you will need to switch to Z-Wave JS UI. https://zwave-js.github.io/zwave-js-ui/#/device-support/custom-device-files

12

Oh. Is the official zwave js addon, config files in a different location?

13

The official add-on does not support the ability to use custom configuration files. You can do it if you access the data volume directly, but that is unsupported.

14

Ok. Do you know where the official configuration files are on GitHub so I can do a pull request? Nobody should have to go through the pain I have with flashing different versions and testing the minimum dimmer value. Lol

15

You’ve already linked the pull request.

16

I think there was a misunderstanding. You could use custom config files in the official add-on, but you need to manually access the docker volume that contains the cache directory and copy in the files. Accessing add-on files is not officially supported, so this is not a good solution for most users. If you know how to, go for it.

On the other-hand, Z-Wave JS UI has a directory browser that lets you upload files, which you can use to upload custom configuration files. See the doc link I posted previously. Anyone can do this without any hacks.

17

Ok. Thanks. Good to know about that.

18

Hi,
I try to run “Z-Wave JS UI” beside my “Z-Wave JS” integration. I only want to use the panel(s)

The configuration is like

grafik
grafik1608×810 36.9 KB

It tells me, that it is connected by I don’t see any devices

grafik
grafik1611×565 20.5 KB

and if I click on

grafik
grafik1605×424 20.5 KB

or
grafik
grafik1606×415 23.1 KB

I get an error.

Anything I can do?

Thank you!

19

That won’t work. You can’t run both beside with a single coordinator. You have to choose one. :wink:

20

But the documentation says that it should work

https://zwave-js.github.io/zwave-js-ui/#/homeassistant/homeassistant-official

and here