LeeG

The first issue the newbie is going to run into is being told his system is multiple official releases behind and must upgrade to 4.4.6 to get support.

doctorjerry The results in your post #7 are the expected results (old node name remains, new node name gone, links transferred). The ! was not expected. It indicates some issue in the Insteon address transfer process. There can be a fair amount of Insteon traffic during the "Replace" process and since it was cleared with a single write update I would not worry about it.

" If I turn the module on from the Admin Console the LED does not change to show if the module is off or on. How do I make the LED change when the module is turned on or off from the Admin Con?" Need to turn the Scene On and Off from the Admin Console. Turning the individual device On/Off does not involve the Scene relationship.

"Log back into the Admin Console, you will notice the old switch is now gone and is replaced with Kitchen New." The old SwitchLinc node is not gone. Scenes and Programs will continue to use the old (fried) SwiitchLinc node name.which now has the Insteon address of the new SwitchLinc node which is now gone.

What does the system do when ISY OFF is pressed? A Program invoked? A Scene turned Off? If a Scene Off is issued all devices in the Scene would turn Off. For some devices to remain On they would not be in the Scene or those devices are part of the Insteon network comm issues you have already mentioned in the initial post.

The best solution is to find and fix the issue(s) with in the Insteon network. Until then the Program can be updated to repeat the Scene. AAAA4 - [iD 006C][Parent 0001] If Time is Sunset Then Set Scene 'Night Time Mood Dim' On Wait 3 seconds Set Scene 'Night Time Mood Dim' On Wait 3 seconds Set Scene 'Night Time Mood Dim' On Else - No Actions - (To add one, press 'Action')

timekiller If you look at the images in http://homeautomationguru.com/insteon-enabled-your-garage-doors/ you will see they use the magnetic switch being strongly recommended by several folks. The I/O Linc garage package you started with does not have the magnetic switch the homeautomationguru uses.

Off=0 On=3 is the same as Off=0 On=5 is the same as Off=0 On=7. The KPL firmware does not allow Off=0 On=3 as a functional combination as the difference between Off and On LED level is too small. Need to know how a device works (KPL in this case) when setting values. From memory the KPL requires a 7 or 8 increment value difference between Off an On levels. That is why manually changing Off/On levels with KPL does not provide the result you are expecting/hoping for.

"For instance, if it takes 5 seconds to dim 50%, and your scene members in a scene one scene have on levels of 50% and another 100%, what happens when you hold a scene controller paddle for 5 seconds? You get the first scene member at 25% and the second at 50%. That's the expectation for asking for a scene to be on at 50% - each member at 50% of its default on level. " Unfortunately Insteon Scenes/Devices have never operated that way. Devices Fade Up/Down at the same rate. When the Fade Stop is issued, if the 100% On device has faded down to 50% the device that started at 50% will be Off. Devices Fade Up/Down at the same rate. Keep in mind Insteon devices are designed to be operated by a human. If the device at 50% On had a defined ramp rate of 8 minutes it would take 4 minutes to ramp down to 25%. Not practical for several reasons. No human will hold a button/paddle for 4 minutes, holding a button for that long would put the device into linking mode, and on and on. All devices ramp up or ramp down at the same rate when commanded to ramp.

xander.angelov Setting the Backlight level On/Off value affects all buttons on the KPL. Need to know the Off level value and the On Level value being set in KPL Brightness popup. The KPL firmware will not allow an On level and Off level that are very close in value as it would be difficult to know which buttons are On and which are Off. Post the KPL firmware level as that can affect when Brightness levels take effect.

pix530 The ISY does not replace an alarm system, it does not have the features required of an alarm system. My alarm system has battery backup and other features not available in my ISYs. ELK alarm system works well with an ISY.

Turn On Event Trace LEVEL 3. Press the KPL button that does not respond to other KPL button press. Post the event log.

Normal house power in US is 240v AC which is made up of two 120 v legs. Most powered Insteon devices run off of 120v. For the Insteon signal to reach devices powered on the other 120v leg two Dual Band devices are required, one powered by 120v leg 1 and one powered by 120v leg 2. There is also a hardwired coupler, 2406H, that can be wired at the power panel to both 120v legs. Without coupling Insteon signals cannot reach powered Insteon devices on both 120v legs. As for the Event Trace, if the KPL that that does not react when linked to another device is not pressed, actual messages from the failing KPL would not be expected to appear in the event trace. When device 1 is pressed, messages from linked device 2 would not be in the trace.

The Event Trace does not show button on 2a.10.fc being pressed. That is why the question about how the 120v legs are coupled. The button press message does not reach the PLM.

What devices are used to couple the 120v legs?

Is the Scene being turned On by an ISY Program? The ISY marks the Secondary button Status On as that is what should happen with the Scene, not what actually happened (assuming Scene turned On by Program). Check the Keypad button Responder On Level and Ramp Rate. What devices are being used to couple the 2 120v legs? The On command may not be reaching the KPL if the KPL is on the opposite 120v leg compared to the PLM and the 120v legs are not correctly coupled.

Adding deviceA to ISY 1 and deviceB to ISY 2 is fine. I run multiple ISYs with that arrangement. The issue is adding deviceA to ISY 1 and ISY 2. There is no 'monitor only' mode in Insteon. Both ISYs will consider the device as owned. Things like ISY 1 having links in deviceA to the ISY 2 PLM is the first challenge. I have not tried that configuration but keeping accurate backups of both ISYs that are in sync will be difficult. I don't think the configuration is practical even if possible.

Yes, that is the function of # Here is the Wiki link to email variables http://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables

Try closing Admin Console, starting with a fresh copy. New Scenes appear at bottom of Scene list until Admin Console is restarted.

First, the Auto DR is part of Electricity support. "Global" is correct for creating a new Scene. What is ISY firmware? What is ISY UI (Admin Console)? What if anything was selected in main node tree when creating Scene? What OS and release is being used?

Thanks for the additional update. I agree that working with battery devices, particularly motion sensors that may require a ladder, adds to the effort involved. The concept in the Wiki is to gate an update when inbound traffic occurs from battery device. It works but as noted before, the device must send some message to the ISY to know when to start the update. The battery device stays awake for a very short time so initiating the update from the ISY must be immediate. For a new device it is much easier to put it into manual linking mode which keeps the battery device awake approx 4 minutes. This eliminates the critical timing associated with the Wiki approach.

Without knowing how jumpers are set (need jumper 5) means it might not be possible to set Motion Sensor with a program (ISY). Also the process requires the motion sensor send a motion signal (On or Off) to the ISY which from your description is not possible at this time. Battery devices sleep to save battery life. If the battery powered device cannot send a message this type of update is not possible Is the motion sensor defined to your ISY or the remote person's ISY that you can log into and access the event viewer?

I tested a v.38. That is pre-I2CS so it takes at least 3 Insteon commands (Set MSB, Peek, Poke) to update a single value. It may be necessary to have a 2-3 second Wait between the last Adjust Scene and the Set Scene 'xxxx' On.

I would not think an old LampLinc would be a problem. What is the firmware level of LampLinc? Displayed on second line, right side of Admin Console. I'll see if I have that level to test here.

Sure. The Adjust Scene changes the On Level and Ramp Rate in the Responder link record. Can be issued any time. Does not matter whether Scene is Off or On. Another Set Scene 'xxxx' On is required for the changed link record values to be used.