Thanks for the explanation; now I know we are talking about the same thing.
One other note I have to mention here, is that I'm running an
almost up to date
Beta Jadahl release.
I also found what is causing the multiple versions of de configuration source files: The Jadahl distribution puts those configuration files in
Domoticz/var/Config/, but when you run an update from the Setup menu within Domoticz, those files are placed in
Domoticz/Config/. That's why updates don't have any effect when done from within Domoticz! I'm not sure how or where to report this.
Another thing I discovered is that the files
/volume1/@appstore/domoticz are actually the same as the files in
/usr/local/Domoticz/ (a symbolic link or whatever this is called in Linux
)
However, this only made things worse for me: Every time I refresh the node, the compatibility node is replaced by an empty node (<Compatibility />)
Finally some positive news: After adding a copy op the definition of Command Class 133 to Command Class 142 including the Compatibility node, although this does not seem to be required in Command Class 133:
<CommandClass id="133">
<Associations num_groups="11">
<Group index="1" label="Lifeline (1)" max_associations="1"/>
<Group index="2" label="Basic on/off input I1" max_associations="16"/>
<Group index="3" label="Multilevel set Flush dimmer" max_associations="16"/>
<Group index="4" label="Start level change/stop level change input I1" max_associations="16"/>
<Group index="5" label="Basic on/off input I2" max_associations="16"/>
<Group index="6" label="Notification report input I2" max_associations="16"/>
<Group index="7" label="Binary sensor input I2" max_associations="16"/>
<Group index="8" label="Basic on/off input I3" max_associations="16"/>
<Group index="9" label="Notification report input I3" max_associations="16"/>
<Group index="10" label="Binary sensor input I3" max_associations="16"/>
<Group index="11" label="Multilevel sensor report temp sensor" max_associations="16"/>
</Associations>
</CommandClass>
<CommandClass id="142">
<Compatibility>
<ForceInstances>false</ForceInstances>
</Compatibility>
<Associations num_groups="11">
<Group index="1" label="Lifeline (2)" max_associations="1"/>
<Group index="2" label="Basic on/off input I1" max_associations="16"/>
<Group index="3" label="Multilevel set Flush dimmer" max_associations="16"/>
<Group index="4" label="Start level change/stop level change input I1" max_associations="16"/>
<Group index="5" label="Basic on/off input I2" max_associations="16"/>
<Group index="6" label="Notification report input I2" max_associations="16"/>
<Group index="7" label="Binary sensor input I2" max_associations="16"/>
<Group index="8" label="Basic on/off input I3" max_associations="16"/>
<Group index="9" label="Notification report input I3" max_associations="16"/>
<Group index="10" label="Binary sensor input I3" max_associations="16"/>
<Group index="11" label="Multilevel sensor report temp sensor" max_associations="16"/>
</Associations>
</CommandClass>
After refreshing the node, I see Lifeline (2) when I hover over group 1, so this means Command Class 142 is used here. When I remove the association for one of the groups and apply it again, it shows 1 instead of 1.1, so this is OK now. Although there is still a delay of about 5 seconds, the icon of the switch is updated:
What I think what is happening, is that when command class 142 is not defined in the config file, Domoticz will create default node for this class. The Compatibility is not supported for command class 133, so it is ignored.
What stays is the fact that Domoticz does not handle this new command class (Multi Channel Association Groups) very well,so I hope this thread have attracted the attention of the developers, so this new OZW feature will be supported in future releases.