All versions of Indigo include support for the following device types: Z-Wave, INSTEON, and X10 (click on the types for details of how to manage devices of that type). The first thing that you need to select is the Type. Indigo also provides you various ways to interactively control these devices and inspect their state (Indigo Touch, Indigo Web Server web pages, etc.) when the motion sensor detects motion) and you can tell a device to perform some action (e.g. There are two primary ways you can use a device in Indigo: you can use changes in its various states to trigger some actions (e.g.

This greatly expands the kind of devices that can be defined in Indigo.

Not only can Indigo interact with Z-Wave®, INSTEON, and X10 devices but Indigo Pro also supports devices provided by third party plugins. Next, we want to go into a little more detail about each of the main object types to help you understand when and why you would want to use them.ĭevices in Indigo are “things” that Indigo can interact with. If you don't find what you're looking for there, check out our Glossary of Terms which includes just about every term we can think of that you might run across. That is the very high-level definition of the primary objects in Indigo. Either a fixed point in time ( at 1:00pm) or more likely some repeating time (every day at 1:00pm).Īction Groups are collections of actions that may be reused (and modified) easily between multiple triggers, schedules, and control pages and executed via various clients (the Mac Client, the Indigo Web Server (IWS) web pages, Indigo Touch, etc).Ĭontrol Pages are user-created interfaces to control their Indigo system - for instance you could create a graphical floor plan with light icons in the various rooms.Ī variable is a place where your home automation logic can store information that changes during the normal operation of your home and that can be used in other parts of your system: for instance, you can have a variable that represents whether your home is occupied or not - then you can have special automation logic that takes place when that variable changes. Indigo can use that event to execute actions in response.Ī schedule is similar to a trigger, but the event that causes the execution of the actions is a temporal event of some kind. A device is any “thing” that Indigo can interact with - usually it's some kind of hardware (light switch, appliance module, motion sensor, etc), but devices can also be other non-hardware things (iTunes server, calendar, etc).Ī trigger is generally some kind of “event” that occurs.

Indigodomo