LeeG

drw Is the RX LED on solid when this happens?

RX LED on solid indicates the ISY is not able to communicate with the PLM. Unplug the PLM for a few minutes and make sure the cable connections are fully seated. After PLM is plugged in again, reboot the ISY. If the RX LED remains on solid it indicates a bad PLM or bad cable.

Removing the battery stops the motion sensor. Install a weak battery but be careful as the motion sensor sends only one low battery message. The battery has to be low enough to report Low Bat but not so low as to prevent the motion sensor from working. How to generate smoke as a test can be interesting. Light a piece of paper and blow out the flame. May produce enough smoke to set off the alarm. Over heat some grease on the stove but that can result in a real fire so caution is advised. Find a neighbor that smokes.

NEVER DELETE THE PLM. The Delete Modem (PLM) action removed all references to the PLM. The Restore Modem (PLM) cannot fix the damage done by a Delete Modem. Go to an ISY Backup taken before the Delete Modem (PLM) was issued. Issue a File | Restore Devices to rebuild each device link database with PLM information. It may be necessary to also issue a Restore Modem (PLM) after the File | Restore Devices completes.

Use this link to go to UDI 'Buy' page. Scroll to the bottom of the page for the Update options http://www.universal-devices.com/sales/products/

The Dual Band KeypadLinc (only KeypadLinc available) is not supported. There are some new device types such as the Door Sensor were released after 3.3.10. The Leak Sensor and Smoke Bridge may have come out after 3.3.10. The KeypadLinc is the most common issue since most installs use them.

The Program is triggered at Midnight and Sunrise +1 hr. More times would be added as additional ORs.

The upgrade is still being shown on the UDI web site under Buy.

The same condition that is triggering the first Program is triggering the second at the same time. If the second program should run only when called by the first program, mark second program Disabled. That way it cannot be triggered by it's If condition. EDIT: as a side note the first program If has an invalid statement in what is posted. Right click on a program name, select Copy to Clipboard, paste into forum. A simple mistype can result in the wrong conclusions.

His ID is stusviews.

Jumper 5 has to be set to enable software setting of the options. Put the motion sensor into linking mode using Motion Sensor set button, just as when adding the motion Sensor to the ISY. Click the Options button and set the options as desired. There is only one set of options.

The Wiki has step by step instructions http://wiki.universal-devices.com/index ... r_ISY-994i

What is the outside temp? The lack of a Red LED when walking past the Motion Sensor field of view would indicate an issue with the Motion Sensor, low battery, incorrect position. Folks do use these outside. The Motion Sensor should be positioned such that someone approaching the door walks across the field of view. Pointing at the door itself is not the best orientation. The Motion Sensor works best when a person walks across the field of view, not directly toward or directly away from the Motion Sensor. Try a new battery.

Glad to hear it is working. Thanks for taking the time to post back the results.

No solution here, however I use Chrome, Java _51 and 4.1.2 with no problem logging on. What OS?

Try adding a Wait 2-3 seconds before issuing the X10 call. The RL2 sends a number of messages when a button is pressed. The Wait allows those messages to complete first. Then Wait 3 seconds Send X10 'A2/On (3)'

It sounds like the symptom changed when moved near the PLM. Run another Event Viewer at LEVEL 3 with it plugged near the PLM.

That was the expected results. The device did not respond to Query Insteon Engine request. No 02 50 response from any of the three request for the Insteon Engine information. Mon 02/24/2014 03:19:03 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00 Mon 02/24/2014 03:19:03 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00) Mon 02/24/2014 03:19:11 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00 Mon 02/24/2014 03:19:11 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00) Mon 02/24/2014 03:19:20 PM : [iNST-TX-I1 ] 02 62 27 BC 10 0F 0D 00 Mon 02/24/2014 03:19:20 PM : [iNST-ACK ] 02 62 27.BC.10 0F 0D 00 06 (00) Mon 02/24/2014 03:19:24 PM : [27 BC 10 0 ] Failed to add device Try moving the device closer to the PLM.

Ditto everything oberkc said. The compound If suggests the Status of Program 'Morning walk on' is not allowing the Wait to finish. As soon as Program 'Morning walk on' changes Status the Wait is terminated and the motion sensor Program retriggerd with a False If, running the Else clause. Before introducing the compound If it was impossible to drive the Else clause. Now driving the Else before the Wait completes seems to be the only way to create the current symptom.

Run Tools | Diagnolstics | Event Viewer at LEVEL 3. Add the 2634-222 and post the trace. It sounds like the 2634-222 is not answering the "What Insteon Engine" command question.

The event trace shows the Set ... Off statements did not run even though there is 4 minutes between Motion On messages. Right click the Program name and select Copy to Clipboard. Paste the actual Program. Are there other Programs that affect this program, such as issuing a Disable for example. The Motion Sensor sent an Off command which would not affect this Program but it could trigger another Program that is interacting in some way. Is the 99i running 3.3.10?

What is the Insteon address of the motion sensor that is driving the posted program? There appears to be multiple motion sensors operating in the event trace, 27.B4.49, 27.B4.2B, 27.B4.33. Also by watching Programs | Summary , Last Run Time and Status columns for the posted Program it will show each time the Program is triggered.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Run the 30+ minute test and post the event trace. Setting the Wait at or past 30 minutes should have no adverse effect.

"it is possible to jump a neutral from another circuit. All neutrals go to the same bar in the load center so it doesn't matter" That can over load the Neutral and cause a fire. It is against code as well. That arrangement can cause much current to flow over the Neutral then the size of the wire is rated for.

Not really. Are Direct commands or Scenes being used to turn On the Dual Band SwitchLincs. The ISY will not send a new ramp rate to a device it thinks is already set to that value. Try changing to something different.