Comfort Automation/ Security System Forums

The next beta version Comfigurator 3.6.1 will have the following changes

Bugs Fixed

1. Update firmware for Controller always asks to Scan for Modules
2. When  a new file is opened and scan for modules discovers KT03, selecting KT03 will cause an exception
3. Upgrading KT03 by direct connection to PC  using the KT03 USB port has an error message that UCM version 6 is required.
   

Latest Firmware Upgrades are shown
After scanning for Modules, the latest firmware for each module will be shown so you do not have to check for updates for every module like in 3.6.0


The Latest Version is shown next to the Current version as shown in the above screenshot. Note that the screenshot shows some \"Current\" versions as higher than \"latest\" versions (eg GSM) because of beta firmware that have been installed.
The firmware can be upgraded in the same was as in 3.6.0 ie by Right clicking and selecting \"Check for Firmware Updates\" or Firmware Upgrade from Local File\"

Known Bugs

1. Trying to upgrade a module from Local File with firmware shown as \"Unknown\" after scanning will allow the firmware file to be selected. It should give an error message \"Minimum firmware is version 6 for Firmware upgrade by Bus\"
2. Velbus and Zwave Configurator still has a few bugs

Comfigurator 3.6.1 is ready for testing

if you have Comfigurator 3.6.0, running it will prompt you to upgrade to 3.6.1
This shows the upgrade check  working

IN the screen shot above ....

The latest version column should have the HIGHEST version number?

The \'version\' column would (to me) suggest that this is the column that has been scanned by comfigurator and is showing the actual status of the UCM\'s scanned.


Am I missing something?

Unless of course you were connected to a test rig that had UCM with higher version numbers and no access to the internet!

Or the higher version number is a beta so not on the list of available Le firmware that comfigurator checks against. I noticed same with the latest beta firmware which was installed locally

Correct, the \"latest\" version is the latest Released version

I suppose my point is that the screen shot may be confusing to 99% of users who would NEVER encounter such a scenario !

Why not have a boolean somewhere in settings that says \"include betas in version check?\" and then in the \"Latest Release\" column show betas as well but maybe in a different colour. With the boolean set the firmware upgrade would also download a beta.

Julian

And to be even cleverer, you would already know if betas had been installed already so the boolean could even be implicit in cases such that you could show the betas based on this too maybe.

J

I second that suggestion.

Ingo

The screenshot will  be modified so that it does not show any beta versions, when we release the final Comfigurator 3.6.x

The boolean would be good but there is so many things happening with comfigurator
The number of people who test beta firmware probably is a smaller number (and smarter ) so they may not need such urgently