Zwave device being incorrectly identified since 2.3.0

Let’s give this a day or so so that @sihui can also have some time to respond. If there’s no veto then I’d suggest we proceed as above :slight_smile:

The xml file is in the zwave directory in userdata. Many times that is /var/lib/openhab2/zwave The correct xml file has the node number in its name.

I have uploaded an older version as well in case it is helpful.

network_d0269028__node_9.xml (7.0 KB) node9.xml (6.9 KB)

Thanks @chris and @Bruce_Osborne for your help.

2 Likes

Here are the text files of the overview type information for the two devices.

output2.txt (1.3 KB) output1.txt (1.4 KB)

I think Chris meant following the guide and getting a login on his site.

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide

You cannot add the information until the new entry is generated from your xml file. We are waiting on any comment from Sihui.

Unfortunately we already have had confusion in the past about overlapping versions for these two devices:

ZWS12 https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/325 :

2019-03-31: "version_max": 1.255
2019-07-06: "version_max": 2

ARZ https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1036 :

2019-03-26: "version_min": 2.1,
2019-03-26: "version_max": 2.1,
2019-03-31: "version_max": 255.255

The main reason for all this confusion seems to be:

In short: Fakro issued wrong device identifications to the ZWS12, type and id 0003:0001 should only belong to the ARZ device.

To me this looks like we should remove the 0003:0001 from the ZSW12 completely. Users with this device need to contact Fakro to get a firmware update.

The comments in the post you linked to said they needed to return the device to Fakro. @chris @robb01 how do we proceed?

Yes, to get the mentioned firmware update.

Ouch. Four devices removed and shipped to Eu from Aus? I doubt the local resellers will want to have anything to do with this but I can ask.
Maybe I should enquire if there is a way of uploading the firmware using a Raspberry Pi or Arduino or do they actually replace a chip?
How has this been handled with other users in the past that @sihui refers to?

You are the first.

We still could go with this suggestion and wait for the next user in trouble :grinning:

1 Like

The would be a decsion for the boss, @chris :wink:

1 Like

I would be in favour of the work around but will enquire with Fakro and my local reseller.

1 Like

Done: https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1190

Chris does not seem to have some spare time, but I think we can proceed with the workaround.
I did cross reference this post in the comments section.
Rob, you need to upgrade your zwave binding to the latest snapshot once the changes got merged (probably after the weekend)

2 Likes

@sihui I just downloaded the Snapshot from
https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.1-SNAPSHOT/org.openhab.binding.zwave-2.5.1-SNAPSHOT.jar
but got this in the console so it’s not the updated version:

  19 │ Active │  80 │ 2.5.1.201912300340      │ openHAB Add-ons :: Bundles :: ZWave Binding
232 │ Active │  80 │ 2.5.0                   │ openHAB Add-ons :: Bundles :: ZWave Binding

But getting this error besides:

Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.zwave-2.5.1-SNAPSHOT.jar

org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [19]

Where do I find the most recent update of the ZW binding?
Also had 2 active bindings so had to manually stop 2.5.0.

I think you need to manually remove the 2.5.0 one in Karaf

1 Like

Acording to
https://products.z-wavealliance.org/products/2477

ZWS12 should have 0002:0011

Thanks @Tomass.

However this issue is not able to be resolved until the firmware in the four devices I have has been updated with the correct ID information or the OH equipment database is adjusted to correct for this anomaly.
Each time the device connects to the zwave network the controller reads this info from the firmware. Currently it is reading the wrong info and consequently setting up the device incorrectly.

However, I understand that in the current situation you have actuators that identify themselves with numbers 0002: 0011 but because of an error in OH they are unrecognizable. If they were identified by number 0003: 0001, they would add themselves to OH as Shutter.? Probably, when completing the data, someone did not notice that the ID number also changed.

It is not uncommon for different versions (or different regions) of a device to have different IDs and the ZWave product database often doesn’t provide all of these. Please do not remove IDs unless you are really sure that there is not the same device with multiple IDs as this is extremely common.