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.
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.
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.
Sadly folks, updating the database is quite far of my knowledge I’m afraid.
I’ve done the full communication with the Aeotec guys, the firmware is released, I did upgraded (hopefully with success), but the device is not recognized:
Window Covering Position/Endpoint Aware
Unknown: type=0003, id=008d (Node:2 Complete)
Hope to be able to access the button parameters soon with the db update, because my physical buttons are not working anymore…
Truth be told, I’m not using anymore OpenHab, neither Hass or any similar.
I’m using Node-Red for all my “scripting” and Zwave2Mqtt to setup my devices parameters only.
Zwave2Mqtt relies on Open-Zwave but the zw141.xml one have not been updated since June (https://github.com/OpenZWave/open-zwave/blob/master/config/aeotec/zw141.xml).
Would downloading the updated xml be enough in my case?
At least, I’ve kept any people using —OpenHab— informed of the situation about the Nano Shutter on this topic over the months… I thought that was a “community” spirit… but I guess simply telling the truth of my real use case was a mistake (obviously by the “community” definition).
One could have said: “OpenHab is not relying on Open-Zwave, so that’s the reason blabla…” but sure, I’ve posted on Zwave2Mqtt discussions.
Thanks for the reminder.