Generate HA switches to "clear alarm memory" for EVO192 zones

[clau-bucur]

Alarm system

EVO192

I see that for HA switches to bypass the zones are auto generated (eg. zone_Name_bypass). Would it be possible to auto generate "clear alarm memory" switches also ?

[jpbarraca]

Probably it's possible but we do not know how to do it. Needs investigation

[clau-bucur]

I'd say similar to bypass switches. Here's a "clear alarm memory" switch I have created:

switch:
  - platform: mqtt
    name: Zone Atelier Clean Alarm Memory
    command_topic: paradox/control/zones/Atelier
    payload_off: clear_alarm_memory
    state_topic: paradox/states/zones/Atelier/generated_alarm
    state_on: true
    state_off: false

[clau-bucur]

Similarly, the keyswitch triggered sensors are missing from auto-generation:

binary_sensor:
  - platform: mqtt
    state_topic: paradox/states/key-switch/1/triggered
    name: Paradox Keyswitch Pod
    payload_on: true
    payload_off: false

[yozik04]

@clau-bucur I assume you have EVO. EVO is the only where it is currently implemented. Please update your first post with this data.

@jpbarraca If you will find time to implement alarm clearing for SP/MG, then we can expose this switch in homeassistant auto discovery.

[yozik04]

@clau-bucur Regarding keyswitch. There is no live event for it so please explain us how you use it. It updates it's state every 10 seconds (by default) which is not great for most of the uses.

[yozik04]

If we expose something to homeassistant then it should work properly, otherwise we will be flooded with issues.

[clau-bucur]

Indeed, I forgot about the 10 second pooling.

I have 3 keyswitches configured as follows:

I set the pooling interval to 2 seconds, so that I receive the changed states more quickly. Whenever a keyswitch is pressed, my binary_sensors change state and I can run different automations based on that. The momentary keyswitches need to be pressed for about 3 seconds before the panel sends the state change. The maintained keyswitches report pretty fast and they hold the state until the switch is toggled off.

So, the maintained keyswitches are a good match even for the default 10-second pooling interval (you'll get the state change a bit late, though).

I have these 3 HA binary sensors up and running for a while. I have not seen any issues.

[w1tw0lf]

I'd say similar to bypass switches. Here's a "clear alarm memory" switch I have created:

switch:
  - platform: mqtt
    name: Zone Atelier Clean Alarm Memory
    command_topic: paradox/control/zones/Atelier
    payload_off: clear_alarm_memory
    state_topic: paradox/states/zones/Atelier/generated_alarm
    state_on: true
    state_off: false

Sorry for responding to an old topic, trying to recreate this. The switch creates but nothing happens when switching it off. Any suggestions ?