I did, don’t worry (angry).
Parameter 80 is actually set to 1 btw.
I had to go through it to configure my physical buttons.
My Nano Shutter configuration is like so:
35: Moving time left to right --> 30
80: Report sent to nodes in association group 1 --> 1
85: Operation mode of external switch --> 1
120: External switch mode of S1 --> 1
121: External switch mode of S2 --> 1
252: Enable/disable config parameters to be locked --> 0
1: Lifeline --> Controller
2: Group 2 --> Search
Polling Period --> 1 Day
Command Polling Period --> 1500
“Search” in Group 2 is the default placeholder of the input. When I click on it, I see a list of two:
• first line is empty with a checkbox (status unchecked)
• second line is “Controller” with a checkbox (status unchecked)
Hi Chris,
I went back on the full documentation. There is nothing I’ve found about a specific calibration except that the parameter 35 looks to take this role.
I tried to set it to 5, and indeed, the roller shutter auto stop 5s later the sent command.
Anyway, in no point this solves the issue about not being able to input intermediate values in the openhab field.
Do you have any new thought?
Regards.
Given that I don’t know of other reports of problems with this device, my assumption is that it works ok for others, but maybe someone else can confirm.
Well, I’ve done a full Nano Shutter device reset, I’ve installed and setup Home Assistant (deactivated Openhab), and I’ve the exact same behavior.
Makes me wonder if the nano shutter support at all intermediate position…
I would really love someone to confirm.
BTW, still waiting for Aeotec to answer my email about this…
I cannot find anything to suggest that this device supports any kind of positioning. It seems to just be a substitute for button pushing.
Having said that, this is the only description I found that spells it out as
Function up / down (without positioning)
No-one in this earlier thread seems to have it working
It would be possible to do some rough positioning using motor run time, but that’s not much use without a working STOP command. I guess the zwave database would need some tweaking to marry up the rollershutter type commands?
This is normal for the current version of Nano Shutter, it does not support positional controls based on the libraries that it supports for Multilevel Switch, although the support for that command class is meant for dimming type controls.
In the Multilevel Switch controls, it supports Ramp UP, Ramp DOWN, and STOP controls only.
It does not support intermediate values.
We are looking into possibly changing this reaction to allow more positional settings for Nano Shutter.
I do and it’s working (from the beginning).
I just cannot set any intermediate value.
But, here’s the rest of my discussion with Aeotec:
In any case, I do have an OTA update but it is not yet certified , i am asking if i can provide it temporarily at this time or if there is still development going on.
I should be able to get back to you earlier next week. At the minimum, i can provide you with the new documentation.
Got a new email from Aeotec Support.
They just made public the last developper documentation for the Nano Shutter. Now including intermediate positioning.
Can be downloaded right there: https://aeotec.freshdesk.com/helpdesk/attachments/6091598260
Just to understand: will Aeotec provide a software update that will cover the custom positioning? How can this software update be installed on a device connected to openhab?
Thanks for the clarification.
Got an email from Chris (Field Application Engineer at Aeotec)
Nano Shutter update is now available for positional control or venetian blinds support: Nano Shutter (ZW141) Update Z-Wave firmeware
I’m not exactly sure what “this” is though - if there is a new firmware, and it changes the functionality, then it will require a new database entry. If the functionality is still the same (no new parameters or channels) then it doesn’t need a change.
