ISY99 / Switchlink Dimmer problem and Programming problem

[geekdoc]

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!

[oberkc]

I programmed keypadlinc "A" to turn on light "B" at 50%. However when physically hit the "A" button, light B turns on at 100%.

 

How did you program the A button? Through the ISY or at the keypad?

 

Remember, or be advised, that these devices, including the ISY, allows one to set different on levels, depending on how a scene is activiated. One could set it up to turn on at 50% if activated by the ISY/PLM and 100% if activated by the keypad.

 

To check, open the scene where you can see the included devices. Click on the scene folder. I assume you see the on level for light B at 50%. Now click on keypad A (within the scene). What is the on level for light B now show? Does it show 100%. If so, change it to 50%. I think, too, there is an option to copy setting from scene. If not, we will have to find another solution.

[geekdoc]

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?

[oberkc]

I suspect this has something to do with your keypad being non-dimmer. Is this a possibility?

 

I have a scene not unlike yours and notice the same thing. When the main scene is selected, all devices show up. Even ramp rates and on levels, even though ramp rates and on levels are not adjustable with relay keypads. Then when you choose one of the controller devices (keypad C, in your case, all devices that are not dimmer go away).

 

Since on levels and ramp rates are not adjustable on relays, I guess the question is not why they don't show up, but why they do when the scene is selected.

 

I also recall certain issues with controlling the load button with another button on the same keypad, but I think this had to do with the mutual exclusion option.

 

If your keypad is a dimming version, we will have to dig a little deeper. Perhaps the forum's smart people have some other ideas.

[geekdoc]

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.

[oberkc]

Yeah, I miss MSDOS. Yes, I agree, there is some level of learning curve with this little black box. Still, I would not like to go back to running through the house pushing buttons. And the programs (if, then, else) is something that cannot be done without a device like this or some other automation software.

[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.

[oberkc]

I have found nothing that I can do manually that I cannot do with the ISY, but many things with the ISY that I cannot do manually. I have also found no limitations that the ISY imparts upon devices.

 

I may have misunderstood your problem, but I also have some 6-button dimming keypads, programmed through the ISY. I can still dim the hardwired light. Press and hold. Am I missing something here?

[gfridland]

geekdoc...

 

I also went though a learning curve early on with Insteon controllers and devices. What I have learned is exactly what oberkc is saying. That is that everything can be done from the ISY.

 

I used to use a different Insteon controller....the EZServe. The reason I went to the UD ISY is that I had the same frustration as you are experiencing when programmin devices.

 

While using the EZServe, I had no ability to reliably create/contol scenes. So I ended up linking manually devices to "duplicate" what the EZServe was supposed to write into the devices. It ended up being a real waste of time and effort.

 

After finally realizing that I was not getting anywhere but back to the beginning with the EZServe, I ended up buying the ISY. Best thing I did as with the ISY I was able to use it a THE interface to control all devices in my home.

 

Any issue I had experienced initially had to do with either poor communication with my devices or the Firewall/Internet Antivirus software. Once resolved, the system is very robust.

 

Issues with KPL's may also be related to the frimware on the specific KPL's and so the dimmin control, led brightness, etc. may be more a KPL issue than the ISY

 

Bottom line...look at communication integrity and the firewall settings if programming issues may again arise.