Loss of 0 when combining Version and SubVersion #6687
-
Checklist
Describe the issueHi, I recently contacted Aeotec support and found that in some cases the firmware numbers were different between Zwave JS UI and Aeotec. They explained to me that some softwares drop the 0 when combining "Version" and "SubVersion" together. For example:
In my case, Zwave JS UI tells me 1.6 when the correct version would be 1.06, thus V1.6 = V1.06 ? Really ? Software versionszwave-js-ui: 9.9.0.09b107a Device informationObserved with Home Energy Meter - Gen5 ZW095 Checklist
Upload LogfileJust an observation after contacting Aeotec support, I have no logs. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
👋 Hey @duylong! Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues. Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one: |
Beta Was this translation helpful? Give feedback.
-
Versions in Z-Wave are just 2 (major, minor) or 3 (major, minor, patch) numbers from 0-255. There is no required formatting of the numbers, e.g. leading zeros, which lead to ambiguity - why isn't 1.06 not formatted as 1.006 considering the version could go up to 1.255? Therefore we format versions the easiest way possible by concatenating the individual parts with dots inbetween, just like SemVer. Meaning:
|
Beta Was this translation helpful? Give feedback.
-
I also have this problem with Shelly, for example, I have a Shelly Qubino Wave 1 module with version 11.03 on their site but in Zwave UI, it is displayed 11.3.0. This problem is disturbing. |
Beta Was this translation helpful? Give feedback.
-
I get semver. I <3 semver. It's great. It'd be wonderful if all products used it everywhere. But they don't. Aeotec delives a firmware expressly called named "1.02" and "6.81.06" IMO, These are the only ZwaveJS Ui being a middleman in this situation and altering what was delivered by the vendor is an extremely confusing idea. |
Beta Was this translation helpful? Give feedback.
They call it like this in their documentation. There's no way for Z-Wave JS to know they do, since all the information we get from the stick is a number
1
(major version) and a number2
(minor version).Similarly, this is the information we get for the firmware version of end devices:
And this is the SDK version (which Silabs finally started formatting like SemVer does in 7.x.y):
We alter nothing, we work with the information we've got. I'm not going to hardcode that the minor version should be zero-padded to length 2 for manufacturer A, to length 3 for manufacturer B, not at all for…