LeeG

I don't remember if I found the function by studying the various ISY capabilities (Adjust Scene in this case) or saw it in an old forum post. Retirement provides lots of free time to learn the functions/features of a product.

The Insteon device is reacting to its normal On Level faster than the Program can override with a lower On Level. The simplest way to make this happen is to adjust the On Level to 30% at midnight and then back to 100% at 5 AM. This does not turn On/Off the device, only affects the On Level when device is manually operated. Define an ISY Scene with the device as a Controller Scene xxxx Controller - Switchlinc Dimmer 1 In an ISY Program code OnLevelChange1 - [iD 0087][Parent 0001] If From 12:00:01AM To 5:00:00AM (same day) Then In Scene 'SwitchLinc Dimmer 1' Set 'SwitchLinc Dimmer 1' 30% (On Level) Else In Scene 'SwitchLinc Dimmer 1' Set 'SwitchLinc Dimmer 1' 100% (On Level)

"It does not like it when I use the real switch." Explaining the problem would help. Difficult to suggest a fix without knowing the problem. I don't see the need for Relay follows Input. Also knowing what Momentary Mode is being used is generally helpful.

The Mini Remote support was added at 4.3.10; 4.3.6 does not have support. SmartLabs changed the subcat value. Unless you have a strong need to move to 5.x I recommend installing 4.3.18

Sorry, no. The device will Fade Up until a Fade Stop is received. Although Fading at a known rate (not the Local Ramp Rate nor Scene Responder Ramp Rate) there is not enough Program control to stop at any specific On Level. Also someone could have changed the current On Level so how long to Wait before issuing the Fade Stop is not easily reacted to.

If there is an ISY Program involved please post that as well as the previous information requested.

No, the KPL button toggle mode has no control over the I/O Linc Sensor operating a KPL LED. Can you post the ISY Scene, the I/O Linc Sensor as Controller, and the KPL button. Unless the Scene is not correct it sounds like a comm problem. What does Help | About show for Firmware and UI levels?

baabm You are correct.

ERR blinking by itself indicates ISY File system problem. Power down ISY and reseat SD card. SD card may need to be replaced. From as ISY User Guide A blinking ERR LED indicates a file system error. Please power off the ISY and try to re-seat the SD card. If that does not help, the SD card may be defective. Please see Appendix C: Replacing / Upgrading Your SD Card

As paulbates has already indicated an EXIO2X4 works as I use one. There are some things to consider. The two EZIO2X4 Relays operate in latching mode by default. That means if driven from an ISY Program the Relays must be turned Off after a second or two. Or use the Simplehomenet Utility Suite (free software package that runs on Windows and requires a PLM) to set the EZIO2X4 Configuration to enable the Relay timers and set for Seconds as well as setting each relay timer to 1 or 2 seconds. The EZIO2X4 first two opto-isolated Inputs are Off until a switch applies 3-30 volts DC to turn Input On. The EZIO2X4 has a +5V connection which can be used to turn On the Inputs. Although the Inputs can be reversed (like using I/O Linc Trigger Reverse) I recommend using a magnetic switch that provides the desired door Closed state. Normally that is a switch that is open when door is closed. I won't describe that as NO or NC because it depends on whether the magnetic switch is expected to be used for security or industrial use. Unfortunately a switch that is open when the door is closed has opposite designation depending on if it is a security switch or an industry switch.

Define an ISY Scene. Put the mini-remote into manual linking mode, add Controllers and Responder.. Scene XXXX Controller Button A Controller Button B Controller Button C Controller Button D Responder OutletLinc Click on Red Button A, the OutletLinc will show as Responder. The OutletLinc On Level should already be set to 100% Click on Red Button B, the OutletLinc will show as Responder. Set the OutletLinc On Level to 75% Click on Red Button C, the OutletLinc will show as Responder. Set the OutletLinc On Level to 25% Click on Red Button D, the OutletLinc will show as Responder. Set the OutletLinc On Level to 0% Take the mini-remote out of linking mode.

Try Google search for "upnp security risk router". Several hits on UPnP security

Great news. Thanks for the feedback.

The ISY has Firmware 4.0.5 (very old firmware). Update to 4.2.30 at a minimum.

What does Tools | Diagnostics | PLM Info/Status show. The trace provides no information as it looks like the ISY may be having an issue with the PLM. Also what does Help | About show for Firmware and UI levels.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Put MS into linking mode and click Options. Update a setting such as Timeout. When System Busy in lower left corner is no longer displayed, copy event trace to clipboard (icon at bottom right next to last of event viewer viewer window). Post to forum.

When uPnP is turned On, is that in the ISY and the router? It is better to have set up port forwarding in router and not use File | Enable Internet Access.

When using "If Control" the commands must match the If statements. If Control 'device' is switched On Or Control 'device' is not switched Off Then Disable Program . Else Enable Program . The Then clause is driven when On command received from device The Else clause is driven when Off command received from device The Actions/rules that If Control uses are not the same as If Status.

There is no catch all for "If Control". Each command that can be expected must be checked. If Control 'device' is switched On Or Control 'device' is switched Fast On Or Control 'device' is switched Fade Up Or Control ' device' is switched Bright Or Control 'device' is switched Dim Or Control 'device' is switched Fade Down etc .......

"If Control" is reacting to manual action of the device by a human. Someone pushed the paddle/button. "If Control" does not trigger the Program when the device is reacting to another device/Scene/Program. "If Status" is reacting to the state of the device. The device can be manually operated, turned On/Off by another device/Scene/Program. Anything that changes the state of the device can trigger a Program. As a side note, "responding/not responding" is used to check comm with the device, not to check what state the device is in. Since these devices/switches are only being operated manually either type check works but using "If Status" is easier as it is not necessary to check for multiple commands. If Status 'device' is not Off Then Wait 15 minutes Set 'device' Off Else

I agree with larryllix, no need to run multiple times a day. The Insteon network would have to be poor for there to be a need. If the Insteon network were/is that poor it would need work, not more queries.

The QueryAll Program has a "Set Scene" statement that should point to the selected item "All Devices" in the posted image. That item has been renamed from "My Lighting" on the 99i.

", then why does the On/Off Plugin Module contain both options if they are exactly the same thing." The 2635-222 Plugin On Off Module Owners Manual describes Blink on Traffic and Error Blink (blinks red if no ACK from a Responder) on page 19. I see no conflicting description for an LED on TX option.

The new PLM was not installed following the correct procedure. The PLM address is zeros (000000). Thu 09/10/2015 15:53:19 : [22 2C D4 1 ] Link 0 : 0FF8 [A200000000FF1F01] Writing [....000000......] Thu 09/10/2015 15:53:19 : [22 2C D4 1 ] Link 1 : 0FF0 [E201000000FF0001] Writing [....000000......] Thu 09/10/2015 15:53:20 : [22 2C D4 1 ] Link 2 : 0FE8 [A213000000FF1F01] Writing [....000000......] Thu 09/10/2015 15:53:30 : [22 BA 5D 1 ] Link 0 : 0FF8 [A200000000FF1F01] Writing [....000000......] Thu 09/10/2015 15:53:31 : [22 BA 5D 1 ] Link 1 : 0FF0 [A213000000FF1F01] Writing [....000000......] Thu 09/10/2015 15:53:36 : [22 CA 66 1 ] Link 1 : 0FF0 [A200000000FF1F01] Writing [....000000......] Thu 09/10/2015 15:53:37 : [22 CA 66 1 ] Link 2 : 0FE8 [A213000000FF1F01] Writing [....000000......] Thu 09/10/2015 15:53:45 : [22 D4 D5 1 ] Link 0 : 0FF8 [A200000000FF1F01] Writing [....000000......] Thu 09/10/2015 15:53:46 : [22 D4 D5 1 ] Link 1 : 0FF0 [E201000000FF0001] Writing [....000000......] Thu 09/10/2015 15:53:47 : [22 D4 D5 1 ] Link 2 : 0FE8 [A212000000FF1F00] Writing [....000000......] Thu 09/10/2015 15:53:55 : [23 DA 58 1 ] Link 0 : 0FF8 [A200000000FF1F01] Writing [....000000......] Thu 09/10/2015 15:53:56 : [23 DA 58 1 ] Link 1 : 0FF0 [E201000000FF0001] Writing [....000000......] Thu 09/10/2015 15:53:56 : [23 DA 58 1 ] Link 2 : 0FE8 [A211000000FF1F01] Writing [....000000......] Thu 09/10/2015 15:54:04 : [23 DB FC 1 ] Link 0 : 0FF8 [A200000000FF1F01] Writing [....000000......] Was a Delete Modem (PLM) issued?

Run Tools | Diagnostics | Event Viewer at LEVEL 3. I don't know what a URTII is? Unless it is a battery powered device no need to put it into linking mode. Simply right click and select Write Updates to Device. Copy event trace to clipboard and post. The I/O Linc Relay can be queried while event viewer is active and post that trace as swell.