Switchboard is an evolutionary replacement of the Indigo Security Script.
The name change is due to the show the difference in the product. Switchboard monitors the other devices, and , and dispatches new commands as needed.
The previous “generation” of security script had a much more limited ability to monitor devices, it could only monitor Security sensors (e.g. DS10A, Big Red Button, Triggerlincs, etc).
Switchboard changes this. It treats all devices the same, so you can monitor non-security devices, as well security devices… This allows you to simply to monitor your door sensors, as with the v4 Security Script, but now you can also monitor your bedroom lights, or anything else in Indigo’s database.
Yes, some of this can already be done in Indigo by making a trigger action… But Switchboard goes beyond this functionality.
What does Switchboard add to Indigo?
- Selectively monitor X10 and/or Insteon Traffic (for plugin purposes.)
- Monitored Device Groups
- Timed Device Profiles
- Monitored X10 Security Devices
- X10 Security Center (Work in Progress)
What do these plugin devices do?
The Monitored Device Group is the backbone of the plugin.
Each Monitored Device Group represents area, region, or just simple a bunch of devices to be monitored. Some Examples are Exterior doors, Garage Door Entrance, or Basement Water Monitors.
- Registered Devices for this Group contains the devices that are associated with this Monitored Group. When a registered device is detected, any Timed Devices or associated Action Groups will be triggered.
- Turn on Timed Device Support, will automatically trigger an associated Timed Device
- Turn on Action Group Support, takes the type of action (e.g. Open, Closed, TurnOn, TurnOff, etc) and will run an action group that you designated in the text field and append the action to the Action Group name. For example, if the Action Group name is “Kitchen”, when a door sensor is opened, it would attempt to run the “Kitchen_Open” Action Group.
The important difference between indigo’s triggers, and this, is that the plugin will automatically launch the multiple action groups. There is no need to create multiple triggers for the Monitored Devices.
The current list of actions that are recognized, and the Action Group names, are:
- On (XYZ_On)
- Off (XYZ_Off)
- Open (XYZ_Open)
- Closed (XYZ_Closed)
- Armed (XYZ_Armed)
- Disarm (XYZ_Disarm)
- Panic (XYZ_Panic)
- LightsOn (XYZ_LightsOn)
- LightsOff (XYZ_LightsOff)
Please keep in mind, that the Action Group suffix is Case Sensitive (XYZ_LightsOff is not the same as XYZ_LiGhTsOff).
- Turn On Email Support, will email the comma separated list of email addresses, when a device in the Monitored Group is triggered. You can set it to only email when “Opened” or “Closed”.
- Turn on Speech Support, will speak the text when a device in the Monitored Group is triggered. You can restrict this to happening only on a Open or Closed triggering event.
Once these Settings are created for the Monitored Group, the plugin will start monitoring the Insteon and/or X10 traffic for these devices.
Another important feature are Timed Profiles. A timed profile contains the custom settings for a device already defined in Indigo. The concept behind the Timed Profiles is that you may want to setup a device to automatically turn on & off when triggered. The Timed Profiles allow selective control on the device, so that it is only triggered when Activated, or De-Activated.Once again, this allows more complex arrangements then the standard trigger actions will allow, but without some of the complicity.Activate this Device When this Profile is used, indicates which device you will be controlling with this Profile.After the device is activated, do not activate again for, allow you to prevent the device from being triggered, to rapidly. For example, a Door Sensor set to trigger a door chime, would probably not want to be set for Always Activate. Why? Simply due to how often the door is triggered. If the chime is being set off every other minute, that will quickly get on someone’s nerves. So you can simply set the profile to only allow it to be activated again after XX minutes.Your options are:
- Always Activate
- Activate again after 1 minute
- Activate again after 2 minutes
- Activate again after 5 minutes
- Activate again after 7 minutes
- Activate again after 10 minutes
- Activate again after 15 minutes
- Activate again after 30 minutes
- Activate again after 1 hour
- Activate again After 5 Hours
- Activate again after 1 Day
Turn the Device on for, allows you to automatically configure this profile to shut the device off after a certain time. Your options are:
- 10 Seconds
- 15 Seconds
- 30 Seconds
- 1 Minute
- 2 Minutes
- 5 Minutes
- 7 Minutes
- 10 Minutes
- 15 Minutes
- 30 Minutes
- 1 Hour
- 5 Hours
- 1 Day
Controlling Variables, is another feature that evolved from one built into the security script. The security script allow the Door Chime feature to be overridden by a variable (“SoundChime”). If set to False, it would prevent the door chime from being used, even if the script was set to use it. (I used the feature to have a “Quiet” way to leave the house, since the variable would be reset a minute later.)
Controlling Variables gives you a similar feature, but without hard coding the variables. If the variable you choose is changed to False, then the Timed Action will not occur. If the variable is true, then the Timed Action will occur.
For example, the chime for the exterior doors in my house, is set to turn on the X10 Chime. Do not activate again for 3 minutes is set, and the Controlling Variable is “SoundChime”. Along with that, it is set to Selectively be controlled on Activation Only.
The Selective Controls, will restrict the Timed Device to only activate when an Activation (e.g. Open, Sensor Opened, etc) or De-Activation (e.g. Closed, Sensor Closed, etc) is detected.
A good example, is for a door or window sensor, you may only want an Alert (e.g. Door Chime) to activate when the door is opened.
The next major improvement with Switchboard, is the Addition of Monitored X10 Devices. The main intent is to allow X10 Security devices to be first class citizens in Indigo’s database, since Indigo does not directly support X10 Security devices.
Before this plugin, X10 Security devices needed to use an Applescript attachment script (for Indigo v4 or less). In Indigo v5, X10 data is available to Python plugins written specifically for that purpose.
Isn’t this just something that Indigo triggers and Action Groups can do?
This one I’m not following very well. Seems to me like again what you want is to provide a custom action that starts some action, part of it’s config would be to specify a duration. That way, the action can be used in any trigger/schedule. Maybe it’s multiple actions depending on what needs to happen during the activated period. It’s possible I’m just not getting what you’re trying to accomplish here though. You’ll definitely want to provide separate actions to cancel a currently in progress action.
Once again, remember, that this is a generalization and expansion of the Security script.
Let’s say a door opens, and you want to be alerted. The security script could activate a “Chime” and turn it on for a set amount of time. Switchboard allows any Insteon / X10 device that is in Indigo’s database to be used, as the trigger.
The most obvious choice is that if DOOR X is opened, activate the Hallway light for 7 minutes, and then automatically turn it off. Yes, you could customize a trigger to do this, but the entire idea of the Switchboard / Security script is that you don’t need to make triggers, the plugin or script handles it for you. You just need to tell the script / plugin what it should do.
Yes a trigger can automatically turn off the device, but then you need to know what trigger to update if you change it. With Switchboard, you are making a “Timed Profile”, that contains the information on what Device you wish to control, and for how long to keep the device on for, and how often the device should be triggered.
How Often the device should be triggered, you are asking? Yes, remember, this has evolved from the Security script. A Door alarm chime, if it went off every single time might become annoying. It can be set to Every Time, or to ignore requests for the next X Seconds/Minutes…. This can’t be done with plain triggers….
Yes, there is some duplication of features (e.g. Triggers) between Switchboard and the built-in Trigger functionality in Indigo. And yes, if the user wanted to set down and write a ton of triggers the functionality could be duplicated without the plugin.
But consider a real world comparison that will highlight the difference between the Indigo (Native way) and using Switchboard.
If you were to try to duplicate Switchboard’s ability, you would need to create at least 2 (or more) triggers for each device you wanted to monitor. Of course, that number will vary, depending on what statuses the device can generate. This means at least 2 (On & Off), but other statuses are possible (e.g. Panic, Alarm Armed, Alarm Disarmed, All Lights Off, All Lights On, etc). For each status that you want to monitor, that another 2 triggers.
Let’s say that we are going to monitor 6 devices, and let’s simplify the scenario, and say they are ApplianceLincs… That’s 12 triggers to that you would need to create, and maintain. If it’s a LampLinc, that’s at least 24 triggers (On / Off / All Lights On / All Lights Off)…And don’t forget creating at least two action groups (On / Off), that you will associate with those triggers.
This plugin would require a single MonitoredDeviceGroup, the 6 devices would be added to the device group…. Assuming they are Insteon devices, you wouldn’t even need to create a “special” device, you would just enroll the 6 devices from the Indigo Device List. Click On the Use Action Group Check box, and type in the root name of the Action Group. You would just need to type the Action Group root name in once…
