LeeG

C Martin I don't understand why the Wait is coded in the Program as it serves no function. The Program will be retriggered regardless of the Wait. The If Status may by the source of variance. The Status must change before the Program is triggered again. This means the Motion Sensor MUST timeout and issue an Off command to change the Status to Off before a Status change to On will trigger the Program Then clause again. The Motion Sensor resets its timeout value each time it detects motion so the time to the next Off and therefore the possibility of the next Status On will vary based on what the Motion Sensor is seeing in it field of view. Lee

It should not have been necessary to do the device delete/add for each Scene. Don't know if the issue was the result of the failed PLM itself or something during the adding of the new PLM that resulted in the lost device control at the Scene level. The Restore Device normally resolves any link record issues but you indicated that had been done. I know of nothing else other than what you are deing at present.

What OS are you running and what Java level is installed? I'm running 1.6.0_23-b05 on XP Be sure to clear the Java cache and use the URL that accesses the 3.1.10 Admin Console. It will not be the same code that ran on 2.8.16.

edilks If Control triggers based on command flow from the device. If Control On triggers each time an On command comes from the device. If a SwitchLinc, each time the top of the paddle is pressed an On command is sent and the Program triggers. This happens whether the device was Off going to On, or already On staying On. If Status uses the device status the ISY keeps track of. The Status must change for the Program to trigger. Pressing the top of the SwitchLinc paddle twice (not fast enough for a Fast On) the Program would be triggered only once, when the device status went from Off to On. The already On to On would not trigger the Program again. Because If Status triggers the Program on a change in Status the additional line in the If is not required to drive the Else. A simple if Status is On triggers the program on both the ON and OFF change in Status. The Then clause runs when the Status changes to ON because the condition is True and the Else clause runs when the Status changes of OFF because the condition is False. The choice of Control versus Status is made based on what situation should trigger the Program. Lee

You are changing the Scene Responder On Level and not the individual device node further up the My Lighting tree. The change to 50% did not change the device link database. There is a Scene being triggered that is setting some devices Off with a Fast Off. Is a Program being triggered by the device On Level change? If so disable that Program for now until the Responder link record not being updated is resolved.

It turned the device On successfully (08.3D.87) so the PLM is working but made no attempt to write a new Responder On Level to the device link database. Try setting an On Level to 50% and see if that takes. Turn the Scene On/Off after changing to 50% and the progress bar and system status in lower left corner shows Ready. Despite what the Admin Console is showing it looks like it thinks the Responder On Level is already 100%. If changing to 50% does not work try deleting the device from the Scene and adding it back.

edilks The Program triggers each time an On command is received from the device. The Else never runs because the Program only triggers with an On command and the If is always True. To run the Else with an Off command add an And Control device not Off to drive the Else on an Off command. If Control 'ICON Dimmer 1' is switched On And Control 'ICON Dimmer 1' is not switched Off Then Send X10 'A1/On (3)' Else Send X10 'A1/Off (11)' Lee

Melor Under Tools| Diagnostics | PLM Info does it show the correct Insteon address for the PLM and indicate Connected? What ISY firmware are you running? Run Tools | Diagnostics | Event Viewer with Device communications events selected (most important option). Make a change to one of the Responder On Level values to 100% and post the Event Viewer trace file. Lee

nlaredo The 2476ST is listed as a supported device in the 3.1.10 Beta release. Other choices would be a 2476S SwitchLinc Relay (without timer) or a 2876S ICON Relay. Don't know if either is in the 2.8.16 device list. Lee

You can use different Ramp Rates assuming the devices are Dimmers. Using a slower Ramp Rate has the visual effect of some coming on later. Different Scenes can be used with a Program turning on each Scene with a Wait or Delay. There is nothing in the Insteon architecture at the Scene level that allows for a Wait or Delay between devices in a Scene.

Some (not all) UPS devices have such good filtering capability they absorb the Insteon signals. It looks like noise to them and does not make it through the UPS to the outboard devices. If the AV equipment is controlled through IR that is one option. If looking to actually remove power from the AV equipment with an Insteon device outboard of the UPS that is likely a problem unless you put a Dual Band device outboard so that communication is through RF rather than the powerline through the UPS. You might consider holding on to the other Access Point. As your Insteon usage grows into RF only devices such as Motion Sensors, TriggerLincs and the newest RemoteLinc2 that looks somewhat like a KeypadLinc having the ability to position a Dual Band device within range of some of these devices may be useful.

Check out this topic. It is very long but look at the last 3/4 pages and folks are discussing the 2.2 replacement adaptor. viewtopic.php?f=25&t=5789&start=255

Depending on the location and load some or all of the UPSs can be plugged into the same FilterLinc. That isolates the UPS which itself is often a source of signal attenuation and any devices powered from the UPS. I suggest a pair of Access Points for phase coupling. They are pluggable so it is easy to find outlets on opposite phases and I think they have better range. The LampLinc LED changing color as the LampLinc is turned On and Off is normal. The color of the LED indicates whether the LampLinc is On or Off. This should be covered in the Quick Start guide and/or User Guide. As a general rule the more Insteon devices installed, particularly in the beginning of an installation the better things work. The devices are active repeaters so the signal quality often improves the more devices installed.

"So Smarthome should be swapping mine out?" Yes.

jeffpdavis1 Put the PLM into test mode by pressing the Set button 4 times. Plug the LampLinc into the same circuit as the PLM. The LampLinc LED will blink (after a few seconds) Red if on the same circuit and Green if on the opposite phase. Would expect it to blink Red for this first test. Now move the LampLinc to its original location. Does the LampLinc LED blink (indicating it is receiving the RF signal from the PLM) and if so what color. The LampLinc can be moved around to different plug points to see how far it will receive the PLM signal. The PLM will stay in test mode for approx 4 minutes. Lee

If it does not work in the new location it is an RF reception problem. Something in the wall, something in the location of the PLM versus the LampLinc. Once the device is successfully added to the ISY it can be moved without concern for any additional definition in the ISY.

v2.2 is the newer version.

jeffpdavis1 Did you click the Finish button? Lee

jeffpdavis1 The ISY will react essentially instantaneously (not quite but for all practical purposes). What devices are being used to couple the 120V phases? Sounds like the ISY PLM is not hearing the messages sent by the devices when the Set button is pressed. Move the LampLinc plug point to the same location as the ISY PLM. Then press the LampLinc Set button again. Be sure the PLM LED is blinking when Start Linking is initiated. Lee

gwarthur Code up your example and try it. The Wait will be canceled and the Program triggered again when the Status changes. Turning the device Off then On again within the Wait period has the effect of starting the Wait over again. Lee

lafleur Check the Programs | Summary page and see if the Activity column indicates Not Saved. This indicates a program change was made but not Saved. The other common problem is the Motion Sensor is linked to the Responder causing the Motion Sensor to turn On the Responder independent of the Program. Lee

rickholloway Glad that helped. If you plan to follow the various Betas the announcement post will include a list of URLs that should be used to access the Admin Console version that applies to the particular Beta. That is where I got the link for 3.1.10. Lee

They pulled it from HL2 because the implementation was poor. They fixed the design and put the feature back. It is built around the fact that the Motion Sensor stays awake for a very short time after sending an On message. It allows an application to send a command to the Motion Sensor that prevents it from going to sleep. Pending updates are sent to the Motion Sensor and when complete another command is sent to allow the Motion Sensor to go to sleep normally. It is a fantastic feature. Motion Sensors are often mounted where access is difficult. Queuing updates and sending them after a Motion On is detected would be a great enhancement to the ISY.

Try the following URL to access the Admin Console. http://www.universal-devices.com/99i/3.1.10/admin.jnlp

rickholloway Thanks. 1.33 is equivalent to [01.21] which is in the 3.1.10 Admin Console list. The 1.33 is decimal where the [01.21] is hex. For some reason the Admin Console being invoked is not at 3.1.10. Java cache not cleared or URL problems are the usual causes for getting the wrong Admin Console version. Does Help | About show 3.1.10 for the ISY firmware level? Lee