markfrancisonly / concord2mqtt

Concord 4 security panel MQTT integration for Home Assistant
MIT License
2 stars 0 forks source link

Unable to Disarm #2

Open digitalconverg opened 2 years ago

digitalconverg commented 2 years ago

Arming from HASS works great. Cannot disarm. Set DirectDisarm to true. Tried all userids including 246 for system master. would appreciate configuration.yaml example for alarm_control_panel to pass remote code for disarm

alarm_control_panel:
   - platform: mqtt
     state_topic: "homeassistant/alarm_control_panel/panel_partition_1/state"
     command_topic: "homeassistant/alarm_control_panel/panel_partition_1/command"
    name: "Panel Partition 1"
     value_template: "{{ value_json.state }}"
     code: REMOTE_CODE
     command_template: "{ action: '{{ action }}', code: '{{ code }}'}"
     code_arm_required: false
     code_disarm_required: true
KewlGuyRox commented 2 years ago

can you please share your docker-compose.yml file. I can't get it to install without downloading the entire repo and executing it locally. Even then its giving me a few errros.

Can you provide your steps please What are you changing/updating.. path for appsettings.json...etc

digitalconverg commented 2 years ago

after reviewing the application, the REMOTE_CODE for MQTT is not used in disarming and anything after the DISARM command is ignored. If the DirectDisarm is set to true in appsettings.json the user code from the panel is used but only if the ACCESS CODE LOCK option is OFF which requires the installer programing code to set. Since I do not have the installer code, I cannot use the DirectDisarm method. When DirectDisarm is set to false, then the user code must be entered at the keypad which is not convenient. I have modified the Concord2Mqtt.cs to send the KeyfobDisarm instead of Key1 on disarm as a work-around.

Suggest a modification to either accept the REMOTE_CODE entered and passed by MQTT or to allow the user code to be configured in appsettings.json if the user code is not provided by the system