.

1. When exit from a configuration or loading new file, message \"Configuration for module UCM has changed or the number of Responses referenced by the module have changed\" may appear even though there is no such change or the module has no eeprom
2. If a module firmware is too old so that it does not report its firmware during a module Scan, the previous modules firmware is reported instead
3. When scanning is being done and a Communications Failure occurs during the scan, Comfigurator may report that a module does not support scanning, due to a long delay in replying due to the Comms failure report
4. If Comfigurator is opened with a diferent file system to the Comfort which is connected, Conversion of file system to the correct one after a scan may cause an exception
5. If last connection was by KT03 USB, and a new file is started without KT03 in the configuration, the connection is still by KT03 USB but the box \"Via KT03\" is not visible and so cannot be disabled. The workaround is to add a KT03 to make  \"Via KT03\" visible, then uncheck the box
   

Quote:Regarding point (2) on your known bugs list; can you expand on this as this sounds like the functionality I need. If I say scan my ucm smarttfit I want it to keep the value stored manually in the cclx file. So this doesn\'t feel like a bug to me.

Quote:One thing I\'ve noticed, if you set show status checkbox on say FLAGS or OUTPUTS, you can highlight a row and then press down arrow key to move focus to the next rows. I.e. when it refreshes the status it refreshes and jumps back to the remembered/current row.

1. When exit from a configuration or loading new file, message \"Configuration for module UCM has changed or the number of Responses referenced by the module have changed\" may appear even though there is no such change or the module has no eeprom
2. If a module firmware is too old so that it does not report its firmware during a module Scan, the previous modules firmware was reported instead
3. When scanning is being done and a Communications Failure occurs during the scan, Comfigurator may report that a module does not support scanning, due to a long delay in replying due to the Comms failure report
4. If Comfigurator is opened with a diferent file system to the Comfort which is connected, Conversion of file system to the correct one after a scan may cause an exception
5. If last connection was by KT03 USB, and a new file is started without KT03 in the configuration, the connection is still by KT03 USB but the box \"Via KT03\" is not visible and so cannot be disabled. The workaround is to add a KT03 to make  \"Via KT03\" visible, then uncheck the box

1. If a module is \"Not Found\" after a scan ie listed in RED, and the configuration is written to Comfort, this will not cause  a Communications Failure. This is because modules that are not found by Scannning will not add to the module count.
2. \" File Creation Time\" in Configuration > System Information has been renamed \"Last Saved\". This is a more accurate description as it shows the time that the  cclx file was last saved.

1. Local Timezone in the default templates is set to London/Dublin/Edinburgh. Users in other countries using Windows 7 may have their Comfort sets to the wrong time zone. Windows XP does not have this problem
2. USB via KT03 may be set in Options > Settings when KT03 has been removed. You have to add bak KT03 in order to uncheck the Via KT03 box
   

1. Local Timezone in the default templates was set to London/Dublin/Edinburgh and users in other countries using Windows 7 may have their Comfort sets to the wrong time zone.

1. The colour of Not Polled Modules after scanning has been changed from Blue to Purple so as not to confuse with referenced modules and responses which are in blue
2. Improvements in GSM4 and Zwave modules which require new UCMs yet to be released
   

1. Some PCs may have UCM connection if USB wrongly set to Via KT03 even though KT03 is not present and the Voa KT03 box is not seen. The workaround to remove this is to add a KT03 in Modules, go back to Options > Settings and uncheck the Via KT03 box
2. For KT03, write to KT03 by direct USB connection fails with error popup \"Failed to Connect to KT03\". However upgrading firmware and using KT03 USB as a UCM is not affected. Write to KT03 by Bus can also work.
   
3. Some of the updated default templates are not updated by this software version. Please uninstall the previous 3.7.x version before installing this version
4. If KT03 configuration is erased (eg due to incomplete write) Reading from KT03 will cause an Exception
5. If a Zone Type which has no Normal Alarm Type (eg Zone Type 30 Digital NO) is assigned to an alarm type, then it causes all zones to be assigned to the changed zone Type
6. If there are 2  UCMs connected to Comfort which have  correct ID but Comfort is configured for 1 UCMs, and the cclx template has default 1 UCM, Scanning for All modules will show the 2nd UCN as \"Not Polled\" which is correct. However scanning for All Modules will not work - no scan is done. However scanning for UCMs only in this case works.
   

1. Reading from Comfort will cause an exception if a write to Comfort has not been done. Workaround is to Write to Comfort first for each system.
   
2. Blinds function is not correct
3. Thermostat function selective write does not write the parameters and does not write the correct parameters to locations
4. The new action \"If Last Security Mode\" has only \"Security Off\"and cannot select other security modes in the condition
   
5. GSM4 - Get status interrupts  Firmware Upgrade for GSM4 and causes it to fail repeatedly. The workaround is to log out and do the upgrade before logging in so Set Status is not on during the upgrade
6. Links to manuals are not complete
7. Selective Write does not select Control Menu when Responses change which are assigned to the Control Menu. To workaround, please use Full WRITE. This may be a bug from older versions
   

1. Help link to Comfort Forums
2. Help test for Security > Status Outputs is improved
3. Supports new UCM/GSM4
4. Supports UCM/Zwave3
5. Link to Manuals for each  products

1. Action 42 - Keypad button causes Family Care Alarm Dialout
2. Action 43 - Clear Event Log
3. Action 184 - Branch if = 2 byte signed constant
4. Action 185 - Banch if <> 2 byte signed constant
5. Action 186 - Branch if >= 2 byte signed constant
6. Action 187 - Branch if < 2 byte signed constant
7. Action 188,0 - Exit if = 2 byte signed constant
8. Action 188,1 - Exit if <> 2 byte signed constant
9. Action 188,2 - Exit if >= 2 byte signed constant
10. Action 188,3 - Exit if < 2 byte signed constant
11. Action 73, 30 - Get Last Security Mode before disarmed
12. Action 73,31 - Get GSM Network Strength
    
13. Action 155 - Send SMS Custom Message (GSM4)

1. Some PCs had UCM connection if USB wrongly set to Via KT03 even though KT03 is not present and the Voa KT03 box is not seen.
   
2. For KT03, write to KT03 by direct USB connection fails with error popup \"Failed to Connect to KT03\".
   
3. If KT03 configuration is erased (eg due to incomplete write) Reading from KT03 will cause an Exception
4. If a Zone Type which has no Normal Alarm Type (eg Zone Type 30 Digital NO) is assigned to an alarm type, then it causes all zones to be assigned to the changed zone Type
5. If there are 2  UCMs connected to Comfort which have  correct ID but Comfort is configured for 1 UCMs, and the cclx template has default 1 UCM, Scanning for All modules will show the 2nd UCM as \"Not Polled\" which is correct. However scanning for All Modules will not work - no scan is done. However scanning for UCMs only in this case works.
6. KT03 schedules - If Days of the week are checked the file saved and reopened, the days of week become unchecked. This is a problem with older versions as well