I updated the firmware of one of my AEOTEC Nano-Shutters to 3.1. This version is supposed to be able to position the blinds (not only OPEN and CLOSE).
When I tried to update Parameter 35 (time for up and down movement), the update does not seem to get through. When I look into the DEBUG log, it looks like it is changed to a default value of 15000.
When I close the blinds, a percentage value of 11% is shown, as opposed to 100%.
Question: Is this firmware version 3.1. reflected in the database yet?
I attach the XML file for the devicenetwork_dd419481__node_120.xml (13.3 KB) @chris I will send you a link to the debug log. Would be great if you can have a look @sihui : I added you because you habe eben alle to help many times
If you have changed devices, as it seems by updating the firmware, then you will need to delete the current thing and add it back again. If there have been changes to the database since 2.5.6, then you will need the latest binding.
Sorry - I’ve not had the chance to look at the logs as yet as I’ve been spending quite a lot of time trying to finish the new database editor.
@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.
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)
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
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?
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.
@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?