This plugin uses mobile me to locate your iphone, and display it's location on a Google Map.  It also will attempt to calculate the distance from the latitude & longtitude that you supply to your iphone.

1. Download the ZIP file, and unarchive it.
2. Copy the “Findmyiphone” folder to /Library/Application Support/Perceptive Automation/Indigo 4/IndigoWebServer/plugins
3. restart the Indigo Server, to allow the plugin to be loaded
4. To Configure the Indigo Server for use of the Plugin, The following Variables need to be made:
   1. MobileMe_UserName – Your MobileMe Username
   2. MobileMe_Password  - Your MobileMe Password
   3. FindMyiPhone_Lat    - The Latitude of your “target”
   4. FindMyiPhone_Long – The Longitude of your “target”
5. Open your Indigo Web Interface, and run the plugin.

Simple, Open your Web Browser, and browse to the Indigo Web server.  From the root of the web server add /findmyiphone.

For Example:

http://entertainmac.:8080/findmyiphone

The Plugin will then attempt to login to MobileMe, find your iPhone via the Find Your iPhone Service, and then compare your iPhone’s Lat & Long to the Latitude & Longitude in Indigo.  It will then do some calculations, and give an estimate of the straight line (as the bird flies) distance between your target & current location.

This site, http://jan.ucc.nau.edu/~cvm/latlon_find_location.html, contains information and links on finding your latitude and longitude, by street address, city, etc…  Just plug the values in, and the script will take over from there…

These two attachment scripts define a suite of AppleScript functions that are callable from Indigo Actions (or other Applications) to sequentially target and control Devices and Actions Groups. This allows users to easily, and with only a couple of actions, select any Device or Action Group as a target. The targeted Device can then be controlled (on/off/dim/brighten), and the targeted Action Group can be executed.

Installed by Indigo into:
/Library/Application Support/Perceptive Automation/Indigo 2/Scripts/Attachments/
device target attachment.scpt and group target attachment.scpt

TargetFirstDevice(), TargetNextDevice(), TargetPreviousDevice(), TurnOnTargetedDevice(), TurnOffTargetedDevice(), ToggleTargetedDevice(), BrightenTargetedDevice(), DimTargetedDevice()
-- and --
TargetFirstGroup(), TargetNextGroup(), TargetPreviousGroup(), ExecuteTargetedGroup()

I needed a script that would reliably close my garage door. Using the I/O Linc (Model 2450 -- 1 input & 1 output set to momentary ON) and the magnet from the garage kit I had all the info required. I wanted the script to address situations where a momentary ON (i.e. button press) would not result in the door closing. This could occur if the door were partially opened (button press may open the door fully instead of closing it) or if the door sticks occasionally and 'rebounds' to the open position. I limit the number of close attempts to five so that the motor doesn't burn out if things go haywire.

The script is a standard external AppleScript.

The script tests the state of Binary input 1. If it's FALSE, the door is open AND if the loop counter indicates fewer than 6 attempts, it proceeds.

After incrementing the counter, it sets an Indigo variable I created called 'vMsgBody' with text. This causes a completely different trigger to send me a text message. I have commented this text out since most users won't have things set up this way. The script then sets the binary output 1 to TRUE. This causes a momentary closing of the output circuit (momentary because the unit was configured that way). This is the equivalent to a button press that activates the door. Usually this will close the door.

After waiting 30 seconds, binary input 1 is polled again to confirm that the door actually closed. If it hasn't, the loop repeats until it has OR until 5 attempts are completed.

This is a generic door-closing script but I actually call it from 2 different triggers to accomplish the desired behavior. I want the garage door to auto-close after 15 minutes, but only if I'm not out in the garage. If I'm in the garage, I'd like it to stay open until 15 minutes after I leave.  I accomplish this by adding a motion detector set up with a 15 minutes to OFF delay.

Trigger 1 is activated the moment the door opens (i.e. when binary input 1 goes to FALSE). By setting a Condition that 'if the state of the motion detector is OFF' (as returned by a short embedded AppleScript under the Conditions tab), I ensure that this script doesn't close the door if I'm moving around in the garage. This trigger is set up with a 15 minute delay after which my generic Door Close script is called.

Trigger 2 is activated by the motion detector going to the OFF state after the detector's built-in 15 min delay. When this happens the generic close script is called immediately. Since the script begins by checking the state of binary input 1, it doesn't do anything if the door happens to be already closed.

So far, this has worked perfectly. But I have thought of a scenario where it would 'fail'. If I open the garage door from the driveway using the garage door remote, when Trigger 1 activates it sees no motion in the garage. It would then begin the 15 minute delay based on this no-motion status. However if I hang out in the garage, although my movements set the motion detector to ON, this status is not tested again by Trigger 1. Therefore the garage door will close with me moving in the garage. The solution is to test the motion state again immediately before calling the generic door close routine (or as another criteria for the repeat while loop although that would make the script a little less generic.

This script downloads and speaks a weather forecast from Weather.com through your computers speakers. 
Note: This script expects the weather report to be in English. That is reasonable since the documentation and support pages for Indigo are in English and it is probably safe to assume that if you found this script you speak some English. BUT: If you would like to use a language other than English for your reports, this script can be tuned to other languages and alternative web sites. If you need help doing this, post your request to the Indigo "Indigo & Applescript" forum. Update 1.0.1 includes revised instructions for locations outside the US and Canada and corrects a minor error in the instructions on changing the number of periods reported.

If you are in the USA, create an Indigo internal variable named "weatherSpeakCode"

and set its value to your local zip code. 

If you are outside the USA, you will need to determine the 

Weather.com code for your location. To do this, go to Weather.com and 

enter your location name and country in the search box and click "search." 

Then, in the forecast page that you see next, look at the page URL. It 

will contain information in the form: "city+country+code?" Use that code 

(it appears between the last "+" and the "?")  For example, for 

Haugesund, Norway the URL is: 

Install this script anywhere on your hard disk and call it in an AppleScript action.

I do this to detect my blackberry and my wife's iphone by watching for them to login to our airport routers. It's a hacked up version of someone else's script that I found online.

Some caveats:

- The airport extreme seems to not like being polled so often, I have to reboot it once a day (I have a controllable PDU in my rack) to keep it happy. SNMP stops responding, it otherwise is fine. The airport express does not seem to have this problem, I complained to apple.
- The iphone will disable the wireless if not plugged in and the screen lock kicks in
- You would need to work out the SNMP OIDs for the MACs of your devices with snmpwalk.
- You need to do the snmpwalk before the snmpget's or it has stale info (I'd love to know why?)
- The time appears to be an epoch in hundredths of a second since boot.
- I use this to turn on our outside lights at night when we arrive. It's sort of hit or miss whether the clients associate fast enough for this to be helpful.

Credit to:

--      Daniel Chote (http://www.chote.com)
-- Date: December 1, 2007

Find the OIDs for your devices with SNMP walk, modify the script, create variables for the OIDs, create a trigger to start the script on Indigo startup.

This shell command script will terminate the Indigo Server (and built-in Indigo web server). It will also disable the "auto start on user login and auto relaunch if crash" behaviour. This will allow you to prevent the auto relaunch of the server if it ever starts misbehaving for any reason. NOTE: requires 3.0.6 or greater.

Double-click on the indigostop.command file. The terminal will launch and try multiple techniques to shut down and disable the server. To renable the server, run the Indigo client application on the server machine and choose the Indigo 2->Start Local Server... menu item.

Maxi Controller is an application (not a script) that displays a working GUI of the Maxi Controller transmitter. It was written by Frank Nicholas in AppleScript Studio and uses Indigo to transmit the X10 addresses and commands. The source project is also available for download and is a great example of using AppleScript Studio to extend Indigo.

After downloading, drag the Maxi Controller application into your Applications folder and double click to launch it.

The Indigo Plugin for Plex duplicates much of the functionality of Indigo's web and iPhone clients, making it possible to control your home automation system with a click of the remote.  This plugin should work equally well when Plex and Indigo are on the same machine, on different machines on the same intranet, or across the internet.

Indigo for Plex requires:

* Indigo 4.X or above, with the server running independently of the client application

* Remote access allowed (with or without authentication)

Indigo Widget is a Mac OS X Dashboard Widget that provides minimal Indigo access of Devices, Variables, and Action Groups. Note the widget communicates with Indigo Server via AppleScript, which is an Indigo 4.x Pro only feature, and thus is not compatible with Indigo 4.x Lite.

See ReadMe file included in .zip download.

See ReadMe file included in .zip download.

This package is used to simplify access to and inneroperability of three applications:

* iTunes

* PandoraBoy (http://code.google.com/p/pandoraboy/) - Plays Pandra "radio stations"

* AirFoil (http://www.rogueamoeba.com/airfoil/mac/) - used to send audio from any application to the AirPort Express units, apple TV(not just iTunes)

My goal is to have a way to control my whole-house audio system that plays iTunes, Pandora and making announcements.

if iTunes were the only application involved, access is very simple - and the fitures in the scripts included in Indigo would more than suffice. When one adds the complexity of adding Pandora to the mix, it gets a little more complex:

* AirPort Express devices only work with iTunes by default

* Pandora - a web service - is not easily controlled with Applescript.

* Most likely, you would not want iTunes and Pandora playing simultaneously. A random mashup of Cake and AC/DC is less pleasing to the ear than one might expect.

A quick note on Pandora: After some brief testing with Pandora, I quickly learned that paying for the "Pandora One" is a great value. The environment described here is not intended for use with the ad-based, free Pandora experience - the frequent pauses and ads make the environment unworkable.

To solve the above issues, two applications were required:

* AirFoil - an inexpensive (but not free) application that allows sending audio from any application to Airport Express devices, Macs, Apple TVs, iPhones and iPod Touches.

* PandoraBoy - a simple wrapper application that allows AppleScript control of the Pandora web-based service.

There are two scripts included in this package that allows simplified control of these applications:

* audioAppStatusUpdater.scpt

Installation directory: /Library/Application Support/Perceptive Automation/Indigo 4/Scripts/Background/

To install this script:

* Press File / New Trigger Action

* set Type to "Indigo Server Startup"

* click the Action tab

* set Type to "Execute Applescript"

* Select the "File" radio button

* Select the script in the dialog box.

This script monotors all three applications, and updates various Indigo Server variables. This script can work as a stand-alone script if you simply would like to have access with the variables, or in conjunction with audioAppControll.scpt to allow full control.

This script will not interfere with the operation of the included "iTunes sync.scpt" - they update a different set of variables and will not conflict with one another.

* audioAppControl.scpt

Installation directory: /Library/Application Support/Perceptive Automation/Indigo 4/Scripts/Attachments/

This is the control script intended to go into the "Attachments" folder. It does require that "audioStatusUpdater.scpt" be installed and running before using the functions provided within. (some functionality may work, but most of the iTunes and PandoraBoy controls will do nothing).

This script has a lot of utility functions for dealing with AirFoil, iTunes and PandoraBoy. Some of the included functions are:

* announceMessage(strMessage)

Lowers volume of either individual application and use "say" command to speak the message. If using AirFoil, you need to set AirFoil to "System Audio" (see connectToSource() below). Because I use the AppleScript "Say" command, this uses the system's Text-to-Speach preferences found in the preferences pane.

* announceCurrentTrack()

Uses above function to announce the current track, artist and album.

* announcePlaylist()

Announces the current playlist / station.

* toggleMusic()

If nothing is playing, iTunes will start. Otherwise, whatever is currently playing will be stopped, and the other player will start. This is the function I use for starting music from a button.

* startPandoraBoy()

Stops iTunes, if playing, and starts PandoraBoy.

* startITunes()

Stops PandoraBoy, if playing, and starts iTunes

* stopMusic()

Stops either app, if one is playing.

* nextTrack()

Skip to the next track of the currently playing source.

* nextPlaylist()

This plug-in is a little different than most IWS plug-ins - it doesn't generate a viewable page. Rather, it's a way to get data IN to Indigo. The Lightsoft Weather Center (LWC) is software that connects your Mac to hardware weather stations (Davis Vantage & Envoy, Monitor, Wizard and La Crosse WS23xx currently) as well as Internet based weather sources.

As far as I know, it's the only commercial Mac-based solution that supports the LaCrosse station, which happens to be the one I have. I wanted to get data into Indigo similar to the NOAA scripts so I could use it primarily to determine if/when to run the sprinklers, but also because, well, it's COOL.

To install this plugin drag the "lwc" folder to the following location:

/Library/Application Support/Perceptive Automation/Indigo 4/IndigoWebServer/plugins/

To use this plugin, just configure LWC's On-Line->Custom CGI with the following URL:

http://host:port/lwc/importData?

I also think it's useful to check the "Send Time As Local" checkbox so you can see the date/timestamp in local time. The plug-in will do the rest. Because there's quite a few variables in LWC that aren't sent to this custom cgi yet, I wanted to take an approach that would not require me to update the plug-in whenever LWC was revised to send more data. So, I decided to just automagically create variables for ALL passed in data. So, given the following URL (which is what's currently being sent from LWC as of 5/13/2009):

http://host:port/lwc/importData?&date=2009-05-12+17%3A22%3A12 &winddir=270 &windspeedmph=0.0 &windspeedmphav_10m=0.0 &windgustmph=0.0 &windgustdir=270 &windgustmph_10m=0.0 &windgustdir_10m=270 &humidity=47 &dewptf=69.836 &tempf=93.20 0&raininch=0.000 &rain24hinch=0.000 &baroinch=28.508 &action=update

the plugin will update/create variables that start with LWC_.

This script will process iCal alert emails and perform several functions:

1. It will optionally speak the event name and time
2. It will optionally execute an Indigo Action Group
3. It will optionally look for specially formatted directives in the Notes field of the event that will tell Indigo to perform various actions (see the wiki post for details)

 See the official wiki post for details.

See the official wiki post for details.

See the official wiki post for details.

This integration between Indigo and PhoneValet will:

1) Create some variables in Indigo that represent various information about PhoneValet data (# of new calls, last caller, etc.). You can then use this data in other scripts or actions, or even show the data on your control pages. Image being able to see who the last caller was to your home over the internet, or how many new calls you have waiting without having to call in to PhoneValet!

2) Use the text-to-speech system of your Mac along with PhoneValet to create answering machine functionality. This is particularly useful if you're using Airfoil to direct your sound through a whole-house av system; or, even, to an AppleTV in your living room. Use an Insteon controller to control your voicemail from anywhere in the house and use your whole-house audio to listen! Each VM menu as spoken by the system will also time-out after 30 seconds as well, so if you don't take any action the system will shut down automatically.

Read the Indigo-PhoneValet Doc.rtf file carefully before attempting anything. There is an installer script that will attempt to do the install.

Again, read the Indigo-PhoneValet Doc.rtf file first.

Script to get the location of a cellphone from Instamapper http://www.instamapper.com/ Lookup the location with geoNames http://www.geonames.org/ and update Indigo with the location.

- Assumes that your account on Instamapper has been setup and API access enabled
- Instamaper stipulates the API not be called more frequently than every 10 seconds
- Geonames offers 50,000 API "credits" a day in their free service. Each lookup in this script uses 1 credit.
- If run every couple of minutes it should be well within their rules as this time.

Install and configure Instamapper on your phone, enable the API feature on their site. Edit the InstaPeople table below with the name of the variable to update and it's instamapper API key

Once configured, store the script in Indigo's background tasks's folder and create a trigger to start the script "on startup". It will run and update your location into an Indigo variable for use in other actions/triggers at the frequency defined in the script. Please make yourself aware of both Instamapper and Geoname's usage policies and do not abuse their great free services.

Installed by Indigo into:

/Library/Application Support/Perceptive Automation/Indigo #/Scripts/Attachments/

Where # is the version number (Indigo v2 and v3 are both in Indigo 2).

iTunes attachment.scpt

This script pauses the song currently playing on iTunes on the computer running Indigo, speaks the song, artist and album, and then resumes playing the song at the same point.

After downloading, drag the Speak iTunes Information script into the folder: /Library/Application Support/Perceptive Automation/Indigo 2/Scripts/

Execute within Indigo, typically as a Trigger Action attached to a RemoteLinc or IRLinc

The script will only execute if iTunes is currently playing, and will speak the track information on whatever speakers are currently in use with iTunes.

To speak with a voice other than the System voice, add the voice name to the associated property at the top of the script; for example, the new Leopard voice Alex works well.

Create a Trigger Action in Indigo to launch this script. 

The script uses the Leopard-only voice "Alex". If you're using an older OS you'll need to change the value of the property "TheVoice". The script has been tested with Indigo 1.8.3.

This plug-in allows Weather Display fMac data integration with Indigo Web Server (IWS). 

Weather Display is the most popular weather station software on the Windows PC and now has been ported to the Mac. It supports a myriad of personal weather station hardware from almost all manufacturers  (Davis, Lacross, Irox, Oregon Scientific, Ultimeter, Weather Hawk, Rainwise, Texas Instruments, Dallas 1-wire, and others) as well as Internet based weather sources. 

And it now supports data transfer straight in to Indigo variables. Read more about WD Mac here: 

http://www.weather-display.com/index.php

The WDMac Plugin goes to work as soon as you install it, waiting for the data you have specified to arrive from Weather Display. If the variable has not been created the plugin will do that for you also, and name the variable based on the field definition you configured in Weather Display. Very cool.

To install this plugin drag the "wd" folder to the following location:

/Library/Application Support/Perceptive Automation/Indigo 4/IndigoWebServer/plugins/

This script will initiate a telnet session to WeatherSnoop, capture its output, and parse it into Indigo variables.

It will create the variables as needed, each of which will be prefixed by "ws_".

Install WeatherSnoop and configure it to work with your weather station, and make sure the "Serve my weather data..." checkbox is selected under the Sharing tab. Edit the script properties to reflect the port number and ip of your WeatherSnoop server. (the defaults of 8080 and "localhost", respectively, are probably fine)

Then, just embed the script in a time/date action and call it periodically.

You can set triggers on the ws_ variables to do things like turn off sprinklers when its raining, retract an awning if its windy, etc.

This plugin controls from Cisco SIP Phones.

If you don't know the Cisco IP Phones, they come in different flavors. The 7971GE has a color touch screen and runs about at US$200. Probably one of the cheapest HA Touchscreen controllers you can get considering that you get a great SIP phone thrown in.

There are also other model like the Cisco 7961GE at about US$100 with the same functionality minus the touchscreen and color.

Just unzip and put into the plugin directory. The plugin directory name needs to be "CiscoServices"

To make the plugin work with the phones, the Cisco Phone Config (SEPXXXXXX.xml.cnf) needs to have the INDIGO server URL configured:

For example:
"<servicesURL>http://indigo_server_ip:8176/CiscoServices/mainmenu</servicesURL>"

For convenience, action groups whose name is prefixed with "cphone." (For example 'cphone.Turn on Lights') will show up in the main menu as well as some sort of shortcut to often used Devices, Actions.

The Device menu actually shows the state of the fixture or switch as well using the pre-installed graphics (Thanks Matt!)

Here it is, an attachment script that will allow Venstar Insteon Thermostat users to monitor their daily usage of AC, Heating, and Fan usage… This is a basic attachment script that is designed to extend Indigo…

When installed, the changes are most noticeable in the Log file…

Received INSTEON “Furnace Link” off (button 2)
Thermostat Insteon Thermostat Event being processed
Thermostat Thermostat requesting Heating – Off
Thermostat Furnace Heat Ran for 14 Minutes
Thermostat Thermostat Event Processing Done

• Download the Venstar Thermostat Usage Monitor Script
• Copy the script (Thermo)  to /Library/Application Support/Perceptive Automation/Indigo 4/Scripts/Attachments
• Copy the Thermo-reset script to /Library/Application Support/Perceptive Automation/Indigo 4/Scripts/Attachments
• Create a Time/Date action, with the action of “Run Applescript”, choose External File, and point it to the Reset script.  Set the time for when you would like it to run (for example, Midnight).
• Restart the Indigo Server

The attachment will monitor for the Venstar to announce Button 1 (AC), Button 2 (Heat), and Button 3 (Fan) traffic, and use these to track the usage for AC, Heating, and Fan. The attachment script will also create new variables to allow the tracking of Heat (Heating_dailymins), AC (AC_dailymins), and the Fan (Fan_dailymins) these variables will contain the the number of minutes that Heating, AC and the furnace fan have been on since the last “reset”.

Please note, you will need to make a new timed action that runs thermo_reset.scpt whenever you want to reset the counters… I would suggest midnight, so that you are capturing the 24 hrs period… The script will append to a csv file in your documents folder that contains the value that are in the AC, Furnace and Fan variables, and then reset the variables to 0.

This set of scripts provide Indigo support for controlling a Jandy Aqualink RS through Serial Bridge and a Jandy Aqualink RS Serial Adaptor.

After downloading and unzipping, drag the Jandy Aqualink attachment script into the folder:

  /Library/Application Support/Perceptive Automation/Indigo 2/Scripts/Attachments

Your Serial Bridge connection will need to be titled Jandy Aqualink RS Serial Adaptor. Create a Time/Date Action to update the status of the pool/spa variables on an ongoing basis.

The following text variables will be created when this Time/Date Action first executes: AirTemp, PoolHeat, PoolLight, PoolPump, PoolSetPoint, PoolState, PoolTemp, SpaHeat, SpaLight, SpaSetPoint, SpaState, SpaTemp.

The following is a list of the commands that can be called in the Jandy Aqualink attachment script from Indigo: JandyGetStatus(), JandyTurnOnSpaHeat(), JandyTurnOffSpaHeat(), JandyTurnOnPoolHeat(), JandyTurnOffPoolHeat(), JandyTurnOnLights(), JandyTurnOffLights(), JandyNewSpaSetPoint(NewSpaSetPoint), JandyNewPoolSetPoint(NewPoolSetPoint), JandyTurnOnSpa(), JandyTurnOffSpa(), JandyTurnOnSpaAndHeat(), JandyTurnOnSpaAndHeatAndLights(), JandyTurnOffSpaAndHeatAndLights().

A few more details are in the Read Me file.

Here is a simple script which defines a method to query a Proliphix thermostat, grab the main zone temperature, and put it into an Indigo variable.

Move the script into this folder:
   /Library/Application Support/Perceptive Automation/Indigo 2/Scripts/Attachments/

Create a Time/Date action that calls the main AppleScript function defined in the attachment script:
    GetThermotemp()

The Xytronix Temperature module can read up to 4 electronic thermometers and this AppleScript passes the temperature readings along to Indigo.  The Temperature Module connects to your Local Area Network (or via the internet with proper routing)  http://www.controlbyweb.com/temperature/

Create a Trigger Action of Type "Indigo Server Startup" and select an Action Type of "Execute AppleScript" that executes this script file. This script will then start as a separate process and run as long as the Indigo Server is running.  Indigo Server automatically terminates the script when it shuts down.

Since AppleScript can cary out much more complex data manipulations than Indigo can, you may want to modify this script to compute temperature differences, trends, etc. and report the results to Indigo via additional variables of your own creation.  Indigo could also examine these variables and cary out complex control requests based on their values.

New version 1.1 is available now.

The Xytronix Temperature module can read up to 4 electronic thermometers and this AppleScript passes the temperature readings along to Indigo.  The Temperature Module connects to your Local Area Network (or via the internet with proper routing). 

Since AppleScript can cary out much more complex data manipulations than Indigo can, you may want to modify this script to compute temperature differences, trends, etc. and report the results to Indigo via additional variables of your own creation.  Indigo could also examine these variables and cary out complex control requests based on their values.

Okay, it’s only a one way integration, any Insteon device that supports a “turn on” or “Turn off” command will automatically be Tweeted when turned on or off, with the appropriate message…

For example:

Desktop lamp was turned on

Desktop lamp was turned off

And yes, there isn’t too much sophistication here with this example script.  Please feel free to make suggestions, and comments…  I’d be happy to consider them for a newer version of the script…

1. Download the ZIP file, and unarchive it.
2. Copy the Indigo Tweet! script  into /Library/Application Support/Perceptive Automation/Indigo 4/Scripts/Attachments
3. Reload the Attachments via the Indigo Scripts menu (Choose Reload Attachments).
4. Add an TwitterID & TwitterPassword variable
5. Set the TwitterID to your Twitter Username
6. Set the TwitterPassword to your Twitter Password
7. Watch as your House talks to you via your Twitter Feed…

Once installed, it is automatic.  It will automatically tweet any On/Off command as it occurs.

This attachment script provides handlers to create Reminders and Pesters (periodic mini-reminders). The thinking here is that sometimes you want to create a reminder at some future time. That you want that reminder to execute some actions, and that you want frequent periodic mini reminders (called pesters) so that you don't forget. 

For instance, let's say you're washing machine is in the basement and you can't hear when it's finished washing a load of clothes. And you, like me, have the memory of a goldfish and will completely forget and leave the clothes in the washer for days. This is an attempt to help out with that problem. Using this attachment, you can create a reminder, hook it up to a button on a keypadlinc in the basement, and have an announcement made when the laundry is done after, say, 30 minutes. It can also create a pester so that it repeats the message every 5 minutes until you cancel it or it runs out. 

Pesters can be created outside of a timer as well if you like, so, for instance, you can use pesters in other situations.

To install this attachment script, drag the Reminders.scpt file to the following location:

/Library/Application Support/Perceptive Automation/Indigo 4/Scripts/Attachments/

Select "Reload Attachments" from the "Scripts" menu in the Mac client to have the attachment loaded.

The script and it's handlers are described in detail inside the script, but for completeness, here is a list of handlers in this script (the type in parenthesis before the handler is the return type):

-- (boolean) createReminder(theName, actionList, reminderValueInMinutes, pesterCount, pesterFrequencyInSeconds, pesterActions,finalPesterAction)

-- (boolean) cancelReminder(theName)

-- (boolean) createPester(theName, pesterCount, pesterFrequencyInSeconds, actionList,finalAction)

-- handlePester(theName, shouldCancel, pesterFrequencyInSeconds)

-- cancelAllPesters()

-- (string) makeStringListIntoString(theStringList)

Here is a definition of the parameters for each handler:

------------------------------------------------------

This is the script that's shipping with Indigo 4.1 (so don't download it unless you're using Indigo 3). It hasn't been tested with Indigo 3, but some users have reported that it works, so we're just providing it here.

Create a startup trigger that runs the script - it's a background script. NOTE: don't call it multiple times or embed it.

Create a variable named _Weather_Fetch_Station and give it the 4 letter code for the nearest NOAA weather center to you. The script will then populate a bunch of variables with weather data that you can use any way you want.

This How-to PDF shows you how to build a relay box so that an Appliancelinc can control a very small load, like LED bulbs.

This solution provides a generic mechanism for defining timers in Indigo.

It's based upon a background task that takes care of decreasing timer values.

All other timer related tasks are done using standard Indigo features like variables and triggers.

That's the brief description. For a full description,  including detailed installation and usage instructions, please see the topic.

The script needs to be placed in the Background Task folder of Indigo.

Next a startup trigger has to be defined that starts this script whenever de Indigo Server starts.

This is a major revision to the original Weather Underground script.

The Wunderground Script will poll a Wunderground Airport Station and/or PWS (Personal Weather Station) and retreive the latest weather information for the specified station code. Data from the PWS and Airport stations can be merged. If more than one PWS is specified, and good data is not available for the first PWS, the script will try the additional PWSs  in order until good data is found. The weather information will be saved into Indigo Variables. Support is provided for weather icons to indicate the current conditions. A basic set of Wunderground icons is included.

Changes in V2.3

This update corrects problems caused by the way AppleScript in Snow Leopard handles dates.

Support for the experimental irrigation control module has been dropped.

Weather reports are now saved to /var/tmp

1) Place this script in Indigo's Background Tasks folder, or any other folder of your choice.

2) Configure the script (instructions are in the script)

3) Create an Indigo Time/Date Trigger and select an Action Type of "Execute AppleScript" that executes this script file. This script file will then be called at the times/frequency you defined for the trigger. 

In Indigo use the Variable Window to enter the codes for the station(s) you have selected

For PWSs create an Indigo variable _Wunderground_PWS_List and set the value to one or more PWS codes separated by spaces.

For example,  KCAREDDI3, KCAREDDI2

For an Airport station, create an Indigo variable _Wunderground_APT and use the airport station code as the value.

This plugin will generate a report for the specified day (yesterday by default) that shows how long each device was on for that day (in minutes). The plugin makes a couple of assumptions:

1. All times are in local time, so the values may be a little odd on days when DST changes.
2. If the first command seen for a device is to turn it OFF, the plugin assumes that the device was on since midnight.
3. For any device whose last command seen was an ON, the plugin assumes that it was on up to midnight.
4. The report doesn't currently include Thermostats, Sprinklers, and IO devices - it does however include some devices that may not make any sense, specifically motion sensors.

This report should be used only as rough insight into what devices in your home are used most. It requires that SQL logging be turned on and SQLite as the database type. The plugin reads all the necessary config information from the IndigoSqlClient.conf file that you must configure in order to make SQL logging work correctly.

NOTE: When the IndigoServer first starts up or switches Indigo Databases broadcasts some device state changes during the startup process that the SQL logger then adds to the log database. Unfortunately, these don't actually represent real state changes. However, from the plugin perspective, it's not possible to distinguish these from normal state changes. Therefore, you may see some days that contain erroneous data. Unfortunately, until we figure out a good solution for those errant changes, you may need to just skip days where you restarted the IndigoServer.

To install this plugin drag the "usageReporter" folder to the following location:

/Library/Application Support/Perceptive Automation/Indigo 4/IndigoWebServer/plugins/

and restart the server. Also, you MUST have SQL logging turned on and configured properly (only SQLite is currently supported).

This plugin will graph the Actual thermostat temperature reading, vs AC & Heating set points.  This is tested against a venstar t1800, but in theory any thermostat that Indigo supports would work…  (But is there any others that Indigo supports?).

In addition, below each graph is a table that contains the raw data.  By default, it is hidden, but clicking on the hyperlink will reveal it.

This does support multiple thermostats…..

1) Download the ZIP file, and unarchive it.

2) Move the “hvac” folder and place it in the following location.

/Library/Application Support/Perceptive Automation/Indigo 4/IndigoWebServer/Plugins

3) Restart the Indigo 4 Server

To Uninstall, just remove the Hvac folder from the Plugins folder, and restart the Indigo Server.

How do you use the Hvac Historical Usage plugin?

Simple, Open your Web Browser, and browse to the Indigo Web server.  From the root of the web server add /hvac.

For Example:

http://entertainmac.:8080/hvac

This application is based on the original Perl script from seanadams. This update packages that script as an OS X app called iHealth. All required Perl modules are included.

iHealth sends Insteon requests to the devices listed in a devices file and measures the response time. Results can help find problem devices or areas that have poor signal propagation.

NOTE: iHealth works on OS 10.5 and 10.6, PowerPC and Intel. iHealth will also run on Tiger, but some problems have been observed. Specifically, the URL passed to Safari to view the report may wrong and the PLM interface may not be brought back online automatically.

Uncompress the zip file and drag the app to the directory of your choice. NOTE: the tool only works with the PowerLinc 2412/2413 - the 2414 isn't supported due to protocol and architectural differences.

Double click on the app and select the options you wish in the GUI window.

iHealth automatically checks to see if Indigo is running, and if it is, the PLM interface is disconnected, and then re-connected after the tests are complete. The GUI provides options for the number of iterations, the location of the output files and the ability to select an existing device file or have the program create one for you.

If you choose to have iHHealth create the device file it will automatically filter out X10 devices and Insteon wireless devices. While iHealth is running, the incremental results of the test process are displayed in Safari and a terminal window tracks the number of iterations completed and the number of devices tested. It is not necessary to save the Safari window since the full report is also saved to disk.

Should iHealth find more than one interface you will be prompted to select the interface to use for testing.

Here’s a relatively quick application to list all your devices via the Web Plugin system of Indigo…

The application will display:

* Device Name
* Description
* Insteon Address
* The Device Type
* The Device’s Firmware level

For example:

Add the plugin to the Indigo Web Server plugin (requires v3.0.6 or greater).

Allows the user / administrator to view the Indigo Log through the Indigo Web Browser Plugin.

1) Download the ZIP file, and unarchive it.  

2) Rename the Folder to “Eventlog” and place it in the following location.

         /Library/Application Support/Perceptive Automation/Indigo 4/IndigoWebServer/Plugins

3) Restart the Indigo 4 Server

To Uninstall, just remove the Eventlog folder from the Plugins folder, and restart the Indigo Server.

This plug-in will allow you to edit variables from a web page (in fact, you can do it without the page but since you can already do that it's redundant). When the edit form is saved, the variable is updated and you're redirected to the control page specified. If you cancel the edit form, you're just redirected to the control page. Another use for this is to have some other process/application/webservice/etc make changes to variables directly: introduces an entirely new integration point. NOTE: requires 3.0.6 or greater, but this functionality is built-in to v4.0.

To install this plugin drag the "variable" folder to the following location:
/Library/Application Support/Perceptive Automation/Indigo 2/IndigoWebServer/plugins/

To use this plugin from a browser, try the url:

http://yourhost:yourport/variable/setVariable?name=your+variable+name&page=your+page+name

You supply the name of the variable and the control page to forward to.

To use this plugin from within the control page editor:

1. In Indigo, open the control page that contains the object you want to click on
2. select the object
3. on the "Click Action:" popup at the bottom select "Link to External URL"
4. in the text box next to the popup, type in the path part of the URL above (you don't need the http://yourhost:yourport/ part). Don't forget to replace spaces in the Control Page names with the plus sign (+). If your control page name has any other special characters in it (:/\&? for example) you'll need to URL encode it before you type it into the box. So, if you had a control page named "Control:page/with?strange&characters@in#it" the URL encoded version would be "Control%3Apage%2Fwith%3Fstrange%26characters%40in%23it". You can go to this handy site to URL encode a string: The URLEncode and URLDecode Page
5. try it!

born from the need for quick loads and simplicity – especially on an iphone. these are replacement mini views for indigo, home automation software for macs in the form of a plugin! instructions for install, and downloads are actively maintained at:

http://github.com/seaofclouds/indigo-mini-view-plugin

this plugin is currently stable, though it is still in development. please follow the status and discussion at: http://www.perceptiveautomation.com/phpBB2/viewtopic.php?p=20078

NOTE: because this is an IWS plug-in, it requires Indigo 3.0.6 or greater.

This plug-in will allow you to perform some Indigo action then redirect to a control page: the idea being that you might have a control on a page that you want to click which could then do something and end up on a different (or the same) control page afterward. NOTE: requires 3.0.6 or greater, but will NOT work with 4.x+ (this functionality is built-in).

To that end, there's currently one function in this plugin, execGroup, which takes an Action Group name and a Control Page name. It executes the Action Group and then forwards to the Control Page.

To use this plugin from a browser, try the url:

http://yourhost:yourport/execAndGo/execGroup?name=your+group+name&page=your+page+name

You supply the name of the action group to execute and the control page to forward to

To use this plugin from within the control page editor:

1. In Indigo, open the control page that contains the object you want to click on
   
2. select the object
   
3. on the "Click Action:" popup at the bottom select "Link to External URL"
   
4. in the text box next to the popup, type in the path part of the URL above (you don't need the http://yourhost:yourport/ part). Don't forget to replace spaces in the Action Group or Control Page names with the plus sign (+).
   
5. try it!

Just a few device icons I created for myself.

• Antique Lamp
• Crystal Lamp
• Palmtree Lamp
• Seahorse Lamp
• Large Seahorse Lamp
• Small accent uplight

These should go into your /Library/Application Support/Perceptive Automation/Indigo 4/IndigoWebServer/images/controls/devices/  folder.