rcwagner

@DennisCYes, you're right. I haven't provided enough info and am probably unfairly tarnishing Java. I'll post more info tonight with my particulars, but from what I recall, these are my general issues: First off, I only use the admin console about 3 times a year when I need to make a change. In the intervening months I've completely forgotten which particular yoga pose is required to connect to the 994. Double clicking start.jnlp really seems to want to start an instance of Internet Explorer and leave a window open. But IE is deprecated and Chrome support for Java seems lacking. At some point I found a "IE extension" for Chrome which seemed to work, but its still iffy and seems to require a particular harsh facial expression and foul language. As I recall, my typical experience is to run start.jnlp, and when it does run, it doesn't find the ISY device. I think I'd much prefer the ISY device just have it's own web interface and once you know the IP address of your device, you're good to go.

Using Java to connect to devices just seems to be such a chore. Sometimes it works, but mostly it doesn't. Is there another way to program the ISY? I'm using the 994 but would be willing to move on to the EISY if I could be assured I wouldn't need Java anymore.

Yes it has a relatively large power transformer. It is several years old, and perhaps 2007ish is about right. I just pulled off the module and sure enough, there is a label on one of the chips: 2412PLM 23 28Sep06. So what does all this info buy me? Can I be certain the EZIO is dead? Or can it be repaired? Going down a slightly different path, are there alternative paths to having an insteon alert on an open garage door? To replace the EZIO will be ~130 from Smarthome. But I see an Insteon 74551 or a GarageHawk G07 for $80 and 70. Are they adequate? Will anything last forever?

I opened the EZIO box and the base board is a Smarthome PowerLinc III Rev B. I'd never noticed before but the back side of the module has a confusing set of product codes and version numbers. Besides the Insteon address, there is one sticker that says "V1.1 0169", Another that says "2662PL 0715", and a third reading "2607Rev1.3 FIRM 52" So far I've only taken the cover off, and pulled off the daughter card. Later maybe I'll remove the base board to look under it. But the caps on that board do not show any obvious (to me) signs of distress.

From the Admin Console I performed a "Restore Modem (PLM)" operation and that seemed to have no effect on the problem. I'm confused by Brian's response. The PLM connected to the ISY is a 2413S, V2.1 with a date code of 1514. But are you saying there is another PLM inside the EZIO? And that one might be bad? My thought is to buy a new EZIO but is there a way to repair the one I have?

I have an ISY 994 and an EZIO-2x4 module (among other things). The EZIO is used to monitor the garage door such that when open an alert light comes on in the family room and the garage lights come on. When the garage door is closed, the alert light goes off immediately and the garage lights go out after 5 minutes. The garage lights (on/off after 5min) are controlled by a program, while the alert light is directly controlled by the EZIO. This all has been working for several years, but now it has failed. In debugging the problem I find that the admin console does not update when the door opens/closes. I'm not sure if it supposed to. However, if I open the garage door and then cause a refresh of the EZIO from within the admin console, the program fires (turning on the garage lights) and the alert light comes on. Likewise with closing the garage door: nothing happens until a do a refresh from within the UD Admin Console. My guess is that the EZIO is not pushing out a state change message (my terminology), so it is likely the EZIO that is partially failed. But I can also imagine a scenario where the 994 is failed. Does anyone have any hints or thoughts on this? BTW, I just updated the admin console and ISY to the latest version (4.5.4) but that had no obvious impact on the problem.

Found it just before you posted! Thanks Stu. New project for tomorrow!

What thread has repair instructions!?!?! I'd do that in a heart beat.

Yes, I've ordered a new PLM. I was just looking at the reviews of the 2413s and many people are complaining about their life expectancy. UD needs to develop their own device! Maybe they can come up with one that lasts longer than 13 months. I'd buy it. Maybe a PLM needs to cost $160 instead of 80.

Hmmm. Maybe it is a bad PLM. Removed power, removed PLM, restored power and I can start the admin console (it asks for password, etc). I see my devices and programs, presumably from the previous restore operation. Then I unplug power, plug in PLM, restore power (did not close admin console). Tried to 'Restore PLM" but that gave an error. What a PITA!

Plugged the PLM back in (this is after my last message). Thought that might have some good effect. Got two popup messages (yikes, who the heck writes error messages in red on a blue background!), one on top of each other. The first one (the one on the bottom, so presumably that one occurred first) said: Socket open failed java.net.ConnectException: connection refused: no further information. The second said: XML Parse Error http://192.168.10.105:62180/0/d.xml So I closed the program and tried again. That just comes up with the admin console, no request for password and empty as far as devices or programs.

@Stu, going to http://isy goes nowhere. I get a message about can't find ISY, check your network connection. I'm not sure how that works anyway. Is there a cache that identifies isy to a particular ip address? Anyway, I pulled the plug to the PLM, and did yet another reset. I tried to connect to http://isy (previous paragraph), and then when to the usual isy.uni.../994i and got the log in prompt! Hey! So I did a restore from a backup, tried to connect again, and couldn't log in

I've tried pulling the memory card - powered it down, took it out, powered it up and got an error light, powered down, reinserted memory card, powered it up. That may have effected the problem a little. However, I also update my version of Java so I'm not sure which caused the change. But, now when I browse to http://isy.universal-devices.com/994i/ the admin console comes up, but that's it. No log in prompt and when I make the log in menu selection nothing happens. I can ping the device (I previously set the IP to a fixed value through the serial port console, so I know the address). I do see the ISY via my router utility (good idea Stu), although the mac address is 00.21.b9 not 89. It shows up as ISY994-EMS in the router. I have done the factory reset, but still cannot get to log in. Oddly enough, when I had problems like this back in February, I wasn't even able to log in via the serial console. This time I can come in via the serial port and log in no problem. But I can't get the device to come up over the LAN. As far as resets go, I hold down the reset for maybe 10s and the lights start to blink, then go to a running pattern, and after holding the reset for 30s more I get a couple blinks on the mem led. Now that the admin console comes up the login popup does not appear, and it looks like the login menu selection is disabled. I can "set Userid/Password" but that does not seem to go anywhere. I have a backup of the ISY. I learned that lesson in February.

Yesterday programs in my ISY stopped running. Today I started troubleshooting (always on a Friday afternoon, with a 3 day weekend looming) and found that I cannot connect to the device over the LAN. If I try the ISY994 Dashboard, the ISYadmin.jnlp or the ISY994 Administrative Console, they all bring up the ISY Finder : Not Found dialog. Clicking refresh searches, but does not find. If I try a web browser direct via http://ISY, or isy.univ..-devi....com/admin.jnlp, it fails to connect. I've tried connecting via the rear serial port, which I can, but then don't know what to do. I tried setting the ip address to a fixed value and then using a web browser to that IP, but it still did not connect. Help!