LeeG

If the probe is connected to the same side of the transformer that is going out to the button and the other side of the probe is connected to the return from the button you could see the results observed. Try connecting the probe to the other transformer secondary connection. Transformer Secondary A B A - goes to the door bell B – goes to the door bell button Door Bell C D C – comes from the transformer secondary D – comes from the door bell button Probe – should be connected to Door Bell C & D

One second is very long for a digital circuit. You do see 18-24v ac on the door bell for as long as the button is pressed and held. One side of the low voltage transformer goes to the bell, the other side of the bell comes from door bell button. You should be seeing low voltage ac on the door bell for that full second the button is pressed.

Is the probe connect to the door bell button or the door bell itself. The fact that the 11-12 volts is there for such a short time it sounds like the probe is connected to the door bell button. I think it should be connected to the door bell and there should be 18-24V ac on the door bell for as long as the button is pressed.

I know of no harm it would cause and that would insure the PLM is clean when the restore starts. When I ran my first PLM Restore it ran for an hour or two because there was much activity to individual devices. Was not expecting that so when the restore completed I started the event viewer and ran another restore. The second time it ran in minutes. Never was able to determine what the ISY found the first time that caused it to interact with the devices.

It can take a long time and there should be no other Insteon traffic while the Restore Modem (PLM) is running. I would take an ISY Backup before starting the PLM restore.

"The voltage is 0 volts when the doorbell is not pressed and 11-12 volt when I press the doorbell button for a split second." Is that measuring the input to the probe or input to the I/O Linc Sensor? Did you try the excellent suggestion of connecting a 9V battery to the probe so see what happens?

Power cycle the ISY and the PLM before considering restoring the PLM.

There are limitations regarding Controllers. They can be assigned to only one Scene (Insteon architecture). Also to duplicate other aspects of a Scene would create duplicate link records in the device and the PLM which creates another issue. The concept of copying a Scene sounds good from a human perspective but it is impossible to a poor choice in the mess it creates.

They are beta units of things to come.

There is nothing to adjust. What are you trying to change?

Assign the KeypadLinc button to an ISY Scene as a Responder. In the Program Set "scene with KPL button' Off. The loop is the result of the way the program is coded. Whenever a Wait or Repeat statement is encountered the If is reevaluated. When something in the Program changes the conditions checked by the If the program is triggered again and either the Then or Else is run depending on whether the If is now True or False. This result has nothing to do with using a Scene to turn a Secondary KeypadLinc button Off. Anything the Program does to change the conditions in the If produces the same results. The normal solution is to break the program into 2 Programs. Program 1 has the If statement, Program 2 has the execution logic. That way Program 1 is not reevaluated because it has not Wait or Repeat statements. Another approach is to use If Control rather than If Status. If Control is dependent on actual command flow from the device so the True/False status is not affected by changes the Program makes to device Status.

The Program that turns the light Off has a Wait which means if any of the conditions in the If change during the Wait the Set 'Driveway Spot' Off will not execute. Suggest looking at the Programs | Summary tab to see if the Program is triggered when the motion sensor sends the Off command. If not the other conditions in the If are preventing the Then clause from running. If it is triggered then look for when the Program 'DrivewayMotionTimerEnable' turns False. If that happens in the 10 second window the spot light will not be turned Off. I guess before any of that be sure the motion sensor –Sensor node is changing to Off. The motion sensor may not be configured to send Off commands. If Status 'Driveway Motion Sensor-Sensor' is Off And Status 'Driveway Spot' is On And Program 'DrivewayMotionTimerEnable' is True Then Wait 10 seconds Set 'Driveway Spot' Off Else - No Actions - (To add one, press 'Action')

I ran that test with good results. First beep was issued at 02:35:06, the 60th beep at 02:36:05. What other activity was running on the ISY during the 60 second period? Fri 02/24/2012 02:35:06 PM : [iNST-ACK ] 02 62 15.9A.F9 0F 30 0E 06 BEEP (0E) Fri 02/24/2012 02:35:06 PM : [iNST-SRX ] 02 50 15.9A.F9 19.70.06 2B 30 0E BEEP (0E) Fri 02/24/2012 02:35:06 PM : [standard-Direct Ack][15.9A.F9-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 02/24/2012 02:36:05 PM : [iNST-ACK ] 02 62 15.9A.F9 0F 30 0E 06 BEEP (0E) Fri 02/24/2012 02:36:05 PM : [iNST-SRX ] 02 50 15.9A.F9 19.70.06 2B 30 0E BEEP (0E) Fri 02/24/2012 02:36:05 PM : [standard-Direct Ack][15.9A.F9-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Else Repeat 60 times Set 'KPL Floor Dimmer 6 button' 14 (Beep Duration)

What did you change between the motion sensor turning the lights Off and the motion sensor not turning the lights Off? What motion sensor options are set?

The end of a Repeat loop is indicated by another Repeat with a loop count of 1. The statements after Repeat 1 time will be executed once. The UDI Wiki has some good examples for each type of Program statement. If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat 2 times Set 'ICON Dimmer 1' On Wait 2 seconds Set 'ICON Dimmer 1' Off Wait 2 seconds Repeat 1 times Set 'KPL Floor Dimmer 6 button' On Set 'KPL Floor Dimmer 6 button' Off Else

"how do I break out of the repeat loop" The Repeat loop will repeat 20 times to flash the light assuming that is the repeat count. The next statement will execute after the repeat finishes. Do you want to cancel the repeat look so it does not flash 20 times? If that is the requirement what activity indicates the loop should be canceled, a different button press, etc. Each time a Repeat is encountered the If condition is reevaluated. Assuming the Repeat is in the Then clause should the If turn False the Repeat is stopped and the Else would then run. " How do I set the button to off " Secondary KeypadLinc buttons cannot be turned On/Off directly. The KeypadLinc button must be assigned as a responder to an ISY Scene and control the Scene Off or On. "I would love it if the lights return to their original state" Insteon has no function to return a device to a previous state.

Can you expand on what is not working. Things like Beep Duration do not work as no device honors that setting (so far). But is Beep Duration a concern. That is why more detail regarding what is actually happening versus what you want to happen will be helpful. Include what Motion Sensor options have been established.

Holding the Set button for a full 10 seconds should factory reset the MorningLinc. A separate circuit is not the issue. The MorningLinc needs to be as many wire feet away from the ISY PLM as possible. There is a much less desirable alternative which I will describe if this does not work. I could not get my MorningLinc into more than 1 Scene, usually the first Scene would lose connectivity between the PLM and the MorningLinc. I moved the MorningLinc to the most distant part of the house and Scene management worked every time.

Delete the MorningLinc from the ISY, Factory Reset the MorningLinc (this will not lose the ability of the MorningLinc Set button to cycle the lockset), add the MorningLinc back to the ISY using Start Linking, and the “keep existing links†option. Before adding the MorningLinc to any Scene, move the MorningLinc to a location distant from the ISY PLM. The MorningLinc will not have to stay in this location, only for adding it to Scenes. Add the MorningLinc nodes to whatever Scenes are needed. Now see if the Scene(s) with the MorningLinc node(s) as Responders will control the lockset. If so move the MorningLinc to whatever location was good for the MorningLinc RF signal to reach the lockset. The purpose of moving the MorningLinc to a distant location during Scene management is to increase the delay between the PLM and the MorningLinc. I was able to add both the Lock and Unlock nodes to a Scene using this technique. If this does not work post back.

That was changed some images back to help with an XML parsing issue (I think that was the reason). Anyway, it was a conscious change. There are other posts discussing the change. EDIT: this was noted in 3.1.13. See page 8 of the following topic, a few posts into page 8 viewtopic.php?f=57&t=7399&start=105&hilit=dusk%2Fdawn

That was not the answer I was expecting so I installed a 2484D. The additional nodes are Blue which means they are Responders not Controllers so they cannot be used to control anything. Also all the buttons present with a button number that matches the upper left button so it is not possible to know which button was pressed anyway.

How many nodes were defined for the KeypadLinc Countdown Timer? I don't think the buttons can be used independently. The number of nodes will answer the question. Smarthome/Smartlabs does not offer a service to reflash devices.

If you have not found the problem before 10 PM, run Tools | Diagnostics | Event Viewer with Level 3-Sevice communications events selected before 10 PM.. The Program statements will be traced at 10 PM. Post the event viewer file.

Do not create set button links when using the ISY. There are a few exceptions for special devices which include instructions on how to do set button links with those devices. The ISY will not be aware of the link created and will overlay and/erase the set button links. Define an ISY Scene, add the RL2 button as a Controller and the SwitchLinc either as a responder or controller depending on how the SwitchLinc will be used. Remember to put the RL2 into linking mode before adding the RL2 button to the ISY Scene.

That is the problem with not issuing the Fade Stop. That is not the normal sequence so hard to tell. Does either Staircase or Staircase Slave button press turn it to 30% after 10PM. You did add the additional 4 Adjust Scene statements to both the Then and Else clauses in the Program. Does the Programs | Summary tab show the Program ran at 10PM and the Status is False indicating the Else clause ran. For now you can change the Set Scene xxx Fade Down to Set Scene xxx Off. That will eliminate the question about Fade Down until the 10PM On Level is resolved.