First, let’s define Programming…<\/p>\n

Programming is telling a computer how to do certain things by giving it instructions<\/strong>.<\/p><\/blockquote>\n
In Indigo, you define devices, such as:<\/p>\n
\n
Door Alarm<\/li>\n
Thermostat<\/li>\n
Light 1 in the Rec Room<\/li>\n
Garage Door Opener<\/li>\n
etc<\/li>\n<\/ul>\n
For basic operations, Indigo has its own Programming scheme, that uses Triggers. \u00c2\u00a0A trigger is a status change on a device. \u00c2\u00a0Here is the list of triggers that Indigo, has built-in. \u00c2\u00a0This is not a complete list of Indigo’s triggers, since 3rd party programmers can add their own triggers… \u00c2\u00a0But it gives you a basic understanding of what triggers are available:<\/div>\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Value<\/th>\n Description<\/th>\n<\/tr>\n
ActiveZone<\/code><\/em><\/td>\n monitor the sprinkler\u00e2\u20ac\u2122s activeZone to become =, !=, or any change<\/td>\n<\/tr>\n
AnalogInput<\/code><\/em><\/td>\n monitor (one of) the analog input(s) available on the device for =, !=, <, >, or any change – stateSelectorIndex is required to be in the range of available inputs<\/td>\n<\/tr>\n
AnalogInputsAll<\/code><\/em><\/td>\n monitors all of the analog inputs available on the device for any change<\/td>\n<\/tr>\n
BinaryInput<\/code><\/em><\/td>\n monitor (one of) the binary input(s) to become true, false, or any change – stateSelectorIndex is required to be in the range of available inputs<\/td>\n<\/tr>\n
BinaryInputsAll<\/code><\/em><\/td>\n monitors all of the binary inputs available on the device for any change<\/td>\n<\/tr>\n
BinaryOutput<\/code><\/em><\/td>\n monitor (one of) the binary output(s) to become true, false, or any change – stateSelectorIndex is required to be in the range of available outputs<\/td>\n<\/tr>\n
BinaryOutputsAll<\/code><\/em><\/td>\n <\/td>\n<\/tr>\n
BrightnessLevel<\/em><\/code><\/td>\n monitor the brightness level of a device for =, !=, <, >, and any change<\/td>\n<\/tr>\n
HumidityInput<\/code><\/em><\/td>\n monitor (one of) the humdity sensor(s) available on the device for =, !=, <, >, and any change – stateSelectorIndex is required to be in the range of available inputs<\/td>\n<\/tr>\n
HumidityInputsAll<\/code><\/em><\/td>\n monitors all of the humidity sensors available on the device for any change<\/td>\n<\/tr>\n
HvacCoolerIsOn<\/code><\/em><\/td>\n monitor the thermostat for any time the air conditioning turns on, off, or has any change (coolIsOn is the current compressor state)<\/td>\n<\/tr>\n
HvacFanIsOn<\/code><\/em><\/td>\n monitor the thermostat for any time the fan turns on, off, or has any change (fanIsOn is the current fan state)<\/td>\n<\/tr>\n
HvacFanMode<\/code><\/em><\/td>\n monitor the fanMode of the thermostat for any change<\/td>\n<\/tr>\n
HvacFanModeIsAlwaysOn<\/code><\/em><\/td>\n monitor the fanMode of the thermostat for a change to\/from kFanMode.AlwaysOn<\/td>\n<\/tr>\n
HvacFanModeIsAuto<\/code><\/em><\/td>\n monitor the fanMode of the thermostat for a change to\/from kFanMode.AutoOn<\/td>\n<\/tr>\n
HvacHeaterIsOn<\/code><\/em><\/td>\n monitor the thermostat for any time the heater turns on, off, or has any change (heatIsOn is the current heater state)<\/td>\n<\/tr>\n
HvacOperationMode<\/code><\/em><\/td>\n monitor the hvacMode of the thermostat for any change<\/td>\n<\/tr>\n
HvacOperationModeIsAuto<\/code><\/em><\/td>\n monitor the hvacMode of the thermostat for a change to\/from kHvacMode.HeatCoolOn<\/td>\n<\/tr>\n
HvacOperationModeIsCool<\/code><\/em><\/td>\n monitor the hvacMode of the thermostat for a change to\/from kHvacMode.CoolOn<\/td>\n<\/tr>\n
HvacOperationModeIsHeat<\/code><\/em><\/td>\n monitor the hvacMode of the thermostat for a change to\/from kHvacMode.HeatOn<\/td>\n<\/tr>\n
HvacOperationModeIsOff<\/code><\/em><\/td>\n monitor the hvacMode of the thermostat for a change to\/from kHvacMode.Off<\/td>\n<\/tr>\n
HvacOperationModeIsProgramAuto<\/code><\/em><\/td>\n monitor the hvacMode of the thermostat for a change to\/from kHvacMode.ProgramAuto<\/td>\n<\/tr>\n
HvacOperationModeIsProgramCool<\/code><\/em><\/td>\n monitor the hvacMode of the thermostat for a change to\/from kHvacMode.ProgramCool<\/td>\n<\/tr>\n
HvacOperationModeIsProgramHeat<\/code><\/em><\/td>\n monitor the hvacMode of the thermostat for a change to\/from kHvacMode.ProgramHeat<\/td>\n<\/tr>\n
KeypadButtonLed<\/code><\/em><\/td>\n <\/td>\n<\/tr>\n
OnOffState<\/code><\/em><\/td>\n monitor the device for a change to\/from on\/off<\/td>\n<\/tr>\n
SensorInput<\/code><\/em><\/td>\n monitor (one of) the sensor input(s) available on the device for =, !=, <, >, or any change – stateSelectorIndex is required to be in the range of available inputs<\/td>\n<\/tr>\n
SensorInputsAll<\/code><\/em><\/td>\n monitors all of the sensor inputs available on the device for any change<\/td>\n<\/tr>\n
SetpointCool<\/code><\/em><\/td>\n monitor the cool setpoint of the thermostat for =, !=, <, >, or any change<\/td>\n<\/tr>\n
SetpointHeat<\/code><\/em><\/td>\n monitor the heat setpoint of the thermostat for =, !=, <, >, or any change<\/td>\n<\/tr>\n
TemperatureInput<\/code><\/em><\/td>\n monitor (one of) the temperature sensor(s) available on the device for =, !=, <, >, and any change – stateSelectorIndex is required to be in the range of available inputs<\/td>\n<\/tr>\n
TemperatureInputsAll<\/code><\/em><\/td>\n monitors all of the temperature sensors available on the device for any change<\/td>\n<\/tr>\n
Zone<\/code><\/em><\/td>\n monitor (one of) the binary output(s) to become true, false, or any change – stateSelectorIndex is required to be in the range of available outputs<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
For example, a basic trigger, could do:<\/p>\n
\n
If \u00c2\u00a0 Device (Thermostat<\/strong>)’s Zone 1 Temperature<\/em> Becomes Greater than<\/strong> 75 then\n
\n
Control Thermostat, Set Mode to Cool On<\/li>\n
Control Thermostat, Set Cool Setpoint to 74 Degrees<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
The basic built-in Trigger system is<\/strong> a programming language. \u00c2\u00a0The trigger system is quite impressive , and allows fantastic control over Indigo.<\/div>\n
<\/div>\n
But what if you want to do more…? \u00c2\u00a0More complex triggers and\/or develop plugins for Indigo? \u00c2\u00a0Indigo is designed\u00c2\u00a0for all levels of Home Automation users, the Beginner, Intermediate, and Expert \/ Power User. \u00c2\u00a0Indigo supports two more programming languages, \u00c2\u00a0Applescript and Python.<\/div>\n
<\/div>\n
The Python Programming language is highly recommended, over Applescript… \u00c2\u00a0But Applescript does offer some better ease of integrating with your Macintosh & Macintosh applications.<\/div>\n
<\/div>\n
Here’s a secret, Indigo’s triggers even allow you to run embedded Applescript and Python scripts. \u00c2\u00a0So in many cases, you don’t need to develop a plugin. \u00c2\u00a0Just trigger a Python or Applescript, from a trigger action..<\/div>\n
<\/div>\n
But learn Python before you sit down and try to write a Python script for the first time.<\/p>\n
This is the Python v2.54 tutorial, which I highly recommend… I wouldn’t start with later versions, simply because v2.5x is the version Indigo currently uses.<\/p>\n
http:\/\/docs.python.org\/release\/2.5.4\/tut\/tut.html<\/a><\/p>\n
Get comfortable with Python, and then read the Indigo 5 Scripting Tutorial…<\/p>\n
http:\/\/www.perceptiveautomation.com\/wik … g_tutorial<\/a><\/p>\n
That covers basic Python coding in the Interactive Script Window.<\/p>\n
If you decide that you want to progress into developing your own plugins, the Indigo Plugin Developer’s Guide covers everything you have asked about… What are the XML files, and the structure of a plugin, etc…<\/p>\n
http:\/\/www.perceptiveautomation.com\/wik … ugin_guide<\/a><\/div>\n
<\/div>\n
<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
First, let’s define Programming… Programming is telling a computer how to do certain things by giving it instructions. In Indigo, you define devices, such as: Door Alarm Thermostat Light 1 in the Rec Room Garage Door Opener etc For basic operations, Indigo has its own Programming scheme, that uses Triggers. \u00c2\u00a0A trigger is a status […]<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":35,"menu_order":2,"comment_status":"open","ping_status":"open","template":"","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"_links":{"self":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/pages\/6212"}],"collection":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/comments?post=6212"}],"version-history":[{"count":0,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/pages\/6212\/revisions"}],"up":[{"embeddable":true,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/media?parent=6212"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Value<\/th>\n	Description<\/th>\n<\/tr>\n
`ActiveZone<\/code><\/em><\/td>\n`	monitor the sprinkler\u00e2\u20ac\u2122s activeZone to become =, !=, or any change<\/td>\n<\/tr>\n
`AnalogInput<\/code><\/em><\/td>\n`	monitor (one of) the analog input(s) available on the device for =, !=, <, >, or any change – stateSelectorIndex is required to be in the range of available inputs<\/td>\n<\/tr>\n
`AnalogInputsAll<\/code><\/em><\/td>\n`	monitors all of the analog inputs available on the device for any change<\/td>\n<\/tr>\n
`BinaryInput<\/code><\/em><\/td>\n`	monitor (one of) the binary input(s) to become true, false, or any change – stateSelectorIndex is required to be in the range of available inputs<\/td>\n<\/tr>\n
`BinaryInputsAll<\/code><\/em><\/td>\n`	monitors all of the binary inputs available on the device for any change<\/td>\n<\/tr>\n
`BinaryOutput<\/code><\/em><\/td>\n`	monitor (one of) the binary output(s) to become true, false, or any change – stateSelectorIndex is required to be in the range of available outputs<\/td>\n<\/tr>\n
`BinaryOutputsAll<\/code><\/em><\/td>\n`	<\/td>\n<\/tr>\n
`BrightnessLevel<\/em><\/code><\/td>\n`	monitor the brightness level of a device for =, !=, <, >, and any change<\/td>\n<\/tr>\n
`HumidityInput<\/code><\/em><\/td>\n`	monitor (one of) the humdity sensor(s) available on the device for =, !=, <, >, and any change – stateSelectorIndex is required to be in the range of available inputs<\/td>\n<\/tr>\n
`HumidityInputsAll<\/code><\/em><\/td>\n`	monitors all of the humidity sensors available on the device for any change<\/td>\n<\/tr>\n
`HvacCoolerIsOn<\/code><\/em><\/td>\n`	monitor the thermostat for any time the air conditioning turns on, off, or has any change (coolIsOn is the current compressor state)<\/td>\n<\/tr>\n
`HvacFanIsOn<\/code><\/em><\/td>\n`	monitor the thermostat for any time the fan turns on, off, or has any change (fanIsOn is the current fan state)<\/td>\n<\/tr>\n
`HvacFanMode<\/code><\/em><\/td>\n`	monitor the fanMode of the thermostat for any change<\/td>\n<\/tr>\n
`HvacFanModeIsAlwaysOn<\/code><\/em><\/td>\n`	monitor the fanMode of the thermostat for a change to\/from kFanMode.AlwaysOn<\/td>\n<\/tr>\n
`HvacFanModeIsAuto<\/code><\/em><\/td>\n`	monitor the fanMode of the thermostat for a change to\/from kFanMode.AutoOn<\/td>\n<\/tr>\n
`HvacHeaterIsOn<\/code><\/em><\/td>\n`	monitor the thermostat for any time the heater turns on, off, or has any change (heatIsOn is the current heater state)<\/td>\n<\/tr>\n
`HvacOperationMode<\/code><\/em><\/td>\n`	monitor the hvacMode of the thermostat for any change<\/td>\n<\/tr>\n
`HvacOperationModeIsAuto<\/code><\/em><\/td>\n`	monitor the hvacMode of the thermostat for a change to\/from kHvacMode.HeatCoolOn<\/td>\n<\/tr>\n
`HvacOperationModeIsCool<\/code><\/em><\/td>\n`	monitor the hvacMode of the thermostat for a change to\/from kHvacMode.CoolOn<\/td>\n<\/tr>\n
`HvacOperationModeIsHeat<\/code><\/em><\/td>\n`	monitor the hvacMode of the thermostat for a change to\/from kHvacMode.HeatOn<\/td>\n<\/tr>\n
`HvacOperationModeIsOff<\/code><\/em><\/td>\n`	monitor the hvacMode of the thermostat for a change to\/from kHvacMode.Off<\/td>\n<\/tr>\n
`HvacOperationModeIsProgramAuto<\/code><\/em><\/td>\n`	monitor the hvacMode of the thermostat for a change to\/from kHvacMode.ProgramAuto<\/td>\n<\/tr>\n
`HvacOperationModeIsProgramCool<\/code><\/em><\/td>\n`	monitor the hvacMode of the thermostat for a change to\/from kHvacMode.ProgramCool<\/td>\n<\/tr>\n
`HvacOperationModeIsProgramHeat<\/code><\/em><\/td>\n`	monitor the hvacMode of the thermostat for a change to\/from kHvacMode.ProgramHeat<\/td>\n<\/tr>\n
`KeypadButtonLed<\/code><\/em><\/td>\n`	<\/td>\n<\/tr>\n
`OnOffState<\/code><\/em><\/td>\n`	monitor the device for a change to\/from on\/off<\/td>\n<\/tr>\n
`SensorInput<\/code><\/em><\/td>\n`	monitor (one of) the sensor input(s) available on the device for =, !=, <, >, or any change – stateSelectorIndex is required to be in the range of available inputs<\/td>\n<\/tr>\n
`SensorInputsAll<\/code><\/em><\/td>\n`	monitors all of the sensor inputs available on the device for any change<\/td>\n<\/tr>\n
`SetpointCool<\/code><\/em><\/td>\n`	monitor the cool setpoint of the thermostat for =, !=, <, >, or any change<\/td>\n<\/tr>\n
`SetpointHeat<\/code><\/em><\/td>\n`	monitor the heat setpoint of the thermostat for =, !=, <, >, or any change<\/td>\n<\/tr>\n
`TemperatureInput<\/code><\/em><\/td>\n`	monitor (one of) the temperature sensor(s) available on the device for =, !=, <, >, and any change – stateSelectorIndex is required to be in the range of available inputs<\/td>\n<\/tr>\n
`TemperatureInputsAll<\/code><\/em><\/td>\n`	monitors all of the temperature sensors available on the device for any change<\/td>\n<\/tr>\n
`Zone<\/code><\/em><\/td>\n`	monitor (one of) the binary output(s) to become true, false, or any change – stateSelectorIndex is required to be in the range of available outputs<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n For example, a basic trigger, could do:<\/p>\n \n If \u00c2\u00a0 Device (Thermostat<\/strong>)’s Zone 1 Temperature<\/em> Becomes Greater than<\/strong> 75 then\n \n Control Thermostat, Set Mode to Cool On<\/li>\n Control Thermostat, Set Cool Setpoint to 74 Degrees<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n The basic built-in Trigger system is<\/strong> a programming language. \u00c2\u00a0The trigger system is quite impressive , and allows fantastic control over Indigo.<\/div>\n <\/div>\n But what if you want to do more…? \u00c2\u00a0More complex triggers and\/or develop plugins for Indigo? \u00c2\u00a0Indigo is designed\u00c2\u00a0for all levels of Home Automation users, the Beginner, Intermediate, and Expert \/ Power User. \u00c2\u00a0Indigo supports two more programming languages, \u00c2\u00a0Applescript and Python.<\/div>\n <\/div>\n The Python Programming language is highly recommended, over Applescript… \u00c2\u00a0But Applescript does offer some better ease of integrating with your Macintosh & Macintosh applications.<\/div>\n <\/div>\n Here’s a secret, Indigo’s triggers even allow you to run embedded Applescript and Python scripts. \u00c2\u00a0So in many cases, you don’t need to develop a plugin. \u00c2\u00a0Just trigger a Python or Applescript, from a trigger action..<\/div>\n <\/div>\n But learn Python before you sit down and try to write a Python script for the first time.<\/p>\n This is the Python v2.54 tutorial, which I highly recommend… I wouldn’t start with later versions, simply because v2.5x is the version Indigo currently uses.<\/p>\n http:\/\/docs.python.org\/release\/2.5.4\/tut\/tut.html<\/a><\/p>\n Get comfortable with Python, and then read the Indigo 5 Scripting Tutorial…<\/p>\n http:\/\/www.perceptiveautomation.com\/wik … g_tutorial<\/a><\/p>\n That covers basic Python coding in the Interactive Script Window.<\/p>\n If you decide that you want to progress into developing your own plugins, the Indigo Plugin Developer’s Guide covers everything you have asked about… What are the XML files, and the structure of a plugin, etc…<\/p>\n http:\/\/www.perceptiveautomation.com\/wik … ugin_guide<\/a><\/div>\n <\/div>\n <\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":" First, let’s define Programming… Programming is telling a computer how to do certain things by giving it instructions. In Indigo, you define devices, such as: Door Alarm Thermostat Light 1 in the Rec Room Garage Door Opener etc For basic operations, Indigo has its own Programming scheme, that uses Triggers. \u00c2\u00a0A trigger is a status […]<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":35,"menu_order":2,"comment_status":"open","ping_status":"open","template":"","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"_links":{"self":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/pages\/6212"}],"collection":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/comments?post=6212"}],"version-history":[{"count":0,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/pages\/6212\/revisions"}],"up":[{"embeddable":true,"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"http:\/\/www.schollnick.net\/wordpress\/wp-json\/wp\/v2\/media?parent=6212"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}