HMIP-WRC2 - SHORT & LONG PRESS

[itn3rd77]

Hi Markus,

yesterday I switched completely to the new integration and I am very happy so far. Thanks for all your efforts!

I just haven't figured out how I should handle the SHORT_PRESS and LONG_PRESS events e.g. on my HMIP-WRC2. The old integration had this special event-type homematic.keypress I used in the automations:

This is how the device looks in Home Assistant (virtual channels enabled):

And this one is from RaspberryMatic:

Thanks for your support.

Best regards
Ingo

[SukramJ]

Just select the device as trigger and then the trigger action.

[itn3rd77]

Thank you, exelent!

[eikowagenknecht]

For anyone looking for more details:

It is still handled with the homematic.keypress event. Just listen to that, then press the button and you see the exact events triggered ;-)

E.g.

hahomematic:

{
    "event_type": "homematic.keypress",
    "data": {
        "interface_id": "CCU3-HmIP-RF",
        "address": "001FDBE98A6CA2",
        "type": "press_long",
        "subtype": 1,
        "device_id": "589045dad0015bb76c01da3ac8b28478"
    },
    "origin": "LOCAL",
    "time_fired": "2022-01-12T12:13:27.028243+00:00",
    "context": {
        "id": "a7664f2170674351e9ac179fb4622da2",
        "parent_id": null,
        "user_id": null
    }
}

pyhomematic:

{
    "event_type": "homematic.keypress",
    "data": {
        "name": "EG.Flur Taster Bad (Gerät)",
        "param": "PRESS_LONG",
        "channel": 1
    },
    "origin": "LOCAL",
    "time_fired": "2022-01-12T12:13:27.037084+00:00",
    "context": {
        "id": "66fd1c5abf4032447e78c0e584156d2a",
        "parent_id": null,
        "user_id": null
    }
}

[SukramJ]

This integration uses device_triggers to make automations configurable via UI.
These values are used to match HA to HM

        "interface_id": "CCU3-HmIP-RF",
        "address": "001FDBE98A6CA2",
        "type": "press_long",
        "subtype": 1,

The HM Name is not good for referencing.

[ThomDietrich]

Via UI that makes sense. In yaml rules this is quite error-prone to maintain:

automation:
  - alias: Regel Badezimmer Lichtschalter lang
    trigger:
      - platform: event
        event_type: homematic.keypress
        event_data:
          address: 001FDBE98A6CA2
          type: press_long
    action:

Would it break your device_triggers if the additional field name was provided with the event? Being able to replace address by name would certainly be a huge improvement here.

[SukramJ]

Don't know. This must be checked.
Manual YAML automation feels like a huge step back.

[ThomDietrich]

Would appreciate if you could 👍

There is no best solution or step back. You have the dialog based way, many users prefer NodeRed, and many power users need the flexibility of yaml based configuration. Don't know about you but I maintain half a dozen instances with hundreds of automations. Not manageable via UI.

[ThomDietrich]

Was this ever resolved? Sorry, can't check atm
Thanks!