m4rky_m4rk
Prominent Member
MH202 Scenario programmer product details
Thread for the MH202 advanced scenario controller discussions
Notes/tips:
Thread for the MH202 advanced scenario controller discussions
Notes/tips:
- Boolean counters need to be set to an initial state, True or False. It is the change of state that is important. This can be done with a scenario that has no start conditions but is set to run at restart of MH202. I also add a Light on/off event so that I know it ran OK and finished after uploading a new config.
- A CEN command in the Action list can be used to trigger another scenario if the same CEN command is in its Start list
- CEN vs Boolean usage: CEN commands cannot be used in the 'only if' list.
- Approximately 5 scenarios can be run simultaneously.
- Actions are executed sequentially.
- The minimum time delay command is 1 sec but an action, eg Light on, takes approx 250ms to execute, So, dummy actions can be used to create delays shorter that 1 sec.
- It is possible to set the start conditions for several scenarios to be identical. Which is actually run can then be decided by the use of an 'only if' condition. This is useful to allow the use of just one CEN address that then triggers other scenarios dependent on, for example, time of year, room temperature, sun sensor etc.
- A tip for debugging. The web admin page of the MH202 shows which scenarios are currently running.
Last edited: