Did it possibly just get calibrated wrong or installed backwards or something?
I started making a patched driver to inverse it, and it works for the reporting, but the set poistion command also needs to be inverted I think.
I assume if you run something like SetPosition 25 it will report back level 25 but physically it would be open around 75%?
In this position it's only little bit opened:
But if it's problem to change it I will keep it like it is. I will get use to that. I prefer that more then fighting again 
Afraid that something can go wrong another time.
Try this out, it should invert everything. ZEN53 Reverse open/closed · GitHub
If it works out I will add it as a setting in the next version.
The open command will only work right if you set it to Always Open Fully
Thank you.
I'll test on Monday - I'm out of home
I'll let you know
Need some more time. Promise to test and let you know.
Sorry for delay
@jtp10181 Hello Jeff,
New drivers works fine!
There is only ONE FAILURE
After closing the rolls the position status stays on the level before action. Examples:
When position is 100 (fully open) you press to fully close, after closing status shows closed but the position indicator shows 100
After setting the position for example to 75% status shows partially open, position shows 75% and when you start closing from this position after closing the status is closed but position stays 75% and on the dashboard the slider stays on 75%
I can live with that but I think you'd like to know.
In case you could fix that that would be amazing of course 
Even without that THANK YOU FOR YOUR SUPPORT!
Piotr
Sounds like you just need to change this setting:
Works!
Amazing! Thank you! So long...
@bange sounds like my ZEN53 driver works perfectly for this device.
Not sure what caused the other user to need the open/closed reversed but you can find the original driver here: [DRIVER] Zooz ZEN53 DC Motor Controller (for shades)
And Reversed open/close: Windows rolls device - Shelly Qubino? - #23 by jtp10181
Let me know if one of those works for you, and which one.
@bertabcd1234 looks like the Qubino Shutter Module does not work on the QNSH-001P10, not sure if its supposed to? But my ZEN53 driver works fine. See above: Windows rolls device - Shelly Qubino? - #11 by jtp10181 . I remember having to put some extra code in there to deal with reports basically saying the device was in transition. I am wondering if the system driver is not handling that correctly? I am parsing the multilevel commands as v4 so I can see and use the targetValue and duration. This lets you determine if the motor is in motion or is done moving.
Not sure, the only models that appear to have been tested are ZMNHCD3 and ZMNHOD3. I don't know if QNSH-001P10 is an entirely different product (quite possible, especially given the above) or just a rebranding Shelly did after taking over Qubino.
That being said, it's not clear exactly what the problem is above. Is it just not reporting events after a change? If so, enabling debug logging and seeing what isn't getting parsed into a device event (look for a line in the logs that starts with "ignored:", followed by some Z-Wave command class data) -- along with a description of what was actually happening on the device at that time -- would be the best help.
thanks @jtp10181, I have installed the ZEN53 driver and applied it to one of my shades.
After multiple presses on open or close, I am able to open/close the shutter. I had indeed to invert the setting but the is the only thing I am able to do.
Status reporting is not working. I don't know how to set an intermediate position and calibration does not work.
Finally, the variables displayed on the variable section are unclear. Is there anything wrong in my set-up or is some more configuration needed that I am unaware off?
You need to turn on debug logging on the device page. Then open and close the shade once. Then post a screenshot of the resulting logs.
Since i switched to another driver and back to the qubino one, I am not able to open/close my shutter, even with the wall buttons.
I did find some information on the qubino website about what the different parameters do but I don't get how to tinker with them from hubitat. Could I get help around that?
https://qubino.com/products/flush-shutter/flush-shutter-tech/
And this is the current logs I am receiving.
None of your screenshots look like they are from my driver.
Whatever driver you are using appears to be incompatible and it is trying to change settings that dont exist on your device and probably setting other settings to undesired values.
I need to see the "Data" section from your device at the bottom of the page. If you are on hub platform 2.4.0 it is on the Device Info Tab.
Y i tried your driver but had to switch back to what should be the official one cause with yours the buttons on my wall were messed-up (up vs down).
Here is the data section of my device.
I am wondering if the struggles I have to change parameters and calibrate could come from using S2 security. I thought it was pretty standard nowadays.
S2 security has nothing to do with it, should not matter. I already explained exactly what the issue is with the driver you are using.
I made a special version of my driver with the open and close reversed and posted it above
Download the Hubitat app
