| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 322 online users.
» 0 Member(s) | 319 Guest(s)
Applebot, Bing, Google
|
| Latest Threads |
Unable to install Add-on
Forum: Comfort with Home Assistant
Last Post: Ingo
Yesterday, 11:14 AM
» Replies: 3
» Views: 1,254
|
Comfigurator 4.0.x
Forum: Comfigurator
Last Post: slychiu
Yesterday, 01:44 AM
» Replies: 3
» Views: 1,155
|
Inconsistent Behaviour
Forum: Comfort with Home Assistant
Last Post: bagushandhoko
02-06-2026, 04:54 AM
» Replies: 2
» Views: 138
|
Random Communication Fail...
Forum: Problems & Troubleshooting
Last Post: Howser
02-03-2026, 07:19 PM
» Replies: 21
» Views: 2,024
|
Comfort Server Manager & ...
Forum: Ethernet UCM/ETH03
Last Post: philcolley
01-23-2026, 04:35 PM
» Replies: 5
» Views: 593
|
Cancelling dial-outs afte...
Forum: Questions on Using Comfort
Last Post: slychiu
01-13-2026, 12:05 PM
» Replies: 6
» Views: 461
|
What SMTP servers do peop...
Forum: Ethernet UCM/ETH03
Last Post: Onix69
01-10-2026, 08:29 PM
» Replies: 6
» Views: 4,890
|
8.030 not upgrading
Forum: Firmware Upgrading Problems
Last Post: MCFH
01-07-2026, 10:16 AM
» Replies: 9
» Views: 1,560
|
Comfort GSM not answering...
Forum: GSM Module
Last Post: caravanboy
12-31-2025, 10:49 AM
» Replies: 21
» Views: 6,169
|
Comfort Forums has been m...
Forum: Forum/Website
Last Post: slychiu
12-31-2025, 02:18 AM
» Replies: 7
» Views: 1,843
|
|
|
| Home Assistant Setup on HAOS |
|
Posted by: Majik - 08-13-2025, 10:23 AM - Forum: Comfort with Home Assistant
- Replies (20)
|
 |
I'm documenting this because, during the installation, I came across a couple of minor issues, and this may be helpful for other people.
The background to this:
I've had a HAOS (Home Assistant Operating System) install running on a Linux VM for a little while with a number of integrations already.
I have a UCM/Pi running the standard UCMPI_OS install, and was, originally, considering installing HA on that, but the documented way to do that is using the Docker image, which has restrictions (no addons) which make it a deal-breaker.
I also looked at the options for modifying UCMPI_OS to run HA directly, perhaps extracting the Cytech Node Red components and running these within Node Red installed as an add-on within HA, but that looked too complex. Also, the UCM/PI connects to Comfort with a local serial interface, and Comfort2MQTT expects a network port.
So, whilst I'm hopeful there may be a future UCM/PI setup that is nicely bundled with HA, I abandoned that for the time being.
So I decided to install onto my existing HAOS system which, I suspect for some existing HA users, may be something they want to do. I don't know how different the standard Linux HAOS is from the Raspberry Pi version, but these are some notes.
Firstly, I hit a minor problem with the broker credentials. The instructions say:
slychiu Wrote: Press the Configuration Tab on top to go to the Options. Enter an MQTT Borker User and password that you choose.
That's cool, but the instructions seem to provide no information about needing to configure the Mosquitto Broker with those credentials, so I ended up with Comfort2MQTT not being able to connect to the broker (errors in the logs).
After a bit of scrabbling around (as the Mosquitto Broker docs aren't that helpful on the subject) I worked out how to configure this:
The format isn't clear from the docs, but it's this:
Code: - username: <username>
password: <password>
After this, it all connected fine. However, I couldn't work out how to upload my cclx file, as the file editor didn't show the addon_configs directory. It appears that, on my installation, the File Editor add-on is restricted to the /root/homeassistant directory, and the addon_configs directory is one level higher than that.
So, in the end I had to use the Terminal & SSH add-on (which I already had installed) and used sftp to upload the CCLX.
Later on, I realised there's a configuration option in the File Editor add-on "Enforce Basepath" which (as per the docs) "If set to `true`, access is limited to files within the `/config` directory.". Unsetting this allows me to navigate to the addon_config directory.
Then I moved onto the configuration.yaml. This is what I configured:
Code: mqtt:
alarm_control_panel:
- name: Comfort Alarm
unique_id: "comfort2_alarm_0fee8e" # E.G. Use last six digits of UCM/Eth03 MAC address to make it unique
code_arm_required: false
qos: 2
supported_features:
- arm_home
- arm_away
- arm_night
# - arm_vacation
- arm_custom_bypass
state_topic: "comfort2mqtt/alarm"
command_topic: "comfort2mqtt/alarm/set"
availability_topic: "comfort2mqtt/alarm/online"
payload_available: 1
payload_not_available: 0
code: "1234" # onscreen keypad Code can be different from Comfort\'s.
# This code is for the onscreen Keypad to Disarm, while the Comfort code in Comfort2MQTT
# configuration is to login to Comfort itself.
# This onscreen keypad code is used in the alarm Keypad to disarm Comfort. It is not the
# Comfort user code, although both can be set to the same code. When you enter the
# onscreen keypad code in the alarm Keypad to disarm, Comfort2MTT will disarm the
# security by using the saved user code.
# Secrets can be used EG. "code: !secret comfort_pin
sensor:
- name: Alarm Mode
unique_id: "comfort2_alarm_mode"
availability_topic: "comfort2mqtt/alarm/online"
state_topic: "comfort2mqtt/alarm"
payload_available: "1"
payload_not_available: "0"
- name: Alarm Message
unique_id: "comfort2_alarm_message"
state_topic: "comfort2mqtt/alarm/message"
availability_topic: "comfort2mqtt/alarm/online"
payload_available: "1"
payload_not_available: "0"
This is nearly an exact copy of the configuration from the instructions, but I found the inline instructions a bit difficult to use as it included additional escape characters which I had to edit out, and copying/pasting it into the file editor messed up the formatting, which needed correction. I'm hoping that using the code block here makes the formatting easier to read and more reliable for copy/pasting.
@slychiu would it be possible to update the instructions to use the code block for better formatting of the configuration.yaml items?
The item "arm_vacation" seems to be commented out, and I'm not clear why.
Then I moved onto adding zones. Again, following the instructions, I added this to my configuration.yaml:
Code: binary_sensor:
- name: Front Door
unique_id: "comfort2_input1"
state_topic: "comfort2mqtt/input1"
availability_topic: "comfort2mqtt/alarm/online"
value_template: '{{ value_json.State }}'
json_attributes_topic: "comfort2mqtt/input1"
json_attributes_template: '{{ value_json | tojson }}'
payload_on: "1"
payload_off: "0"
payload_available: "1"
payload_not_available: "0"
device_class: door
- name: Hall PIR
unique_id: \"comfort2_input2\"
state_topic: \"comfort2mqtt/input2\"
availability_topic: \"comfort2mqtt/alarm/online\"
value_template: \'{{ value_json.State }}\'
json_attributes_topic: \"comfort2mqtt/input2\"
json_attributes_template: \'{{ value_json | tojson }}\'
payload_on: \"1\"
payload_off: \"0\"
payload_available: \"1\"
payload_not_available: \"0\"
device_class: motion
(Again, mainly posting these for a copy/paste reference)
After a reload, these zones show up in the entities under the MQTT Integration, and under "Binary sensor" in the Overview Dashboard. To reload, I selected "Manually configured MQTT entities" on the Developer tools page.
An interesting point was, I configured one of the binary sensors incorrectly (due to escape chars in the cut/paste) and, after I corrected it, HA still had the original entity as well as the corrected one. I had to manually delete the entity. Maybe a full restart of HA would have cleared this as well, but be aware that this might occur.
That is my adventure to date, and I hope some of this is useful to others. If I come across any other "gotchas" or points of note, I will update.
Cheers,
Keith
|
|
|
| Home Assistant addon 1.5.0 crashes soon after startup |
|
Posted by: Jon798 - 08-03-2025, 07:22 AM - Forum: Comfort with Home Assistant
- Replies (18)
|
|
Hi,
System was running as expected with addon 1.4.3. Upgraded to v1.5.0 and now the addon crashes soon after startup. Debug log here:
Code: [08:08:08] WARNING: [33mTLS encryption option disabled.[0m
[08:08:08] INFO: [32mStarting Comfort to MQTT...[0m
2025-08-03 08:08:08 DEBUG Starting new HTTP connection (1): supervisor:80
2025-08-03 08:08:08 DEBUG http://supervisor:80 "GET /addons/self/info HTTP/1.1" 200 10392
2025-08-03 08:08:08 INFO Importing the add-on configuration options
2025-08-03 08:08:08 INFO Completed importing addon configuration options
2025-08-03 08:08:08 DEBUG The following variable values were passed through via Home Assistant
2025-08-03 08:08:08 DEBUG MQTT_USER = ComfortAddon
2025-08-03 08:08:08 DEBUG MQTT_PASSWORD = ******
2025-08-03 08:08:08 DEBUG MQTT_SERVER = 172.30.33.0
2025-08-03 08:08:08 DEBUG MQTT_PROTOCOL = TCP/1883 (Unsecure)
2025-08-03 08:08:08 DEBUG COMFORT_ADDRESS = 192.168.4.205
2025-08-03 08:08:08 DEBUG COMFORT_PORT = 1001
2025-08-03 08:08:08 DEBUG COMFORT_LOGIN_ID = ******
2025-08-03 08:08:08 DEBUG COMFORT_CCLX_FILE = comfigurator.cclx
2025-08-03 08:08:08 DEBUG COMFORT_BATTERY_STATUS_ID = 0
2025-08-03 08:08:08 DEBUG MQTT_CA_CERT = ca.crt
2025-08-03 08:08:08 DEBUG MQTT_CLIENT_CERT = client.crt
2025-08-03 08:08:08 DEBUG MQTT_CLIENT_KEY = client.key
2025-08-03 08:08:08 DEBUG MQTT_LOG_LEVEL = DEBUG
2025-08-03 08:08:08 DEBUG COMFORT_TIME= True
2025-08-03 08:08:08 WARNING MQTT Transport Layer Security disabled.
2025-08-03 08:08:08 INFO Comfigurator (CCLX) File detected, 248467 Bytes
2025-08-03 08:08:08 INFO Connecting to Comfort (192.168.4.205) on port 1001
2025-08-03 08:08:09 INFO MQTT Broker Connection Success
2025-08-03 08:08:09 DEBUG Subscribed to 8 Zone Outputs
2025-08-03 08:08:09 DEBUG Subscribed to 16 Zone Inputs
2025-08-03 08:08:09 DEBUG Not Subscribed to any RIO Inputs
2025-08-03 08:08:09 DEBUG Not Subscribed to any RIO Outputs
2025-08-03 08:08:09 DEBUG Subscribed to 254 Flags
2025-08-03 08:08:09 DEBUG Subscribed to 32 Sensors
2025-08-03 08:08:09 DEBUG Subscribed to 255 Counters
2025-08-03 08:08:09 DEBUG Not Subscribed to any Responses
2025-08-03 08:08:09 DEBUG Synchronizing Comfort Data...
2025-08-03 08:08:09 DEBUG Synchronization Done.
2025-08-03 08:08:19 ERROR Comfort connection error during recv: [Errno 104] Connection reset by peer
2025-08-03 08:08:19 ERROR Comfort Socket Error [Errno 104] Connection reset by peer
2025-08-03 08:08:19 ERROR Lost connection to Comfort, reconnecting...
2025-08-03 08:08:29 INFO Connecting to Comfort (192.168.4.205) on port 1001
2025-08-03 08:08:29 DEBUG LU04
2025-08-03 08:08:29 INFO Comfort Login Ok - User 4
2025-08-03 08:08:30 INFO Setting Comfort Date/Time
2025-08-03 08:08:33 DEBUG OK
2025-08-03 08:08:33 DEBUG b?00000000000000000000000000
2025-08-03 08:08:33 DEBUG Zones Bypassed: 0
2025-08-03 08:08:33 DEBUG V?FE080D22400100
2025-08-03 08:08:35 INFO Comfort II ULTRA detected (Supported Firmware 8.013)
2025-08-03 08:08:35 DEBUG EL11F1FFFFFFFF
2025-08-03 08:08:35 DEBUG 1 Installed SEM(s) detected
2025-08-03 08:08:35 DEBUG Hardware Model CM9000-ULT
2025-08-03 08:08:36 DEBUG DL7FF9040001010082
2025-08-03 08:08:36 DEBUG SN0101010000
2025-08-03 08:08:36 INFO Refresh Key: 01010000
2025-08-03 08:08:36 INFO Serial Number: Invalid
2025-08-03 08:08:37 DEBUG M?0004
2025-08-03 08:08:37 INFO Security Off
2025-08-03 08:08:37 DEBUG Z?0005
2025-08-03 08:08:37 DEBUG Max. Reported Zones/Inputs: 16
2025-08-03 08:08:37 DEBUG Y?0000
2025-08-03 08:08:37 DEBUG Max. Reported Outputs: 16
2025-08-03 08:08:37 DEBUG f?00FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
2025-08-03 08:08:40 DEBUG S?00
2025-08-03 08:08:40 DEBUG a?000000000000000000
2025-08-03 08:08:40 DEBUG r?0100100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:40 DEBUG r?0110100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:40 DEBUG r?000010FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
2025-08-03 08:08:40 DEBUG r?001010FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
2025-08-03 08:08:41 DEBUG r?0020100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:41 DEBUG r?0030100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:41 DEBUG r?0040100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:41 DEBUG r?0050100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:41 DEBUG r?0060100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:41 DEBUG r?0070100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:42 DEBUG r?0080100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:42 DEBUG r?0090100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:42 DEBUG r?00A0100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:42 DEBUG r?00B0100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:42 DEBUG r?00C0100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:42 DEBUG r?00D0100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:42 DEBUG r?00E0100000000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:43 DEBUG r?00F00F000000000000000000000000000000000000000000000000000000000000
2025-08-03 08:08:49 DEBUG IP0201
2025-08-03 08:08:51 DEBUG IP0200
2025-08-03 08:08:51 DEBUG IP0501
2025-08-03 08:08:53 DEBUG IP0500
2025-08-03 08:09:18 ERROR Error sending command
Traceback (most recent call last):
File "/comfort2/comfort2.py", line 1514, in readlines
data = self.comfortsock.recv(recv_buffer).decode()
~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
TimeoutError: [Errno 110] Operation timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/comfort2/comfort2.py", line 3256, in <module>
mqttc.run()
~~~~~~~~~^^
File "/comfort2/comfort2.py", line 2584, in run
for line in self.readlines():
~~~~~~~~~~~~~~^^
File "/comfort2/comfort2.py", line 1534, in readlines
self._send_keepalive_and_check() # Send keepalive and check socket status
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/comfort2/comfort2.py", line 1492, in _send_keepalive_and_check
self.comfortsock.settimeout(original_timeout)
^^^^^^^^^^^^^^^^
UnboundLocalError: cannot access local variable 'original_timeout' where it is not associated with a value
[07:09:19] WARNING: [33mHalt add-on with exit code 1[0m
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Not sure what to try to resolve this? Rolling back to v1.4.3 has it all working again.
Thanks in advance for any help.
Jon.
|
|
|
|
| ETH03 keeps going offline |
|
Posted by: Krobar - 08-01-2025, 10:39 AM - Forum: Ethernet UCM/ETH03
- Replies (9)
|
|
I have to disconnect and reconnect for it to re-appear on the network. The UCM/General with ETH03 is always fine. The UCM/Universal with Eth03 after 1-10 days just disappears (Both via IP and the search function in Comfigurator). Have purchased both a new UCM universal card and ETH03 from Laser and tried swapping the cable but the issue continues. Can anyone help with troubleshooting further or a potential fix?
|
|
|
|
| Seller finding |
|
Posted by: emabonacchi - 07-27-2025, 02:36 PM - Forum: Forum/Website
- No Replies
|
|
Hello and first of all, scuse me for my bad english.
I am a Cytech customer from about 15 years and now i need to buy two new Control panels but i can not find a seller. Can someone show me where to buy?
I live in Italy but i can buy from any suggested seller.
Thank you.
|
|
|
|
| Migrate from ETH02 to ETH03 |
|
Posted by: darnold - 07-07-2025, 01:15 PM - Forum: Ethernet UCM/ETH03
- Replies (3)
|
|
I recently received an ETH03 module to replace my existing ETH02 module. A couple of questions:
1) Can I simply install the ETH03 module on the existing UCM board that currently hosts the ETH02 module?
2) Since I use the ETH02 board to access the system via Configurator is there a way to upgrade it over the network or do I need to connect to the Comfort alarm via a serial connection in order to configure the ETH03 module?
Thanks.
|
|
|
|
|
