Domoticz

Hi,

I have added a ZMNHOD1 shutter to control my blinds. It is kind of works, but it only know 2 states, fully closed or fully opened. I cannot stop the blinds at a certain point, like I can do with the switch. Domoticz says it has sent the Off command when I click on the blind up/down icon again and the blinds stop for a second but then they go all the way down.

Does anyone have experience with this shutter or something similar?

Thanks in advance,
Marton

I have a Qubino ZMNHCD1 Flush Shutter Plus (should be the same, just another region).
Also noticed that it's only open/close.
I don't need a semi opened state because it controls a stair. So I never looked into this issue.

I have been trying to figure this out, but after a while the blinds are not working anymore. I did not change any settings/parameters. And I don't even know what's wrong but I cannot change parameter 76. Motor operation detection. I change it to another value and it goes back to what it had before.

Tried to exclude/include the node, reset the motor's limit settings. Nothing helped.

Hello, i have the same issue . i want to have to open the blinds to a certain point but cannot. Only on or off .

There is a solution ?

I understand your frustration, I've been there myself
After days of googling arround, the solution for my 2 Qubino's ZMNHCD1 (230V version) was changing parameter 76 to 50 and parameter 85 to 30 according to user Nicolas on https://www.domotique-store.fr/domotiqu ... nhca2.html under 'QUESTIONS ET AVIS' (website in French).
I changed the default values in the configuration file /home/pi/domoticz/Config/qubino/ZMNHCDx.xml, power off and after a few seconds power on the blinds again and finally exclude and re-include the devices. Now it's working like a charm without issues.

Good luck!

I don't understand what powermeting has to do with the availablity of a stop button?
I changed the device type/subtype/switchtype in the database. Will test tomorrow if everything's ok. (can't right now cause everybody's a sleep)

Hi, so you confirm that domoticz can open the store to 50% with this change ?

Sorry, I was not clear, my reaction was meant for marton.
Yes I can confirm that they can open/close partially, however with the Z-Wave default parameters the qubino modules reacted very weird. I managed these modules to work in Domoticz for a couple of days and then suddenly they stopped working, even when operated manually by push button. Nothing worked anymore, only a power off and on did activate the modules again. After changing the mentioned parameters all seems to work normally now without issues.

A have the same problem don't work any more until power down electric power . But it's not a solution ... and it's append randomly to all module ZMNHCD1

I use ZMNHCD1 and open/close and percentage position commands are worked. It is set up as blinds percentage inverted.

Pico wrote:I use ZMNHCD1 and open/close and percentage position commands are worked. It is set up as blinds percentage inverted.

My shutter works with up/down (open/close) and slider (percentage) too, but the STOP button does not work. If I ie try the shutter in Openhab, STOP works as it should (just moving z-wave stick to OH computer).

What does Domoticz send to the Z-wave layer when pressing stop?

/Andreas

--- tapatalk'd

After a complete rebuild of my domoticz system, reset of all nodes I also notice this behaviour.

The solution is to start a "Forced Shutter calibration" option 78.

Hi,

I've the same issue with this module that I cant stop it at the moment that I sent the stop command.
strange thing I experienced in the log of my device is this:
that at the moment I sent a percentage to it, this is logged, with directly after the current state of the module (percentage) and than some time later when the requested state has been reached again an entry with the actual (requested) percentage.
so it seems that the module is not getting informed in time about the state which it has during moving.

so eg if I move from closed to 50% the in between statusses are not recognized and therefore the module only knows the previous (closed) state as this was the state which was last stored in the module...