I think it would be helpful to consolidate rules if I can specify multiple triggers and do if statements based on which trigger started the automation.
For example, I have a Pico remote with 5 buttons. If I create a rule thats triggered by any of the buttons being pressed and then in the actions say "If button 1 pressed, do this, else if button 2 was pressed, do this. etc".
Same thing with a cloud end point automation I have, if I could specify multiple cloud end points and then run the actions based on which one triggered the automation, I could consolidate a lot of rules.
I'm not sure just what you mean by "helpful". You could do something like this, but imo it's the wrong direction to take. What you end up with is fewer rules (which are free to begin with), that are less efficient and more complex. If what you mean by helpful is that you then have fewer rules in your list of apps, that's not a great goal.
For multiple buttons, look at Button Controllers. Each button controller handles all of the buttons of a button device, and gives you all of the flexibility of RM actions for each.
So, to some extent it is possible, although I recommend not going that direction. Separate rules are the most efficient, easiest to understand, and easiest to maintain. Multiple triggers with IF-THEN-ELSE-IF... can lead to other problems. If any of these actions have delays, it would tend to blow up on you with multiple triggers causing simultaneous execution of the same rule (which doesn't work).
Thank you for the feedback. This is good advice. Is there a rule manager of some kind to organize the rules a little better? My goal was trying to trim down my number of rules so it's easier to manage and organize.
With that said, I think your advice is sound and will go in that direction.
No, there isn't such a thing right now. What many users do is use a naming convention to help keep rules organized. We are looking at further UI improvements to address this issue as well.
