hchain

I deleted all scenes, then recreated them. I never understood that a device can be both Controller and Responder. I believe that was my mistake. Note: When adding a device to a scene, the prompt says: "XX is a controller. Do you want to make it a Responder?" So I thought it was an either/or and never selected Yes. I guess it should say "Do you want to make it a Responder also/too/as well? But it's all good now. Again, thanks for all inputs, they were all informative.

I have 3 KP, some of the buttons are the same on 2 or 3 KP. Let's assume I have a "Den_Lights" on the 3 KP. When I press "Den_Lights" on KP1 to turn the lights ON, the button turns ON. When I press it again, the lights turn OFF and so is the button on KP1. I want the corresponding buttons on KP2 and KP3 to turn ON and OFF in sync with KP1. Obviously, any change on any KP should be reflected on the other 2 KP.

Creating new scenes and assigning them to the buttons solved the issue. Where can I find good instructions on how to set these keypadlinc? I still have problem synchronizing them (buttons ON/OFF on all KP). Thanks for everyone's help on this, it's much appreciated.

This is what I just did originally: I removed the 2 dead keypads and replaced them with the new ones. I added the 2 new keypads to the Device list, then added my ALL_OFF scene to each. The scene does not work on the new keypads, but it works on a 3rd keypad, so I assume the scene is correct. This is what I did today: I connected the 2 dead keypads on an extension cord. One is completely dead, one is blinking continuously. The ON/OFF buttons (A) do not work. This is exactly what I had before removing them. I restored an ISY back-up (the 2 old keypads are there but with a red !). I added the 2 new keypads to the Device list. >>> I can only use the 'Replace with' function Dead to Dead (choice of 2) and New to New (choice of 3 since I have a 3rd working KP). The dropdown lists of the dead KP do not show the new KP (and the new do not show the dead). Any suggestion to move forward? Thanks in advance!

I cannot find this "Replace with" function. How do I get to it? I tried right click and double click on the keypadlinc (button A, and all other).

Brian, Can I restore a version with the old keypads and use the Replace function? If not, what is the 'manual intervention' required?

No, I did not. I physically replaced the keypads, deleted the old ones from the list of devices, then added the new keypads. RV

I just replaced 2 dead keypadlinc with new ones purchased from Insteon. I installed them, added a scene on button G using them as Controller. As far as I can tell, it's exactly the same setup as a 3rd unit elsewhere in the house with the same scene. However, when I press the corresponding G button on either keypad, the scene is not triggered. The ON/OFF button of the new keypadlinc are working fine (Button A) so I assumed they are correctly wired (hot, load, neutral, and ground). On one unit, I added scenes on 2 more buttons, and they don't work either. Anything I need to check to troubleshoot this? Thanks for the help.

Larry, I just found this in the ISY cookbook If Garage / Garage Door.closed' Status is Off Then Wait 1 second Set Scene 'Mudroom / MudRm kpl.LED.A' On Is this what you are talking about? Same with MS I assume: If Motion detected Then Wait 1 second //Do something// RV

Thanks for the above responses from... Geddy: I would say 'most' (thinking about it, I realize that at least one garage relay did not go ON, but most is definitely true). kclenden: I will implement this and see how it helps. Larryllix: This is a little bit above my head, but I will study it

No, the PLM is NOT on the UPS, only the eisy is. Regarding the "not locked," I mean it was working fine, did not have to reboot. (I had some issues in the past where I had to reboot the ISY but I have now added a UPS and I do not expect this to happen again. I think I had it one time with the eisy but that was probably my error when upgrading from the ISY to the eisy.) >>> You should check for random programs running the next time this happens. Is there a log for the program runs?

Thanks, Techman. Looking at this article, it's possible that a dead battery in a motion detector be the cause. I looked at the log but cannot make any sense of it. Can you look at it and tell me if anything draws your attention? I would certainly appreciate it. The All ON event happened between 16:00 hrs on 3/28 and 8:00 hrs on 3/29. Sorry it's a large range but it would take longer to explain Note: My motion sensors are indicated as EQT_MT in the device name. All the X10 are virtual devices, i.e., they do not exist. I am creating them to drive buttons on my eKeypad display. If you do not have the time, I understand and thanks for the link. UDReport.txt

For the second time in a few weeks, all my devices (lights and relays) turned ON at a random time. Yesterday was in the evening when I have no schedule event. The eisy was not locked this morning, I did not have to reboot it to turn off the relays (I turned off the lights manually yesterday but did not notice that my pool refill relay was ON and I will have a nasty water bill next month). The eisy is on a UPS (not the PLM). Is there an event I can catch to trigger an email for instance (I may not be at home when this happens)?

Just in case it's useful to anyone... When using the portal as indicated above by rwsani99 to access the ISY/eISY from eKP: >>> Enter config info: my.isy.io, Port 443, Failover No, HTTPS, Username, Password the Username has to be the Portal username (email), not the ISY/eISY username. RV

Thanks!, I will read carefully.