I have a Comfort 11 system. The transformer has started humming and so I assume it is near then end of it\'s life. I am told it is the older type of transformer. I understand from my supplier (Laser Systems) that a replacement is no longer available from them. Can anybody advise where I might get a replacement?
Cheers

I\'m doing a system check and noticed that when Comfort was dialling from my door station to my mobile - I would receive the call but as soon as I answered it, the call was dropped. I tried the dial test and this did the same. I talked into the phone but did not get \"dial test\" spoken response. If I don\'t pick it up it still drops the call. It used to keep going until my mobile voice mail answered. We have had a VOIP system for over 10 years and this is the first time I have had a problem.
I can call my mobile from the house phone and connect successfully. So signal is adequate and VOIP are working.I can access Comfort\'s menu from both the house phone and remotely via my mobile, so the phone module is working. It is dialling out and reaching its destination but appears to be dropping after a 2-3 seconds.
Any thoughts what mught be causing this ? Is there a tweak in the tuning parameters ?
Comfort II Ultra v7.116  UCM 10 v7.096

I have a CM9000 with a UCM/ETH03, a UCM/Pi and an LEM01 giving a total of 24 zones on it. I also have a SEM/01C mounted in SEP01/C expansion box with an LEM03 (16 Zone module).I\'m about to start a removation and I will need at least another 12 zones to cover additional windows, smoke alarms and external doors.What\'s my best option, I don\'t think I can add any more LEMs so should I get another SEM/01 or is there a better way of doing this?
Thanks!

I have noticed that if I arm remotely (phone or via app) and later enter the building to disarm locally, there are no warning blips to indicate a disarm is needed. In fact the keypad makes no announcements on disarm.
I cannot find much in the manuals about how remote disarms work, other than Action Code 73,14 which detects a remote access.
1) does remote arming just reproduce the action of pressing a keypad key activating any attached response ?
2) Why no blips to indicate disarm needed ??
Comfort II Ultra v7.116  UCM 10 v7.096

We have two door stations, when pressed they both chime as normal. However the internal phone does not ring and the two internal keypads do not chime.With security set to \"Away\" the door station takes a message as per normal.
The system was originally installed in 2003 and fairly extensively upgraded in 2014.  I do not know the age of each of the boards in the unit.I am in Melbourne and we do not have knowledgeable Comfort service available (unless  there has been a recent change).  Can you suggest how I might tackle this problem.

I posted this on Discord, but as it seems to be dead over there I will post it here as well. I have setup a number of Sonoff NSPanel Pro devices to act as wall-mounted touchscreens for HA and I wanted to use them as alarm contol panels along with controlling lights, heating, etc. As Comfort is setup with a number of different codes for family members, guest, etc. I wanted to allow everyone to be able to sign-in to the alarm using their own codes.By default, the HA MQTT Alarm Control Panel only allows one fixed code in the configuration, but I have discovered that it now allows the code to be validated by the alarm system itself. I\'ve tested this out and it works perfectly. This is my setup with the old settings commented out:

Attached Files

Thumbnail(s)
   

I’ve recently had a situation where a particular zone went into trouble mode. So I disabled it via Comfigurator.

My Comfort installer took a look yesterday but we couldn’t find any problems. He thinks it’s the LEM03 Local Expansion Module because the failing zone was on that board. The testing, refitting connectors, touching it, etc, seemed to ‘fix’ the problem, until a few hours later when three more zones (also on the LEM03) went into continuous trouble mode, despite Comfort being in Security Off mode as I was home.

At this point the internal and external sirens are going. If I typed in my code the sirens would stop only momentarily before picking up again. Scenes! Absolute chaos inside!! It’s hard to think with Comfort screaming at me from every source - keypad, phone, sirens, etc.

I tried to enter the engineer menu so that I could got into security test mode, hoping that would calm all the sirens. But I simply could not manage it. I’d enter my user code, then try to enter the engineer menu before the sirens kicked off again and Comfort keypad would just beep at me. I could not hear what it was saying over the noise of the sirens. It was hopeless, and I gave up trying to access the engineer menu at this point.

Eventually I got Comfigurator up - I had to sit through Windows updates, what a horrifically timed nightmare! - and was eventually able to DISable the zone inputs by changing the zone type to blank, then upload a new configuration. We’re going to change the LEM03 board next.

But my question is: how should I have handled this zone trouble situation? What can I do immediately from the keypad to calm Comfort down? So that I know how to better cope next time around.

I was doing some work on my system and I noiticed that there was a firmware upgrade available for the UCM/ETH03.
The upgrade seemed to go OK, but the device is no longer responding. If I do a scan for modules I get \"Module scan timed out. Please retry the scan later.\" Also, the Comfort Server Manager (ETH03) does not find the module.

I tried resetting the ETH03 module and that didn\'t work and I also tried uploading the previous firmware. It seemed to go OK but the version shown didn\'t change and I\'m still getting timeouts.
Any ideas?

Sure it’s old but still otherwise works very well, except the back light has got very dim. Any way to fix this/part I can replace to brighten it up?

If the Comfort system does not have a UCM at ID1, Scanning for modules using UCM at another ID or ETH03 plugged in to CM9001 will show the result shown below. UCM ID1 (which is not present) has  UCM Type  shown as OTHER and Firmware is 255.255. This will be fixed in the next version (currently 3.13.9). It otherwise has no effect on the functions of Comfigurator so do not worry

Attached Files

Thumbnail(s)