Alarmo - Template for ready_to_arm

I’m currently setting up an “alarm system” with Alarmo.

Ready to arm should be transmitted to KNX via a binary sensor so that I can display it on an MDT glass push button.

According to the Alarmo manual, there’s an event for this, and there’s also an example for creating a template. However, this fails due to my lack of knowledge.

I inserted the example into the configuration.yaml as follows:

template:
  - triggers:
      - trigger: event
        event_type: alarmo_ready_to_arm_modes_updated
        event_data: 
          entity_id: alarm_control_panel.wohnung
    binary_sensor:
      - name: "Alarmo Ready To Arm Away"
        state: '{{ trigger.event.data.armed_away }}'

The area “wohnung” and the entity alarm_control_panel.wohnung exists.

Now my two problems:

1st:
Behind “-triggers,” I see “Property triggers is not allowed” displayed in red.

2nd:
If everything works, will the binary sensor “Alarmo Ready To Arm Away” be created automatically? Or how can I change the state of an existing entity from the KNX integration?

Create an automation for this using knx.telegram trigger.

You can skip the binary_sensor (and Knx expose to send its state to Knx) by using the event in an automation and sending with the knx.send service.

Alternatively it may work to Knx expose the entity alarm_control_panel.wohnung using a value_template. But that’s more complex to get right imho.

Sorry, but i think you misunderstood my problem:

Forget KNX.

My Problem ist, that i want to generate (and toggle) a binary sensor within HA dependent of the event “alarmo_ready_to_arm_modes_updated”.

KNX then will be the next step.

Your yaml looks fine. Where exactly did you put it and where do you see this warning?

I put it in configuration.yaml by editing with Studio Code Server.

Screenshot (to see the warning in red):

The VSCode extension doesn’t do real HA validation. It has its own schema that may not be up to date with latest HA features. Real validation can be done in HA at developer tools → yaml

You’re right. Actually the entity is created.

But now the next problem: the entity doesn’t change it’s state - it remains “unknown”.

Tried to listen to the event with developer tools → no result, seems to be never fired.

Posted it in the developer’s thread.

Thanks anyway.

With actual release of v1.10.9 it works fine. The entity changes its state as expected.

Reason was, that the docs describes a feature that wasn’t yet implemented.