LeeG

The rapid flashing indicates the motion sensor was/is linked to one or more devices that can no longer be reached. This should be corrected as it consumes some battery life needlessly. Put the motion sensor into linking mode and issue a Restore Device which should get rid of any links that are not valid.

Thanks. When the Show Device Links Table display completes (all link records read) the Compare button becomes active. When the Compare button is clicked a second popup is displayed. One of the popups will show the results of the Compare. Do all the link records match?

I am saying the motion sensor is not communicating through the PLM RF. If it was the Hops Left=x count would be better. One possibility is the PLM RF is not working. Another possibility there is interference in the 900 MHz band blocking the PLM and/or motion sensor. Another possibility is something physical is blocking the RF between the motion sensor and PLM. Metal, wood, something that is reducing the RF signal level to the point where the PLM is not reacting to motion sensor traffic. The event trace is good at showing what is happening but says nothing about why. My 900 MHz wireless phone works over 1000' from the house so RF interference could be from outside. Additional analysis can be done if other RF devices are available such as a RemoteLinc Mini (RemoteLinc2). The RL2 position relative to the PLM is easy to change so see if a better Hops Left=x count can be achieved in a different position. This is where Insteon debug tools are lacking, both powerline and RF.

"Now if somebody manually turns the light off before sunrise, does the ISY query constantly to turn it back on?" No. The ISY does not query a device (except at 3 AM). Only if a Program If section checked the Status of the light and performed Action would something happen to the light. "Or would the light just stay off?" Yes, it would stay Off. Only if a Program specifically checked the Status of the light and did something when it found it Off would something happen. "Since the program condition is 'leave the light on until sunrise' Same goes for the planned fan program. If the fan is supposed to run on medium speed at let's say 70 degrees, but somebody switched the fan manually, would a program always return the speed back to medium as long as it is 70 degrees?" No, not the way you have it phrased. The posted Programs check for thermostat temps anded/ored with weather data. If either of these change values the Program is triggered so it depends on the new values and the way the If is coded. The Programs do nothing relative to the Status of lights or fans. The ISY makes no attempt to interpret what conditions it thinks you wanted. A Program is triggered based on what the If section is checking. None of the posted Programs checks for the status of a light or fan so what happens to those devices is of no consequence.

This is what the trace entries of a Motion Sensor a few feet from a 2413S PLM should look like Mon 05/27/2013 05:52:56 PM : [iNST-SRX ] 02 50 14.99.51 00.00.01 CB 11 01 LTONRR (01) Mon 05/27/2013 05:52:56 PM : [std-Group ] 14.99.51-->Group=1, Max Hops=3, Hops Left=2 Mon 05/27/2013 05:52:56 PM : [ 14 99 51 1] DON 1 Mon 05/27/2013 05:52:56 PM : [ 14 99 51 1] ST 255 Mon 05/27/2013 05:52:56 PM : [iNST-SRX ] 02 50 14.99.51 00.00.01 CB 11 01 LTONRR (01) Mon 05/27/2013 05:52:56 PM : [std-Group ] 14.99.51-->Group=1, Max Hops=3, Hops Left=2 Mon 05/27/2013 05:52:56 PM : [iNST-DUP ] Previous message ignored. Mon 05/27/2013 05:53:11 PM : [iNST-SRX ] 02 50 14.99.51 11.01.01 CB 06 01 (01) Mon 05/27/2013 05:53:11 PM : [std-Group ] 14.99.51-->11.01.01, Max Hops=3, Hops Left=2 Your Motion Sensor is not communicating through the 2413 PLM RF

That sounds like a comm problem between the KeypadLinc locations except you indicated two other buttons controlling a different load stay in sync which suggests a Scene issue. Do a Show Device Links Table and Compare for both KeypadLincs. If either shows a mismatch (except for very last link record) do a Restore Device for that device. If the Compare does not show a problem then post the Show Device Links Table display. Need to see all the links in both KeypadLincs. The display can be saved as an XML file. Copy the XML file and post to the forum with all the XML tags intact if all the link records displayed cannot be posted as an image.

Perhaps more detail will help in the analysis. Can either KeypadLinc button turn the InLineLinc On and Off? If yes is the problem that the other KeypadLinc button does not reflect the On/Off status established by the KeypadLinc turning the InLineLinc On and Off. If both KeypadLinc buttons will turn the InLineLinc On and Off, neither KeypadLinc button will reflect the action of the other Are there any Green Icons to the left of the KeypadLinc nodes

CopyRon Thanks for both traces. There is a major problem with communications. In the first trace three commands were issued. The first two have max hops=3 hops left=0 which is as bad as it gets and still work. The third command got no response from the device. There are three possibilities, the device is bad which I rule out since it is not limited to a single device. The other possibilities are bad PLM or something on the PLM circuit. With the device being powered at the PLM plug point it could be things like UPS, PC power supply, other electronics which are not filtered that are attenuating the Insteon signal, or the PLM transmitter signal is very weak. Try using a long extension cord, plugging the PLM and device into the extension cord, plugging the extension cord into an outlet as far away as possible. If the Hops Left=x count continues at 0 then I would conclude the PLM transmitter is bad. If the hops left=x count improves when power is coming from a distant outlet there is something at the current plug point that is absorbing the Insteon signal. It would be common for things like a UPS, PC power supply, etc that are not filtered to significantly reduce the Insteon signal. The Fast Off command trace was perfect. max hops=3 hops left=2 is as good as it gets. The drastic variation between the single command in the second trace and the multiple commands in the first trace could mean the interference is transient in nature allowing a single command to work well at times and destroying communication at others. Or the PLM transmitter degrades as more messages are sent.

"Ok.. but I don't see an application other than monitoring devices to see they're working." That is its function.

Yes, you need a different magnetic switch SECO-LARM SM-300Q/WH Surface Mount Magnetic Contact Switch, Normally Open Or SECO-LARM SM-226L-3 which is what the garage kit came with in the past Smarthome carries both of these

"can you actually link a controller device to another controller device??" Yes. The device firmware does not have a list of all device types (cat/subcat) values to know which might be a Controller and which might be a Responder. Also the Controller does not know which Group/Node is being linked to so a device such as an I/O Linc could be a Controller or Responder. Regardless, devices do not have a list of all devices types to know what it is being linked to.

The Red ! indicates the ISY/PLM cannot communicate with the device. With this happening to devices receiving power from the same circuit as the PLM either the PLM is defective or something on the PLM circuit is absorbing (or noise) the Insteon signal. An Event Viewer at LEVEL 3 while accessing a device powered from the PLM circuit will show how bad communication actually is. The Hops Left=x count should indicate the degree of problem.

jerlands The is/is not Responding is looking for the Red ! indicating the ISY is/is not able to communicate with the device.

The 2-wire SwitchLinc is designed for use with incandescent loads. The 2-wire SwitchLinc steals power through the incandescent bulb(s) which it cannot do through LEDs.

DO NOT put the collection of RF devices into linking mode. Putting more than one device into linking mode cancels each other out. Do the Restore Modem (PLM) without putting any RF devices into linking mode. When the Restore Modem is complete, if there are RF devices that have a Red ! or Green pending Icon, put one device at a time into linking mode, selecting Write Updates to Device. When that device is complete do the next one with pending updates. Putting an RF device into linking mode is just that, it is in linking mode. If a second RF device is put into linking mode at the same time the devices are linked together. That is how a Set button link is done. Not what you are looking for.

Unfortunately SmartLabs/Smarthome stopping selling the garage kit with the magnetic switch that has both a NO and NC magnetic switch built in (had 3 wires). The only good solution is to change the magnetic switch to NO which is closed when the magnet is away from the switch (I/O Linc will be On when door is Open).

Only by process of elimination. The Event Viewer at LEVEL 3 can be used to monitor the Hops Left=x counts to have something objective to look at to see if removing an appliance (unplugging) has an effect. By exercising various devices to see which have good comm and which have marginal comm a pattern may develop. It is time consuming and often frustrating but well worth the time to obtain a good Insteon network.

The answer to the first question is No. The Blue wire, which is normally connected to Line, can be disconnected from Line allowing the InLineLinc Relay to be used as a dry contact NO relay.

A device needs to be filtered only if it is causing a problem. Usually a device causing a problem when turned On but not when Off needs something. If the Insteon network does not have a problem when a device is On no need to add a filter. Electronic devices need to be unplugged to see if Insteon network improves. Todays device continue to provide AC to power supplies so things like IR or power On from sound work. That is why it is necessary to unplug them when testing to see if things improve.

Do a Show PLM Links Table followed by Count. Do this 4 times to verify the PLM link count is the same each time. Any Insteon traffic reaching the PLM during the Show will cause the link records displayed to be falsely high or low. A Restore Device will restore the links in a device. Unless all the devices that are having problems were being power cycled by the one breaker I suspect PLM link table problem over a device link table problem (if it is a link problem). Any time there are multiple power cycles I worry about the final state of Insteon devices particularly if the power was Off for a short period of time. It takes several seconds for the power supply to bleed off when power goes Off. Repeated cycling can catch a device with marginal power which affects how the device operates when power is restored. If an Access Point was involved with the power cycles I would do the 4 tap Set button test to insure the Access Points are functional. The PLM link table can be restored with a File | Restore Modem (PLM). Why was the breaker being cycled?

When a device that should report status updates does not it is either 1 - responder link record in PLM missing 2 - controller link record in device missing 3 - comm issue – powerline or RF 4 – defective device or defective PLM (both are very low on possibility list) If the ISY did not power off with the circuit breaker cycles it would not know to query devices.

Nothing is needed in the second Program If section. If $Zone6 is 1 And Program 'stay_mode' is True Then Run Program 2 Else If Then Set Scene 'Foyer' On Wait 1 minute Set Scene 'Foyer' Off Else

"Would the [calm down] action in the following example execute...'" Yes. There is no False to the "If Control 'panic button' is switched On". The Program triggers when an On command is received from 'panic button'.

Let's say I have a program with no "Conditions," just a scheduled time of "If Time is 9:00:00AM" 1) Is the Else block in such a program irrelevant (would never execute)? The Else clause will not execute based on If evaluation which is always True and evaluated only once at the specific time. 2) If I am silly enough to have a "Wait 30 minutes" as the first command in my Then block, would commands following the Wait execute despite the fact that the program's time condition is no longer true (it's no longer 9AM) at the end of the 30 minute wait? In other words, does the completion of a Wait/Repeat command/block only cause non-time Conditions to be reevaluated? Statements after the Wait 30 minutes will execute, because of number 1. There is no False evauation of a specific time. 3) Does using a time period (From [time] for [duration] or From [time] to [time]) complicate this at all? I don't think it complicates it but it certainly changes things. When the To time (or ending time with duration) arrives the Program is triggered. The If evaluates to False as the time (albeit mill-seconds) has past so the If is False driving the Else clause. If there was a Wait in the Then clause and the Wait time had not expired before the To time or ending time arrives the If is reevaluated to False and the statements after the Wait would not be executed. 3) What is infinity minus 1? Context?

whywork When running these tests have the Event Viewer running at LEVEL 3 while the thermostat is being warmed. The key is whether there is a cmd1=6E (temp change) message coming from the thermostat as it is warming. A temp change message being received (please post message) without the new temp being displayed would indicate an ISY question. I suspect the temp change message is not being received but the only way to know that for sure is to have the Event Viewer running at LEVEL 3 while the thermostat is warming. Sun 05/26/2013 09:30:48 AM : [iNST-SRX ] 02 50 1F.0F.B4 22.80.0B 01 6E 2D (2D)