Difference between revisions of "WHO=0 - Scenarios"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
+ | ====What is a scenario?==== | ||
+ | A scenario is a list of simple commands, stored in a scenario device like '''F420''' (16 scenarios) or '''IR 3456''' (max. 20 scenarios). More and smarter scenarios can be stored in a scenario device like '''MH200''' or the newer model '''MH200N'''. These smart scenario devices support event- and time-driven scenarios, even with IF-THEN-ELSE clauses. | ||
+ | |||
+ | ====Examples==== | ||
+ | Scenarios are launched in a similar way like lighting commands: | ||
+ | <pre> | ||
+ | *0*5*89## launch scenario #5, connected to address 89 | ||
+ | *0*9*49#4#02## launch scenario #9, connected to address 40 on interface 2 | ||
+ | </pre> | ||
+ | |||
+ | Since a scenario is just a list of commands, they don't have a status and therefore you can't do a status request on a scenario. | ||
+ | |||
+ | ====Programming a scenario==== | ||
+ | |||
Revision as of 17:15, 21 November 2014
What is a scenario?
A scenario is a list of simple commands, stored in a scenario device like F420 (16 scenarios) or IR 3456 (max. 20 scenarios). More and smarter scenarios can be stored in a scenario device like MH200 or the newer model MH200N. These smart scenario devices support event- and time-driven scenarios, even with IF-THEN-ELSE clauses.
Examples
Scenarios are launched in a similar way like lighting commands:
*0*5*89## launch scenario #5, connected to address 89 *0*9*49#4#02## launch scenario #9, connected to address 40 on interface 2
Since a scenario is just a list of commands, they don't have a status and therefore you can't do a status request on a scenario.
Programming a scenario
WHO Table | WHO=1 - Lighting |