The latest snapshot has the fix (hopefully- do not know if the xml above was tested as working) to the problem identified by @AlexMartin13.
I didn’t find the time to try the .xml file manually, but updating to the snapshot binding worked a charm! Thanks for all your help @apella12
After that success, unfortunately I needed to reinstall openHAB for unrelated reasons. In doing so I forgot the URI needed to update the zwave binding to the latest snapshot using the bundle:update approach. After reading the docs and forums, I tried using the following URI:
bundle:update 280 https://openhab.jfrog.io/artifactory/sandbox-snapshot/org/openhab/addons/bundles/org.openhab.binding.zwave/4.1.2-SNAPSHOT/org.openhab.binding.zwave-4.1.2-20240105.154215-12.jar
And it looks like it’s updated okay:
280 │ Active │ 80 │ 4.1.2.202401051542 │ openHAB Add-ons :: Bundles :: ZWave Binding
However, the device is still unrecognised even after waking, reinitilaising and re-adding.
This is what I see in the console when waking the device:
17:43:29.229 [WARN ] [zwave.discovery.ZWaveDiscoveryService] - NODE 135: Device discovery could not resolve to a thingType! 0071:0002:035D::3.10
17:43:30.121 [INFO ] [commandclass.ZWaveVersionCommandClass] - NODE 135: Command Class COMMAND_CLASS_ASSOCIATION has version 0!
Is this the correct version of the binding?
no. You will need a 4.2 snapshot. I posted the site above (#9) on jan 18