LeeG

The PLM could fail with X10 only but it is not likely. An X10 Controller often sends a signal stronger than a PLM. See if the X10 Controller plugged into the same outlet as the PLM works the 220v X10 device. A new PLM can be used but I don't think it will fix the problem. The more Insteon devices in use the less reliable X10 becomes because Insteon devices do not repeat X10 messages and each Insteon device in the path reduces the X10 signal. If a new PLM is used be sure to follow the Wiki instructions exactly for replacing the PLM and never issue a Delete Modem (PLM).

The actions are not the same. With Trigger Reverse checked the Relay turns On when the button is released. The button is not being cycled so the Momentary Timeout controls when the Relays turns Off. With Trigger Reverse unchecked the Relay turns On when the button is pressed. Now however the button is released which turns Off the Sensor which turns Off the Relay (Relay follows Sense). Using an ISY Program to control Relay cycle avoids the issues using Relay Follows Sense.

"Is this situation my misunderstanding of the way the IOLinc works or is it a possibly defective unit?" That is the expected operation of a I/O Linc. Suggest using an ISY Program to perform the timing of the Relay rather than using Trigger Reverse and Relay Follows Input.

Likely an older PLM that is exposed to capacitor issues. Try a Restore Modem (PLM) to reload PLM link database. If that works a replacement PLM is needed or replace the failing capacitors.

When multiple devices do not have messages received by PLM it sounds like the PLM has lost some/all of its link records.

Restore the ISY Backup taken just before PLM was replaced. That takes the ISY back to the old PLM information. Then power down ISY and PLM. Power up PLM, wait 30 seconds and power up ISY. Then Restore Modem (PLM).

It turns On all the X10 units with an A10 address. It is an easy way "for me" to verify Heartbeat is working. As I mentioned before most folks would use a Notify to send an email.

"Right after I adjusted the backlight to 1/15, in the middle of the day my son went around and started trying to "turn off" all they lights because he thought the KPLs were showing all lights on. He was used to the way they used to look before I started messing with them. " Thanks, now I understand the problem. Will be interesting to see how long it takes to acclimate folks to some times the Off buttons are dark when Off and some times they are illuminated when Off.

I have no problem knowing which buttons are Off or On. All my KPLs are set to the same LED Brightness values. If one KPL has the Off buttons set to the same brightness as On buttons on another KPL then the KPLs are poorly configured.

Davonavo Only changes in state are logged. Since the Heartbeat does not change state unless Wet at Heartbeat time nothing would be expected in the Log. Use a Program to check for Heartbeat and if the Heartbeat does not occur send an email. Example that is sending an X10 message but email is the normal action by most HeartBeat - [iD 0044][Parent 0001] If Control 'Leak Sensor-Heartbeat' is switched On Or Control 'Leak Sensor-Heartbeat' is switched Off Then Wait 25 hours Send X10 'A10/All Lights On (5)' Else - No Actions - (To add one, press 'Action')

Unless the LED Brightness was adjusted before the Restore Device the Factory Reset did nothing long term as the Restore Device changed it back to what was set through Admin Console. Up until these latest KPLs all KPLs over the last ten years came with a setting that had Off state buttons as dim and On state buttons brighter. The buttons were clearly visible in both states during daylight conditions. What you are seeing now (before altering through Admin Console) would be considered an exception by previous KPLs. My KPL out of the box was/is set to 0/5, not 0/15.

Using a new KPL out of the box (hardware v7.3), I added it to ISY. Then did a Query and saw where Factory Reset value for LED Brightness is 05 (Off=0, On=5). I set that same values using ISY and found KPL buttons maintained the same level of Off and On brightness as the original factory setting. If that is not reproducible on your KPL suggest returning it for new unit.

My newest KPL is hardware v7.3. Setting it to Off=0/On=15 (as yours is) has the buttons which are Off basically dark. Removing a button cap shows one of the Off button LEDs as so dark as to be not illuminated. Yours .... Sun 07/19/2015 03:10:49 PM : [iNST-ERX ] 02 51 33 CF 55 39 01 9C 15 2E 00 01 01 00 00 20 20 1C FF 0F 80 00 00 00 00 My v.7.3 Sun 07/19/2015 07:29:38 PM : [iNST-ERX ] 02 51 33 14 23 22 80 0B 11 2E 00 01 01 00 00 20 20 1C FE 0F 02 00 00 C2 00 I don't see how a button that is Off can get any darker than not illuminated.

Happy to. There is an insteondetails.pdf document on insteon.com that may help with how Insteon works. There is more detail than most folks are looking to learn but some of the higher level information may be helpful.

If not discovered yet, try Off=3/On=15 for factory reset values. A Query of the KPL, the 2E Extended response, Data 9 field has the Off/On LED value if the KPL is still set to factory reset. Sun 07/19/2015 03:59:05 PM : [iNST-ERX ] 02 51 15 9A F9 22 80 0B 11 2E 00 01 01 00 00 20 20 1C FE 3F 00 C0 00 00 00

Add buttons A, B, C, D (assuming those are the correct buttons) as Responders to the All Lights Off Scene. Turning the devices On/Off controlled by the buttons has no affect on the KPL Controller buttons that affect those devices.

Factory Reset of KPL ... pull Set button to remove power for 30 seconds push Set button all the way in below frame level, it will beep in a few seconds where Set button is released. This will reset KPL configuration but since the KPL has not been Deleted from the ISY a Restore Device will restore configuration. Before doing the Restore Device set the LED Off/On level to match whatever level you want. Then do Restore Device.

EricK You are back so far in ISY image that is likely why you do not have the heartbeat node. They do add as a TriggerLinc which is what the device was called before they switched to Open Close Sensor

The I/O Linc is powerline only, NO Dual Band RF. This means that outlets on the opposite 120v leg to PLM are dependent on your phase bridging to function. Also some GFI protected circuits can interfere with Insteon.

You are using the Off button level of 0 (effectively LED not powered in Off state) as a general statement of On/Off level relationship. Unfortunately that does not track if you walk the values up starting with Off=1 On=0, 1/1, 1/2, 1/3. Here the LED is powered in both Off and On state and the difference in brightness does apply. It is also useful to remove one of the button caps so the actual LED can be viewed as the numbers are walked up one at a time, 1/4, 1/5, 1/6, 1/7, ....., 1/15, 2/0, 2/1, 2/2, etc. I found it helpful to do the testing in a darkened room as it can be difficult to see if any change actually occurs as the numbers are walked up in 1 increments. The KPL can be Factory Reset without Deleting from the ISY. That will bring the LEDs to factory reset level for a reference point but a Restore Device can be done to restore the KPL after the LED numbers are set as desired.

The Off/On LED brightness numbers can be set to values the device cannot process. The Off/On levels will be 8 increments apart, Off=7 On=15 for example. Setting Off=1 On=15 does not result in 14 increments difference between Off and On. One number or the other is always the controlling factor with what amounts to an 8 increment difference. It has been years since I played with these numbers. HouseLinc started using a single percent number (20% for example) to avoid the issue. Since HL is no longer supported it is no longer possible to draw a comparison anymore. You can Delete the KPL and do a Factory Reset before adding it back but you lose all the unique configuration. Can also play with the numbers until you get what you want, with the understanding that 8 is the magic number for separation.

EricK Your v1.B hardware Open Close Sensor (without pins for physical Jumper) has both Heartbeat and the ability to use both Open and Close nodes. Use Group Devices to bring all nodes together so heartbeat node is with the other nodes. The use of both Open and Close nodes is now software controlled rather than the physical jumper. It will require support added to Admin Console for v1.B hardware, firmware v.43.

A 1 cm gap between switch and magnet is large (1cm is equivalent to 0.39370 inches). I strongly suggest moving the magnet to no more than 1/4 inch at the full closed position.

rominejc "Obviously,this is because the open/close sensor remains open (and therefore on)." Unfortunately that is not how the Open Close Sensor works. As was stated by Stusviews the On command is sent once from the Open Close Sensor. The Motion Sensor will send multiple On commands, once each time motion is sensed. How often this happens depends on the Options set in the Motion Sensor. Suggest you indicate how you have configured the Motion Sensor. Also indicate what should happen under the various conditions; door opened and closed, door opened and left open, door already open. This covers a trip down the stairs. Then explain what you want to happen when traffic is going up stairs; motion sensor starts process, what stops it?. When door is opened, what if door is already open when trip up stairs starts. Does door have to be closed to turn Off lights? It does not help to offer a suggestion (probably two Programs at least) without knowing how the logic should perform to meet your requirements.

When the X10 device is replaced with a Insteon device the Open Close Sensor and Motion Sensor can turn light(s) On directly with a Scene without any delay going through a Program. Program logic can be used to turn Off the light(s) where any delay is not an issue. A Dual Band Insteon device should be used to control the light(s). It is unusual for a delay to exist in Program execution of more than 1 to 1.5 seconds. The Motion Sensor can be slow to react based on Options chosen but would not expect a long delay from Open Close Sensor unless poor RF reception requires multiple attempts by Open Close Sensor to get a response from a Dual Band device. Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3 to trace Insteon/X10 activity. Post the event trace for analysis.