So if I understand, the device adds the controller to the Assoc group twice, once with EP 0 and EP 1. This is odd because the lifeline is only supposed to be with EP 0. That is why there is no config in the ZW DB to set endpoints. Peeking at the ZUI JSON (see below. I’m guessing this code is meant to fix the information from the device by shifting the associations on EP1 (and EP2?) to the correct group. Unfortunately to my knowledge OH ZW does not have a way to do that. What might work is to change the limit on Group 1 from 1. ZUI looks like they have used 9.
wave2pm_0_0.xml (30.8 KB)
For test I changed the binding XML two ways 1) I eliminated the automatic group 1 association completely (You might have to add if nothing shows up and 2) increased the limit on Group1 to three. You’ll need to add to your binding with this procedure to test. If it works the DB can be changed
"endpoints": {
"0": {
"associations": {
"1": {
"label": "Lifeline",
"maxNodes": 9,
"isLifeline": true
},
"2": {
"label": "SW1: On/Off",
"maxNodes": 9
},
"3": {
"label": "SW1: Start/Stop Level Change",
"maxNodes": 9
},
"4": {
"label": "SW2: On/Off",
"maxNodes": 9
},
"5": {
"label": "SW2: Start/Stop Level Change",
"maxNodes": 9
}
}
},
"1": {
"associations": {
"1": {
"$import": "#endpoints/0/associations/2",
"isLifeline": false
},
"2": {
"$import": "#endpoints/0/associations/3"
}
}
},
"2": {
"associations": {
"1": {
"$import": "#endpoints/0/associations/4",
"isLifeline": false
},
"2": {
"$import": "#endpoints/0/associations/5"
}
}
}
},