Hi Claude, please see below.
My Paradox MQTT connection addon is standard, didn’t change anything on that except for Alarm host IP, and MQTT user/pass
In my configuration.yaml, I have the following:
alarm_control_panel: - platform: mqtt state_topic: "paradox/alarm/state/1" command_topic: "paradox/alarm/cmnd/1" payload_disarm: "DISARM" payload_arm_home: "ARM_HOME" payload_arm_away: "ARM_AWAY" qos: 1 name: "Control State Home" - platform: mqtt state_topic: "paradox/alarm/state/2" command_topic: "paradox/alarm/cmnd/2" payload_disarm: "DISARM" payload_arm_home: "ARM_HOME" payload_arm_away: "ARM_AWAY" qos: 1 name: "Control State Garage"
I’ve just had time to rebuild my HomeAssistant setup, and have encountered an issue where command_topic isn’t allowed to be in sensor format anymore, so I had to remove that.
So for the arm/disarm ‘sensor’, I have this in my sensors.yaml
- platform: mqtt state_topic: "paradox/alarm/state/1" qos: 1 name: "Alarm State Home" - platform: mqtt state_topic: "paradox/alarm/state/2" qos: 1 name: "Alarm State Garage"
And for the actual switch component (arm/disarm separate zones), that just works from the data in configuration.yaml. The command that does the switching is the command_topic line, so when you reference the entity it will bring it up for you.
And this is how I’ve got them referenced in my groups.yaml - cut down version so you can test if it works for you.
default_view: view: yes icon: mdi:home entities: - sensor.alarm_state_home - sensor.alarm_state_garage - group.Alarm Alarm: name: Alarm icon: mdi:alarm-light view: yes entities: - alarm_control_panel.control_state_home - alarm_control_panel.control_state_garage - sensor.alarm_state_home - sensor.alarm_state_garage
Tested and working on Home Assistant 0.87.1 with Paradox addon v5 running on HassOS 2.8 on a RPi 3B
Let me know if you have any more questions 