Consolidating FIVE Timed Events Into ONE!

[macromark]

I've been using the new Conditional Actions feature since the first beta was released and I've been slowly shrinking my event list as I find new ways to implement it. Today, I worked a bit on the office system (HomeTroller Plus) and the Lighting Events group with these results:


So we now have 9 core events instead of 21! One event in particular replaced 5 individual events that were all triggered based on different times. In that event, I replaced the individual triggers with a simple recurring trigger that fires every minute and checks the time. Here's what that looks like:



Now, obviously the resolution of this particular event is 1 minute. If you must fire events at precise times, this approach would not be your best option.

[TC1]

This is a verrrry interesting and novel approach to event consolidation. My only apprehension is using a recurring trigger to qualify a fixed point in time, ie, 5:25pm, etc.

Is there a possible edge case where the recurring trigger fires internally at say 5:25:59 and by the time an action conditional test fires, at the end of a long list, it's now 5:26?

[macromark]

This is a verrrry interesting and novel approach to event consolidation. My only apprehension is using a recurring trigger to qualify a fixed point in time, ie, 5:25pm, etc.

Is there a possible edge case where the recurring trigger fires internally at say 5:25:59 and by the time an action conditional test fires, at the end of a long list, it's now 5:26?

Ok, had to research this... When the recurring trigger fires, it takes a timestamp of that moment and then uses that to evaluate the conditions below. So, even if the event fired at 5:25:59 and did not reach the action group below until 5:26, it would still execute that action group because it would be using the timestamp.

[TC1]

Either way, I love your example because hopefully it will inspire all of us who see it to think outside of the box with the new conditional capabilities. IMO, a lot of longtime HS users have been "programmed" into how to create events based on the older, limited capabilities. So many new possibilities now.

[macromark]

Either way, I love your example because hopefully it will inspire all of us who see it to think outside of the box with the new conditional capabilities. IMO, a lot of longtime HS users have been "programmed" into how to create events based on the older, limited capabilities. So many new possibilities now.

To clarify, there's no "either way" in this particular case. Even if the event fires at 5:25:59.99999999, it will definitely still execute this action group with the 5:25 condition no matter how long it takes to process all the other conditions and actions in between.

That said, you are 100% correct about the rest! My most used trigger now is This Device Just Had its Value Set of Changed. Just two weeks ago, I had never used that even once for any of my events. Now it's a staple for doing "parity" actions (turning stuff on and off, open or close, etc).



So... plenty to unlearn as the feature rolls out.

[rmasonjr]

To clarify, there's no "either way" in this particular case. Even if the event fires at 5:25:59.99999999, it will definitely still execute this action group with the 5:25 condition no matter how long it takes to process all the other conditions and actions in between.

That said, you are 100% correct about the rest! My most used trigger now is This Device Just Had its Value Set of Changed. Just two weeks ago, I had never used that even once for any of my events. Now it's a staple for doing "parity" actions (turning stuff on and off, open or close, etc).



So... plenty to unlearn as the feature rolls out.

whoa - ok - that is cool. Same here, I never used This Device Just Had its Value Set of Changed...

[rmasonjr]

very cool macromark

[randy]

That is how I did my 8-button Remotec remotes. There used to be an Event per scene value, now all in a single Event.with 24 action groups.



In our bedroom and living room, we each have a remote. I used to have an Event per scene value and each Event Triggered by one or the other remote. Now it is a single Event with Action Groups for each button press.

[TC1]

randy, on the 8-button Remotecs, have you ever successfully labeled them? From looking at pics, there seems to be enough "lip" around the button area perimeter to attach a transparent p-touch label using their smallest tape size. I'm probably going to order one to see what it's like.

[randy]

Yes, I use a P-touch with clear tape. I cleaned the remotes with alcohol. These labels have been on for several years. This is a bad example because the remote was very used before we put the labels on. Our others got the labels whn new.

[racerfern]

randy I have three remotecs all programmed the same. I tried making an EasyTrigger group (prior to these latest releases) so that if the value in any of the remotes in the group changed, etc.

The event would not work, I had to go back to If, or if,, or if > Then.

Thoughts? An EasyTrigger issue?

When I bought my Remotecs they came with a variety of pre-named labels for that 1/8" border around the buttons. I wish I could find the rest that I put somewhere.

[TC1]

Yes, I use a P-touch with clear tape. I cleaned the remotes with alcohol. These labels have been on for several years. This is a bad example because the remote was very used before we put the labels on. Our others got the labels whn new.

Bingo, I had basically the same idea. Great minds think alike. For the price, IMO these are perfect table top remotes where one can't run a charging wire for a tablet. Thanks!

[randy]

randy I have three remotecs all programmed the same. I tried making an EasyTrigger group (prior to these latest releases) so that if the value in any of the remotes in the group changed, etc.

The event would not work, I had to go back to If, or if,, or if > Then.

Thoughts? An EasyTrigger issue?

When I bought my Remotecs they came with a variety of pre-named labels for that 1/8" border around the buttons. I wish I could find the rest that I put somewhere.

First of all, there is no assurance any of the remotes changed, since they can be “set” without changing. In that regard Easy Trigger won’t work because it cannot Trigger on a “set” only a change. I just use a trigger for set or changed for multiple remotes. Here are two, you would just have three. I also use Conditional Actions, so there is an Action group for each value on each remote.



At the end of the Event I erase the Central Scene values on all remotes. You would do three. This is because when any remote is set every remote is evaluated. Since you are only looking at values for all remotes, any value still in any remote (even from yesterday) would be evaluated for its Action Group.

[pistacheL0]

Theoretically,

Coulld we use "if any device has been set or changed", and create a unique event for all our automation? "

[pistacheL0]

To clarify, there's no "either way" in this particular case. Even if the event fires at 5:25:59.99999999, it will definitely still execute this action group with the 5:25 condition no matter how long it takes to process all the other conditions and actions in between.

That said, you are 100% correct about the rest! My most used trigger now is This Device Just Had its Value Set of Changed. Just two weeks ago, I had never used that even once for any of my events. Now it's a staple for doing "parity" actions (turning stuff on and off, open or close, etc).



So... plenty to unlearn as the feature rolls out.

I think theses type of notions should be documented.

Also, it would be nice to have a centralized topic(or subforum) where people could exchange about this new creative option.