Zwave js ui config db override

Hi, I am trying to implement my Yale YRL210 Lever Lock via zwave. This is the older yale lock with zwave dongle (pre-azure line).

The device has the follwoing IDs:
ManufactureID ProductType-ProductID
0x0129 0x0003-0x0000

however, the ZWave Config DB only has
0x0129 0x0003-0x0409

I installed ZWave JS UI

so I downloaded and modified the config file and added it to my store/config dir, but when I re-interview the device (I tired to restart too), It still shows up as unknown product, what am I doing wrong?

image

FROM:

{
	"manufacturer": "Yale",
	"manufacturerId": "0x0129",
	"label": "YRL210",
	"description": "Push Button Lever Lock",
	"devices": [
		{
			"productType": "0x0003",
			"productId": "0x0409"
		}
	],

TO:

{
	"manufacturer": "Yale",
	"manufacturerId": "0x0129",
	"label": "YRL210",
	"description": "Push Button Lever Lock",
	"devices": [
		{
			"productType": "0x0003",
			"productId": "0x0409"
		},
		{
			"productType": "0x0003",
			"productId": "0x0000"
		}
	],

Full File Here

I have a PR open with ZWaveJS too, but not sure when it will be merged, so I’d like to test it

I have a device whose name is unknown. I could give it a name by clicking the pencil at the top right. But as long as its entities are available I don’t care. I guess the device was not in a database.
image
I use it to detect motion in the front room and turn on a light. It also reads air temperature and illuminance. I use illuminance to disable turning on that light if it is already light enough.

First step would be to check the driver logs and confirm it’s loading the custom file. You should see User-provided device config loaded for the lock node ID. If it says Embedded device config loaded then it’s not finding it.

@Dave2001 Thanks, I’m looking to get additional/proper functionality of the device, not just an atheistic thing.

Yes, you are correct, its not in the DB, that I am sure of.

@freshcoast , I looked at the driver logs and it says:

2024-12-08T20:38:20.912Z CNTRLR [Node 001] Embedded device config loaded
2024-12-08T20:38:20.922Z CNTRLR [Node 004] Embedded device config loaded
2024-12-08T20:38:20.929Z CNTRLR [Node 006] Embedded device config loaded
2024-12-08T20:38:20.935Z CNTRLR [Node 008] Embedded device config loaded
2024-12-08T20:38:20.939Z CNTRLR [Node 012] Embedded device config loaded
2024-12-08T20:38:20.944Z CNTRLR [Node 014] Embedded device config loaded
2024-12-08T20:38:20.948Z CNTRLR [Node 015] Embedded device config loaded
2024-12-08T20:38:20.952Z CNTRLR [Node 016] Embedded device config loaded
2024-12-08T20:38:20.954Z CNTRLR [Node 017] No device config found

My device of concern is NODE 017, so its not loading an Embedded or custom file.

Here is my file structure setup, did I put it in the right place?

For anyone who stumbles on this, solved my issue, any non-absolute “templates” have to be added to the config dir too…it works now!

B2024-12-08T20:38:13.131Z CONFIG Error parsing config file yrl210.json: Could not parse config file /data/store
/config/templates/yale_template.json: ENOENT: no such file or directory, open
‘/data/store/config/templates/yale_template.json’
Import stack:
in #volume_inverted
in /data/store/config/yrl210.json (ZW0340)

1 Like