LeeG

jdheltne Sorry, I had to go out for a few hours. oberkc has you covered in both his answers. I would only add that the reason the Program is using a Scene with KeypadLinc button D as a Responder to turn On/Off button D LED is that a Secondary KeypadLinc button cannot be turned On/Off directly. A Secondary KeypadLinc button has to be turned On/Off with a Scene. oberkc Thanks for jumping in with all the good information.

Look at the user Guide for the Dual Band devices you are using to couple the 2 120V legs. It describes the test process and what the test verifies. Most houses in the US have 2 120V legs. Insteon signals have a hard time getting from one leg to another because they have to travel out to the utility transformer and back to get on the other leg. The Insteon signals are generally degraded by that time and cannot control devices power from the other leg. All of this is explained on every Sales page and every device User Guide. Dual Band devices are used to put the Insteon signals on the other 120v leg from where they originate.

Sorry, I did not get the multi controller aspect from the last post. Either a single ISY Scene with all the Controller devices/buttons defined as Controllers or a Program that detects the status of a device and reflects that back to other devices/buttons. Perhaps if you lay out the configuration, what devices such as SwitchLincs, KeypadLinc buttons, etc that you want to participate and exactly how they should participate would help. What devices should control what, what devices should reflect status of other devices.

The other thing is AV, Avast and another name that does not come to mind can get in the way.

GMD99 If the download was done with safari it unzips the file by default which must not happen. If the file was unzipped download again with the option that does not unzip.

Did the ELAM issue a 0x0D command? The FanLinc does NAK the 0x0D command, the event trace would indicate the ApplianceLinc does not NAK that command. The ISY took the 0xFF as an I2CS indicator and issued the I2 command to put the ApplianceLinc into linking mode which worked as the ApplianceLinc LED started to blink. The PLM command 02 64 should have generated the PLM side of the link with an exchange of information from the ApplianceLinc to the PLM with the ApplianceLinc address, cat/subcat and firmware information. That exchange appears not to have happened since the PLM command did not issue the 02 53 response. I’ll be gone for a few hours this afternoon. Think I will order a new ApplianceLinc when I get back.

That is correct. An Insteon device can be a Controller of one Scene only. Insteon design unrelated to the ISY. If you want the KeypadLinc to turn those devices On/Off create an ISY Scene, add the KeypadLinc button as Controller and the four devices as Responders. Turning the KeypadLinc button On/Off will turn the four Responders On/Off. EDIT: Scenes cannot be cascaded. That is Scene A cannot be added to Scene B. Not an Insteon capability. The individual devices have to be added to Scenes, not Scenes to Scenes.

A 0x02 indicates an I2CS device. I don't think it is a comm issue either. The PLM does not require any changes that I am aware of to support I2CS. All the commands needed have been there, just not needed in this sequence to get a device added to the ISY (or any other application for that matter). Might try a PLM power cycle the next time. The commands being executed to add an I2CS device should produce the same results as if a manual Set button link was being generated. Only being done programmatically without need to press any Set buttons. Do you know if the FanLinc that was added is an I2CS device? The FanLincs I purchased when they first came out are not I2CS. The later ones at Rev 1.05 v.41 are I2CS. If the FanLinc is I2CS and it added successfully with Auto Discover that clears the PLM. I do not think this is a PLM issue unless it was in a bad mode because of some power glitch that also hung up the ISY.

You must have linked the KeypadLinc to the OutletLinc directly with the Set button. That should not be done when using an ISY. The ISY It is not aware of those links and will eventually overlay or delete them. You have a communications problem. As on the other forum where you posted the same issue, it is likely the 2 120V legs are not coupled. The other possibility is the ISY PLM is plugged into a circuit that has other electronic equipment such as PC/UPS etc. If this is the case all that equipment should be put on a FilterLinc to keep the PLM signal from being interfered with. Run the Dual Band device test described in the device User Guides to verify the 120V legs are being coupled. What ISY firmware is being used and how long ago were the OutletLincs purchased. They could be I2CS devices which require 3.2.2.

“Can you use auto-detect to link new I2CS modules in V3.2.2?†I used Auto Discover with an I2CS FanLinc. The event trace shows the I2CS ApplianceLinc and PLM did not complete an exchange. This is what should have happened… Fri 03/16/2012 06:55:49 PM : [LNK-BGN ] 02 64 01 00 06 Fri 03/16/2012 06:55:50 PM : [LNK-STAT ] 02 53 M(01) gid=00 14.9E.F5 012E 41 Note the 02 53 response from the PLM identifying the FanLinc Insteon address, cat/subcat and firmware level. This does not appear in the posted event trace. I would try moving the ApplianceLinc closer to the PLM but I don’t see a comm issue up front as the previous commands sent to the ApplianceLinc worked fine. What is the PLM firmware level?

Was the KeypadLinc button linked to the OutetLinc with an ISY Scene? What happens when the OutletLinc is turned On/Off through the Admin Console? Does the Admin Console indicate a problem communicating with the OutLetLinc? Is there a red ! to the left of the OutletLinc mode in the My Lighting tree?

The ISY Scene that has KeypadLinc button C as a Controller and the SwitchLinc as a Responder, Remove the SwitchLinc from the Scene and add it back to the Scene. When added to the Scene a popup "Confirm Add" is displayed showing the SwitchLinc is a Responder. Click the Controller/Responder button to change it to a Controller. Add the KeypadLinc button to an existing 3-way Scene is the same process as above. Add the KeypadLinc button to the existing 3-way Scene. When the "Confirm Add" popup appears listing the KeypadLinc button as a Responder, click the Controller/Responder button to change it to a Controller.

I'll check that next. I'm on an Alpha where the Query is fixed so I will have to reload 3.2.2. Perhaps the Query problem was found on 3.2.1 and fixed on 3.2.2. EDIT: my apologies, the FanLinc Fan Query does work correctly on 3.2.2

Okay, thanks for that information. I will see if I can recreate. Note that there is a glitch with Query on the Fan side of the FanLinc that does not report the correct Fan state. This will be fixed in 3.2.3. I did not think it affected the displayed Fan state from a KeypadLinc button press. EDIT: Confirmed. The KeypadLinc buttons turn the FanLinc Fan to Low/Med/High/Off as the Scenes are defined but the FanLinc Fan node does not reflect the change in state except for Off.

With the Scenes deleted there is no way to verify but it sounds like the FanLinc Fan Responder On Level for each KeypadLinc Controller button was not adjusted to the required On Level. Setting the On Level for the Scene (when Scene name selected) sets the FanLinc Fan On Level when the Scene name is used. Each KeypadLinc button node listed below the Scene name has to be selected and the respective Fan On Level set for each KeypadLinc button as a Controller. Insteon establishes unique responder values for each Controller. When the Scene name is selected the ISY PLM is the Controller. EDIT: was the FanLinc added to the ISY under 3.2.2?

Without the trace I have no objective information to suggest the next step. I moved to 3.2.2 the day it came out with no major issues.

Looks like the Level was not set to 3-Device communications events. 3.1.17 does not have the Query Insteon Engine. That is a new feature in 3.2.x.

No idea why that response to moving the slider to 100%. Run the requested event trace.

This is part of whay I tried to post before the entry was deleted for some reason. What ISY firmware is being used? It may be the I/O Linc options are being set with I1 rather than I2. If on a 3.2.x beta right click the I/O Linc Sensor node, select Diagnostics | Query Insteon Engine. Then run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Use Set Options to set a Momentary mode, then set it to latching mode and post the event trace.

Check the Responder On Level for the Relay in the Scene. It defaults to a 0% On Level which reverses what the commands do.

In a garage application the I/O Linc relay operates in Momentary mode, turning itself Off after the defined timeout. The I/O Linc Relay does not signal any device it turned itself Off so the Relay node will sit as On forever unless and until a Query is done. If the I/O Linc linked in the house but not in the garage there is a comm problem getting to the garage circuit the I/O Linc is plugged into. It can take dozens of commands that must all execute successfully to add any device. It is not uncommon to have link issues where dozens of commands must work back to back even though the device may control successfully. In this case the device cannot be controlled successfully adding to the conclusion there is a comm problem.

Button H cannot turn Off different Scenes. Button H cannot be defined to turn Off three different Scenes for example. Not possible in Insteon. Create a new ISY Scene that has button H as Controller and all the other devices that should turn Off as Responders. If button H should only turn Off the devices (never turning them On) set button H to non-toggle Off mode. That way when button H is pressed it only sends Off commands. In ISY there are always alternatives. An ISY Program can be written to trigger from a Button H Off command and the Program turn Off multiple Scenes.

Not what is causing it but normmally all that is necessary is exit the Admin Console and invoke it again. No need to clear Java cache.

gviliunas Right click the IOLinc Sensor node, select Diagnostics | Query Insteon Engine. Try the Set Options update again. I am able to set the timeout interval okay and the IO Linc relay does respond with the new value but the new value is not displayed the next time I click Set Options. I know why that is and I will send a trace to UDI about that. If the new timeout value does not have an effect on the device, independent of the fact that the new value does not display, run an Event Trace with Level 3 set, trace a Set Options changing the timeout value . Exit Set Options and then click Set Options again and post the trace.

I don't know about the sonos but normal AV equipment and the ISY I put in a vote for the Logitech Harmony. They make several models depending on how many different pieces of equipment to be controlled. The Harmony is loaded from the web with the definitions needed. I've used a simple Harmony 300 for a year or so with good success. Although I do not use it to control the ISY IR day to day I did load up the default ISY IR definitions initially to see how well it worked. I'm sure there are other good remotes. The Harmony has worked well for me.