Better to use "Choose" as an Action than add the "Triggered by". And add "Options" for each trigger ID.

@iambuschi

6 ай бұрын

Soo many ways.. Like it! :) Thx!

@HollyFredD

6 ай бұрын

I was about to comment to say the same thing. "Choose" allows multiples choices in a more organized and condensed approach. That's the way I do it.

@iambuschi

6 ай бұрын

Disadvantage is that you don't see anything in collapsed view.. I think both appraoches have their place.

@CamiloSperberg

6 ай бұрын

​@@iambuschiyou can add your own description which will then display in the collapsed view

@yearofthechris

3 ай бұрын

@@CamiloSperberg Great to know!

thank you for leaving in the troubleshooting. it's nice to see someone else getting frustrated with things not working also.

Nice. Try to "Change Mode" to "Queued" or "Parallel" and it will prevent the script from locking and ignoring the button commands.

@iambuschi

6 ай бұрын

Yes, you are right.. Would help with quick button presses. But my remote is just crap really.. Also single presses go missing often times.

Holy mother of all what is annoying, I had a naming scheme to organize my automations. Now I can reduce it tremendously. Thanks a bunch.

@iambuschi

6 ай бұрын

That is the emotion that made me do the video.. I was really struck once I realized this path exists :)

Wow .. this is good to know I didn't realize this is how to use trigger ids. Thanks for the info.

Thank you - I got it now too. It's really difficult to find the options in oter languages and I had to switch to English before I found the right options.

Thanks for this. The UI has changed a bit since you made this so its a little bit different now but essentially the same, I just had to search for the If Then and Triggered by options. I got rid of 4 automations today though using your info.

Great thanks I also missed this feature. With Automations I have just been using standardised naming at the start of each automation name for example Switch On, off, Warning, Notification, Alert and then using sort to give some structure. However the use of Trigger IDs is way better.

@iambuschi

6 ай бұрын

I was really excited when I realized this option exists.. Have been slowly migrating automations over during the last days.. What I really like is the option to fix changed entities in Yaml mode. Really a quality of life improvement..

Nice vid. I suppose when HA was started automation was around action, and that's how it is structured. Now we have devices with multiple buttons and we evolving to create automations around devices instead of single actions.

@iambuschi

6 ай бұрын

Glad you like it. True.. Have the feeling the automations section deserves an overhaul and more love (I am not yet in the latest version though).. Feels a bit neglected, when for me it is the most important part of HA.. Might be biased here :)

I been meaning to do this with my automations for a while but I keep forgetting. I've been using trigger ids with new automations, but I need to clean up old ones. For example, I have a ZooZ Zen34 switch which is a momentary rocker up/down switch, but it has events for short press up, short press down, long press up, long press down, double click up, double click down, 3x click up, 3x click down. And of course I have every one of those as a seperate automation lol. Trigger ids will heal a lot.

@iambuschi

6 ай бұрын

Yes! :-D

You could also use a HA blueprint for button automations. Allot quicker then doing it yourself and there is one out there for almost every remote!

@iambuschi

6 ай бұрын

To be honest, haven't played with blueprints really yet... Sounds like I should change that?

You need to update your HA instance, the whole sutomation screen got a revamp and now you can search for actions, conditions and whatnot. Takes some time getting used to it but it's way quicker to create an automation now.

@iambuschi

6 ай бұрын

Thx for the hint.. I am using Ha in Docker on a PI4 and somehow the last update cycle didn't reach those images (yet). Until now I was too lazy to dig into it. But now I am looking forward to the changes even more.. :)

A long time ago I made a folder and kept each type of automation, lights, alerts, heating, switches. This seems to have worked but this was years before Trigger IDs

@iambuschi

6 ай бұрын

Can you elaborate what you mean with folders?? Maybe I am still missing something..? :-)

@jamescrook99

6 ай бұрын

@@iambuschi so you can create folders in your config yaml location, and then have automations in the folder. I choose to break mine up into types. But 99% of mine are hand written, not using the web interface yo make them. I would post a link but KZread removes them. Have a google for "home assistant folder automactions configuration"

Home assistant was like a second job, I swapped back to Hue and the family is happy again. HA need to have much more friendly defaults for users who don't want to spend so much time at the computer.

@iambuschi

6 ай бұрын

I love the flexibility and possibility to push HA further and further using the endless integrations and plug-ins.. But at times it can be also time consuming, agrred.. I guess one need to find the right corner to stay happy taking all other constraints into account.. Sounds like you found it for you.. And that is all that counts.. :)