LeeG

Michel Did you notice all the addresses started with FF. That seems unusual for some many different Insteon addresses.

The Relay status has no relevance. For a garage application the I/O Linc Relay is in momentary mode. The Relay is On for a few seconds to initiate door movement, then turned Off automatically by the momentary mode timeout. The Relay is a Responder Only so it does not report back that it has been turned Off automatically. For the Relay to show Off something has sent an Off command to the Relay. It makes no difference to the operation of the I/O Linc Relay as it is physically Off anyway but look for something in a Program that is issuing an Off command. Or a Scene is sending an Off command which can turn the Relay On for a few seconds depending on which momentary mode is defined. See the I/O Linc User Guide for the characteristics of the three momentary modes. The various command responses are associated with Scene On/Off only. An Insteon Direct command always turns the Relay On and an Off command always turns the Relay Off (normally a no-op as the Relay is normally Off).

Right click the Scene name, select Diagnostics | Scene Test. Is the test successful? The ISY Scene does not have automatic retries associated with Insteon Direct commands so a Scene may have issues if the powerline is marginal to those locations. The Scene Test will verify the necessary link records are present. Responders is fine.

The RemoteLinc should stay awake for 4 minutes. If the RemoteLinc times out of linking mode, put it back into linking mode, right click the RemoteLinc primary button and select Write Updates to Device. The Restore should pick up from where the device timed out.

Sorry, no. The Replace xxxx With presents a list of devices that can be selected as replacements. A KeypadLinc cannot be a replacement for a SwitchLinc.

Insteon devices do not provide that information. Will have to use which breaker controls which device.

No direct experience with this. I saw a suggestion to use a sacrificed RF remote control, where an I/O Linc Relay would be connected in parallel with the RF remote button that would normally be used to reverse the Fan direction. I use the same principle with my garage doors as they are RF operated only. No normal wired button. Has worked well for the garage doors. The RF remote is already mounted on the wall so it was easy to connect a pair of wires to the door controller button that opens/closes the garage door. No idea if the same concept would work for the Fan Motor. Do not remember seeing any post back whether the suggestion worked for the other user.

Have not seen a filter with that capacity. The large amperage elements for heating are not likely causing any problem as they are simple resistance elements. More likely the electronics including the power supply are the actual source of the interference. These are generally low current devices which can be filtered but it means going inside the appliance, identifying and localizing the electronics with an inline filter.

I would do a factory reset. The "Ignore" is the End Of List record at the end of every device link database. The Compare describes it as Ignore as it is understood to be the EOL record which the ISY does not waste space in the ISY memory for a record that has no meaning past the first byte. The Restore Device should not write back the "Extra" records.

oberkc The OP is asking how to reverse the rotation of the Fan Motor (Does anyone have any suggestions about lack of a physical direction switch).

A factory reset of the RemoteLinc2 will clear the link database. The normal procedure would be a Restore Device which causes the ISY to rewrite the RemoteLinc2 link database. I suggest doing a Show Device Links Table followed by a Compare button click when the display completes. That will show if the ISY thinks some of those links should not be there. If the ISY says all the links that exist are correct then I would delete the RemoteLinc2, add it back with "Erase existing links' (should not matter with a factory reset) and recreate the Scenes.

In the Program the If Status triggers the Program any time the Status changes. That can drive the Else clause regardless of the time of day. That may produce some results that are unexpected and perhaps not desired. By defining a Folder with the If Status as the Folder Condition, a Program in that Folder can be triggered only when the If Status is true. By putting the If time range check only in the Program under that folder a change in the If Status cannot drive the Else clause in the Program.

Sorry, I misinterpreted the information. Either the ACK from the SwitchLinc is not making it back to the RemoteLinc2 OR there are other links for those buttons in the RemoteLinc2,. After putting the RemoteLinc2 into linking mode with its Set button, run Show Device Links Table for the RemoteLinc2. Look for E2 ....... Controller links to a device address that is not expected. If the links are correct move the RemoteLinc2 to a different Dual Band device location and try the buttons again.

The ISY Scene Responder On Levels for the FanLinc Motor have been set correctly. The KeypadLinc as Controller Responder On Levels for the FanLinc Motor are NOT set correctly. For each ISY Scene, below the ISY Scene name is the node Name of the KeypadLinc button as Controller. Click the KeypadLinc node Name below the ISY Scene name and set the appropriate Responder On Level for the FanLinc Motor. Currently the FanLinc Motor On Level is set for High for all three KeypadLinc buttons. 0FF8 : A2 00 1B.FD.7E FF 1F 01 0FF0 : A2 00 1B.FD.7E FF 1F 02 0FE8 : A2 18 1B.FD.7E FF 1F 02 ISY Scene – Motor High 0FE0 : A2 03 11.E4.24 FF 1F 02 KeypadLinc button A (6 button) – Motor High 0FD8 : A2 19 1B.FD.7E BF 1F 02 ISY Scene – Motor Med 0FD0 : A2 04 11.E4.24 FF 1F 02 KeypadLinc button B ( 6 button) – Motor High 0FC8 : A2 1A 1B.FD.7E 3F 1F 02 ISY Scene – Motor Low 0FC0 : A2 05 11.E4.24 FF 1F 02 KeypadLinc button C ( 6 button) – Motor High 0FB8 : A2 1B 1B.FD.7E 00 1F 02 ISY Scene – Motor Off 0FB0 : A2 1C 1B.FD.7E FF 1F 01 0FA8 : A2 01 11.E4.24 FF 1F 01 0FA0 : 00 00 00.00.00 00 00 00 Device Record Count : 12

Thanks Brian, that format is okay. I have a Java program that converts the XML into the equivalent link records.

What is the device type? For example, OutletLinc Dimmers will blink Red when the magnetic key is not in place indicating it cannot turn On without the key.

Run Diagnostics | Show Device Links Table against the FanLinc Light node and post the results including the Insteon address of a KeypadLinc that does not set the speed correctly. That will show whether the links have been set correctly.

Each ISY Scene that has a KeypadLinc Secondary button as Controller and the FanLinc Motor as a Responder will have a different Responder On Level. Below the ISY Scene name is the name of the Controller Secondary KeypadLinc button. Click on the KPL button name and set the Responder On Level (for the FanLinc Motor) to the desired speed. This has to be done for each of the 3 or 4 Scenes being used for FanLinc Motor speed.

I am seeing an unusual response to the 02 64 command. In one case there is a 03 response, in another a 01 response. Note the 06 response in my trace entry which is the standard response from a PLM when the serial command is accepted. Is there any possibility the PLM is full, not being able to create a new link. The command sequence being executed is trying to establish a link between the new device and the ISY PLM. This is a requirement of I2CS devices before the PLM can create additional links or control/configure the new device. Sun 09/02/2012 06:27:26 PM : [LNK-BGN ] 02 64 01 00 03 Sun 09/02/2012 09:17:58 AM : [LNK-BGN ] 02 64 01 00 01 Tue 06/05/2012 08:12:17 PM : [LNK-BGN ] 02 64 01 00 06 A Show PLM Links Table and Count will produce a count of the links in the PLM. The issue with this is any inbound Insteon message from a device will create false high/low record counts. It is necessary to run multiple Show PLM Links Table and Count to see if a consistent count be get obtained.

The RF SwitchLinc did not complete the exchange with the PLM. See the message in red from a device add of an I2CS device. This message is missing in the posted trace. Suggest moving an Access Point closer to the RF SwitchLinc. Be sure not to lose phase coupling in the process. The PLM can also be power cycled before doing the next device add. Tue 06/05/2012 08:12:17 PM : ---- Initializing the linked devices ---- Tue 06/05/2012 08:12:17 PM : ---- All Linked Devices are now initialized ---- Tue 06/05/2012 08:12:17 PM : ---- Add remaining devices ---- Tue 06/05/2012 08:12:17 PM : [iNST-TX-I1 ] 02 62 1C FD D5 0F 0D 00 Tue 06/05/2012 08:12:17 PM : [iNST-ACK ] 02 62 1C.FD.D5 0F 0D 00 06 (00) Tue 06/05/2012 08:12:17 PM : [iNST-SRX ] 02 50 1C.FD.D5 19.70.06 AB 0D FF (FF) Tue 06/05/2012 08:12:17 PM : [standard-Direct Nack][1C.FD.D5-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Tue 06/05/2012 08:12:17 PM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Tue 06/05/2012 08:12:17 PM : [iNST-ACK ] 02 62 1C.FD.D5 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01) Tue 06/05/2012 08:12:17 PM : [iNST-SRX ] 02 50 1C.FD.D5 19.70.06 2B 09 01 LNK-ON (01) Tue 06/05/2012 08:12:17 PM : [standard-Direct Ack][1C.FD.D5-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Tue 06/05/2012 08:12:17 PM : [LNK-BGN ] 02 64 01 00 06 Tue 06/05/2012 08:12:17 PM : [LNK-STAT ] 02 53 M(01) gid=00 1C.FD.D5 0700 41

Look at the ISY Error Log for something like Open failed for [/CONF/1E62A3.REC] or Init failed, etc

Click Network to display summay of devices. Click Address column header to sort by Insteon Address. Look for 1E 62 A3

Devices come with full LED brightness. An Off/On of 7/15 should get it back to that level.

An ISY Program cannot turn Secondary KeypadLinc button C On/Off. There is no Insteon Direct device control command that turns Secondary KeypadLinc buttons On/Off. A Secondary KeypadLinc button has to be assigned to a Scene either as a Controller or Responder and turn the Scene On/Off.

An IP address that starts with 192.168.x.x is not an external IP address. There are literally hundreds of thousands of users with devices that carry 192.168.x.x. They are IP addresses relative only to the local network. Log on to the Modem rather than the router. The WAN address of the modem is the IP address to access from the outside world. My ISP provides a modem/router combination. When logging into the router it is actually logging into the modem so the WAN address is the outside IP address. I did not look back through all the old posts (my error). For the router to present a WAN address of 192.168.x.x it must be a separate box from the modem. From the routers perspective it is a WAN address as it is what the router talks to when talking to the device above it. However, that cannot be a WAN address relative to the external internet.