Aeotec Nano-Shutter problem with firmware update to 3.1

ffr · July 10, 2020, 9:31am

thanks a lot.

ffr · July 10, 2020, 4:19pm

@sihui @chris : just installed the latest Zwave Binding and now, I can nolonger edit any ZWave things.
in PaperUI I get “ERROR 500: Internal Server Error” when trying to edit a ZWave thing
in Habmin, for all of my ZWave devices the configuration parameters are not even displayed anymore
Editing non-Zwave things still works fine.

I already deleted cache and temp files - did not help.

any suggestions?

ffr · July 10, 2020, 4:35pm

uuuu … found the issue myself. The old version of the ZWave binding was somehow still active. Uninstalled this via PaperUI and editing of the things is now working again.

Bruce_Osborne · July 10, 2020, 4:36pm

The install script automatically uninstalls this first

ffr · July 10, 2020, 5:22pm

@sihui
ok, got the new ZWave binding installed and running.
For this device ZW141 there are two XML files in the JAR file - one for old firmware and one for the new firmware.
The XML file for the new firmware shows a number of new configuration parameter for blinds control.
After inclusion of the device, the device shows as Firmware Version 3.1 in habmin. The new configuration parameters are not there though. The XML File created for the device during inclusion does only show the old parameters.
Here are the two files:
XML file in JAR: zw141_3_0.xml (17.6 KB)

XML file in the userdata folder: network_dd419481__node_122.xml (13.7 KB)

what is wrong here?

Bruce_Osborne · July 10, 2020, 5:31pm

Did you delete the Thing from OH (do NOT exclude from network) and re-add it?
You need to do that to get the new binding settings.

ffr · July 10, 2020, 6:03pm

I actually used a different device for this latest attempt. It had not been included before.
To verify, I just now deleted and re-added the device that I had included previously with the old version of the binding.
Still only the old parameters in Habmin
Additional info: in Habmin Manufacturer ID is 0371, but it says “unknown manufacturer”
@sihui

sihui · July 11, 2020, 6:51am

We have two ZW141 for that device with manufacturer aetoec id 371 in the database where it should only be one:

https://github.com/openhab/org.openhab.binding.zwave/blob/2.5.x/src/main/resources/ESH-INF/thing/aeotec/zw141_0_0.xml

github.com

openhab/org.openhab.binding.zwave/blob/2.5.x/src/main/resources/ESH-INF/thing/aeotec/zw141_3_0.xml

<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
  xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
                      https://openhab.org/schemas/thing-description/v1.0.0">

  <thing-type id="aeotec_zw141_03_000" listed="false">
    <label>ZW141 Nano Shutter</label>
    <description><![CDATA[
Nano Shutter<br /> <h1>Overview</h1><p>Aeotec Nano Shutter is a Z-Wave motor controller specifically used to enable Z-Wave command and control (up/down/stop) for existing window covering motors. It can connect to 2 external manual switches/buttons to control the motor up/down/stop independently.</p> <p>Its surface has a pin socket, which can be used for connecting to the touch panel, so you can also use the touch panel to control the Nano Shutter.</p> <p>The wireless module is powered from the mains supply. In the event of power failure, non-volatile memory retains all programmed information relating to the units operating status.  Nano Shutter is also a security Z-Wave plus device and supports Over The Air (OTA) feature for the products firmware upgrade.</p> <p>It can be a repeater in the Z-Wave network. Acting as a bridge for communication, it will forward Z-Wave command messages to their destinations if the originating controller is out of range from the destination node. </p> <br /> <h2>Inclusion Information</h2><ol><li>Set your Z-Wave controller into pairing mode.</li> <li>Press the Action Button on the Nano Dimmer or toggle the external manual switch once, the green LED (non-secure indication) will blink to indicate the Nano Dimmer is entering into pairing mode.</li> <li>If the Nano Dimmer has been successfully added to your Z-Wave network, its RGB LED will be solid. If the pairing was unsuccessful, the red LED will be on for 2 seconds and then remain a colourful gradient, repeat the instructions above from step 1.</li> </ol> <br /> <h2>Exclusion Information</h2><ol><li>Set your Z-Wave controller into removal mode.</li> <li>Press the Action Button 6 times on the Nano Dimmer or toggle the external manual switch 2 times in fast succession.</li> <li>If the Nano Dimmer has been successfully removed from your Z-Wave network, its RGB LED will remain colourful gradient. If the removal was unsuccessful, the RGB LED will still be solid (following the state of the output load), repeat the instructions above from step 1.</li> </ol>
    ]]></description>
    <category>Blinds</category>

    <!-- CHANNEL DEFINITIONS -->
    <channels>
      <channel id="blinds_control" typeId="blinds_control">
        <label>Blinds Control</label>
        <properties>
          <property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC</property>

This file has been truncated. show original

I think the zw141_0_0.xml needs to be deleted, @chris ?

chris · July 11, 2020, 7:28am

These two files are both for the same database entry - the filename changed at some point as the version was updated. I guess that somewhere along the lines someone updated the version to limit this to version 3 for some reason - I guess that now means anyone with this device with version less than 3 will find the device doesn’t work.

Is this device is available in version < 3, or is that only available with the older manufacturer ID?

ffr · July 11, 2020, 8:35am

I do not know if devices with different versions always have different manufacturer IDs.
My devices originally had the “old” manufacturer ID and with the firmware update (I used the Aeotec firmware update tool) got a different manufacturer ID.

Bruce_Osborne · July 11, 2020, 8:49am

Normally no. The manufacturer has one id assigned.

Likely either a manufacturer got bought or a device was contracted to another company before they got their own if assigned.

chris · July 11, 2020, 9:03am

Aeotec started using a new manufacturer ID a while back - I’m not sure why, but they registered a new ID.

Ok, I’ll just remove the old entry and we can hope this doesn’t cause problems for others.

ffr · July 11, 2020, 10:12am

@chris When do you think, the new JAR will be available? Question: would it solve my problem if I deleted the duplicate file from my downloaded JAR?
I just need to delete and re-add the devices - no need to exclude, right?

Bruce_Osborne · July 11, 2020, 10:20am

Correct ( and wake up long enough for full discovery).

chris · July 11, 2020, 11:17am

I believe it should already be available - at least, it was recompiled earlier after I made the change.

sihui · July 11, 2020, 3:09pm

Yes, it was this horrible conversation with a former openHAB user:

That user did a firmware upgrade, so maybe only devices which were upgraded are affected:

ffr · July 11, 2020, 3:25pm

The firmware version 3 functionality is now available to the upgraded devices.
I have not yet deleted and re-added a version 1 device, so I do not know if that would still work.
Thanks for your support, guys.
I am still struggling a bit with setting the devices up to the point I want them, though. Right now, I guess the nano-shutter wants to make a fool out of me. Will continue tomorrow.

bf8392 · October 19, 2020, 7:22pm

What progress did you make? The nano shutter fools with me too XD. The external switches are not working as expected and I want to update to 3.1…should I?

bf8392 · October 19, 2020, 8:24pm

As an Answer to my own question and for everyone having Problems with the Aeotec Roller Shutter:

You should DEFINITELY Uoadte the device, as it is completely unusable on firmware 2.2 (not only in openhab, but also with the external buttons…
Before you file an Issue, DO THE UPDATE! -> All my problems (missing settings, “funny behaviour” etc.) have resolved with the update, and the device works perfectly now.

ffr · October 31, 2020, 3:14pm

@bf8392 the shutter works for me as well, with 3.1 .