Indigo 2.0.5 now supports the new INSTEON EZIO8SA, EZIO2X4, and EZIO8T. These are general purpose input/output modules that include binary inputs, analog inputs, 1-wire sensor inputs, and outputs (triacs and relay). They can be used to control and monitor low voltage devices such as contact closures, landscape lights, relays, valves, alarm systems, etc.
Indigo supports turning the individual outputs on/off, as well as uploading the output auto-off delay durations.
Indigo also supports defining the alarm trigger points for the analog and 1-wire inputs. To create Indigo Trigger Actions based on binary inputs changes (or the alarm thresholds are passed on the analog or 1-wire inputs), use the Trigger Action type Device State Changed. From there, once you have selected an EZIOxx device, you'll be able to create Indigo Triggers whenever the binary input states change.
Note that trying to create Trigger Actions on the type INSTEON Command Received will not work because Indigo does not create links in the EZIOxx for the individual inputs. Instead, Indigo sets a flag in the EZIOxx which has it broadcast an INSTEON Status Changed Broadcast message to Indigo. Therefore, the only INSTEON command that will ever be received during an input change from an EZIOxx is the Status Changed Broadcast (ON commands for the individual inputs will not be sent to the PowerLinc). This is why you must use the Device State Changed trigger. It will let you create Triggers based on when specific input value states change versus just a global "something changed" trigger.
Also note there are some improvements to the Control Page editor which allow you to show the state of a specific EZIOxx input or output. These changes also let you show the on/off status of a specific sprinkler zone. Here is an example of a EZIOxx Control Page in action:
http://goprism.com:8000/controlpage?name=ezio8sa_example
Some older EZIOxx firmware versions aren't compatible with Indigo because they don't broadcast input status changes. Those units can be returned to SimpleHomeNet to be updated. I believe that change went into firmware version 1.4, but I'm not positive.
Hopefully, this will be enough to get folks started! As always, let me know if you find any bugs/issues.
Regards,
Matt