MMAltair

I like the idea of implementing a backup function in UD Mobile. My phone has plenty of storage for the backup files and it gets backed up automatically. I know the UDI team is busy deprecating the Java console but if this is primarily a UD Mobile effort perhaps there is an opportunity.

Thanks for the ideas. I ended up replacing the modem and manually restoring the Insteon network by deleting, resetting, and re-adding each device. Things are mostly working now with the exception of a couple of devices that still get some communication errors. I will investigate that issue later. On the programs topic I have hundreds of programs with many of them tightly integrated with UD Mobile. It would be an enormous task to try and recreate the programs along with their associated variables. I plan to be much more diligent about keeping EISY backed up on a regular basis. It would be nice if there were a way to automate regular backups of IoX, perhaps within the local EISY file system. Thanks again Mike

Thanks for the ideas. I'm pretty sure the Insteon network is the only issue in my system so perhaps the PLM Restore I tried messed up the PLM tables. I'm reluctant to try an old backup since I will lose programming and it will likely still leave my Insteon network in broken state due to the Insteon device links changes I've made trying to debug the current problem. My next step is to delete a deice, do a factory rest on it, and re-add it to IoX. Hopefully this will solve the problem of IoX thinking there is a problem with the re-added devices.

It's certainly possible that an Insteon device was affected by the power outage. The devices I've deleted and re-added seem to work just fine with the exception of still having an ! mark in front of the names in IoX. In the logs I've looked at there aren't any retries going on indicating there aren't communication issues. I'm going to try an experiment where I delete a device, factory reset it, and re-add it to see if that clears up the problem of the system think something is wrong with the device. Thanks for the feedback.

I deleted the device using the "Delete" menu option by right clicking on the Device name in My Lighting. I then added the device back using the drop down menu "Link Management" and then selecting "New Insteon/A10/X10 Device". The device has an ! mark in front of it. I didn't do a factory reset on the device before I re-added it. I have not added the device back to the scene that it was originally part of. Should I be removing devices from the scenes first before deleting and re-adding them to IoX? One interesting observation I see is anytime I make a change to a device IoX is out writing to many devices that have nothing to do with the device I'm currently working on. I would expect this behavior if the device I'm working on were part of a scene that another device is in but this is not the case. Seems odd. Another thing I just figured out is the PLM link table only has entries for the devices I have deleted and re-added to IoX (10). It has no entries for all of the other devices in my system (~ 30 devices). I suspect that when I tried to do a restore on the PLM somehow the PLM link table was erased. I haven't been very diligent about creating back ups for IoX. The last backup I have is from when I updated the system to 6.0.4 back on 3/7/2026. I've made quite a few programming changes since then and would hate to lose all of that work by restoring an old backup to try and fix the Insteon issue. Here's the PLM Links table -

I'm back trying to make progress on this. I have not replaced the PLM and instead am trying to understand the source of the problem. As an experiment I deleted 2 devices that are in a scene and re-added the devices to the system. In this experiment the devices work fine after re-adding them but I still get an ! mark in front of each device in the My Lighting list. I then did a compare between the Device tables and the IoX tables and it shows a mismatch on one table entry. Do you have any idea why there would be a mismatch on the one entry after deleting and re-adding the device? I have included the screen shot below. Thanks

Thanks. This log was a test log where I only tried on/off commands to one device that has an ! mark which doesn't work along with on/off commands to a couple of devices that have ! marks and were deleted/re-added and they do work. I have to disable a bunch of my polyglot plugins during the test since they fill the device communication log with unrelated entries. Additional background: After the power failure none of my insteon devices worked so I tried unplugging the PLM, plugging it back in, and then restarting EISY to no avail. I then repeated this procedure but this time I unplugged power from EISY after restarting the PLM and then things seemed to work. However, a few days later it was apparent that only some devices were working. As a debug step I did try and do a restore on the PLM with no change in behavior. One thing I should mention is around the time I noticed things weren't working I tried launching the Admin console using the wrong version of start.jnlp which worked (and shouldn't have). Shortly after this i realized my mistake and re-launched with the correct version of start.jnlp which also worked. I don't know if this error contributed to the problem or not. As I stated before, I believe I need to rebuild my Insteon network with my new PLM and delete/re-add each Insteon device so the devices are aware of the new PLM. I plan to try and do a Restore on the new PLM to see if this improves things. It will take me a few days to do this work. Mike

Just getting back to this. Thanks for the ideas. I did check the Device Communications event log and do see some Nacks when I send commands to devices that have not been deleted and re-added to the system. I still suspect this is related to the power outage we had a few weeks ago. Since nothing else has changed in the house I think the PLM was likely damaged (It's old) by the power outage. My next step is to replace the PLM with a new one I bought a few moths ago, as a spare, and see if this resolves the issue. Below is a snippet of the event log - Mon 08/03/2026 12:06:53 PM : [INST-TX-I1 ] 02 62 1A 38 33 0F 11 FF Mon 08/03/2026 12:06:53 PM : [INST-ACK ] 02 62 1A.38.33 0F 11 FF 06 LTONRR (FF) Mon 08/03/2026 12:06:53 PM : [INST-SRX ] 02 50 1A.38.33 3D.94.80 2F 11 FF LTONRR (FF) Mon 08/03/2026 12:06:53 PM : [Std-Direct Ack] 1A.38.33-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Mon 08/03/2026 12:06:53 PM : [D2D EVENT ] Event [1A 38 33 1] [ST] [255] uom=100 prec=0 Mon 08/03/2026 12:06:53 PM : [1A 38 33 1 ] ST 255 (uom=100 prec=0) Mon 08/03/2026 12:06:57 PM : [INST-TX-I1 ] 02 62 1A 38 33 0F 13 00 Mon 08/03/2026 12:06:57 PM : [INST-ACK ] 02 62 1A.38.33 0F 13 00 06 LTOFFRR(00) Mon 08/03/2026 12:06:57 PM : [INST-SRX ] 02 50 1A.38.33 3D.94.80 2F 13 00 LTOFFRR(00) Mon 08/03/2026 12:06:57 PM : [Std-Direct Ack] 1A.38.33-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Mon 08/03/2026 12:06:58 PM : [D2D EVENT ] Event [1A 38 33 1] [ST] [0] uom=100 prec=0 Mon 08/03/2026 12:06:58 PM : [1A 38 33 1 ] ST 0 (uom=100 prec=0) Mon 08/03/2026 12:07:11 PM : [VAR 2 42 ] 4 Mon 08/03/2026 12:07:12 PM : [D2D EVENT ] Event [n006_1921681219] [GV0] [38] uom=56 prec=0 Mon 08/03/2026 12:07:12 PM : [n006_1921681219 ][STS] GV0 38 (uom=56 prec=0) Mon 08/03/2026 12:07:13 PM : [D2D EVENT ] Event [n006_192168165] [GV0] [8] uom=56 prec=0 Mon 08/03/2026 12:07:13 PM : [n006_192168165 ][STS] GV0 8 (uom=56 prec=0) Mon 08/03/2026 12:07:15 PM : [INST-TX-I1 ] 02 62 71 9D 3F 0F 11 FF Mon 08/03/2026 12:07:15 PM : [INST-ACK ] 02 62 71.9D.3F 0F 11 FF 06 LTONRR (FF) Mon 08/03/2026 12:07:16 PM : [INST-SRX ] 02 50 71.9D.3F 3D.94.80 2F 11 FF LTONRR (FF) Mon 08/03/2026 12:07:16 PM : [Std-Direct Ack] 71.9D.3F-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Mon 08/03/2026 12:07:16 PM : [D2D EVENT ] Event [71 9D 3F 1] [ST] [255] uom=100 prec=0 Mon 08/03/2026 12:07:16 PM : [71 9D 3F 1 ] ST 255 (uom=100 prec=0) Mon 08/03/2026 12:07:26 PM : [INST-TX-I1 ] 02 62 71 9D 3F 0F 13 00 Mon 08/03/2026 12:07:26 PM : [INST-ACK ] 02 62 71.9D.3F 0F 13 00 06 LTOFFRR(00) Mon 08/03/2026 12:07:26 PM : [INST-SRX ] 02 50 71.9D.3F 3D.94.80 2B 13 00 LTOFFRR(00) Mon 08/03/2026 12:07:26 PM : [Std-Direct Ack] 71.9D.3F-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 08/03/2026 12:07:26 PM : [D2D EVENT ] Event [71 9D 3F 1] [ST] [0] uom=100 prec=0 Mon 08/03/2026 12:07:26 PM : [71 9D 3F 1 ] ST 0 (uom=100 prec=0) Mon 08/03/2026 12:07:28 PM : [VAR 2 43 ] 3 Mon 08/03/2026 12:07:34 PM : [VAR 2 41 ] 3 Mon 08/03/2026 12:07:39 PM : [INST-TX-I1 ] 02 62 71 0E A6 0F 11 FF Mon 08/03/2026 12:07:39 PM : [INST-ACK ] 02 62 71.0E.A6 0F 11 FF 06 LTONRR (FF) Mon 08/03/2026 12:07:42 PM : [VAR 2 42 ] 3 Mon 08/03/2026 12:07:43 PM : [INST-TX-I1 ] 02 62 71 0E A6 0F 13 00 Mon 08/03/2026 12:07:43 PM : [INST-ACK ] 02 62 71.0E.A6 0F 13 00 06 LTOFFRR(00) Mon 08/03/2026 12:07:51 PM : [INST-TX-I1 ] 02 62 4D 9B F0 0F 11 00 Mon 08/03/2026 12:07:51 PM : [INST-ACK ] 02 62 4D.9B.F0 0F 11 00 06 LTONRR (00) Mon 08/03/2026 12:07:51 PM : [INST-SRX ] 02 50 4D.9B.F0 3D.94.80 AF 11 FF LTONRR (FF) Mon 08/03/2026 12:07:51 PM : [Std-Direct Nack] 4D.9B.F0-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Mon 08/03/2026 12:07:57 PM : [INST-TX-I1 ] 02 62 4D 9B F0 0F 13 00 Mon 08/03/2026 12:07:57 PM : [INST-ACK ] 02 62 4D.9B.F0 0F 13 00 06 LTOFFRR(00) Mon 08/03/2026 12:07:57 PM : [INST-SRX ] 02 50 4D.9B.F0 3D.94.80 AF 13 FF LTOFFRR(FF) Mon 08/03/2026 12:07:57 PM : [Std-Direct Nack] 4D.9B.F0-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Mon 08/03/2026 12:07:59 PM : [D2D EVENT ] Event [ZY004_199] [ST] [100] uom=51 prec=0 Mon 08/03/2026 12:07:59 PM : [ZY004_199 ] ST 100 (uom=51 prec=0) Mon 08/03/2026 12:07:59 PM : [D2D EVENT ] Event [ZY004_199] [DON] [100] uom=78 prec=0 Mon 08/03/2026 12:07:59 PM : [ZY004_199 ] DON 100 (uom=78 prec=0) Mon 08/03/2026 12:07:59 PM : [D2D EVENT ] Event [ZY004_199] [ST] [0] uom=51 prec=0 Mon 08/03/2026 12:07:59 PM : [ZY004_199 ] ST 0 (uom=51 prec=0) Mon 08/03/2026 12:07:59 PM : [D2D EVENT ] Event [ZY004_199] [DOF] [0] uom=78 prec=0 Mon 08/03/2026 12:07:59 PM : [ZY004_199 ] DOF 0 (uom=78 prec=0) Thanks Mike

I tried "restoring" a device that wasn't working with no success. I also tried to restore the modem with no change in behavior. Another thing I discovered is that many more of my devices aren't working although I don't know how many without testing them all. It turn's out the ! mark is only displayed if EISY tries to communicate with a device. I was aware of a number of devices not working (EISY not controlling them) since they are controlled programmatically and I notice when things aren't working. The only thing that has worked so far is to delete a device and re-add it to the network. It takes about 10 min to delete a device and 15-20 min to re-add it. It's going to take weeks to fix this. I may try to restore a new modem and go from there.

Thanks for the feedback. The devices are all dual band devices so I have assumed they are not having communication issues. As I stated in my description, changes made at the device show up in the EISY Admin console so communication seems to work in one direction but not the other. In addition once I delete a device and re-add it to EISY I can then send commands to the device but it still shows up with an ! mark indicating something is wrong. I may try doing a restore on a device that I haven't tried deleting and see if this helps. Mike Will give it a try and report back. Mike

I'm looking for some guidance on how to fix my Insteon network. Background. We had a power outage a couple of weeks ago which seemed to precipitated my issues. My EISY system is on a UPS but not the Insteon modem (for obvious reason). The UPS gave up after about 2hrs so both EISY and the modem were down. When the power came back on the EISY system couldn't talk to the Insteon network. I initially tried unplugging the modem, plugging it back in, and then rebooting EISY, all to no avail. I then tried completely powering off (removing power) EISY and that seemed to resolve the problem. Fast forward a week and now I have multiple Insteon devices showing up with an ! in front of the name and EISY is unable to talk to the devices. However, if I turn on a switch manually this change shows up in EISY for this device. Clearly EISY is getting messages from the ! devices but isn't able to communicate with them. Only about 15 devices out of 41 Insteon devices in the network have this problem. I have tried deleting some of the devices and readding them to the network which seems to allow EISY to control the devices but there is still an ! in front of these re-added devices. Another interesting clue is when I do anything with the network (for example checking the PLM status under Tools) it comes up with the PLM version and then starts updating the network (ie. shows the dialog box to not touch or change anything while the network is updated). This update goes on for 15 minutes or more before it finishes and I see Writes going on to Insteon devices that are not necessarily the ones that have the ! in front of their names. My modem is an older serial modem (Ver v9E) that has worked reliably for years going back to my older ISY system. I suspect the modem flash is corrupted but am not sure how to proceed. I have a spare serial modem that I could try but I don't want to make things worse than they already are. I also have a spare USB modem but it is currently at a 2nd home so not something I can substitute in the near term. BTW: The rest of the EISY system is working perfectly after the power outage. This includes multiple Z-Wave devices, multiple Plugins such as a Yolink network, an ELK system, Ambient weather system, etc. UD Mobile also works fine. Can anyone tell me the conditions under which EISY show an ! in front of an Insteon node name? Is there a logical next step I should try in the debug process? Thanks Mike

I tried this fix and it seems to work. I don't know how many nodes I have but it is a large number. The Elk Plugin by itself populates hundreds of nodes since it exposes all of the zones, counters, outputs (256 of these), and other items related to the security system. The browser isn't involved in this particular issue so I didn't need to do anything related to it. In any case I think I'm back in business. Thanks much for you help! Mike+

I have an EISY system running IoX FW/UI ver 6.0.4 where when I launch the Java admin console using the EISY Finder it loads the "Main" Screen tab properly but when I click on the "Programs" tab it hangs up to the point where I have to use Windows Task Manager to end the Java process. It always hangs at the point where it is creating the Scene Widgets. This has been working reliably for many years and just started not working today. I've tried clearing the Java cache, updating Java to the latest version (Version 8 Update 491), and rebooting EISY, all to no avail. I can launch the Web Browser admin console just fine but this doesn't have the required functionality. As a side note, I have a 2nd EISY system on the same network (different home on a different VLAN) and when I launch the Admin console on it everything works just fine using the same computer with the same .jnlp file. Has anyone else seen this behavior? Any additional debug steps I can take? Mike

I ran into the same problem. Lost my favorites associated with the my Z-Wave door locks. In addition (as stated in other posts) the Z-Wave lock information no longer shows up in UD Mobile. I ended up creating some programs to monitor the conditions of the Z-Wave locks and translate this information into some state variables for use in UD Mobile Favorites. A bit ugly but this work arounds works. Mike