Events in TipControl allow your IoT system to respond dynamically<\/strong> to changes in driver variables. Each event (except timer events) is tied to a specific variable located under Events are easiest to manage via the TipControl Designer<\/strong>:<\/p>\n\n\n\n Each event includes a Code Box<\/strong> where you define the actions to perform when the event fires. This is written in TipControl Language<\/strong>.<\/p>\n\n\n\n Want to see it in action? Download an example project from our website to explore how events work in real-world scenarios.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" \u26a1 TipControl Events: Reacting to Driver Variables Events in TipControl allow your IoT system to respond dynamically to changes in driver variables. Each event (except timer events) is tied to a specific variable located under drv.<drivername>.var…. Events are triggered when driver variables are updated or when the driver\u2019s update() function is manually called (though this is rarely necessary). \ud83d\udd27 Event […]<\/p>\n","protected":false},"author":4,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-872","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/tipcontrol.com\/index.php?rest_route=\/wp\/v2\/pages\/872","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tipcontrol.com\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tipcontrol.com\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tipcontrol.com\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/tipcontrol.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=872"}],"version-history":[{"count":7,"href":"https:\/\/tipcontrol.com\/index.php?rest_route=\/wp\/v2\/pages\/872\/revisions"}],"predecessor-version":[{"id":910,"href":"https:\/\/tipcontrol.com\/index.php?rest_route=\/wp\/v2\/pages\/872\/revisions\/910"}],"wp:attachment":[{"href":"https:\/\/tipcontrol.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=872"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}drv.<drivername>.var...<\/code>. Events are triggered when driver variables are updated or when the driver\u2019s update()<\/code> function is manually called (though this is rarely necessary).<\/p>\n\n\n\n\ud83d\udd27 Event Settings<\/h3>\n\n\n\n
\n
\ud83e\udde0 Supported Event Types<\/h3>\n\n\n\n
Type<\/th> Behavior<\/th><\/tr><\/thead> EQUAL<\/code><\/td>Fires once when variable equals value; resets if not equal.<\/td><\/tr> BELOW<\/code><\/td>Fires once when variable is below value; resets if equal or above.<\/td><\/tr> EQUALBELOW<\/code><\/td>Fires once when variable is below or equal; resets if above.<\/td><\/tr> ABOVE<\/code><\/td>Fires once when variable is above value; resets if equal or below.<\/td><\/tr> EQUALABOVE<\/code><\/td>Fires once when variable is above or equal; resets if below.<\/td><\/tr> WEQUAL<\/code><\/td>Fires on every update while variable equals value.<\/td><\/tr> WBELOW<\/code><\/td>Fires on every update while variable is below value.<\/td><\/tr> WEQUALBELOW<\/code><\/td>Fires on every update while variable is below or equal to value.<\/td><\/tr> WABOVE<\/code><\/td>Fires on every update while variable is above value.<\/td><\/tr> WEQUALABOVE<\/code><\/td>Fires on every update while variable is above or equal to value.<\/td><\/tr> CHANGE<\/code><\/td>Fires when variable changes by a specified amount (numeric only), for all other variable types on any change.<\/td><\/tr> TIMER<\/code><\/td>Fires every X milliseconds; variable is ignored.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n \ud83d\udee0\ufe0f Using Events in TipControl Designer<\/h2>\n\n\n\n
\n
\ud83d\udca1 Event Management<\/h3>\n\n\n\n
\n
\ud83e\uddec Event Coding in TipControl Language<\/h2>\n\n\n\n
\ud83e\udde0 Key Concepts<\/h3>\n\n\n\n
\n
me<\/code> refers to the driver the event is installed on. Example: If installed on drv.button<\/code>, me<\/code> is equivalent to drv.button<\/code>.<\/li>\n\n\n\nme<\/code> to write generalized code<\/strong> without hardcoding driver names.<\/li>\n\n\n\nreturn(false)<\/code>. Note:\u00a0me.event<\/code>Enabled(eventName,false) will\u00a0not<\/strong>\u00a0work for the event itself, even in a subsequantially called macro.<\/li>\n<\/ul>\n\n\n\n