Now it is a different story
As you already found out in your above post in a snapshot release you can install the snapshot zwave binding just by hitting the install button in a GUI.
From this back and forth I would suggest to check via karaf and bundle:list | grep ZWave that only the recent snapshot binding is active.
Only if you want to use newer snapshot bindings with old stable releases
It’s pretty easy: in your first post you told us you are on 2.3 stable. So I told you how to get the latest database definitions (add 2.4 binding jar). In some later post you were magically on 2.4 snapshot. Now I told you how to get the database updates if on that version (remove the jar and just install zwave through GUI).
Now you have two zwave bindings on your system, so remove one. You may need to clean the tmp and cache folder and restart openHAB again …
Nothing magical about it. I was on stock 2.3. I followed the detailed instructions for updating the binding (linked earlier) which include the line;
If you are not already running 2.4 snapshots, then upgrade OH using the procedure for your platform.
That’s where the magic happened!
Anyway, I really do appreciate all the pointers. I have removed the JAR file and cleared tmp and cache directories as instructed. I now have a single zwave binding listed in Karaf.
Still no joy though, the Dual Paddle stubbornly reports as a single.
Have you compared the xml to the database? The binding generates the xml with info from the device, and uses it to identify it in the db. Please post your xml.
If the device has two paddles, then this seems like a device issue… the binding is doing everything it’s supposed to do. Maybe it was loaded with the wrong firmware? Or the firware has changed and the type:id changed too. You sure it has two paddles ?
Yes. Visual inspection confirms. No firmware updates on the device. And it’s reported correctly in Home Assistant, just that platform cant access the second paddle (known issue).
Do you have more than one of these devices, and do they behave the same? You’ll probably need the expert for this one (@chris), but OTMH I do not see a way to resolve it.
You could hack the definitions in your binding to make this work, but probably best as a last resort.
I think we’ve seen this before with this, or other TKB devices . They use the same set of codes for multiple devices which is a real ballache.
Anyway, how to extract ourselves from this…
This device was added quite recently, so I can probably track down who added it, and we can try and have a discussion about this. We might be able to differentiate the devices using firmware versions, if not, and they really are exactly the same, then we’ll have to rethink.
Sure I can join trying to find out what we want to achieve… I have one piece of TZ35S in my installation. Do we need documentation or ?
It works correctly, however sometimes it reports back with delays good it responds to remote changes quickly.
I have dual paddle TZ37 switch also and it responds much better.