This is a guide to setting up encrypted remote access  using DuckDns and Lets encrypt to secure the connection. This content is mainly from https://smarthomeaddict.co.uk/2022/07/ho...tsencrypt/ which is one of the  best guides.

Why this method?

•     It’s a quick and relatively easy way to get remote access to Home Assistant.
  
•     It provides an SSL certificate to keep your connection secure.
  

•     There is a need to open up a port in your router to forward the port.
  
•     Internal access will now report a certificate error, but you can safely ignore this
  

1. Forward port 8123 to internal Port 8123. Protocol is TCP
   
2. Forward port 443 to internal Port 8123. Protocol is TCP
   

The MSM01 built-in Temperature sensor is mapped to a Comfortsensor

1. Comfort Sensor for Temperature in deg C
2. Comfort Counter for Temperature Setpoint deg C
3. Comfort Flag for Enable Setpoint (and Alarm)
4. Comfort Virtual Input trigger alarm when Temperature exceeds the Setpoint

1. Comfort Sensor for Humidity in %
2. Comfort Counter for Humidity Setpoint in %
3. Comfort Flag for Enable Setpoint (and Alarm)
4. Comfort Virtual Input which triggers alarm when the humidity reading exceeds the Setpoint

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.



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

The temperature and Humidity can be mapped to Comfort Sensors eg



Setpoints for temperature and humidity can be set up, so that if the temperature or humidity exceeds the setpoints, an alarm can be triggered.


Comfort has an integration to the Home Assistant Platform see http://www.comfortforums.com/forum143/5577.html Home Assistant can be installed in a Respberry Pi. The Home Assistant User Interface can be accessed by Browser on any computer (PC, MAC, Linux) or on Mobile phone apps for iOS and Android. Notifications can be set up for registered Mobile phones when any temperature or humidity alarm occurs.


The current sensor value for Temperature and Humidity can be displayed on the Dashboard



Home Assistant also allows powerful graphing capabilities for the sensor values. The duration over which the sensor values can be selected eg 1 week, 1 month, and the time scale of the graphical display be  adjusted as well as the vertical Axis scaling and units.




Similarly Water Leakage sensor values can be displayed if required.
The Sensor Data displayed on the graph can be exported to a csv file


For details on configuration and setup in Home Assistant please see http://www.comfortforums.com/forum143/5624.html  
Comfort EMS with MSM01 can be packaged and configured with Raspbery Pi and Home Assistant if required

I recently updated my firmware to the current version from quite an old version and also installed a GSM module. 

We always had the system programmed so that when we pressed the lock symbol the alarm would bypass the garage sensors and then set to away mode. We could then access the garage on our way out of the house. 

If we were going out and wanted the whole house including the garage to be alarmed then we pressed \'FF\' and the system was set to vacation mode.

Since my recent upgrade, pressing FF does not do anything. We can only set to vacation mode by using the GSM module.

Is there now a different way to set to vacation mode that I have missed? 

Thanks  

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)