Template trigger or Device Trigger? What is the better method

[123 (Taras)]

@dtrott

Are you even using MQTT “Action” events

• If we are talking about the the kind of trigger used in Didgeridrew’s example, where a State Trigger is monitoring a remote’s event entity (ostensibly created via Zigbee2MQTT version 2.0+) then the answer is yes.

• If we are talking about an MQTT Trigger listening to the remote’s MQTT topic, like in your example, then no.

@dtrott

I haven’t seen any reference to that in your previous posts in this thread.

I didn’t explicitly indicate which trigger type I use until you quoted me and suggested MQTT “action” events require significant more “setup” therefore not worth it for one or two buttons. Had you not quoted my post, I wouldn’t have replied with my clarification.

My reply was the first indication (in this thread) that I use that type of trigger for all of my remotes, regardless of how many buttons they have. Originally, I used a State Trigger with a remote’s now-deprecated sensor entity. In my experience, it was a fairly simple transition to the event entity.

I need the ability to detect consecutive identical button events (like a double-press of on) and some of the triggers shown above are not fit for this purpose. Depending on the OP’s needs, it may influence which trigger they should consider using.