LeeG

The flashing LED indicates the RemoteLinc has not received an ACK for one or more Responder devices. Replace the batteries first. Simple and has no adverse effects. If that does not resolve the situation, try moving the RemoteLinc closer to an Access Point to see if something is reducing the effective range of the RemoteLinc. It is possible the PLM link database was damaged by the power problems. The RemoteLinc is automatically linked to the ISY PLM as a Responder so the RemoteLinc has to talk to whatever device it is controlling (unless done through a Program) as well as the ISY PLM for each button press. Restoring the PLM will rebuild the PLM link database but this could take some time as other devices may be accessed during the process. If the RemoteLinc is the only device having a problem it might be easier to just delete the RemoteLinc and add it back to the ISY. It will have to be added back to the Scene(s) but again this may be quicker than a full PLM restore IF THIS IS THE ONLY DEVICE having a problem. Posting an Event Viewer trace with Device communications events selected might help if the batteries do no fix the problem.

There is always going to be disagreement over what “Scene On†means. A Scene that turns some devices On, some devices dimmed and some devices Off (common home theater scenario); if one of the devices that was physically turned Off by the Scene On command is turned On independently, does that mean the Scene is Off because all the Responders are not in the original Scene initiated state. I’ll bet if I asked three people that question I would get six answers. Perhaps something like “If Scene device Status = Scene definitionâ€. That is still problematic as there are situations where the exact state of a device cannot be known without a Query which should never be used to determine second by second state. It could be process intensive to check the Status of dozens of devices against the defined Scene status. Something an application running on a PC does not care about but could be a consideration for a small (by comparison) dedicated processor. Bottom line, the ISY has no such feature. There is a Product Request topic where new ISY features/functions can be requested.

Although I am running with a 2412S at present I tried the 1223PS. It does fit my 1+ year old ISY-99i Pro/IR. It would be helpful to know what does not fit.

The ISY User Guide indicates the following ... 5-30 VDC 300 mA minimum Center positive 2mm male barrel jack What part does not fit? The hole in the back of the ISY is not large enough to accept the barrel or the center pin does not fit inside the barrel?

A technique that has been useful is to connect a wired device to an Appliance cord that has a plug on one end and bare wires on the other. Plug the Appliance cord near the PLM and see if things improve. I would expect good communication when receiving power near the PLM. I have not seen a device that would not at least ACK the basic Set MSB, Peek commands (except for motion sensors and triggerlincs which are exceptions to keep memory size small). The Set MSB and Peek commands have been Depreciated for years but there is so much software in existence today that uses these commands I really don’t think Smartlabs did away with them for KPLs. Also a few of the commands were ACKed even though the majority failed to get any response.

The trace looks like a comm problem. Note the 9 second elapsed time between the commands being issued which did not receive a response from the device for the first two attempts. Mon 06/13/2011 04:42:44 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:42:53 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:02 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:03 PM : [iNST-SRX ] 02 50 12.3A.85 13.24.AA 23 28 02 SET-MSB(02) Same thing with the other device. No response to these three commands. Mon 06/13/2011 04:43:09 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 2B 64 06 PEEK (64) Mon 06/13/2011 04:43:18 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:27 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:31 PM : [F C1 DE 1 ] Memory : Write dbAddr=0x0264 [00] - Failed

This is Michels response last week ... Brian, if and only if you have 994 with Zigbee enabled. So, this is a bug. Thanks for reporting. With kind regards, Michel

The master bathroom motion sensor is mounted in the bathroom above the entrance doorway. There is a slight delay in entering the motion sensor field of view but I did not want any false trips. I do not change the On Level based on time for the bathroom lights. They turn On at mid level with the ability to override the timed Off with a press of a KeypadLinc button. The override turns the lights On to full bright. I've had a standard motion sensor built into a wall switch for the walk-in closet light for many years. Was not sure if a motion sensor for the bathroom lights was a good idea. I could not do without it now. As a side benefit the light bulbs last much longer.

This is an example of changing the Local On Level and Local Ramp Rate at different times of day. Times are obviously for test purposes only. At 6:37 PM the Local On Level is set to 60%. At 6:38PM the Local On Level is set to 100%. If changing Responder values, the In Scene parameter would be the name of the Controller with the Set parameter the name of the Responder. If From 6:37:00PM To 6:38:00PM (same day) Then In Scene 'SwitchLinc Dimmer' Set 'SwitchLinc Dimmer' 60% (On Level) In Scene 'SwitchLinc Dimmer' Set 'SwitchLinc Dimmer' 2.0 Sec (Ramp Rate) Else In Scene 'SwitchLinc Dimmer' Set 'SwitchLinc Dimmer' 100% (On Level) In Scene 'SwitchLinc Dimmer' Set 'SwitchLinc Dimmer' 8.5 Sec (Ramp Rate) This example has been tested and functional on 3.1.3 .

iostream212 Use the “Adjust Scene†Action to adjust the On Level and/or Ramp Rate of the Responder. Be sure to select the Controller that will be used to affect the device in question. If the Local On Level and/or Local Ramp Rate is to be changed select the device for both the “In Scene†and “Set†parameters. Note that some devices must be power cycled for the changed Local values to have an effect which makes time based changes impractical. If neither of these covers what you are looking for please post additional information. Lee

My IRLinc Tx shows correctly. Each button node is displayed under My Lighting.

IE8 on XP, Java 1.6.0.23_b05, do not see problem on 3.1.3.

1. Does that mean that I can cross link any two Switchlincs I have installed and make them into a quasi 3-way circuit? Yes. Not limited to SwitchLincs. You can cross-link any number and type of Insteon devices so long as the device has Controller capability. 2. Are they cross linked through the ISY admin console only? In other words, they cannot be cross-linked outside of the ISY console? Cross-linking is just another term for Scene and all Scenes must be created by the Admin Console. That is a logical rule, not a physical rule. If you link outside of the ISY using Set buttons and/or paddle presses ISY will not be aware of the link and can overlay the link records. 3. If I cross link switch A and switch B, when I press either switch, do lights A and B both come on? Yes. Is that not the neatest thing! 4. Do I understand you correctly that I cannot put a dimmer Switchlinc in if it is controlling a normal outlet? It has to be a simple on/off switch? It is against electrical code for any type of dimmer to power an outlet. If the outlet was accidently dimmed and an appliance plugged into the outlet like a TV or vacuum cleaner the appliance could be damaged. A dimmer could be linked to a SwitchLinc relay or KeypadLinc Relay that is controlling the outlet. The Insteon device that has the Red Load wire connected to the outlet must be a Relay device. 5. When you say some of the traveler wires have to "retasked", what does that mean exactly? Is there a primer you can point me to? The Smarthome User Guides for the various devices have diagrams that cover some of the basic 3-wire circuits and how they have to be changed. One of the 3-way switches does not have unswitched 120V AC. That is the nature of a 3-way circuit. Most 3-way circuits are simple and easy to convert so that unswitched 120V AC is run to all the Insteon devices. Some circuits get very messy with power running to the fixture being controlled rather to one of the 3-way switch locations. If you cannot figure it out from the diagrams in the User Guides I suggest getting an electrician or neighbor who has electrical knowledge. There are some current and retired electricians on the Smarthome forum who are very good at walking folks through a 3-wire change. To cross-link Insteon devices, define an ISY Scene. Right click on the SwitchLinc, KeypadLinc button, ICON, etc node in the My Lighting tree and select Add to Scene. Add each switch as a Controller of the Scene. The ISY assumes the device is also a Responder if the device has Responder capability. When all the switches have been added to the Scene as a Controller the ISY will write all the link records necessary for each switch to be able to turn the Load On/Off and keep the other switches status LEDs in sync.

Kentinada A. Both switches have to be Insteon devices. Insteon devices are not like standard 3 way switches. All wired devices must receive unswitched 120V AC which means that some of the traveler wires will have to be retasked. Insteon devices function as 3/4/5 way devices by being cross-linked together rather than an wired together. B. Yes, one can be a SwitchLinc or ICON, one can be a KeypadLinc. To control an outlet the device that is actually controlling the load must be a Relay device (not a dimmer, dimmer would be against code). C. The OutletLInc would not be controlled by the existing 3-ways switches. As with all wired Insteon devices the OutletLinc must received unswitched 120V AC (except 220V load controller which runs on 220V). Lee

Kentinada Happy to help. You will find all the users on the ISY forum of great help, ready to provide information and suggestions. The UDI personnel provide the best ISY support in the business. The best group of folks I have had the pleasure of interacting with. Hope you find the ISY as much fun to work with as the rest of us have. Lee

Kentinada The On Level (Applied Locally) and Ramp Rate (Applied Locally) relate to what the device does when turned On locally with a button/paddle press. Ex, how a SwitchLinc responds when the SwitchLinc paddle is pressed On. For each Controller of a Scene, the Responders have an On Level and Ramp Rate the Responder will react with when that Controller activates the Scene. Clicking on the Scene name shows the Responder values when the Scene is turned On with a Program or through the Admin Console. Clicking on each additional Controller of a Scene (entry below Scene name in Red), the Responder values (On Level and Ramp Rate) are those the Responders will react with when that Controller turns the Scene On. This is all standard Insteon stuff. The ISY makes it easy to define but the Insteon Responder hardware is actually using the various On Level and Ramp Rate values based on which Controller turned the Responder On. The Responder On Level and Ramp Rate are stored in link records in the Responder link database stored in the respective Responder memory. Lee

"Do I create a scene so that I can activate that single scene to control multiple devices at once thus simplifying my programming?" That is one reason for defining a Scene. Responders in a Scene react simultaneously to Scene commands. The same thing can be done in an ISY Program turning individual devices On/Off but the devices react sequentially rather than simultaneously. Also some devices can only be controlled with a Scene. KeypadLinc Secondary buttons must be turned On/Off with a Scene. KPL Secondary buttons cannot be turned On/Off with Direct commands. "I am still notmsure why you would add a controller device (remotelinc or keypadlinc) to a scene." Every Scene has at least 1 Controller. If only Responder devices are added to a Scene the only Controller is the ISY PLM. The Scene can only be turned On/Off with an ISY Program or through the Admin Console. If other Controllers are added to the Scene, such as a KeypadLinc button or RemoteLinc button then the Scene can be controlled from the Controller button and through an ISY Program or Admin Console. If the Controller button has an On/Off indication, such as a KPL button which has an underlying LED, that LED will turn On/Off when the Scene is turned On/Off by other Controllers of the Scene. When a device is added to an ISY Scene as a Controller it is assumed to also be a Responder if the device has Responder capability. A KeypadLinc button added as a Controller is also assumed to be a Responder. A RemoteLinc button added as a Controller is not assumed to be a Responder as a RemoteLinc had no Responder capability. If this does cover all the questions please post back.

Yes, each RemoteLinc button can be a Controller of an ISY Scene. Define an ISY Scene. Right click on a RemoteLinc node and select Add to Scene. The responders are added to the Scene the same way. Unlike say a KeypadLinc, RemoteLinc buttons cannot be turned On/Off programmatically. Remember the RemoteLinc must be put into linking mode by pressing the Bright/Dim buttons together until LED blinks continuously for Scene updates to be written to the RemoteLinc.

Yes, the Zone valve connections would be moved from the existing controller to the EZFlora. The EZFlora supports 8 Zones. The UDI Wiki has a discussion of a sample set of ISY Programs for controlling the EZFlora zones. Basic Zone control is as simple as using an ISY Program to turn On/Off an EZFlora Zone at a particular time. The Zones can be turned On/Off through the Admin Console, just as lighting can be turned On/Off. Note that one Zone can be turned On at a time. Turning On a Zone turns Off any other Zone that may have been On.

captfisk The If is not correct. It should be Sunrise -1 hour (next day).

Kentinada Access Points are not added to the ISY. They have no options, no configuration, no link information. It would serve no purpose to define them as devices the ISY is aware of. The PLM is interfaced to through the Serial interface connection on the PLM. The ISY is aware of the PLM through the Serial interface and is not explicitly added to the ISY either. Lee

thruster999 Have Programs been exported and then imported on a different ISY backup level from which they were exported? Lee

captfisk Was some of the primary ISY information copied/exported to the summer ISY? Lee

captfisk The QueryAll Program on my system looks like the following .... If Time is 3:00:00AM Then Set Scene 'My Lighting' Query Else - No Actions - (To add one, press 'Action') I have no explanation for the Not Specified. This Program is a backup if the powerline has issues. I have disabled this Program on my system as I want to know if a powerline problem has surfaced. Assuming the Program is enabled the effect is to Query all the installed devices at 3 AM. In case any device status change was not received by the ISY/PLM the Query will bring the Current State information in sync with actual device status. Were any of the Dual Band devices verified to be on opposite phases? "I have to login to the summer home SY to operate the lights." Meaning some other means of operating the lights are not working? What other method is not working and is there some symptom, message, etc besides the device(s) not reacting?. Do any of the nodes under the My Lighting tree have a Red ! to the left of the node entry? Lee

captfisk What is difference in the QueryAll Programs?. What is the symptom at the vacation home? Programs don't run, devices not reacting, etc? What Insteon devices are installed? Did the Access Points show the correct LED result for proper phase coupling? What ISY firmware level is installed? Lee