creeble Posted October 31, 2011 Posted October 31, 2011 Hi all. I'm new to Insteon and the 99i, and I'm trying to figure out the best approach to programming my system (for which I haven't quite acquired all the parts). I've got a pretty modest 16-channel x10 system now that I'm planning on replacing. I've been using a device called WebIO to program the x10 system, in combination with a controller program I wrote myself (in Perl, on a Linux server machine that's up all the time). It has served my needs very well, doing mostly simple time-based events: sunset-30, turn on these, sunset+30, dim these. All Units Off at the bedside is probably the #1 function (no programming required). Nothing very fancy at all. My question is, what's the best/easiest methodology to use to do the same things in the 99i? At the moment I've only got two Insteon lamp modules, a ControlLinc and a RemoteLinc, but I will be replacing all 20 or so modules in due course. It seems like I need a Scene for each group of lights that I want to control, then a program for each event -- which may mean multiple, redundant programs? For example, in my current x10 programming, many lights come on at sunset-30, but then only a few dim at sunset+30. So I gather that I need a Scene for each unique group of lights, and then a sunset+30 program (perhaps only one, with multiple actions in the Then clause?) to adjust them. Does this sound right? Finally, how does one do an All Units Off command? Presumably I need a Scene with all the responders in it, tied to one (or more) controllers? Thanks for any help, I'm looking forward to the increased reliability and flexibility! Okay, wait, one more question: To control my existing x10 switches (it's going to take me weeks to replace all of them as I'll probably need to run some neutral wires to boxes), I just need to upgrade (software) on the 99i to include the x10 module?
LeeG Posted October 31, 2011 Posted October 31, 2011 Creeble The implementation will consist of multiple Scenes and multiple ISY Programs. To have a group of devices react together at the same time the easiest way is to define a Scene with the specific devices as Responders and an ISY Program that triggers with the appropriate condition. For several of your examples the ISY Programs would be triggered at a specific time, Sunset -30 as an example, turning the appropriate Scene On. A Program can have multiple Actions if needed. As a Scene can have some devices turn On full, others turn On to different % On and even some turn Off the decision is more when things happen as far as whether different Scenes are needed. The All Off is simple. Assuming it is driven by a button on a Controller (RemoteLinc button for example) an ISY Scene is defined with the RemoteLinc button as Controller and whatever devices should turn Off as Responders. No ISY Program is needed in this case. Pressing the Controller button Off turns all the Responders Off. The All Off function can be driven from multiple Controllers simply by adding additional Controller buttons/paddles as Controllers of the Scene. Multi-way switch configurations also require an ISY Scene. If 3 Insteon devices control the same load, one directly and two indirectly in a virtual multi-way configuration, one ISY Scene with all three devices defined as Controllers is used. This cross-links all the devices such that any can turn On/Off/Dim the load and the other switches status LEDs will stay in sync. The optional A10/X10 Module is not needed for an ISY Program to control X10 devices. ISY Program Actions can turn On/Off X10 devices with the option Module. The optional module allows X10 devices to the defined in the My Lighting tree as Insteon devices and refer to the symbolically. Hope this helps get you stated. Post back any additional questions as needed. Lee
creeble Posted October 31, 2011 Author Posted October 31, 2011 Thanks for the swift reply, Lee! I'm still just a bit confused about two things: First, to turn *all* devices off, I still need a Scene with *all* of the devices in it, correct? I mean, there's no general "broadcast" equivalent to "all units off" like x10? Also, when you say: The optional A10/X10 Module is not needed for an ISY Program to control X10 devices. ISY Program Actions can turn On/Off X10 devices with the option Module. The optional module allows X10 devices to the defined in the My Lighting tree as Insteon devices and refer to the symbolically. I think I understand; I can just call the X10 device by name and function (I10 dim, for example) to control X10 with the "stock" 99i, but the add-in module allows me to name them and use them more interchangeably like Insteon devices. Right? Do I also understand correctly that a 99i Scene actually sets up the link tables for the Insteon devices, such that the 99i isn't actually called upon for direct controller->responder actions like turning a "scene" (said group of responders) on and off? Like in your example of a three-way switch? Best, Eric.
LeeG Posted October 31, 2011 Posted October 31, 2011 Creeble “First, to turn *all* devices off, I still need a Scene with *all* of the devices in it, correct? I mean, there's no general "broadcast" equivalent to "all units off" like x10?†There is no Insteon function that can be put on the powerline in the blind (like X10 messages) that turns All device Off. A few devices such as the RemoteLinc have an All Off button but this still requires links between the RemoteLinc and its Responders. A Scene with the devices that should respond to the All Off is the approach. †The optional A10/X10 Module is not needed for an ISY Program to control X10 devices. ISY Program Actions can turn On/Off X10 devices with the option Module. The optional module allows X10 devices to the defined in the My Lighting tree as Insteon devices and refer to the symbolically. “ My apologies, I missed a “not†- ISY Program Actions can turn On/Off X10 devices without the optional A10/X10 Module. The optional module allows symbolic reference to X10 devices by name but does not provide any new X10 functional capability than the basic ISY. “a 99i Scene actually sets up the link tables for the Insteon devices, such that the 99i isn't actually called upon for direct controller->responder actions like turning a "scene" (said group of responders) on and off?†That is absolutely right. Scenes that have Insteon devices as Controllers and Responders have links between the Controller(s) and Responder(s) such that the ISY is not involved in the interactions. The ISY could be powered down or under maintenance and the device to device control is fully functional. This is the way Insteon itself works. The ISY PLM needs to be powered as button/paddle presses inform the ISY PLM of the action. If the PLM itself is not available the Controller will retry the communications with the PLM causing unnecessary powerline traffic. Lee
creeble Posted October 31, 2011 Author Posted October 31, 2011 Ah, great, thanks Lee! You added one bit there -- the PLM actually holds the link between the controller(s) and the responders in a scene then? Got it, so the PLM does indeed need to stay up for those links to work. Thanks for the help. I'm sure I'll be back on here after I get a little further into my install... Best, Eric.
LeeG Posted November 1, 2011 Posted November 1, 2011 creeble The Controllers and Responders themselves hold the link records that allow the Controller(s) to turn the Responder(s) On/Off. These links are created by ISY based on Scene definitions and operate independent of the ISY or the ISY PLM. There are links between all Controllers and the ISY PLM. These are created when each device is added to the ISY and allow the ISY to keep track of individual device state changes as well as trigger Programs based on button/paddle presses (state changes). It is the links created when the device is added to the ISY that requires the ISY PLM to be functional all the time to avoid powerline communications errors when a button/paddle is pressed. Lee
creeble Posted November 1, 2011 Author Posted November 1, 2011 Terrific, I completely understand. Thanks, Lee. I've got a lot of wiring to do... Eric.
Recommended Posts