Jump to content

Admin Console crashing on Mac Pro 10.13.6


Recommended Posts

I received my ISY994i and 2413 modem today. I plugged everything in, downloaded the start.jnlp loader and ran it.

It found my ISY on 192.168.1.207. Version is 5.0.13D.

I clicked on Admin Console. A Java app took over my screen.

An "Authenticating ISY" popup appeared with a login form. I logged in as admin/admin.

I got an Initializing popup, then "Loading Variables", then "Creating Widgets".

Then it seemed to get stuck at "Starting Subscription".  After about ten seconds the message changes to "Starting Subscription, Attem..."  The popup was too small to print the whole message.

What happened next was unpredictable. Either I got an error popup with "Subscriber didn't reply to event: 1 [46]" and "Subscriber didn't reply to event: 1 [45]"
   or
I got a message "Cannot establish subscriptions"
   or
The application simply crashed and disappeared.

After reading something on the forum about it I disabled Avast A/V but I still can't get past this. I also disabled my Indigo 6 server.
I used the ethernet cables that came with the 2413 modem.
I can ping the ISY's LAN IP from the Mac.

Any ideas?

The computer is a late-2013 Mac Pro (cylinder) with 64GB of memory and SSDs running High Sierra (1.13.6).
Java version is 8, Build 201 which the Mac says is the latest.

The ISY is showing only one blue light on the panel, if it matters.

 

Link to comment

This is my exact same setup, so we know it should work. I would try flushing your Java cache, maybe even pull the power on ISY, wait awhile, power it up again and wait till it settles down to one blue light (power, normal) and try logging in again.


Sent from my iPad using Tapatalk

Link to comment
[mention=7880]Dr. Q[/mention],
Thank you. The issue was that the deployment directory for Java cache was corrupt. Renamed it, Java created a new one and all is OK.
With kind regards,
Michel

Thanks for that, Michel. I’ll put that in my troubleshooting Rolodex.



Sent from my iPad using Tapatalk
Link to comment

Thanks for the help.

I got the ISY994 Administration Console to load by disabling Web Shield in Avast.  Whitelisting the IP wasn't working for me. It had to be shut down completely.

I added one Insteon device, a KeypadLink (2486D) and had the app crawl its link table.  It seemed to be working fine insofar as it read the links in the device correctly. It even got their device types more or less correct.  But as you can see almost all of them were flagged with errors.

On one of the few that seemed okay (07.8C.10), I renamed it to Foyer Ceiling Light. It even got the device's current status right: ON.  But when I click to shut it off, nothing happens. Or I get that error message, below.

The 3rd image is my Indigo 6 Insteon controller.  All these devices work with it and using the same wall socket as the UA's modem.

Any thoughts?

Screen Shot 2019-02-24 at 1.08.06 PM.png

Screen Shot 2019-02-24 at 1.08.18 PM.png

Screen Shot 2019-02-24 at 1.11.21 PM.png

Screen Shot 2019-02-24 at 1.20.58 PM.png

Link to comment

Two things, in reverse order:

The error popup you are getting indicates that you have a communications problem between the PLM and the Foyer Ceiling Light device.  Possibly noise on the electrical line, a signal sucker on the electrical line, or perhaps you do not have the two phases of your electrical system bridged.  The first might be due to anything electronic that's plugged or wired in, ranging from LED and CFL lighting, to modern garage door openers, to computer power bricks, even down to cell phone chargers.  The second is most commonly associated with UPS or battery-backup systems that you might have, although some high-tech power strips (e.g. the Monster brand strips used in media cabinets) might also have what they term "noise filters" (and said noise filters cannot distinguish between the Insteon signal and noise).  The latter is commonly diagnosed by using the built-in test on the various Insteon dual-band devices (such as an appliancelinc and your PLM) -- refer to the manual to do the "4-button test" or whatever they call it...

Crawling your existing links is a waste of time, not only in the time it takes to do the crawl, but in the small eternity of time that you (and everyone on this forum who might try to help) will invest in the sure-to-fail effort.  I was given this same advice when I set up my ISY -- and I thought I knew better than everyone else on this forum, and surely I could preserve all my links and make it work...  Well, by trying it anyway, I accomplished nothing other than wasting a lot of my time.  So, don't waste your time -- document what you have and like about, then one by one, factory reset each Insteon device and add it to the ISY,  then set up the scenes natively in the ISY.  Sounds like a lot of work, but it's less work than trying to preserve your links.  Trust us.

Link to comment
Thanks for the help.
I got the ISY994 Administration Console to load by disabling Web Shield in Avast.  Whitelisting the IP wasn't working for me. It had to be shut down completely.
I added one Insteon device, a KeypadLink (2486D) and had the app crawl its link table.  It seemed to be working fine insofar as it read the links in the device correctly. It even got their device types more or less correct.  But as you can see almost all of them were flagged with errors.

On one of the few that seemed okay (07.8C.10), I renamed it to Foyer Ceiling Light. It even got the device's current status right: ON.  But when I click to shut it off, nothing happens. Or I get that error message, below.

The 3rd image is my Indigo 6 Insteon controller.  All these devices work with it and using the same wall socket as the UA's modem.

Any thoughts?
539443883_ScreenShot2019-02-24at1_08_06PM.thumb.png.e6de7e2b3b4c1a82c787faa4d1d68ec9.png
524935655_ScreenShot2019-02-24at1_08_18PM.png.397bc598819933c76ce7e309ec12c851.png
1227958607_ScreenShot2019-02-24at1_11_21PM.thumb.png.ea4ef82dda7600152d5f54010719010f.png
1143138656_ScreenShot2019-02-24at1_20_58PM.png.8abb4e8d2a802e314dd4cc71d572ba9a.png

Is your 2413U PLM still plugged in? Unplug it and try relinking the device.


Sent from my iPad using Tapatalk
Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...