Hi,
Being very new here. I am happy I got the Aeotec Button to work.
I saw some things to get it working here, but I totaly did not get it.
So, I made it work to create three diferent automations for it.
1 for short press an other for double press and one for long press.
This seems a little strange and after geting more devises it wil get prety geotic I think. Is there a better way to configure it, that is not to hard to do?
A lot depends on personal taste and what is easy to combine in one automation. Personally I mostly name my automations on what happens, not on what triggers it. In other words, I care about what what you try to accomplish rather than what you do to make it happen.
So I might have an automation “Kitchen light on” with multiple triggers in it if there are multiple buttons (or other things) turning it on. Although it is not always that clear cut, because scenes are one script operating on multiple targets. But a scene is still the intended outcome, so not different in terms of naming logic. And sometimes I have multiple automations acting on the same target, often leading to names like “Do this when something happens”. That is mostly inspired by reducing the complexity of automations when there are many conditions involved.
I never have scripts named after buttons though, exactly because a button should do one clear cut thing, while that clear cut thing might happen for multiple reasons. Those are now easily grouped together, so it is easy to think about the behaviour of that particular light or other thing that is being controlled, such as a fan, heater or whatever.
The only downside is that I cannot easily see all the functions of a multi button device in one place. Luckily HA helps by listing automations with the device. So in the end that too is not that hard. Below is an example of a button device controlling multiple scenes (and you’d have to look in the automation too see which button triggers each automation):
