[zwavejs] Initialization or update failed, Could not build channels on Yale YRD210

[kamakazie2]

Hi im running OH 5.1.0.M2 running on Windows 11.
I cannot get node 12 Yale YRD210 to add to openhab.

I have a Kwikset lock that works fine, and several door sensors and a few dimmers all working in zwave Js UI and OH. However for some reason this lock will not link up with OH.

I can control the lock from Zwave-Js UI just fine. However every time i try to add the thing to OH i get the Initialization or update failed, could not build channels. I deleted and tried to re add it. I tried to let it discover on its own... nothing.

Any ideas?

[mhilbush]

@lsiepel probably will ask you to put the binding in TRACE mode and send him the big JSON string that is loaded when the binding starts. And also probably will ask for the specific error message you are seeing, along with the relevant section of the TRACE log where the error occurs.

If the JSON string is too big, you can just send the portion for node 12.

[kamakazie2]

Understood. Ill grab the logs when i get back tomorrow.

[kamakazie2]

Here is the error i get when i try to add it from the inbox

2025-11-20 19:57:50.032 [WARN ] [.internal.handler.ZwaveJSNodeHandler] - Node 12. Error generating type information
java.lang.NullPointerException: Cannot invoke "org.openhab.binding.zwavejs.internal.api.dto.MetadataType.ordinal()" because "type" is null
at org.openhab.binding.zwavejs.internal.conversion.BaseMetadata.correctedType(BaseMetadata.java:468) ~[?:?]
at org.openhab.binding.zwavejs.internal.conversion.BaseMetadata.itemTypeFromMetadata(BaseMetadata.java:534) ~[?:?]
at org.openhab.binding.zwavejs.internal.conversion.ChannelMetadata.itemTypeFromMetadata(ChannelMetadata.java:74) ~[?:?]
at org.openhab.binding.zwavejs.internal.conversion.BaseMetadata.<init>(BaseMetadata.java:131) ~[?:?]
at org.openhab.binding.zwavejs.internal.conversion.ChannelMetadata.<init>(ChannelMetadata.java:61) ~[?:?]
at org.openhab.binding.zwavejs.internal.type.ZwaveJSTypeGeneratorImpl.generate(ZwaveJSTypeGeneratorImpl.java:153) ~[?:?]
at org.openhab.binding.zwavejs.internal.handler.ZwaveJSNodeHandler.setupThing(ZwaveJSNodeHandler.java:738) ~[?:?]
at org.openhab.binding.zwavejs.internal.handler.ZwaveJSNodeHandler.internalInitialize(ZwaveJSNodeHandler.java:491) ~[?:?]
at org.openhab.binding.zwavejs.internal.handler.ZwaveJSNodeHandler.lambda$3(ZwaveJSNodeHandler.java:452) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.lang.Thread.run(Thread.java:1583) [?:?]

And here are the properties from the Node Js Ui screen attached
js detail.txt

[kamakazie2]

Here is trace log

openhab.log

[lsiepel]

This is solved by #19500
The fix will be available in the next patch release. and is already available in daily snapshots.

[kamakazie2]

Thank you ill get the latest snap tonight

[kamakazie2]

Works like a charm.. thanks again