Sorry - I’m not familiar with this device so can’t really comment on how it works. From what I can see the binding is sending the correct commands.
Question is, does anyone got it to work? It’s obvious I’m not the only one owning a Nano Shutter and trying to use it with openhab.
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.
The log above is reasonably clear at least.
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…
or if you have a defective product…
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.
Ok, so you should have access to these up/down commands at least so you should have control of the device.
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.
You can’t. You will need special software:
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
Updated user guide: Nano Shutter user guide.
I saw that the nano shutter on the database is not updated (last update in august. https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/912)
Who’s normally doing this?
Chorus of “You are!”
Well, you can at least. Probable need advice about versioning though.
This is a community project, so, the community
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…
That doesn’t sound like any of openHAB’s business?
Well, since the device is unknown and there is no parameter for the it, I cannot edit the parameters 85, 120, 121 for instance, to setup my buttons behavior.
you need to upgrade to a recent 2.5 snapshot binding: