#Custom device JSON with zwave-js-ui (store/config/)

1 messages · Page 1 of 1 (latest)

earnest swallow
#

I've got some Zooz ZSE70 motion sensors which don't have a config file yet, but there's a couple pending PRs (e.g. https://github.com/zwave-js/node-zwave-js/pull/7405).

I'm currently using latest zwave-js-ui (9.27.7) standalone Linux executable running under systemd. I've tried a couple things to try to get it to find the JSON file, but the device still shows up as "Zooz 0x0004 Unknown product 0x0006" and there's no log message like "User-provided device config loaded" shown when reinterviewing the device. I did not try excluding and reincluding the device with the JSON file in place (yet).

Am I missing something? Files such as settings.json and logs are stored in ~homeassistant/zwave-js-ui/store, and the "config" dir ~homeassistant/zwave-js-ui/store/config was automatically created ages ago by zwave-js-ui.

I tried placing the file from the PR at ~homeassistant/zwave-js-ui/store/config/zse70_800lr.json as well as ~homeassistant/zwave-js-ui/store/config/devices/0x027a/zse70_800lr.json. FS permissions are OK.

Was using the following docs: https://zwave-js.github.io/node-zwave-js/#/config-files/overview https://zwave-js.github.io/zwave-js-ui/#/device-support/custom-device-files?id=using-custom-device-configuration-files

rough wing
#

It just goes in the config dir, I don't think it works with subdirs

#

ah you did that

#

Did you modify the PR to include your device? it doesn't add any new ones.

earnest swallow
#

Restarted zwave-js-ui between interview attempts as well

#

The PR is to another unmerged branch...

rough wing
#

does the config path in the settings point to the same directory?

earnest swallow
#

let's see, it'd be in the JSON?

rough wing
#

in the UI is easiest

earnest swallow
#

"deviceConfigPriorityDir": "/storage/root/homeassistant/zwavejs2mqtt/store/config",

#

oh crap, hah.

#

yeah that's gotta be it, thanks!

#

yep, didn't even need to reinterview