Qubino ZMNHCA2 Flush shutter intermediate position issue

[rirethy]

Hello,

I start a zwave configuration. At the moment, in my config, I have : Sigma design Zwave+ USB controler, 1 Aeon MiniMote, 1 Qubino ZMNHAA2 (Flush 1 relay), 1 Qubino ZMNHCA2 (Flush shutter) (after having tested Fibaro modules)

Everything is working well, all devices are well recognise in zwave hardware setup, I drive the Qubino ZMNHAA2 (Flush 1 relay) with the Aeon Minimote through domoticz scene and remote "code". The ZWave devices react well to actions in the domoticz interface.

The Qubino ZMNHCA2 (Flush shutter) USED to be fully functional : ON/OFF and all intermediate positions with dimmer functionality. When it worked, I've set up some scenes to fit my usage.

But since end of may, I did not reccord exactly when, nor on which domoticz version, the Flush shutter ca be used only as a ON/OFF switch. That is the dimmer functionality is not working. I can use the slider, or my scenes, it do not work.

I try to reboot, to get from git the latest version of the "config" OpenZwaveDirectory, to remove my zwcfg* files. The problem is still there.

I highly suspect the OpenZWave version that has been updated almost at the moment where I discover my problem. (We are now on the 1.3-293-ga4ea66b-dirty version).

I run on a Raspberry PI B, with the latest beta Domoticz version. ALL other devices managed by Domoticz are working well : french "teleinfo", 1Wire, GPIO, virtual devices, ...

Thanks in advance for any help provided.

Does anyone got the same issue ?

As I do not want to recompile all domoticz to include a new version of OZW, I wait a version of Domoticz that will include another version of OZW. but, it's quite long.....

It would be really great that could change OZW version without having to touch to Domoticz.

Beside this problem, all my other devices in Domoticz are working well.
My setup is : Raspberry Pi B, and Domoticz in Beta version. Actually : V2.2548

[gizmocuz]

there is no newer openzwave version?

[rirethy]

The point, is not necessarely to have the very latest version of OpenZwave. The point is to have the possibllity to change the OWZ version. That way, when having an issue, it will be possible to check if it's a Domoticz or a OZW bug (by mixing Domoticz and OZW versions).

At the moment, with Domoticz V2.2561, it reports this OZW version : 1.3-293-ga4ea66b-dirty
When checking the OZW web site, the latest official stable version is : 1.2.919. And the 1.3.xxx branch seems to be actually a snapshot of actual work, and only for test (thus, not bug free).

I do not say that it is a bad thing to be on a snapshot version, but if so, i think Domoticz (beta version) should follow the snapshot version. OZW snapshot is actually at version 1.3.312 (compared to the 1.3.293 actualy in use)

I do not doubt that donwnload and recompiling OWZ almost at each Domoticz delivery increase your workload. That's why I had suggest as a Domotics enhancement, to be able to use our own version of OWZ with any delivery of Domoticz, without having to recompile Domoticz that is a quite long task.

Anyway, I continue to use Domoticz, and I'm very happy with it. Just a bit sad no to be able to automatically close at bit my shutters when the temperature in my house is too high.

Just my two cents.

[gizmocuz]

I dont think you have read the above carefull
There are patches

[gizmocuz]

And you can compile yourself

[rirethy]

OK, Thank you. I'll try recompiling.

[willumpie82]

Hi,

have you been able to solve your problem? i have a ZMNHCD1 and i'm encountering the same issue, because there was no native support for this device I added it manualy to the zwave config.
I also noticed that i don't get a power meter channel as with all my other Qubino modules