curtbinder
commented
11 years ago The values being stored should be the actual values in the XML tags and not the overridden values. There needs to be a display indicator that shows the values were overridden.
update app to use the new override functionality, see Libraries/Issue#73
This is how the override is going to work: Any value above 100, usually 255, indicates the override is disabled. And consequently any value below and including 100 indicates the channel is overridden.
Wifi Command: /pox,y where x=channel to override y=value to override
Channels: // PWM Override IDs
define OVERRIDE_DAYLIGHT 0
define OVERRIDE_ACTINIC 1
define OVERRIDE_CHANNEL0 2
define OVERRIDE_CHANNEL1 3
define OVERRIDE_CHANNEL2 4
define OVERRIDE_CHANNEL3 5
define OVERRIDE_CHANNEL4 6
define OVERRIDE_CHANNEL5 7
define OVERRIDE_AI_WHITE 8
define OVERRIDE_AI_ROYALBLUE 9
define OVERRIDE_AI_BLUE 10
define OVERRIDE_RF_WHITE 11
define OVERRIDE_RF_ROYALBLUE 12
define OVERRIDE_RF_RED 13
define OVERRIDE_RF_GREEN 14
define OVERRIDE_RF_BLUE 15
define OVERRIDE_RF_INTENSITY 16
define OVERRIDE_CHANNELS 17
pwma, d, expansion, ai, radion PWMAO, PWMDO, PWME0-5O, AIWO, AIBO, AIRBO, RFWO, RFRBO, RFRO, RFGO, RFBO, RFIO
Example Commands: To override the actinic channel to 45%, send command: /po1,45 To remove override of actinic channel, send command: /po1,255
Examples XML data: Not overridden with actinic channel outputting 60%:
Overridden with actinic channel outputting 45%:
If someone clicked the AP% for example, a slider would popup that would let you adjust that % and place the new value on the override variable. The controller would then adjust the channel to this new value.
need to store the override values in the database as shorts (or bytes), the same as the pwm channels