As mentioned above, the association groups are not the same as channels. While association groups may be used to configure what messages are sent, it’s the channels that matter, and these relate to the actual commands that are sent from the device, to the gateway.
What I’m interested in is the CHANNELS at the moment since this defines the functionality of the device.
I meant setting up association groups from the old version of the OH.
About channels
One controlled device can be connected directly to a switch( TZ66D) or dimmer(TZ65D).
We can manage it through the “channel” property of OH.
button 2 can control only remote devices using association groups
physical wiring of the versions with one(TZ65/66S) and two buttons (TZ65/66D) are the same
Connections:
L: Line voltage input
L’: Switched load output
N: Line neutral
3: Auxiliary switch signal input
Isn’t the problem with the TZ35? Don’t we need to understand the difference between the TZ35 which is currently using the IDs that you say your other device has, and the other device?
Maybe I’ll see if I can find some time over the next few days to try and work this out.
The problem is that I can’t use the second dimmer button. Two groups can be assigned to it (group 2 - one click, group 3 - double click).
Almost all my dimmers do not have a directly connected load.
I use z-wave dimmable lamps (Domitech Smart LED ) and control it through association groups
I expect to see the setting of the other association groups (group 2, group 3, group 4 ).
But what matters is not so much the groups - but the COMMANDS that are sent. Groups are simply a configuration setting. We need to know the command classes that are used to send commands between the device and the gateway.
I will try and find time to work this out from the database. Ultimately though we are stuck - either we fix your issue and break it for someone else, or we leave it alone. Ideally we’d try and get feedback from others with these devices so we can understand where the error really is.
The switch sends commands to devices(Domitech Smart LED ) using a z-wave without OH. I can’t setup it using one assotiation group.
The problem has appeared with this update TZ35S reporting as TZ65D . I have already suffered. I reported a problem a few months ago. Please roll back the changes. I think if were more association groups to set up this it would not be a problem. The problem appears when the association group is only one
you did not help me at all
@chris
I tried to install earlier versions of OpenHub. In version 2.2, the type of my z-wave switches is determined correctly (TZ65D Dual Paddle Wall Dimmer). And I can do all the necessary settings.
https://dl.bintray.com/openhab/apt-repo2/pool/main/2.2.0/
Starting with the version 2.3 my devices are not detected correctly.
https://dl.bintray.com/openhab/apt-repo2/pool/main/2.3.0/
You have an error in the device database and there is no solution for working with my devices.
I think this manufacturer has reused device codes that causes this sort of problem.
Maybe this is linked -:
You are right, many models are produced with one identifier:
These are two-button switches and one-button switches. It is better to assume that the switch as a two-button.
This will allow setting more configuration parameters such as four associative groups.
Both are bad and will cause problems for someone - either someone doesn’t have a channel, or someone will have errors with their network due to incorrect definitions.
Basically, this incorrect definition makes things pretty difficult unless there is some other way to differentiate these devices - currently that is the firmware version, device type and device id.
In the current state of the database, having the latest version of OpenHub, how can I configure the associative group 2, 3 or 4?
If these groups are not in the database, then it is not possible to do this via OH unfortunately.
@chris if you add this device as TZ35D
then users of TZ35S can configure group 1
and users of TZ35D can set up groups 1-4
and we will all see 4 groups in the settings, which is a bit incorrect for the one-button version users
Tell me if I’m wrong.
Perhaps this link will be interesting to you
Can you elaborate on what is interesting 
At the end of the day, we need to find a way to differentiate these devices.
No - you are correct.
But you miss off other issues such as the binding will request configuration and associations that do not exist in the device as the database is wrongly configured. This will cause users delays and timeouts in these devices.
As I said - both options when incorrectly applied will cause problems if the device someone has isn’t the one that is defined.
At the end of the day, we need to find a way to differentiate these devices.
I can collect any debug information if it helps
I can collect any debug information if it helps