<![CDATA[Comfort Automation/ Security System Forums - Comfort with Home Assistant]]> https://www.comfortforums.com/ Fri, 11 Sep 2026 11:35:00 +0000 MyBB <![CDATA[Moving from Alfawerks to Comfort2MQTT]]> https://www.comfortforums.com/thread-5872.html Fri, 05 Jun 2026 07:08:48 -0400 DavidJ]]> https://www.comfortforums.com/thread-5872.html 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.]]> 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.]]> <![CDATA[MQTT to Comfort]]> https://www.comfortforums.com/thread-5869.html Wed, 03 Jun 2026 09:16:40 -0400 bmistry3]]> https://www.comfortforums.com/thread-5869.html
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]]>
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]]> <![CDATA[UCMA/Pi for Home Assistant]]> https://www.comfortforums.com/thread-5859.html Sun, 17 May 2026 02:57:20 -0400 slychiu]]> https://www.comfortforums.com/thread-5859.html



This includes a Raspberry Pi CM4 Compute module so there is no need for an external Raspberry device
The configuration is simple as it comes with a preconfigured Micro SD card 
You can upload the CCLX file using the Comfort Add-on's Web UI,a nd the zones and Outputs are auto-dscovered. No need to edit yaml files excedpt for advanced applications

Notifcations to Mobile  and Encrypted remote access are easily implemented

See the website at https://www.cytech.biz/brochure/UCMA-Pi.html
Instructions in the Comfort Forums here: http://www.comfortforums.com/thread-5857.html based onthe manual

The manual download link is https://cytech.biz/download_files.php?item_id=1520 

The Cytech Comfort MQTT add-on was based on thh work by koochyrat and Ingo, and it remain open-sourced, with the repository  at https://github.com/cytechtech/ucmpi4]]>



This includes a Raspberry Pi CM4 Compute module so there is no need for an external Raspberry device
The configuration is simple as it comes with a preconfigured Micro SD card 
You can upload the CCLX file using the Comfort Add-on's Web UI,a nd the zones and Outputs are auto-dscovered. No need to edit yaml files excedpt for advanced applications

Notifcations to Mobile  and Encrypted remote access are easily implemented

See the website at https://www.cytech.biz/brochure/UCMA-Pi.html
Instructions in the Comfort Forums here: http://www.comfortforums.com/thread-5857.html based onthe manual

The manual download link is https://cytech.biz/download_files.php?item_id=1520 

The Cytech Comfort MQTT add-on was based on thh work by koochyrat and Ingo, and it remain open-sourced, with the repository  at https://github.com/cytechtech/ucmpi4]]> <![CDATA[Cannot find folder to copy comfort file]]> https://www.comfortforums.com/thread-5855.html Tue, 12 May 2026 13:33:07 -0400 bmistry3]]> https://www.comfortforums.com/thread-5855.html
In the instructions it says "Comfort configuration File (.cclx) file to be used for object enrichment EG. Zone Names etc. Place this file in the Home Assistant /addon_configs/ folder using the File Editor. is a folger with the name which includes comfort2mqtt."

On my HAOS which installed on a Proxmox VM, I cannot find the HomeAssistant/addon_configs folder ?

Can someone help please ?]]>
In the instructions it says "Comfort configuration File (.cclx) file to be used for object enrichment EG. Zone Names etc. Place this file in the Home Assistant /addon_configs/ folder using the File Editor. is a folger with the name which includes comfort2mqtt."

On my HAOS which installed on a Proxmox VM, I cannot find the HomeAssistant/addon_configs folder ?

Can someone help please ?]]> <![CDATA[Moving from Alfawerks to Comfort2MQTT]]> https://www.comfortforums.com/thread-5835.html Fri, 27 Mar 2026 06:14:07 -0400 DavidJ]]> https://www.comfortforums.com/thread-5835.html I therefore wondered what the most practical approach in moving would be. Can I Simply turn off Alfawerks - I assume just unplugging the ethernet is enough? and can I therefore use the one existing UCM to do both the very occasional programming, obviously stopping the comfort2mqtt in the process and use this for comfort2mqtt? Or can I repurpose the Alphawerk module or is the appropriate course of action, whch I am trying to avoid, to remove the Alphawerk module and replace with a new UCM?
Thanks]]> I therefore wondered what the most practical approach in moving would be. Can I Simply turn off Alfawerks - I assume just unplugging the ethernet is enough? and can I therefore use the one existing UCM to do both the very occasional programming, obviously stopping the comfort2mqtt in the process and use this for comfort2mqtt? Or can I repurpose the Alphawerk module or is the appropriate course of action, whch I am trying to avoid, to remove the Alphawerk module and replace with a new UCM?
Thanks]]> <![CDATA[HA using UCM UCM/ETH02 (PC01-069A module)]]> https://www.comfortforums.com/thread-5828.html Mon, 23 Feb 2026 15:20:54 -0500 mindi65]]> https://www.comfortforums.com/thread-5828.html I'm trying to integrate my Cytech Comfort Ultra 2 alarm system with Home Assistant using the Comfort to MQTT add-on.
My setup:

Alarm system: Cytech Comfort Ultra 2
Communication module: UCM/ETH02 (UCM PC01-069A LAN board with Tibo NetModule)
IP address: 192.168.1.230:1001
Home Assistant: Running on QNAP NAS
Add-on: Comfort to MQTT (successfully connects to UCM and MQTT broker)

Problem:
The add-on connects successfully to both Comfort UCM and MQTT broker, but shows this error in the logs:
Illegal Comfigurator CCLX file detected, no enrichment will be loaded.
What I've done:

Exported .cclx file from Comfort Configurator software
Uploaded it to /config/comfort2mqtt/ directory
Configured the file path in add-on settings
Restarted the add-on

The add-on finds the file but rejects it as "illegal".
Questions:
What CCLX file format/version does Comfort to MQTT require?
Are there specific export settings I need to use in Comfort Configurator?
Will the integration work without the CCLX file (with default entity names)?

Current behavior:

Connection to UCM: ✅ Working
Connection to MQTT: ✅ Working
CCLX file enrichment: ❌ "Illegal file" error

Any help would be appreciated!

Is it good idea to continue it using UCM/ETH02 ?  Dodgy

BR//Mindaugas]]> I'm trying to integrate my Cytech Comfort Ultra 2 alarm system with Home Assistant using the Comfort to MQTT add-on.
My setup:

Alarm system: Cytech Comfort Ultra 2
Communication module: UCM/ETH02 (UCM PC01-069A LAN board with Tibo NetModule)
IP address: 192.168.1.230:1001
Home Assistant: Running on QNAP NAS
Add-on: Comfort to MQTT (successfully connects to UCM and MQTT broker)

Problem:
The add-on connects successfully to both Comfort UCM and MQTT broker, but shows this error in the logs:
Illegal Comfigurator CCLX file detected, no enrichment will be loaded.
What I've done:

Exported .cclx file from Comfort Configurator software
Uploaded it to /config/comfort2mqtt/ directory
Configured the file path in add-on settings
Restarted the add-on

The add-on finds the file but rejects it as "illegal".
Questions:
What CCLX file format/version does Comfort to MQTT require?
Are there specific export settings I need to use in Comfort Configurator?
Will the integration work without the CCLX file (with default entity names)?

Current behavior:

Connection to UCM: ✅ Working
Connection to MQTT: ✅ Working
CCLX file enrichment: ❌ "Illegal file" error

Any help would be appreciated!

Is it good idea to continue it using UCM/ETH02 ?  Dodgy

BR//Mindaugas]]> <![CDATA[Inconsistent Behaviour]]> https://www.comfortforums.com/thread-5826.html Wed, 04 Feb 2026 04:56:59 -0500 bagushandhoko]]> https://www.comfortforums.com/thread-5826.html
.jpeg   WhatsApp Image 2026-02-04 at 16.59.24.jpeg (Size: 51.56 KB / Downloads: 13) ]]>
.jpeg   WhatsApp Image 2026-02-04 at 16.59.24.jpeg (Size: 51.56 KB / Downloads: 13) ]]> <![CDATA[comfort2mqtt/alarm/message]]> https://www.comfortforums.com/thread-5818.html Tue, 04 Nov 2025 12:54:57 -0500 srooks]]> https://www.comfortforums.com/thread-5818.html

.png   rse-dev-env.png (Size: 44.85 KB / Downloads: 23) ]]>

.png   rse-dev-env.png (Size: 44.85 KB / Downloads: 23) ]]> <![CDATA[initial status]]> https://www.comfortforums.com/thread-5817.html Tue, 04 Nov 2025 06:11:41 -0500 srooks]]> https://www.comfortforums.com/thread-5817.html comfort2mqtt/alarm/refresh) .. which is useful when HA reloads the configuration.  

Is there a way to get the zones / counters / flags refreshed too .. other than restarting the comfort mqtt add-on ?

I guess another way is to default sensors (smoke, fire) to off state .. mine are appearing 'unknown' .. need to research how to do this !]]> comfort2mqtt/alarm/refresh) .. which is useful when HA reloads the configuration.  

Is there a way to get the zones / counters / flags refreshed too .. other than restarting the comfort mqtt add-on ?

I guess another way is to default sensors (smoke, fire) to off state .. mine are appearing 'unknown' .. need to research how to do this !]]> <![CDATA[Bypass an input from Home Assitant]]> https://www.comfortforums.com/thread-5815.html Wed, 29 Oct 2025 11:55:29 -0400 Howser]]> https://www.comfortforums.com/thread-5815.html <![CDATA[Node red]]> https://www.comfortforums.com/thread-5813.html Tue, 28 Oct 2025 12:48:51 -0400 111rdw]]> https://www.comfortforums.com/thread-5813.html <![CDATA[Comfort2MQTT and UCM/PI]]> https://www.comfortforums.com/thread-5659.html Mon, 25 Aug 2025 04:26:16 -0400 bmistry3]]> https://www.comfortforums.com/thread-5659.html
If one already has the UCMPI running and using Node Red and talking to HA, what are the advantages of removing it and moving to Comfort2MQTT

I assume biggest advantage is you remove the UCMPI hardwar from the equation

Thanks
Bhupendra]]>
If one already has the UCMPI running and using Node Red and talking to HA, what are the advantages of removing it and moving to Comfort2MQTT

I assume biggest advantage is you remove the UCMPI hardwar from the equation

Thanks
Bhupendra]]> <![CDATA[Home Assistant Setup on HAOS]]> https://www.comfortforums.com/thread-5658.html Wed, 13 Aug 2025 06:23:44 -0400 Majik]]> https://www.comfortforums.com/thread-5658.html
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:

.png   comfort2mqtt-1.png (Size: 42.65 KB / Downloads: 123)

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]]>
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:

.png   comfort2mqtt-1.png (Size: 42.65 KB / Downloads: 123)

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]]> <![CDATA[Home Assistant addon 1.5.0 crashes soon after startup]]> https://www.comfortforums.com/thread-5656.html Sun, 03 Aug 2025 03:22:05 -0400 Jon798]]> https://www.comfortforums.com/thread-5656.html
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: TLS encryption option disabled.
[08:08:08] INFO: Starting Comfort to MQTT...
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: Halt add-on with exit code 1
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.]]>
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: TLS encryption option disabled.
[08:08:08] INFO: Starting Comfort to MQTT...
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: Halt add-on with exit code 1
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.]]> <![CDATA[Voice Assistants]]> https://www.comfortforums.com/thread-5636.html Sat, 17 May 2025 23:41:18 -0400 ]]> https://www.comfortforums.com/thread-5636.html
The Getting Started Guide is here https://support.nabucasa.com/hc/en-us/ar...ew-Edition

one of the many Youtube videos on the setup and usage is https://www.youtube.com/watch?v=vceoL59pmkk

Setting up is easy. However note that if you use Duckdns with Lets Encrypt so that access locally and remotely by by https, Voice  PE will not work as it requires access by http for setup and operation.



You can select a preferred pipeline for processing the voice. This is done at setup but you can change it in Settings > Voice Assistants 



A good description of these options are in the video https://www.youtube.com/watch?v=zhlIaBG3Ldo at around  2 minutes.

My experience is the performance of the speech recognition is far better with Nabu Casa Cloud (which requires a subscription) compared to the local processing options, though this may be due to my accent - It may work better for european and american  voices. There may be ways to tune the speech recognition engines but I have not explored them. The Cloud processing option is also significantly faster than the local processing.





]]>
The Getting Started Guide is here https://support.nabucasa.com/hc/en-us/ar...ew-Edition

one of the many Youtube videos on the setup and usage is https://www.youtube.com/watch?v=vceoL59pmkk

Setting up is easy. However note that if you use Duckdns with Lets Encrypt so that access locally and remotely by by https, Voice  PE will not work as it requires access by http for setup and operation.



You can select a preferred pipeline for processing the voice. This is done at setup but you can change it in Settings > Voice Assistants 



A good description of these options are in the video https://www.youtube.com/watch?v=zhlIaBG3Ldo at around  2 minutes.

My experience is the performance of the speech recognition is far better with Nabu Casa Cloud (which requires a subscription) compared to the local processing options, though this may be due to my accent - It may work better for european and american  voices. There may be ways to tune the speech recognition engines but I have not explored them. The Cloud processing option is also significantly faster than the local processing.





]]>