+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Software Applications (https://www.comfortforums.com/forum-4.html)
+--- Forum: Comfort with Home Assistant (https://www.comfortforums.com/forum-143.html)
+--- Thread: Comfort 2MQTT with Home assistant Raspbery Pi Questions and comments (/thread-5579.html)
- slychiu - 12-04-2024
This topic is for questions and comments as the original posts are closed topics
- bs85 - 12-26-2024
How would you do a force arm away from an automation?
- Ingo - 12-26-2024
You can do it in two ways:
1. Using MQTT as the Automation Action or
2. Using the Alarm Control Panel Automation Action
/comfort2mqtt/alarm/set and use \'ARM_HOME\' and then send \'ARM_CUSTOM_BYPASS\' as this is the \'#\' character to force arm. The native Alarm Control Panel does not have a \'#\' character so I am using this function instead.
The second option is probably better, just select the Alarm Control Panel as the automation action and then Arm \'Home\' and arm \'Custom\' to get the same results.
- Ingo - 12-27-2024
Apologies, \"ARM_AWAY\" is Away Mode.
- bs85 - 12-27-2024
Thanks for thr reply.
Still can\'t get it to force arm i can see ARM_AWAY and then ARM_CUSTOM_BYPASS being sent in MQTTExplorer but the panel still counts down then get the arm failure
Comfort II Ultra 8.013
< ER00
< EX021E
< SM000140
< SM000140
< OK
< SM000140
< SM000140
< SM000140
< SM000140
< SM000140
< SM000140
< SM000140
< MD0001
< KL00010000
< AM0600
< KL02010000
< S?03
< DT2024122707360400
< AL040303080100
< SM000140
< SM000140
< cc00
< SM000140
< AM0D01
< KL00010000
< S?00
< DT2024122707362300
< AL140000830201
< AM0801
< KL00010000
< S?00
< DT2024122707362300
< AL110000140201
< MD0001
< SM000040
< KL00010000
< SM000140
< SM000000
- Ingo - 12-27-2024
I suspect it\'s unique to ARM_AWAY only. It probably waits for you to exit and is correctly bypassing any open zones but fails on entry/exit activation. I will have to think about this one as there is slightly different command that can be used for \'being at home\' and arming to AWAY mode, and one where you are \'not at home\' and arming to AWAY mode. In this mode it does not wait for an exit door to activate/deactivate.
Edit: I found a way via MQTT but the native Alarm Control interface of Home Assistant doesn\'t support arming to two different AWAY modes. You have to use MQTT. I will release an update soon. The command to send via MQTT is REM_ARM_AWAY for Remote Arm Away.
- bs85 - 12-28-2024
Thanks working now
- slychiu - 12-28-2024
How to write the mqtt for this?
alarm_control_panel:
- name: Remote Arm Away
unique id: \"comfort2_remote_arm_away\"
state_topic: \"comfort2mqtt/alarm\"
value_template: \'{{ value_json.State }}\'
command_topic: \"comfort2mqtt/input20/set\"
availability_topic: \"comfort2mqtt/alarm/online\"
json_attributes_topic: \"comfort2mqtt/alarm/set\"
json_attributes_template: \'{{ value_json | tojson }}\'
payload_on: \"REM_ARM_AWAY\"
payload_off: \"0\"
payload_available: \"1\"
payload_not_available: \"0\"
This causes error
- Ingo - 12-28-2024
I don\'t think you can do that. It\'s not a function of the \'alarm_control_panel\' native to Home Assistant as that keyword is not recognized by them. Then there is the \'#\' key that must be sent also.
See the DOCS in the latest release for a test example where I used a button to trigger an automation which in turn fires two MQTT messages to force arm in away mode.
- slychiu - 12-29-2024
Thanks Ingo. That works. I have removed the 2nd action Custom Bypass, as I can use the stand alone Custom bypass button if needed