Z-WAVE Device configuration file not recognized

Hi there!

This question is related to my post “Merten Shutter Connect 504519 – Not Working Command Classes:

How can I be sure that Z-Wave JS UI (version 10.1.5) is using the custom configuration file I provided in the UI under “Store,” in the “Config” folder? How can I ensure that it is actually being used?

The log (as mentioned in the post above) only shows:
“2025-03-31T20:57:53.159Z CNTRLR [Node 009] ConfigurationCC: Loading configuration parameters from device config”

Thank you,
Christoph

After you restart Z-Wave JS, in the driver logs you’ll see these messages for each node:

Embedded device config loaded
User-provided device config loaded

The first means the Z-Wave JS device config is being used. The second means your config override is being used.

Thanks a lot.

There is : 2025-04-14T16:40:01.913Z CNTRLR [Node 009] Embedded device config loaded

I find no string like user-“provided” (using Strg-F) in the log.

May I bother you with this screen-shot?

The filename is the same as in

The content is postet in the related topic (see above)

I tried many things (Google, ChatGPT, Forums) to get around on my own, but I am stuck.

Thanks for your support to get my Covers running again under homeasssitant.

Christoph

You need to restart Z-Wave JS UI after uploading the config.

Also, in your other topic:

2025-03-31T20:51:23.314Z CNTRLR « [Node 009] node info received
                                  supported CCs:
                                  · Manufacturer Specific
                                  · Version
                                  · Configuration
                                  · Association
                                  · Multi Channel Association
                                  · Basic Window Covering
...
2025-03-31T20:51:38.343Z CNTRLR   [Node 009]   skipping query for Basic Window Covering (0x50) because max imple
                                  mented version is 0

The command class is already detected so you don’t need to add it.

The problem is that Z-Wave JS doesn’t support “Basic Window Covering” Command Class. You should be able to use Multilevel Switch instead.

That was the key to get the edited .json in the config section recognized. THANKS!!!

One step further… and now still nothing happens when using the “perform a level change” button:

Here we have [9-38-0-Down] while the following works with [2-38-1-Down]
While this is a similar “Rolladen”-Controller (it features a light-sensor) and uses the same configuration file , this is 1:

I think this number relates to the lifeline.

In the groups section I entered this:

Where to change this parameter or link ?

Thanks in advance

Christoph

I would start looking at driver debug logs. https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs

Where to change this parameter or link ?

Sorry, I don’t understand the question. Change what parameter? What’s a link?

Hello!

BTW: The shutter moves when the physical buttons are used.
All existing switches are single-surface with one up and one down button. They are Merten 503525

The debug-log said:

> 2025-04-15 09:58:26.835 INFO Z-WAVE: Calling api writeValue with args: [
>   { nodeId: 9, commandClass: 38, endpoint: 0, property: 'Up' },
>   true,
>   null,
>   [length]: 3
> ]
> 2025-04-15 09:58:26.838 INFO Z-WAVE: Writing true to 9-38-0-Up
> 2025-04-15T07:58:26.844Z DRIVER   one or more queues busy
> 2025-04-15T07:58:26.848Z DRIVER » [Node 009] [REQ] [SendDataBridge]
>                                   │ source node id:   1
>                                   │ transmit options: 0x25
>                                   │ callback id:      42
>                                   └─[MultilevelSwitchCCStartLevelChange]
>                                       startLevel: 0 (ignored)
>                                       direction:  up
> 2025-04-15T07:58:26.849Z SERIAL » 0x011100a901090526042000ff25000000002ab8                            (19 bytes)
> 2025-04-15T07:58:26.856Z SERIAL « [ACK]                                                                   (0x06)
> 2025-04-15T07:58:26.857Z SERIAL « 0x010401a90152                                                       (6 bytes)
> 2025-04-15T07:58:26.860Z SERIAL » [ACK]                                                                   (0x06)
> 2025-04-15T07:58:26.862Z DRIVER « [RES] [SendDataBridge]
>                                     was sent: true
> 2025-04-15T07:58:26.999Z SERIAL « 0x011d00a92a00000d01a27f7f7f7f0201030a000000010100007f7f7f7f7fba    (31 bytes)
> 2025-04-15T07:58:27.005Z SERIAL » [ACK]                                                                   (0x06)
> 2025-04-15T07:58:27.008Z DRIVER « [REQ] [SendDataBridge]
>                                     callback id:            42
>                                     transmit status:        OK, took 130 ms
>                                     repeater node IDs:      10
>                                     routing attempts:       1
>                                     protocol & route speed: Z-Wave, 9.6 kbit/s
>                                     routing scheme:         LWR
>                                     ACK RSSI:               -94 dBm
>                                     ACK RSSI on repeaters:  N/A
>                                     ACK channel no.:        2
>                                     TX channel no.:         1
> 2025-04-15 09:58:27.016 INFO Z-WAVE: [Node 009] Value updated: 38-0-Up false => true
> 2025-04-15 09:58:27.018 INFO Z-WAVE: Success zwave api call writeValue { status: 254 }

Sorry—hopefully this clarifies things:
Node 2 (as shown in the image in the post above) exposes two switches—similar to a double switch (even though it’s not). These are accessible via endpoint 1 and endpoint 2 (like left and right—correct?). The control for endpoint 1 from Node 2 works fine.
However, Node 9 only offers endpoint 0 (as seen in the image in the post above), and I don’t understand why—especially since it’s nearly the same device. It doesn’t respond.
So, my intention was to change the endpoint, but I couldn’t figure out how to do that. I tried forcing it to endpoint 1 in the config, but the change was rejected when I attempted a re-interview.

Thanks

Christoph