geekdoc

Well, I decided that I am going to go back to pushing buttons. Because you can't dim and control the hardwired light with the KPL button when programmed through the ISY, I'm finding that most of my home's installation is useless. Meaning, I used a fair number of KPLs in my installation and the hardwired light is always going to be part of the desired scene. My only regret is that this limitation isn't spelled out on Smarthome before I purchased everything. Oh well... Thanks again for the help.

I scanned this thread and didn't see any references to it. Maybe I'm not looking in the right place. -Why can't a KPL turn off (0%) the lights hardwired to the unit? -I don't understand what the message is really trying to tell me when I do "buttons grouping"/mutually exclusive buttons. Let's say I want A = Fan On, Lights 50%, B = Fan on, lights 100%, C = Fan off and lights 50%, D = Fan off and lights 100%. Obviously when I hit "D" I want all other modes to go away with a single button press. But if I follow what the dialog box says and put "A" as my controller and "B" "C" and "D" as responders, I don't see how I can adjust them as "Off" in a scene.

The Keypadlinc is a dimmer and I don't seem to have the same problems you have. Since I last posted, I tried several other computers to resolve my 2nd problem of the "Socket Open Failed java.lang.NullPointerException" when trying to save a program. I rebooted the ISY, unplugged it, and restored it without any success. I also repeated the "FR" and my ISY had the "Error" light continuously lit. My version was listed as 2.7.0. I wondered if somehow the "FR" command was still screwed up in that version and noticing in the Alpha test firmware that later versions were listed as fixing the "FR" command, I opted to make the leap to 2.7.10. The firmware upgrade fixed my programs issue. I can again save programs without any issues. Now what's interesting (to me) is that the firmware upgrade also added the "On/Off" lights that were attached to the keypadlinc. What's also interesting is that if you select "0" as the power level for that particular light, you get a message saying "Keypadlinc local sub-buttons cannot turn off the load! You may want to chose a very low On level instead." Fascinating. Anyone with any ideas why this is? I have to say that I'm finding this box a bit frustrating as it's advertised as a central way to program all the switches without having to do the run around holding buttons thing. Instead I'm finding that I'm spending more time trying to get it to work that I'd otherwise have spent. Reminds me a lot of the days of MS DOS.... those that understood it could do great things but anyone on the outside had a hard time making it work as expected.

Thanks Oberkc. I'm currently trying to program via the ISY. I didn't realize that I should copy scene attributes. OK, so I have keypadlinc "C" trying to turn on the on button on the keypadlinc and another light. I have all 3 listed in a scene. If I go to the scene name, I see the 2 lights and attributes listed on the bottom right quadrant of my browser. However if I click on the button within the scene, the light which is physically attached to the keypadlinc is no longer an option. And if I physically turn on the keypadlinc via the "C" button, the light which is part of the on/off buttons does not turn on and off. Any ideas?

I have 2 problems and am hoping for some help. I have multiple switchlink dimmers and multiple 6-key dimmers. I have the ISY99 and PLM. I didn't hook up the ISY until after I had connected multiple switches and had made some programs using the switch keypads. I went through ISY linking through some direct addressing and some through crosslinking (I allowed the current links to remain). After programming I noticed that some switches continued to act per the old programs. I tried restoring the devices, the PLM, and the ISY and none of it helped. So this morning I did a factory reset using telnet. Today I re-entered all of the links manually and chose the top "remove links" option. This seems to have gotten rid of the old links in the switches and keypads. Now I'm experiencing a couple new issues. I programmed keypadlinc "A" to turn on light "B" at 50%. However when physically hit the "A" button, light B turns on at 100%. I'm not sure what to do at this point. When I control the scene via my computer/isy, it acts appropriately. The second issue is when I go to save a program, I now get an error that says "Socket Open Failed java.lang.NullPointerException". Following the factory reset, I did not have any programs in the "Program Summary" tab, including the 3 AM query. Thanks!