Comfigurator 3.7.6 is released

This is another major release with many new features, imrpovements and bug fixes see see http://www.comfortforums.com/forum20/3543.html


Please post comments, feedback and questions

I note that you say \"The new features described here require Comfort and UCM firmware version 7\". One of my Eth modules is an old one on which the firmware cannot be upgraded (5.92). Can I still use the Comfigurator 3.7.6 upgrade while such a UCM exists on my system?

The new features require the use of a UCM version 7 with Comfigurator
You say that one of the UCMs is 5.92. As long as that is not the UCM that you connect to Comfigurator, it should not be a problem.

Thanks. I connect via an ETH UCM running on 7.016. I assume therefore that the new Comfig version will work.

Yes, it will
You can also upgrade UCM  to the latest firmware 7.028 by right clicking on the module and select \"Check for Updates\"

I have a problem identified with Comfigurator and Z-Wave.
It also happened with 3.6.8, and possibly before that I don\'t know.

In the UCM Z-Wave Mapping, a change takes place without the knowledge of the user in the \"Data 1\" and \"Data 2\" fields, maybe other fields as well.

This seems to happen when unrelated responses are added or changed in Comfigurator. The \"Register number\" in the z-wave mapping window changes, and the name of the associated response changes. If you do not notice this change and leave the error stand, and the new cclx file is uploaded to Comfort, then the correct z-wave responses stop working and/or the wrong responses are executed.

We have not come across this so far
Do you have an example of how this occurs?

Unfortunately I cannot simply recreate the error. I will try and see if I can identify the actions which precede the change, and let you know more at that stage.

It seems to happen after a number of responses have been added or amended. I notice that with comfig ver. 3.7.6.0 I get a dialog warning me that the response number has changed, and asking me do I want to write the change to eeprom.

I have managed to recreate the error I spoke of in one particular situation, though there must be others.

I have a number of screenclips which demonstrate this. I will do this over a few posts to keep the screen clips relevant.

Look at the Z-Wave Mapping data jpg attached (\"ZWave-1.jpg\")

The register Type is \"Response\"; the Register Number is \"435\", the response Register Name is \"UtilityDoorOn\".

Also look at the responses and the numbers attached to the responses (\"ZWave-3.jpg\"). Note that \"UtilityDoorOn\" is #435.