Events, flags, sensors and Drivers can be utilized to create if/then events. Events can be triggered off a certain time of day, or something that exists in the devices driver. For example, if the driver has a system event variable that says "when zone is turned on" you can trigger a macro, command or string of commands whenever that zone is turned on. Most drivers have system based events; some have extensive system based events.

With flags, you can set a flag to a Boolean value and then test that flag in order to perform a function. For example, if the TV_IS_ON flag = Y then don't wait 10 seconds to send an input. Pretty typical and common; URC calls this "variables".

With sensors, you can determine the power, video, audio and other states and base an action on that. For example, if you have an audio sensor hooked up to your SONOS CONNECT, you can have the processor turn on the receiver every time the sensor detects audio on the SONOS connect. This would allow you to use the SONOS app exclusively without using a remote control to turn on the receiver.

Certain utility drivers are written in order to test one or more flags, variables, driver output, etc. and base events based on that. They offer more comprehensive if/then and can take a combination of factors present and base a command or macro on that. For example, if the current weather temperature outside is < 32 and the current temperature inside is < 65 degrees, do THIS.

You can also base events on contact closure, voltage, and other ways with RTI's processors. There are MANY ways to create and if/then.

Hope this helps,
Vincent
Total Control Remotes LLC