ZWave binding migration to development version

Hi @chris, afer upgrading openhab all my switches (TKB home TZ65D) appear in the INBOX with wrong type - as TZ35S.
I have three kinds of TKB Home devices - TZ65D,TZ65S,TZ66D. Before updating openhab their type was correctly determined by openhab. But now all of this devices was appeared as TZ35S in inbox.

What is the difference between these devices? Often manufacturers use the same IDs for multiple devices.

If the devices are different, then we need to resolve this so that the correct channels are provided. If they are actually different versions of the same device, then I’m not sure that it matters?

I would suggest if this is really a problem to start a new thread so that the conversation is not hidden here as we’ll need to find other users of these devices to try and sort out the different versions.

Main difference is count of association groups:
TZ65S (as TZ35S) has group 1
whereas TZ65D has 3 association groups

Hi @chris, my tkb home devices still appeared as TZ35S.

I think my trouble related to TZ35S reporting as TZ65D

I also have a device ID 0808:0808

ii openhab2 2.5.0~S1608-1 all openhab2
ii openhab2-addons 2.5.0~S1608-1 all openhab2-addons

I can’t set addition channels.

Yes, this was my point earlier and why we need to look at the differences between these two devices.

Sorry - I’ve just realised this is a repeat conversation of another thread - it’s best not to cross-post so I won’t continue replying here.

Where can I download the latest 2.5-SNAPSHOT build of the zwave binding?
I need to pick up the latest device xml files.

https://ci.openhab.org/job/openHAB2-Bundles/org.openhab.addons.bundles$org.openhab.binding.zwave/

If you want the XML files, it’s it best and certainly easiest, to get them from Github?

That works. Wasn’t sure if there were code changes that go with the XML changes