brock.travis

That answered all of my questions. I really appreciate it!

When you link these devices through the ISY, (for example a switchlinc and lamplinc) is that relationship stored within the switchlinc, the PLM or the ISY? Are scenes stored in the devices that are members of the scene or in the PLM when the scenes are created though the ISY? I plan on setting up a keypadlinc and IOLinc to operate a garage door. Can I set up this relationship so that the button LED informs me of the IOLinc status using just the ISY? I understand how to do this already with the set buttons on each device, but I want to know if it can be done through the ISY and still respond accordingly if the ISY or PLM were removed. All in all, I don't want to handicap my entire network should the PLM or ISY malfunction. I would also assume the commands would execute more quickly if the linking information was stored in the devices rather than the PLM as every command would have to go through the PLM first. I'll be setting up programs for more advanced operations such as sprinkler control.

I am about to start building my INSTEON network using the ISY-99 PRO as my primary controller. My question is, can you program all of your devices (linking, multi-linking, cross-linking) from the ISY interface and never have to do any manual linking what so ever? If the ISY is removed from the network, will those devices remain linked and still function as though you never had the ISY in the first place? Can I do all of my programming without any manual linking and use only the INSTEON addresses? The reason I ask is that I will most likely be installing a few devices out of reach where it would be a near impossibility to press the set button and run to another device in order to link them. I'd like to program my entire system from the ISY alone, but not have my system fail should the ISY no longer be available to each device. I believe I read that the ISY writes configuration to each device individually rather than hosting the "running" config on its own internal database.