So, I cannot even get past first base with the installation and setup of Comfort on Home Assistant. When I attempt to install the Comfort2Mqtt add-on I receive the following error:
2025-01-30 12:53:30.356 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /store/repositories - Cmd(\'git\') failed due to: exit code(128) cmdline: git clone -v --recursive --depth=1 --shallow-submodules --
http://github.com/djagerif/comfort2mqtt /data/addons/git/7bea2ab5 stderr: \'Cloning into \'/data/addons/git/7bea2ab5\'...fatal: protocol \' http\' is not supported[code]Having tried to troubleshoot this I am at a loss as to why I can\'t install the add-on.
I have the Alphawerks (old Home Assistant) still in place. Although I was previously unably to get Comfort2MQTT running alongside Alphawerks yesterday I managed it using the original UCM that would otherwise connect to Comfigurator. Given I seldom use Comfigurator and am merely trying to test the viability of moving away from Alphawerks I assume this is OK. So now effectively I have two systems one old (Alphawerks) and one new (comfort2Mqtt).
All basics appear to be working fine there I have not used UCM/Eth03 but have found the relevant zones through MQTT and setup just fine.
My question is around alarm panel and bypass, I believe the setup described in previous pages as folllows:
The following should be added to the file under the default entries:
mqtt:
alarm_control_panel:
- name: Comfort Alarm
unique_id: \"comfort2_alarm_a46ee0\" # 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
Differs from mine as below:
- name: "Comfort Alarm NEW"
state_topic: "comfort2mqtt/alarm"
command_topic: "comfort2mqtt/alarm/set"
value_template: >
{% if value == '0' %}disarmed
{% elif value == '1' %}armed_away
{% elif value == 'day' %}armed_home
{% elif value == 'night' %}armed_night
{% else %}disarmed{% endif %}
code: "xxxx"
unique_id: comfort2mqtt_new_alarm
I appreciate that HA has gone through numerous iterations and setup may have changed. Whilst it kinda works it does not display state nor can I work out how to disarm (I have no button). And although I found a way around remote setting (with bypass) I did not manage to make the one suggested (with # sign) work.
What am I missing please?
For State you need a State topic as per the recommended example. Also add Availability so that HA know the system is Available or Unavailable.
I am unsure why you wouldn't want to use the example in the documentation, it works perfectly fine. You also need the separate '#' button configuration as the Home Assistant Alarm Control Panel has no concept of a # button, they only provide standard keypad keys.
(02-11-2026, 11:14 AM)Ingo Wrote: [ -> ]For State you need a State topic as per the recommended example. Also add Availability so that HA know the system is Available or Unavailable.
I am unsure why you wouldn't want to use the example in the documentation, it works perfectly fine. You also need the separate '#' button configuration as the Home Assistant Alarm Control Panel has no concept of a # button, they only provide standard keypad keys.
Ok I now have the following working:
- name: "Comfort Alarm NEW"
unique_id: comfort2mqtt_alarm
state_topic: "comfort2mqtt/alarm"
command_topic: "comfort2mqtt/alarm/set"
availability_topic: "comfort2mqtt/alarm/online"
payload_available: 1
payload_not_available: 0
qos: 2
code_arm_required: false
code: "****"
supported_features:
- arm_home
- arm_away
- arm_night
- arm_custom_bypass
For remote arm I have this:
show_name: true
show_icon: true
type: button
name: Arm Alarm Away
entity: input_boolean.remote_arm
icon: mdi
hield-lock
tap_action:
action: toggle
confirmation:
text: Are you sure you want to set the alarm?
show_state: true
Which is probably not necessary but seems to work.
My question is: This all now seems to work OK, I need to use it in conjunction with the Alpohaweks one until I have migrated, automations, etc over. At that point I can then remove Alphawerks and presumably use the UCM dedicated to the wonderful work of Comfort2Mqtt. Therefore in the meantime its sharing the port for Comfigurator (which I dont use) no idea if it does other stuff in the background?. Am I likely to come across any issues at this stage other than some self-created confusion? Thanks for all your work BTW.
Edit: I have just realised I am seeing regualar unavailable I assume this is related to use of the Alphawerks system and a clash, though they are using different ports?
Thanks. I cannot comment on your setup as the App has been designed and tested against a dedicated UCM/Eth03. I myself use port 1001 for the App and 1002 for the trusty ComfortClient application from way back.