No configuration options for newly joined devices

MRobi1 commented 1 year ago

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?

NO, my problem is NOT within Z-Wave JS UI

Checklist

[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem was not mentioned there.

Describe the bug

What causes the bug? Included 3 "new" devices that were previously on the network

What do you observe? Inclusion completes fine. Able to control on/off of devices without issue. However no configuration options are present.

What did you expect to happen? Configuration options for devices to show up

Steps to reproduce the behavior: Include new device to network

Newly included device:

Same model device already on network:

Device information

Manufacturer: Inovelli Model name: LZW31-SN and LZW30-SN Node ID in your network: 76, 77, 78

How are you using `node-zwave-js`?

[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?

zwave-js-ui: 8.23.0 zwave-js: 11.12.0

Did you change anything?

yes (please describe)

If yes, what did you change?

Moved some devices to new positions in house over the period of about a week.

Excluded devices from network and uninstalled
A few days later re-installed in new location and included devices

Did this work before?

Yes (please describe)

If yes, where did it work?

These 3 devices were all previously on the network. Also have several of the same model devices already on the network and configuration options are all there.

Have attempted to re-interview several times. Tried refresh values/update topics. Factory reset devices. Exclude/Include multiple times. Restart ZwaveJS. Restart HA. Restart server. Unplug/re-plug zwave stick. Have tried to manually update parameters through HA which throws an error.

EDIT: Attempted downgrading firmware and upgrading firmware again but still no configuration options and still won't accept setting known parameters manually.

Attach Driver Logfile

zwavejs_2023-08-23.log

AlCalzone commented 1 year ago

2023-08-23T19:28:28.577Z CNTRLR   [Node 076] User-provided device config loaded
2023-08-23T19:28:28.580Z CNTRLR   [Node 077] User-provided device config loaded
2023-08-23T19:28:28.584Z CNTRLR   [Node 078] User-provided device config loaded

You're not using the official config files for those.

Actually you don't for a lot of other devices aswell:

2023-08-23T19:28:28.410Z CNTRLR   [Node 019] User-provided device config loaded
2023-08-23T19:28:28.413Z CNTRLR   [Node 020] User-provided device config loaded
2023-08-23T19:28:28.418Z CNTRLR   [Node 025] User-provided device config loaded
2023-08-23T19:28:28.424Z CNTRLR   [Node 026] User-provided device config loaded
2023-08-23T19:28:28.431Z CNTRLR   [Node 027] User-provided device config loaded
2023-08-23T19:28:28.436Z CNTRLR   [Node 028] User-provided device config loaded
2023-08-23T19:28:28.439Z CNTRLR   [Node 030] User-provided device config loaded
2023-08-23T19:28:28.443Z CNTRLR   [Node 032] User-provided device config loaded
2023-08-23T19:28:28.447Z CNTRLR   [Node 033] User-provided device config loaded
2023-08-23T19:28:28.450Z CNTRLR   [Node 035] User-provided device config loaded
2023-08-23T19:28:28.457Z CNTRLR   [Node 037] User-provided device config loaded
2023-08-23T19:28:28.461Z CNTRLR   [Node 038] User-provided device config loaded
2023-08-23T19:28:28.467Z CNTRLR   [Node 039] User-provided device config loaded
2023-08-23T19:28:28.474Z CNTRLR   [Node 040] User-provided device config loaded
2023-08-23T19:28:28.478Z CNTRLR   [Node 044] User-provided device config loaded
2023-08-23T19:28:28.483Z CNTRLR   [Node 045] User-provided device config loaded
2023-08-23T19:28:28.486Z CNTRLR   [Node 046] User-provided device config loaded
2023-08-23T19:28:28.491Z CNTRLR   [Node 047] User-provided device config loaded
2023-08-23T19:28:28.525Z CNTRLR   [Node 059] User-provided device config loaded
2023-08-23T19:28:28.533Z CNTRLR   [Node 060] User-provided device config loaded
2023-08-23T19:28:28.542Z CNTRLR   [Node 062] User-provided device config loaded

MRobi1 commented 1 year ago

You're not using the official config files for those.

Well that's interesting. How do I change that? Those other nodes are also all Inovelli devices, same models, and working fine.

MRobi1 commented 1 year ago

You're not using the official config files for those.

This turned out to be my issue. I had added these way way back to enable multicast, which is now part of the official config. Deleting the custom config files and re-interviewing worked. As for why the custom config files worked for probably almost 2 years, and also on all the other devices is beyond me. But they're no longer needed and it's working. Thanks!

AlCalzone commented 1 year ago

As for why the custom config files worked for probably almost 2 years, and also on all the other devices is beyond me

The format for config parameters changed long ago from an object to an array. A while ago I had to remove the code that parses the legacy format. Your config files were probably still in the old format, and this broke after re-interviewing.

zwave-js / node-zwave-js