Qubino Flush Dim State issue

[hestia]

About the .silent(), it's not only for Qubino, also tested with FIBARO FGD212 Dimmer 2+
https://www.domoticz.com/forum/viewtopi ... 07#p232244

[Louk]

Thanks
I didn't refresh the node before adding 1 in the group 1!

What do you mean by "refresh the node"; what do you need to do for this?

In my case, I'm running Domoticz on my Synology NAS, so I'm facing a different file structure: So there is no Conf folder. I found 3 files named ZMNHDDx.xml:

/volume1/homes/Beheerder/Config/qubino/ZMNHDDx.xml
/volume1/@appstore/domoticz/Config/qubino/ZMNHDDx.xml
/volume1/@appstore/domoticz/var/Config/qubino/ZMNHDDx.xml

I don't know which of the 3 files is used to configure the device, so I modified all 3 of them (added the Compatibility node to CommandClass 133). However, non of these changes lead to a solution of the issue.

In the end, I put the change in the ozwcache_*.xml file that is locateted in /usr/local/domoticz/var in my case. Now I can change the association in the Z-wave group table from 1.1 to 1.

However, I still need polling enabled to get stable updates in Domoticz.

[hestia]

What do you mean by "refresh the node"; what do you need to do for this?

=> Setup / Hardware / your z-wave hw / Setup
=> select the NodeID
=> at the end of the list in the middle, there is the "Refresh Node Info" to click!

In my case, I'm running Domoticz on my Synology NAS, so I'm facing a different file structure: So there is no Conf folder. I found 3 files named ZMNHDDx.xml:

For RPI, it is here: /home/pi/domoticz/Config/qubino

=> So I guess is is here for Syno: /volume1/@appstore/domoticz/Config/qubino/ZMNHDDx.xml

non of these changes lead to a solution of the issue.

=> You need to refresh the node

[Louk]

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.

[hestia]

I hope this thread have attracted the attention of the developers, so this new OZW feature will be supported in future releases.

Happy to know your issue is solved for the moment.
You seem to be more an expert than me regarding z-wave config!
I'm not sure the developers work on this issue ; I didn't find issue open on the problem...
https://github.com/domoticz/domoticz/is ... issue+wave

[Louk]

I'm not an expert at all, but a retired trouble shooter and operational (software) support engineer, so I was trained to think about possible causes

Because I'm a bit tight up the coming week, i will report this issue on the Github Domoticz forum next weekend (thanks for the link!).

[Diplo95]

Hello,

I step in this discussion because I have a similar issue with a Qubino ZMNHCD1. I run domoticz v2021.1. I tried several times the manip explained above but without any success : I still remain on 1.1 canal.

Sadly, I see the state of my shutter is sometimes correct but sometimes not : it's erratic.

Have you got another solution for this behaviour ?

thx

[bert]

Ran into this issue after noticing the 1.1 group membership on a 'new' unit I installed this evening.

Fixed this with:
replacing the two config files from the rar archive in post: https://domoticz.com/forum/viewtopic.ph ... 53#p225153 (post mentioned before here) with the ones on my PI

And then (also from various posts here above):
- stop domoticz
- delete ozwcache.... file in /domoticz/Conf
- start domoticz and let it finish z-wave initialization (takes LONGER as usual)

that fixed the whole situation. for me. no need to change groups or anything; the dimmer is on 1 as per normal.


Apparently, changing <CommandClass id="133"> to <CommandClass id="142"> is needed (too?) which happens with replacing the config files.

When will this stuff ever get hassle-free plug-n-play