Software » Mainswitch

h1. Behaviour

* Mainswitch only listens to -ambient light changes, Media-Switch- keepAwake-Events

** This makes sense. If the light automatically fades out, someone can switch it on again and does not need to care about mainswitch.

** Multiple mainswitches are no problem

** CANSwitch timeout has to be shorter than MainSwitch, otherwise you get hard-off, meaning an short illumination flash

** timeouts gets reset at 1/2 of the configured time, except target value is "0"

** CANSwitch default timeout: 4h. When you enable light at 18:00, timout is at 22:00. Waking it up on 22:00 extends to 0:00.

** fading must be done before other switches are switched off, or TV gets shut off before user can reset via light

** CANSwitch must send the value "0" target ambient light, so CANDis shows right value. But only when fading down finished.

** When watching TV at day, it will switch off after 4 hours without warning. It can be switched on again.

** Warning can be shown on CANDis; Quite silent beep. "Keep awake" "OK"

** CANSwitch has to remember amibent light value on timeout fade-out. When an wakeup occurs, the previously set ambient light can be restored.

** Devices need areals in EEPROM. Bus could be routed in complete house. Kitchen already has different context.

** Regional events. 'wannaSleep', 'keepAwake', 'overTemperature', 'underTemperature';

** CANSwitch sends 'keepAwake' when media is switched on or light is set to value > 0

** CANDis does usually not send regionalEvents, only in the Sleep-warning

h1. Problems / Open points

* Regional events look super specific. Shoould this better be an object?

* Can existing events be used for this