ixlr8

Long overdue update. The Lamp Module that had random events finally died. I pulled the cover off and it smelled like somebody 'let the smoke out'. I found another Lamp Module I didn't know I had and programed it to act the same as the one with the random events, but didn't install it in the same program. Everything seems to be working properly. Looks like I had an Insteon LED module and a Lamp Module both failing for the same issue. They were purchased at the same time, maybe some sort of factory defect? All seems to be working properly which is leading to a happy wife. :)

I am still getting random uncommanded on/off events from the lamp module, although the number of events is greatly reduced at the different outlet. I have 2 LinkFilters around here somewhere from another project, if I can find them, I will install one and see what happens.

Replacement devices have used the same outlet. I now have the lamp/lamp module plugged into a different outlet on a different circuit. We shall see what happens.

I did a 'factory reset' last night, "enabled" all the programs associated with the lamp module and did a "restore device". I just checked the logs and they didn't show any random on/off events overnight. 12 hours of no random events doesn't mean it is fixed, but it is a good trend. I will report back in a few days with an update. Through all this I did find some minor programming issues not related to this issue I need to correct. EDIT: I spoke too soon, since I originally posted this note I have had 3 random on/off events for the lamp, with no programs commanding the lamp on or off. Not sure if disabling any of my programing will do any good at this point. Back to the drawing board.

Okay, I have disabled all programs that control the lamp module and the lamp still turns on/off. The log file shows the status of the lamp module changing from 0% to 100% with no command given to turn on/off the lamp. L R Lamp Status 100% Sat 2020/10/17 07:22:32 AM System Log L R Lamp Status 0% Sat 2020/10/17 07:22:36 AM System Log L R Lamp Status 100% Sat 2020/10/17 07:27:23 AM System Log L R Lamp Status 0% Sat 2020/10/17 07:27:25 AM System Log L R Lamp Status 100% Sat 2020/10/17 07:27:43 AM System Log L R Lamp Status 0% Sat 2020/10/17 07:27:45 AM System Log When I did the initial install of the module, I selected "Remove all existing links", I do this for all new modules. I assumed that would clear out any garbage that was in the module. Should I do a 'factory reset' anyway? I am at a loss as to what is going on.

Looking at the time stamps on the Program Summary listing, it looks like I might have a flaky keypad. It is the only thing that comes close to the time of the last random light coming on. I will need to verify time stamps with events, this could take a while. I have some days where the light does not randomly come on at all, then this morning it was coming on 7-8 times an hour, starting at 4am.

I have never done a 'factory reset' on a new device as I didn't know I should, or how to do it.

No, I didn't know that, thanks. I did the "find" 3 times thru all my programs, I did find a program I forgot about. But I don't see how any of the programs I have could be causing the issue. I only have one; On-delay-off program and that delay is for 20 minutes.

Short story- I have a light plugged into a lamp module that randomly turns on for a few seconds and then turns off. I can't find anything in my programs or scenes that would cause it. Long story- I had a light plugged into a lamp module that worked fine until the lamp module blew up. I decided to try one of the new Insteon Led Bulbs, so I went thru my programs/scenes and replaced the lamp module with the ILB. After installing the ILB, I noticed that the bulb would turn on/off randomly and sometimes not come on when it should. I figured there was something wrong with the ILB. I removed the ILB and installed a new lamp module for that light. Now the new lamp module is doing the same thing, at random times, day and night, bulb comes on for 1-10 seconds and then goes off. Most of the time it is on for 1-2 seconds. The error logs I have looked at just show the command to turn on or off, but not what is generating the command. Is there any way to see/log what program/scene is causing this random behavior? Is there a way to temporarily disable a program or scene so I can try to find the culprit by removing different programs/scenes until it stops happening? I would rather not have to delete programs and then go back and re-write them. Thank you

Thank you

I have a program that I want to run in the morning, but not every morning and of course which day changes week to week. I presently have a program set up that IF keypad B is ON, then the program runs at a certain time. But at the moment, I have to manually press keypad B to turn it OFF. Is there a way to turn OFF keypad B via an ISY command rather than having to do it manually? Thank you

They didn't have it when I ordered the caps for mine, so I didn't change that cap, I just replaced the others and the PLM is now working again.

Before I saw your note, I did a "modem restore", exited out of the Admin console and then logged back into the Admin console, still had same error, couldn't communicate with KPL-B and KPL-B still showed red '!'. I just saw your note and went to run the test you requested and when I logged in, I did not get the communication with KPL-B error and all items the KPL-B now had 1011 in front of them. I then did a "restore device" and this time it spent a few minutes writing to the device and now all looks normal. !!?? To everybody who helped, thank you. I don't understand what happened, or why it is working, but at the moment everything looks to be running as it should. I did do one thing in follow up to the repair of the PLM that I probably shouldn't have, I connected the repaired PLM to the ISY with the ISY still running. I suspect I should have unplugged the ISY first.

I have no battery operated devices in my system, no 1011 next to any device. Just red ! next to all KPL-B keys. To be clear, from my last post, I think all the sensors controlling the KPL-B key lights are associated with scene's and not programmed thru the PLM/ISY.

Thanks for your input, here is what I have done and where things stand now. KPL- A; PLM had error it couldn't find it after my repair of the PLM. I did a "show device links table" for that KPL and it now appeared that the PLM could see it, but there was no communication to or from that KPL. Per your suggestion I did a "restore device" for KPL A, the system showed it was writing to the KPL- now it seems to function properly. Thank you KPL- B; Again PLM had error it couldn't find it, I tried doing the 'show device links table' for that KPL and it still shows that the PLM can't find it. I tried your suggestion to 'restore device' and unlike for KPL-A, nothing happened when I did that to KPL-B. I have sensors for doors open/closed and lights on/off in my shop, and the lights on KPL-B keys are working correctly to show the status of the sensors. So I am assuming that KPL-B is communicating some way. I have not rebooted the ISY controller or a modem restore yet. Jim