<![CDATA[Comfort Automation/ Security System Forums - Firmware Upgrading Problems]]> https://www.comfortforums.com/ Sat, 22 Aug 2026 13:07:23 +0000 MyBB <![CDATA[Firmware on CM9001/A - cannot upgrade]]> https://www.comfortforums.com/thread-5982.html Wed, 17 Jun 2026 17:49:40 -0400 cc_uk]]> https://www.comfortforums.com/thread-5982.html
In trying to troubleshoot this I wanted to try older firmware on the CM9001/A to determine if SCS used to work.

I ran into problems - I downgraded to ULTA 7.252.   SCS still didn't work, but found I was then unable to upgrade again to 8.034.  I got a message to say that the firmware did not match the system type.

after a reset the CM9001/A no longer responds - ONLY the right hand red LED of the bank of 4 LEDs is lit (ID0?), ie to the immediate right of the ALM LED.

I am assuming either the board is faulty or the FW is corrupted.    I then tried to upgrade with the firmware upgrade cable, but noted that a CM9001/A needs a UCM/USB and not ETH03.

Since I don't have a USB module I will have to order one, though Laser do not appear to have them in stock.  Before I order one on back-order through them please could you help me with advice on whether you think this is likely to work or is this CM9001/A faulty?]]>
In trying to troubleshoot this I wanted to try older firmware on the CM9001/A to determine if SCS used to work.

I ran into problems - I downgraded to ULTA 7.252.   SCS still didn't work, but found I was then unable to upgrade again to 8.034.  I got a message to say that the firmware did not match the system type.

after a reset the CM9001/A no longer responds - ONLY the right hand red LED of the bank of 4 LEDs is lit (ID0?), ie to the immediate right of the ALM LED.

I am assuming either the board is faulty or the FW is corrupted.    I then tried to upgrade with the firmware upgrade cable, but noted that a CM9001/A needs a UCM/USB and not ETH03.

Since I don't have a USB module I will have to order one, though Laser do not appear to have them in stock.  Before I order one on back-order through them please could you help me with advice on whether you think this is likely to work or is this CM9001/A faulty?]]> <![CDATA[8.030 not upgrading]]> https://www.comfortforums.com/thread-5821.html Tue, 25 Nov 2025 13:24:36 -0500 MCFH]]> https://www.comfortforums.com/thread-5821.html I was on 8.013 and tried to upgrade to 8.030 - it just doesn't take it.
I then manually upgraded to 8.017 (which was never offered to me automatically) and it upgraded fine.
Any thoughts?
Thanks
Mark]]> I was on 8.013 and tried to upgrade to 8.030 - it just doesn't take it.
I then manually upgraded to 8.017 (which was never offered to me automatically) and it upgraded fine.
Any thoughts?
Thanks
Mark]]> <![CDATA[Clock 1 day ahead]]> https://www.comfortforums.com/thread-5619.html Fri, 21 Mar 2025 05:54:26 -0400 ]]> https://www.comfortforums.com/thread-5619.html I already tried to use another ntp server pool to automatically correct the time from the UCM to the Comfort system, but since months the clock goes wrong after a few days.  The time is exactly correct, but the day always differs 1 day.  So when we are friday, comfort is already at saturday.
I maybe could uncheck the setting to automatically correct the time from ntp servers, but that also means that clock drift etc... may encounter after some time.
Anyone experience with this odd behaviour ?

Kind Regards,
Bart]]> I already tried to use another ntp server pool to automatically correct the time from the UCM to the Comfort system, but since months the clock goes wrong after a few days.  The time is exactly correct, but the day always differs 1 day.  So when we are friday, comfort is already at saturday.
I maybe could uncheck the setting to automatically correct the time from ntp servers, but that also means that clock drift etc... may encounter after some time.
Anyone experience with this odd behaviour ?

Kind Regards,
Bart]]> <![CDATA[Problem upgrading KP04A]]> https://www.comfortforums.com/thread-5519.html Tue, 12 Nov 2024 11:54:41 -0500 ]]> https://www.comfortforums.com/thread-5519.html It starts with the \"Upgrading Firmware\" dialog but then I get a \"Firmware Upgrade Timed Out - Continue from Last Address\" pop up.
Clicking \"Yes\" on this just repeats the failure.
The keypad is now reporting \"Upgrading Mode\" and flashing some red lights. I can\'t seem to do anything to unstick it.
How can I fix this?
Cheers,
Keith]]> It starts with the \"Upgrading Firmware\" dialog but then I get a \"Firmware Upgrade Timed Out - Continue from Last Address\" pop up.
Clicking \"Yes\" on this just repeats the failure.
The keypad is now reporting \"Upgrading Mode\" and flashing some red lights. I can\'t seem to do anything to unstick it.
How can I fix this?
Cheers,
Keith]]> <![CDATA[Firmware 8.001]]> https://www.comfortforums.com/thread-5497.html Wed, 17 Jul 2024 18:10:16 -0400 ]]> https://www.comfortforums.com/thread-5497.html <![CDATA[Firmware upgrade versions]]> https://www.comfortforums.com/thread-5469.html Wed, 07 Feb 2024 17:22:18 -0500 ]]> https://www.comfortforums.com/thread-5469.html
I have an install with a 9000 Comfort 2 panel with firmware - Week, 5.045, file system 34 and UCM type 10 v 5.092 (old serial UCM). X10 is also in use in this install, so no option for a 9001 upgrade

It\'s using the last version of Comfigurator 2 (v 2.2.3) and whilst the upgrade to Comfigurator 3 is on the to do list (as is updating to a UCM6/ETH), that won\'t happen yet but it will be good to be able to nevertheless update the Comfort and UCM firmware to the latest version.

Are there any restrictions to what version of both Comfort and UCM Serial to upgrade to whilst maintaining compatibility for the current Comfigurator 2 (CCL) file?]]>
I have an install with a 9000 Comfort 2 panel with firmware - Week, 5.045, file system 34 and UCM type 10 v 5.092 (old serial UCM). X10 is also in use in this install, so no option for a 9001 upgrade

It\'s using the last version of Comfigurator 2 (v 2.2.3) and whilst the upgrade to Comfigurator 3 is on the to do list (as is updating to a UCM6/ETH), that won\'t happen yet but it will be good to be able to nevertheless update the Comfort and UCM firmware to the latest version.

Are there any restrictions to what version of both Comfort and UCM Serial to upgrade to whilst maintaining compatibility for the current Comfigurator 2 (CCL) file?]]> <![CDATA[Slave comm failure and then instant recovery after upgrade to 7.207]]> https://www.comfortforums.com/thread-5418.html Sat, 11 Feb 2023 13:50:16 -0500 ]]> https://www.comfortforums.com/thread-5418.html
Code:
07/06 00:00 Reset Comfort Controller0
7/06 00:00 Comm. failure # Slave 1
07/06 00:00 Comm. restore # Slave 1
02/11 18:22 Date/Time Change UCM 1
02/11 18:24 Sign in - User # 10
2/11 18:36 Sign in - User # 1
02/11 18:37 Sign in - User #1
02/11 18:38 Sign in - User # 1
02/11 18:39 Reset Comfort Controller
02/11 18:39 Sign in - User # 1
02/11 18:40 Sign in - User # 1
02/11 18:40 Comm. failure # Slave 1
02/11 18:40 Comm. restore # Slave 1
 
Seems stable after the restore - is this a reported bug or smoothing else? FYI, controller is 7.201Thanks!
]]>
Code:
07/06 00:00 Reset Comfort Controller0
7/06 00:00 Comm. failure # Slave 1
07/06 00:00 Comm. restore # Slave 1
02/11 18:22 Date/Time Change UCM 1
02/11 18:24 Sign in - User # 10
2/11 18:36 Sign in - User # 1
02/11 18:37 Sign in - User #1
02/11 18:38 Sign in - User # 1
02/11 18:39 Reset Comfort Controller
02/11 18:39 Sign in - User # 1
02/11 18:40 Sign in - User # 1
02/11 18:40 Comm. failure # Slave 1
02/11 18:40 Comm. restore # Slave 1
 
Seems stable after the restore - is this a reported bug or smoothing else? FYI, controller is 7.201Thanks!
]]> <![CDATA[UCM Firmware upgrade succeeds but doesn't actually upgrade]]> https://www.comfortforums.com/thread-5406.html Mon, 21 Nov 2022 14:28:03 -0500 ]]> https://www.comfortforums.com/thread-5406.html I\'ve tried resetting the system to no avail.
Any ideas?

IGNOTE THAT - its burst into life! No idea what changed...]]> I\'ve tried resetting the system to no avail.
Any ideas?

IGNOTE THAT - its burst into life! No idea what changed...]]> <![CDATA[Failure with upgrading Firmware by UCM/USB]]> https://www.comfortforums.com/thread-5306.html Thu, 06 May 2021 06:49:38 -0400 ]]> https://www.comfortforums.com/thread-5306.html
This sometimes causes a loss of communications after some time.  It may work well for a long time, but may cause problems at other times.
It is best to remove any other USB devices from the computer before trying the firmware upgrade.. 
 

This applies to upgrading by firmware upgrade cable as well as by direct comfigurator upgrade.

We had a situation where firmware upgrade repeatedly failed using both methods. Then we noticed that there was another USB plugged in After removing the other USB, the firmware upgrade was immediately able to work
]]>
This sometimes causes a loss of communications after some time.  It may work well for a long time, but may cause problems at other times.
It is best to remove any other USB devices from the computer before trying the firmware upgrade.. 
 

This applies to upgrading by firmware upgrade cable as well as by direct comfigurator upgrade.

We had a situation where firmware upgrade repeatedly failed using both methods. Then we noticed that there was another USB plugged in After removing the other USB, the firmware upgrade was immediately able to work
]]> <![CDATA[Unable to connect to UCM ETH03 after firmware UCM upgrade]]> https://www.comfortforums.com/thread-5294.html Fri, 26 Mar 2021 18:41:02 -0400 ]]> https://www.comfortforums.com/thread-5294.html I have upgraded Comfort, Slave and UCM GSM4 this evening with no issues. All on latest non-beta versions.
I then upgraded UCM ETH03 from 7.098 to firmware 7.141. It said it was completed and suggested a module rescan but now I cannot connect Comfigurator any more Sad
I have reset Comfort but still no luck.
I can run Comfort Server Manager and see the ETH03 module (firmware 2.23) and I can ping it from my PC but I just cannot connect to it on the configured ports 1001 or 1002.
Does anyone have any suggestions of what I should try next?

]]> I have upgraded Comfort, Slave and UCM GSM4 this evening with no issues. All on latest non-beta versions.
I then upgraded UCM ETH03 from 7.098 to firmware 7.141. It said it was completed and suggested a module rescan but now I cannot connect Comfigurator any more Sad
I have reset Comfort but still no luck.
I can run Comfort Server Manager and see the ETH03 module (firmware 2.23) and I can ping it from my PC but I just cannot connect to it on the configured ports 1001 or 1002.
Does anyone have any suggestions of what I should try next?

]]> <![CDATA[New system after upgrades has all Flags set to ON]]> https://www.comfortforums.com/thread-5170.html Wed, 06 May 2020 18:16:01 -0400 ]]> https://www.comfortforums.com/thread-5170.html Being so apparently unreasonable, I question myself if it could be something caused by me.But what? I do not even know how to do it so thoroughly (ALL Flags)
I noticed because I had setup a response 75 to zone 1 as it is always nice to have an audible response to testing.
It was chiming before firmware upgrades performed on all modules (see previous topic).Right after FW upgrades I heard no more chime and thought it was something with the sensor on zone 1. Played response 75 directly from Configurator and no chime.I assigned zone announce to zone 1 and it was working fine.I played DoorPhoneChime (response 67) and chime was played
Response 75 tests Flag1=0 to play the sound (although it says it tests Flag16 - old error)I checked the flags and they were all set to ON.Cleared Flag1 and chime was again OK with response 75
Then I looked if I could Write Selectively Flag1 to 0 from Configurator to Comfort (just to check)I found I could not (no selection) Therefore I could not have done ALL Flags ON this way.
So, my questions are:
  1. Is it supposed to start with all Flags ON as default (previously all flags OFF) ?
  2. If yes, why ? and how it helps ?
  3. If not, how can that possibly have happened to me ? How can that be done, even if unintentionally
  4. How can I \"undo\" ALL Flags ON and set them OFF?
ThksCarlos]]> Being so apparently unreasonable, I question myself if it could be something caused by me.But what? I do not even know how to do it so thoroughly (ALL Flags)
I noticed because I had setup a response 75 to zone 1 as it is always nice to have an audible response to testing.
It was chiming before firmware upgrades performed on all modules (see previous topic).Right after FW upgrades I heard no more chime and thought it was something with the sensor on zone 1. Played response 75 directly from Configurator and no chime.I assigned zone announce to zone 1 and it was working fine.I played DoorPhoneChime (response 67) and chime was played
Response 75 tests Flag1=0 to play the sound (although it says it tests Flag16 - old error)I checked the flags and they were all set to ON.Cleared Flag1 and chime was again OK with response 75
Then I looked if I could Write Selectively Flag1 to 0 from Configurator to Comfort (just to check)I found I could not (no selection) Therefore I could not have done ALL Flags ON this way.
So, my questions are:
  1. Is it supposed to start with all Flags ON as default (previously all flags OFF) ?
  2. If yes, why ? and how it helps ?
  3. If not, how can that possibly have happened to me ? How can that be done, even if unintentionally
  4. How can I \"undo\" ALL Flags ON and set them OFF?
ThksCarlos]]> <![CDATA[New system after upgrades reports unable to check most recent version]]> https://www.comfortforums.com/thread-5169.html Wed, 06 May 2020 14:15:33 -0400 ]]> https://www.comfortforums.com/thread-5169.html From the back of my head I think these were the versions updated:
  • UCM from 7.117 to 7.136
  • KP04 from 7.005 to 7.014
  • Comfort from ? to 7.160
  • And Eth03 to 2.23
Previous to upgrade, Configurator was showing latest version, and so I knew there were upgrades available.After the upgrade Configurator reports \"Unknown\" on that field for Comfort, UCM and KP04.
If I insist and ask to Check for upgrades, a message is displayed \"Unable to obtain update information\".
Is this a known problem? And is it really a comm/check problem or a wrong message? 
TkxCarlos]]> From the back of my head I think these were the versions updated:
  • UCM from 7.117 to 7.136
  • KP04 from 7.005 to 7.014
  • Comfort from ? to 7.160
  • And Eth03 to 2.23
Previous to upgrade, Configurator was showing latest version, and so I knew there were upgrades available.After the upgrade Configurator reports \"Unknown\" on that field for Comfort, UCM and KP04.
If I insist and ask to Check for upgrades, a message is displayed \"Unable to obtain update information\".
Is this a known problem? And is it really a comm/check problem or a wrong message? 
TkxCarlos]]> <![CDATA[COMFORT II SPC upgrade issue]]> https://www.comfortforums.com/thread-5107.html Sat, 31 Aug 2019 12:19:12 -0400 ]]> https://www.comfortforums.com/thread-5107.html I have a Comfort SPC II that I did an upgrade of the UCM of the Module via the Comfigurator with latest Version.
I have a ETH01  for connect to the board.
After the upgrade ir got no error, but when I see the keypad it got with no letters on the screen.
I noticed that the Comfigurstor lost the connection to the UCM.
I resented via the reset switch button and it starting displaying again.
But I have no connection to the System now..
I also opened the DSManager but cannot find the UCM Sad
What can I do now?
How can I revert this update or connect to the UCM
.?
I dont have USB to connect directly..
Is it any issue with the Tibbo Board?
Please help me.
Thanks
Nuno
]]> I have a Comfort SPC II that I did an upgrade of the UCM of the Module via the Comfigurator with latest Version.
I have a ETH01  for connect to the board.
After the upgrade ir got no error, but when I see the keypad it got with no letters on the screen.
I noticed that the Comfigurstor lost the connection to the UCM.
I resented via the reset switch button and it starting displaying again.
But I have no connection to the System now..
I also opened the DSManager but cannot find the UCM Sad
What can I do now?
How can I revert this update or connect to the UCM
.?
I dont have USB to connect directly..
Is it any issue with the Tibbo Board?
Please help me.
Thanks
Nuno
]]> <![CDATA[Firmware Upgrading System failure]]> https://www.comfortforums.com/thread-5069.html Tue, 11 Jun 2019 05:20:56 -0400 ]]> https://www.comfortforums.com/thread-5069.html <![CDATA[Unable to connect to UCM eth02]]> https://www.comfortforums.com/thread-5046.html Wed, 17 Apr 2019 04:47:55 -0400 ]]> https://www.comfortforums.com/thread-5046.html I then did the firmware upgrades and I thought all was fine. I went back to the system a couple of hours later and it appears that ucm eth02 is not connecting to the network. If I run the dsmanager on the network nothing Is found but if I plug the module directly to my laptop I can see the UCM and set the IP or dhcp.
When plugged into the lan the device does not show up in the list of connected devices on my router list.
Can anyone help me trouble shoot this?]]> I then did the firmware upgrades and I thought all was fine. I went back to the system a couple of hours later and it appears that ucm eth02 is not connecting to the network. If I run the dsmanager on the network nothing Is found but if I plug the module directly to my laptop I can see the UCM and set the IP or dhcp.
When plugged into the lan the device does not show up in the list of connected devices on my router list.
Can anyone help me trouble shoot this?]]>