Difference between revisions of "WHO=0 - Scenarios"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
====Programming a scenario==== | ====Programming a scenario==== | ||
| + | |||
| + | == WHAT Table== | ||
| + | {| class="wikitable" style="float:left;" | ||
| + | ! style="text-align:left;"| WHAT | ||
| + | ! style="text-align:left;"| Description | ||
| + | |- | ||
| + | |1..16<br>1..20 | ||
| + | |Scenario 1 to 16 (F420)<br>Scenario 1 to 20 (IR 3456) | ||
| + | |- | ||
| + | |1 | ||
| + | |UP | ||
| + | |- | ||
| + | |2 | ||
| + | |DOWN | ||
| + | |} | ||
Revision as of 18:21, 21 November 2014
What is a scenario?
A scenario is a list of simple commands, stored in a scenario device like F420 (max. 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*48#4#02## launch scenario #9, connected to address 48 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
WHAT Table
| WHAT | Description |
|---|---|
| 1..16 1..20 |
Scenario 1 to 16 (F420) Scenario 1 to 20 (IR 3456) |
| 1 | UP |
| 2 | DOWN |
| WHO Table | WHO=1 - Lighting |
