Ability to modify device config files on the fly?

[NYZack]

Given that zwave js is in active development, it would be great to be able to modify or create device configuration files to fix gaps for particular devices - for instance, I have some motion sensors for which parameter settings haven't yet been implemented. It seems like it would be fairly straightforward for me to implement this by referencing the Open Z-wave configuration files, without having to wait for the implementation to happen in the main zwave js code.

[robertsLando]

If you are using docker you can use the Docekfile.contrib file to build your own image with custom branches/edits, otherwise you can use the 'nodejs' way and clone/link the repositories locally

[ivdimitro]

Given that zwave js is in active development, it would be great to be able to modify or create device configuration files to fix gaps for particular devices - for instance, I have some motion sensors for which parameter settings haven't yet been implemented. It seems like it would be fairly straightforward for me to implement this by referencing the Open Z-wave configuration files, without having to wait for the implementation to happen in the main zwave js code.

If you are using docker you can map the device folders from inside the container to local folder in which you can put your test files. For example:
./0x0371:/usr/src/app/node_modules/@zwave-js/config/config/devices/0x0371 ./0x0086:/usr/src/app/node_modules/@zwave-js/config/config/devices/0x0086 ./0x019b:/usr/src/app/node_modules/@zwave-js/config/config/devices/0x019b ./index.json:/usr/src/app/node_modules/@zwave-js/config/config/devices/index.json

you will need to add index.json if you are adding new manufacturers.

[NYZack]

Well, that's a harder question! How about a way to copy-and-paste or upload a config file, which would then be placed in the appropriate config folder? There might be some rudimentary error checking (JSON sanity check, for instance).

By the way, I noticed that when I added a custom config file that had a JSON syntax error and restarted zwavejs2mqtt, ALL of my devices showed up as "Unknown" (not just the one that had the bad config file).

[NYZack]

Another (simpler) option might be to place the device config folder in the exposed shared folder (the "store" folder), where the settings and cache files are currently stored.

[AlCalzone]

That was part of the plan - even better that it also works in the HA ecosystem.

I noticed that when I added a custom config file that had a JSON syntax error and restarted zwavejs2mqtt, ALL of my devices showed up as "Unknown" (not just the one that had the bad config file).

Definitely not intended :( ==> zwave-js/node-zwave-js#1825

[popescunsergiu]

zigbee2mqtt has a way in HA to make this possible by defining a list of device config files under property: external_converters: []

Can this be a way for Z-WaveJS to accept device config files so it's easier to test them before committing?

[AlCalzone]

@popescunsergiu did you see this?
https://zwave-js.github.io/zwavejs2mqtt/#/development/intro?id=testing-custom-devices-config

[AlCalzone]

This has been possible for a while now:
https://zwave-js.github.io/zwavejs2mqtt/#/development/intro?id=testing-custom-devices-config