mfullerca

Sorry, I'm not sure what you're talking about. I work in network security and have never heard the term "java firewall allowances", nor does Google turn-up anything obvious. The Mac isn't mine and I'm not a Mac person, so I don't know what all settings it has, but the Ubuntu system is the same one that I'd been using for years to manage the isy994i and nothing relevant has changed on it, nor does it have a "firewall", nor is there anything between it and the isy994i. Also on Ubuntu I've always downloaded the .jar's and run Java from the command-line so that I'm not susceptible to all these browser-running-Java security issues, cache issues, etc. Ultimately the fact that I get the exact same behaviour on the Mac (launched through the browser) and Ubuntu (run from the command-line) is telling that the problem is on the isy994i end, not the client/browser end.

Yes, both are 4.7.3 (that was the first thing that I checked).

Hi. I have an isy994i running 4.7.3 (both firmware and UI). I've had it since 2013 (3.x firmware!) and it generally works fine, but on the upgrade from 4.6.2 to 4.7.3 the "Emails/notifications" tab broke, and now I need to change my email address and cannot. All the other tabs work, and the "Emails/notifications" tab exists, just clicking on it messes-up the UI. There is still something going on because if I use the tab key to navigate, occasionally it'll paint an input box, and with enough effort I can figure-out what some of them are, but there's not enough context to find the right button to edit and save my email address. Btw I've tried this on both MacOS and Ubuntu. On Ubuntu where I'm running Java from the command-line, I also tried Java 8, 9, and 11, and all exhibit this problem. Below is the exception I get when I click on the "Emails/notifications" tab: Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at java.desktop/javax.swing.JTable.prepareRenderer(JTable.java:5758) at java.desktop/javax.swing.plaf.synth.SynthTableUI.paintCell(SynthTableUI.java:679) at java.desktop/javax.swing.plaf.synth.SynthTableUI.paintCells(SynthTableUI.java:576) at java.desktop/javax.swing.plaf.synth.SynthTableUI.paint(SynthTableUI.java:360) at java.desktop/javax.swing.plaf.synth.SynthTableUI.update(SynthTableUI.java:273) at java.desktop/javax.swing.JComponent.paintComponent(JComponent.java:798) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1075) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:908) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1084) at java.desktop/javax.swing.JViewport.paint(JViewport.java:737) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:908) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1084) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:908) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1084) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:908) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1084) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:908) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1084) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:908) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1084) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:908) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1084) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:908) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1084) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:908) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1084) at java.desktop/javax.swing.JComponent.paintChildren(JComponent.java:908) at java.desktop/javax.swing.JComponent.paint(JComponent.java:1084) at java.desktop/javax.swing.JComponent.paintToOffscreen(JComponent.java:5256) at java.desktop/javax.swing.BufferStrategyPaintManager.paint(BufferStrategyPaintManager.java:246) at java.desktop/javax.swing.RepaintManager.paint(RepaintManager.java:1313) at java.desktop/javax.swing.JComponent._paintImmediately(JComponent.java:5204) at java.desktop/javax.swing.JComponent.paintImmediately(JComponent.java:5014) at java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:857) at java.desktop/javax.swing.RepaintManager$4.run(RepaintManager.java:840) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:89) at java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:840) at java.desktop/javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:815) at java.desktop/javax.swing.RepaintManager.prePaintDirtyRegions(RepaintManager.java:764) at java.desktop/javax.swing.RepaintManager.access$1200(RepaintManager.java:69) at java.desktop/javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1880) at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:764) at java.desktop/java.awt.EventQueue.access$500(EventQueue.java:97) at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:717) at java.desktop/java.awt.EventQueue$3.run(EventQueue.java:711) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:89) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:734) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:199) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)

So I didn't follow-up in March because I just returned the bad modem vs replacing it since the old modem wasn't bad, replacing the PLM was such a pain, and testing a replacement just to have a spare on hand didn't seem recommended, so it seemed a bad ROI to buy and sit on one w/o testing it, especially if there's a known bad batch in circulation. Fast-forward to July and the old PLM died (after 3.5 years) so I ordered a new one (overnight). It works so far, V2.2 production date 1617. Two questions / comments: 1. Why do these fail so readily? It seems annoying for such a critical component. And is there anything I can do to mitigate the risk? E.g., normally I'd put something like this on a high-end surge suppressor / noise filter, but those are not recommended for obvious reasons. 2. After restoring the PLM I noticed the LED flashing on my motion detector even though it's disabled. Last time this happened I debugged it to having an incorrect link. This happened this time, too, and so I started doing Diagnostics -> Show Device Links Table -> Compare and discovered just about everything has entries for the old PLM. Is this expected? Is this harmful and I should be doing a "Restore Device"? Thanks!

Btw, the "old" / still working one is V1.7 (as I remembered), production date 1222 (which makes sense -- I likely got the system in late 2012 or early 2013).

LeeG, good news! Restoring the last backup seems to have fixed everything and, as a bonus, it seems I took my last backup after I'd re-written my programs (so I'm not so dumb as to not keep my backups up-to-date, I just have a bad memory ).

LeeG, any way to save the recent modifications to my programs when restoring the backup? Or any other way around this (e.g., hand-edit the link XML and reload, or factory reset, re-add, and "replace device"), because I need to weigh the man-hours of trying to reproduce ~3 hours of changes to the programs vs this.

Teken, "new"/ dead PLM says V2.2 1546. "Old" PLM will have to wait until I'm back home, but IIRC it is V1.7.

LeeG, apparently this board won't allow upload of .xml files? So I put them in a Zip: Kitchen.* is the switch from #4 (24.EF.1B) Landscape.* is the device in the scene from #4 (22.70.6D) Thermostat.* is one of my failed thermostats (just for additional data) Recall the PLM is 1E.46.31 (also broken PLM was 3D.C8.09). Thanks! links.zip

Yes, Firmware and UI are the same (attached). PLM is 1E.46.31 v9B. At level 3 ("Device communication events"), I see events if I take action from the ISY994i, but if I go manipulate devices, there's nothing. I tried: Changed temperature on one thermostat. Did jumping jacks in front of motion detector. Changed temperature on other thermostat. Activated a scene from a switch (one switch, one outlet). Pressed a button that normally activates a program on the ISY994i. Everything failed but #4 (the scene worked, but it is between a switch and an outlet; the ISY994i is a passive observer for that). No events logged. These are all devices with previously ~98% event reliability. I attached the event log, anyway, but my unlogged actions start with #1 around 9:00:00pm. I also tried to restore a RemoteLinc 2 at 9:01:27pm to no avail. ISY-Events-Log.v4.3.26__Thu 2016.03.17 09.13.52 PM.txt

*sigh* The new PLM is totally dead (LED dark, doesn't respond to factory reset, no beep or anything). So I went back to the original one and I did as LeeG suggested (Power down ISY and PLM. Connect PLM and power it. After 30 seconds power ISY. When ISY and Admin Console are fully up, run Restore Modem PLM. When that is finished run "Restore Devices" which will take some time. Any battery powered devices must be restored "one device at a time"). No change from my original post: devices seem to not update the ISY994i. I'm tempted to go back to the last backup and repeat the process, but I'd done a rewrite of some of my programs and I'd rather not lose that so I'm not going to do that unless someone says it is absolutely necessary and better than re-linking every device (I only have 12). The annoying thing is, though, I've already reset and restored 8 of the 12 devices, and some at least 5 times (the motion sensors), so I have no faith it will help.

Nope, fortunately I avoided the "Delete Modem" trap.

I realize that now, but there was nothing in the UI to indicate that this was a bad idea. And yes, this was my conclusion about the effects/results as well. IIRC the error was the one that indicates it can't communicate to the PLM at all (0.0.0 or something like that). Given all the bad things I've heard about PLM reliability, I'd like to use the new one so I have one with perhaps a longer life remaining and a known good emergency backup on hand, but I don't want to waste a lot of time. E.g., if I'd have known what I was getting into, I'd have not tried to test it. Thanks. Btw, I already did this process twice (once with each), but I will try again since I now have more confidence it is the right thing to do. Re: the battery devices, it would be nice if something made this clear as well. I believe I was inadvertently linking a motion detector with its neighbor by trying to do them at once.

I have an ISY994i running 4.3.26. Similar to the user in "New PowerLinc Modem 2413S - most of my devices no longer communicate": http://forum.universal-devices.com/topic/17943-new-powerlinc-modem-2413s-most-of-my-devices-no-longer-communicate/?hl=%2Bplm+%2Blinks I made the grievous error of installing the new PLM w/o power cycling[*]. After reading the correct procedure and trying a few iterations, I eventually concluded the new one may be defective (not 100% sure, but "Diagnostics->PLM" Status was giving an error). I decided to just go back to the old one, also with the proper procedure, but since then almost nothing works right: I've manually reset and "Restore device" stubborn devices I've got the admin console to the point it can see every device, no "1011" icons, etc. If I "Query" any device, the admin console immediately gets the correct state However, if I change state of any device (on/off, thermostat change, etc) the admin console fails to see the event Similarly, all motion detectors do nothing So, it is as if all devices function properly independently, but when their state changes, they are not notifying the PLM. Any ideas? I'm at my wits end because I'd think a reset and "Restore device" should fix it, and everything seems fine otherwise. To make matters worse, I'm about to go on vacation and I really need a few key components to function before I leave or I'll come back to a dead lawn, etc. Thanks! __ * I bought one as a "backup" because I thought my current one broke, but old one just needed power cycled. I'd foolishly decided I should test the new one to make sure it worked.