ZWavejs2Mqtt custom device help

[MrB]

My Yale Keyfree Connected worked fine in the deprecated ZWave integration, being recognised as:

YRD220 / YRD240
Yale / Real Living Touchscreen Deadbolt
Firmware Range: All Versions
Product Manufacturer: 0x0129
Product Identifiers: 0x0002:0x0000, 0x0002:0x0209, 0x0002:0xaa00, 0x0002:0xffff, 0x2022:0x0209

Since upgrade to ZWavejs + ZWavejs2Mqtt it is recognised as the following and no longer function correctly:

YDM3109 / YDM4109
Yale / Smart Living Keyfree Smart Lock
Firmware Range: All Versions
Product Manufacturer: 0x0129
Product Identifiers: 0x0006:0x0000

I want to force the use of a custom json which will make the lock be recognised as it used to be. I have placed the json in the data store and set directory in the ZWavejs2Mqtt settings. The local device file is ignored. What am I doing wrong please?

[mwav3 (Tim)]

This thread will have info that should help

Z-Wave Device Not Identified Correctly

There is a way to force a custom device config, but you have to use zwavejs2mqtt over zwavejs. I’ve never tried it myself. https://zwave-js.github.io/zwave-js-ui/#/device-support/custom-device-files?id=using-custom-device-configuration-files If you just want to change an unlisted parameter, and know it’s parameter number, you can also do that right within the zwavejs2mqtt control panel, with no custom device config needed [Screenshot_20210913-204514_Home Assistant] I would also include it…

[freshcoast]

Did you restart zwavejs2mqtt after adding the file? Do the logs show anything? Often this is the cause of a syntax error in the file.

If you think the current device config file is wrong or missing information, you can submit a bug report to get it fixed. That way you don’t need to use a custom file.