The Multisensor Module MSM01 has internal sensors for Temperature & Humidity as well as connections to water leakage detection cable for Water Leakage. It also has 4 external inputs for Dry contacts which can trigger alarms or Responses in Comfort.



see http://www.comfortforums.com/forum139/4919.html for more info.

The temperature and Humidity can be mapped to Comfort Sensors eg






 The Comfort 2 mqtt addon in Home Assistant can be configured to display the temperature and Humidity sensors on the dashboard, eg Entry in configuration.yaml

   - name: Temperature
     unique_id: \"comfort2_sensor1\"
     state_topic: \"comfort2mqtt/sensor1\"
     value_template: \"{{ value_json.Value }}\"
     availability_topic: \"comfort2mqtt/alarm/online\"
     json_attributes_template: \"{{ value_json | tojson }}\"
     json_attributes_topic: \"comfort2mqtt/sensor1\"
     device_class: temperature
     state_class: measurement
     unit_of_measurement: °C
     payload_available: \"1\"
     payload_not_available: \"0\"

   - name: Humidity
     unique_id: \"comfort2_sensor2\"
     state_topic: \"comfort2mqtt/sensor2\"
     value_template: \"{{ value_json.Value }}\"
     availability_topic: \"comfort2mqtt/alarm/online\"
     json_attributes_template: \"{{ value_json | tojson }}\"
     json_attributes_topic: \"comfort2mqtt/sensor2\"
     device_class: humidity
     state_class: measurement
     unit_of_measurement: \"%\"
     payload_available: \"1\"
     payload_not_available: \"0\"
the dashboard should show 

Unable to see Comfort II Ultra (MQTT client), Comfort2MTTBridge (MQTT client).
I am using a Mosquitto broker on another device. I can see the messages at the MQTT broker but not in HA.
I am a newbie to HA.
I have reinstalled from scratch and arrived at the same problem.

Hi, I upgraded to the latest version and lost my SEM01. I was asked to download the older version to see what happened, and that seems to have fixed the lost SEM01. Everything seems OK, but on a restart of the system (power Reset), I get a comms failure on SEM01. This clears when I log in on the keyboard or do a module scan through Comfigurator. and states \'communications restored\' I have also communications error 33 restored. when the communications is in fault mode non of the inputs are working in SEM1   

Hi Chiu, I am having a few problems with my system after doing some upgrades. I have lost coms with my slave 01 after doing the upgrade. All I did was checked each module for updates and di them.
The last one was slave 1 and it upgraded to version 8.021 and when it rebooted at the end it states coms failure to slave 1 and of course I have no inputs from that point on.
I have re done the upgrade and all seems to work but I still have no coms to the at sem   

Hi,
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

Does anyone know how you change the ID of this UCM I think it is  ETHge V2.2.3Or can you point me at the relevant manual? Thanks

Attached Files

Thumbnail(s)
   

I would like Night Mode auto arm to make no noise from the key pads on auto arm or auto disarm.
I have been following the advice in this thread:
http://www.comfortforums.com/view_topic.php?id=384&forum_id=1

Auto arm still announces \"night mode\" on the key pads but with no beeps.Audio disarm is completely silent as expected.
My \"Auto Arm Night from Security Off only\" response looks like this:

I am based in the UK and my phone line has been changed to fibre with DECT phones so I have lost the phone connection to my Comfort system. I can see that a GSM4 would allow me to remote disarm my system but my Comfort system is old and I need some help understanding which parts need new hardware or firmware for a GSM4 to work. My system is as follows:

Comfort Ultra II
Version 7.093
File system 34 
Vocab 5 
Custom vocab = No 
System vocab 28 
User vocab 1 
LCD text 1 
LCD KP minimum version 3 
UCM type 10 
Version 7.076 
I am attaching a photo of my UCM in case this helps (I think it is pretty old).

I will be most grateful for any advice.

Guy 

Attached Files

Thumbnail(s)
   

In Home assistant the user code used to log in to Comfort is in the Comfort2MQTT Add-on Configuration page. The comfort user code must be entered.
In File Editor in Alarm Control Panel, there is another user code (default 1234) which is used to for the Home assistant keypad to disarm Comfort. This is not the comfort user code. when you disarm using the Home assistant keypad, the Add-on will do the actual disarming using the Comfort user code in the Add-on Comfiguration.

If you try to change the user code the Comfort keypad, you may get wrong code This is because Home assistant periodically logs in to Comfort with the exiting code. so it is advisable to stop the AddOn when you try to change the keypad user code.

We are planning a new UCMPi using a CM4 Compute module intead of a full raspbery Pi and will try to make it easier to manage this duplication of user codes

Ive recently run into a problem which this information *might* help others trying to use this great application. I have a Comfort system with a CBus and ETH3 UCM fitted. I run the Koochyrat software (slightly modified) on a RPi400 that links to my MQTT server on another RPi4. HA runs on a RPi5 and links to the MQTT server. Of course, this means I can control CBus lights etc from HA via MQTT and via the Python script that is looking at internal events on Comfort. Recently, I found I was unable to login using Comfigurator. I tried everything - new Ethernet cables; reset the ETH3 module; power off - nothing worked! I was looking at a (very expensive!) new ETH3 module, although I could ping the Comfort server and I could login via Julian Wigman\'s excellent application - Comfort Client v 5.1.6.2. But not Comfigurator! After many hours of frustration I noticed that my Comfiguarator network port was set to 1002 - as is the Koochyrat Python program! I changed this port to 1001 using the Options/Settings - and everything works!! How was it changed? I don\'t know - but I now have the port 1001 timeout set to 02 and port 1002 set to 00 (thanks, Slychiu, for that tip!). So, just make sure that your Comfigurator port is NOT the same as the Python access (or anything else)- and all appears well! I hope this tip -and the very useful error comment!! - helps......