It it normal for the firmware version to not reset each major iteration? Example I have right now is the firmware on my BlaQ is 1.5.1.6 and I’m updating it to firmware version 1.5.7.7. Shouldn’t it reset the last number making the actually firmware be version 1.5.7.1?
When I first bought the BlaQ the firmware versions last digit would reset when a major update (second or third digit would be different) was introduced, but the past 2 firmware update this hasn’t been the case like I said above. Is this normal or is something wrong?
No. There were several versions that may not have been released to the public. Everytime the code is changed and committed, the version number is increment. It can be major, minor, revision and build.
In this case you got the seventh build of version 1.5.7.
That’s the problem though 1.5.7 or Major, Minor, and Revision (aka Project version) is provided by Konnected the manufacturer. The .7 Build is provided by the user/customer via the Konnected App based on the settings the user/customer sets up not by Konnected themselves. This Build version will increase everytime the user/customer changes a setting, but for every new Project version the Build version should reset. So in my case my version is 1.5.7.x from Konnected themselves and the build is the first of this 1.5.7.x so in theory should be version 1.5.7.1 not 1.5.7.7. Konnected even documents that here: Updating Firmware with the Konnected App down under Project and Build Versions.
@nate Am I understanding this correctly? With every new Project Version Firmware if updating shouldn’t the Build Version portion of the firmware reset? Or does the Build version always increase no matter what?