I am just about to upgrade an old SEM to a new SEM.

Before I do that I wanted to check the error that has just occurred. 
 
On keypad I had battery warning and then slave 1 - I've (again) tried to attach the event log file but get cannot upload this file type so have forwarded it to your e-mail.


If you look in the event log you will see that we have a series of coms failures - it possible this may have all kicked off when they had a power cut a couple of weeks ago ( i called in them and had to power everything down to get it all to come good system reset on keypad or manually just kept rebooting into a fault state.

If the charging circuit has failed what should the LED be doing ? Currently solid D14 (green).

I am about to fit a new SEP with outputs (OP01) and include an LEM01 with outputs.

Firstly if I try to fit the LEM01 on op of the master slave then there are NOT 4 fixing holes (i can only match 2 on one side).

Secondly if I fit the OP01 pcb to the base SEP pcb then there is no space at all for the LEM01.

Would it not be best to supply the LEM01 with a longer ribbon cable and say it does not fit on top of the master or slave !

I have in front of me OPO3 and OPO3B what is the difference?

Are they totally interchangeable ?

I've identified a bug with Comfig 3 - on another thread ref ID 0 

Chiu has suggested that I use Comfig 4 that gets over the issue (as far as I can see I've NOT actually uploaded the file live only on non connected PC).

I'm really nervous about using Comfig 4 on older existing Comfort installations. 

Please bear in mind that we deal with some large properties that historically have large complex installations. I attach .cclx file of a property we are attending tomorrow. It developed a slave com fault and i have a 'new' slave panel (just purchased from Laser but not ARM !) to change out - the old slave is the large square chip type.
The main CPU is still on firmware 7.194

Can you give me some assurance that if I use Comfig 4 that its not all going to go horribly wrong !
So for example what testing as been done with C4 on larger older comfort installations ?
Has anybody else used C4 on older installs ?
Should I update the firmware to 8 ?

I have an old CBUS UCM (square chip type)
From my understanding it acts as a translator so you can send a CBUS address to CBUS via the CBUS UCM and visa versa

I have a client with a large number of CBUS commands coming into Comfort from external external CBUS switches to operate blinds (that are wired via comfort).

I have just changed the old UCM for the new UCM and now nothing works either way. Am I to assume that the latest UCM 2 is NOT performing a direct translation and that anything that is already programmed will have to be re-programmed to be incorporated into the CBU UCM menu structure ?

.cclx file attached (not it now has a large no of responses in red !)

We did an upgrade to a main CPU a couple of years back using Comfig 3.14.14.0 all went well and its been fine.

I have just re-opened the file using Comfig 3.14.14.0 then gone to alter some settings. When I go to modules tab UCM - module ID 0 appears.

If I open the same file in Comfig 4.0.4.0 there is no ID 0 and the listing is by my reckoning correct.

---------------------------------------------------

We have only used Comfig 4 on new installations.

What should I do in this situation ?

I will be attending site tomorrow to replace a faulty CBUS UCM so will need to know which way o proceed

Thanks

I've semi successfully migrated from Alphawerks to comfort2mqtt on my Home Assistant setup and wanted to share what I've done and ask a few questions.
My setup:

Cytech Comfort II Ultra (CM9001) with UCM/ETH03
Home Assistant running on Intel NUC
Comfort firmware: 7.183
comfort2mqtt addon: latest version

What I did:

The Alphawerks module used a separate UCM with custom firmware (confirmed it cannot be repurposed)
Unplugged the Alphawerks ethernet cable to take it offline
Started comfort2mqtt connecting to the ETH03 at 192.168.0.50 (1001)
Successfully connected, logged in as User 1, CCLX file detected and loaded
All 24 zones, alarm panel, outputs and fob buttons are now live in Home Assistant via comfort2mqtt

Current issue — reconnect loop:
After connecting, comfort2mqtt logs the following repeatedly approximately every 22 seconds, I had trialled if I could get Comfort2MQTT working a few months ago and dont recall the errors maybe this is now appearing due to a change:
ERROR    Comfort II ULTRA detected (Unsupported Firmware 7.183)
ERROR    Error sending command 'cc00', closing socket.
ERROR    Lost connection to Comfort, reconnecting...
It reconnects immediately and successfully each time, and the system appears to be currently stable and connected, but the loop is a concern for reliability.
Questions:

Port 1001 vs 1002 — I'm currently connected on port 1001 rather than the recommended port 1002 (which is suggested for HA use, leaving 1001 for Comfigurator). Is there any operational problem with staying on port 1001 for comfort2mqtt? I chose this because port 1002 failed to connect — possibly a timeout setting issue in Comfort Server Manager.
Firmware upgrade — I can see the latest firmware is 8.030 (November 2025) and as stated am currently on 7.183. Will upgrading to 8.030 fix the cc00 reconnect loop? I assume so however, is it safe to jump directly from 7.183 to 8.030, or should I upgrade in stages through intermediate versions?
Risks of firmware upgrade — Are there any risks to my existing Comfort programming, zone configuration, or responses when upgrading? Will I need to do anything in Comfigurator after the upgrade? Is there anything specific should be backed up or check before proceeding?
Serial Number: Invalid — The log also shows Serial Number: Invalid after each login. Is this something to be concerned about?

Thanks in advance for your help.

Over the last few months when the alarm is activated it will ring through to my mobile but there is no voice response.
Before you would have been told where the activation was etc.
Does anyone have the same issue.

Could someone share their code to send MQTT message from HA to Comfort to set a virtual input for  zone.

I have tried but cannot get Comfigurator to see that zone set when HA triggers it, I can see other PIR zones in status.

i would like to start using virtual zones now and need some guidance on how to send,

Thank you

Hi, I tried to change my email address (only because I didn't receive any notifications on reply to a thread even though I was subscribed to it).

Anyway, I went to my profile, changed the email address and received an automated email.

The first link in the email ended up with a page saying "Your account has already been activated or does not require email validation."
So as instructed I tried the second link in the email. After entering my username and activation code I received the same message.

The email clearly says that if I don't validate my changed email address then it won't work.

Is this normal?