Hi guys. my ISY 994i has all of the sudden become very sluggish in controlling my devices. I occasionally get an error or two showing no comms with certain devices but a click within the admin console or the web UI usually wakes it back up and everything's fine. all of the sudden it takes four or five on clicks to get a device to turn on. this is intermittent. it only happens 50% of the time the other 50% of the time it's clean and crisp as it has been for the past 13 years. I do have backups of everything and I could do a full restore but I haven't had to touch my ISY in like 5 years. It just runs. Could one of you guide me resetting the PLM, the isy and the link table please? Below are some errors that I was seeing before cleaning up the programs and rebooting and then last is a error log of a clean boot. I did just renew my Alexa portal which had been expired only one day. The issues I am seeing started about a month previous.

Thank you!!

As found when I logged in.

Sat 2025/08/02 04:58:59 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:04 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:09 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:14 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:19 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:24 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:29 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:34 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:39 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:44 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:49 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:54 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 04:59:59 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 05:00:04 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 05:00:09 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 05:00:14 AM System -170001 [UDSockets] PSub:41 error:6

Sat 2025/08/02 05:00:19 AM System -170001 [UDSockets] PSub:41 error:6

Clean boot after clearing out old unused programs and a few devices:

Mon 2026/01/19 01:00:00 AM System -10 n/a

Mon 2026/01/19 07:29:29 AM System -10 n/a

Tue 2026/01/20 03:01:54 AM System -10 n/a

Tue 2026/01/20 08:01:38 AM System -170001 [Auth:-10104] 192.168.22.194:54719->80, Num=3

Tue 2026/01/20 08:01:38 AM System -170001 [Auth:-10104] 192.168.22.194:54720->80, Num=4

Tue 2026/01/20 08:01:45 AM System -170001 [Auth:-10104] 192.168.22.194:54730->80, Num=5

Tue 2026/01/20 08:22:34 AM System -10 n/a

Tue 2026/01/20 08:48:38 AM System -5 Start

Tue 2026/01/20 08:48:48 AM System -110022 /CONF/INSTENG.OPT

Tue 2026/01/20 08:48:48 AM System -110012 /CONF/INSTENG.OPT

Tue 2026/01/20 08:48:52 AM System -110022 /DEF/F6/I1/NLS/EN_US.TXT

Tue 2026/01/20 08:48:53 AM System -110022 /CONF/UXT.BIN

Tue 2026/01/20 08:48:53 AM System -110012 /CONF/UXT.BIN

Tue 2026/01/20 08:48:55 AM System -170001 [Network] Established

Tue 2026/01/20 08:48:55 AM System -60001 pool.ntp.org

Tue 2026/01/20 08:48:55 AM System -140000 my.isy.io

Tue 2026/01/20 08:48:55 AM System -60001 pool.ntp.org

Tue 2026/01/20 08:51:10 AM System -10 n/a

Tue 2026/01/20 08:52:17 AM System -10 n/a

Tue 2026/01/20 09:05:47 AM System -10 n/a

Tue 2026/01/20 09:19:04 AM System -5 Start

Tue 2026/01/20 09:19:05 AM System -110022 /CONF/INSTENG.OPT

Tue 2026/01/20 09:19:05 AM System -110012 /CONF/INSTENG.OPT

Tue 2026/01/20 09:19:09 AM System -110022 /DEF/F6/I1/NLS/EN_US.TXT

Tue 2026/01/20 09:19:10 AM System -110022 /CONF/UXT.BIN

Tue 2026/01/20 09:19:10 AM System -110012 /CONF/UXT.BIN

Tue 2026/01/20 09:19:11 AM System -170001 [Network] Established

Tue 2026/01/20 09:19:12 AM System -60006 n/a

Tue 2026/01/20 09:20:48 AM System -10 n/a

Edited 13 hours ago13 hr by bwbeisne
adding isy firmware version, fixing typo

If the problem appears global and random, I usually suspect comms problems or failing PLM. Perhaps a failing Insteon device has the ability to flood the communication paths, but I am not sure how to troubleshoot such an issue besides trial-and-error.

Unfortunately, I am not much help with regards to error messages.

I do suspect it might be the PLM again but last time it just totally failed. It wasn't partial. Do you know the steps to clear out and fully reset the PLM?

@bwbeisne not that it would be the entire answer to your issue since it's "worked" this long, but you're on an outdated firmware. It's a small update from 5.3.3 to 5.3.4. I would suggest you make a backup of your system and update to 5.3.4 to see if there are any fixes in that update that might resovle other underlying issues. The release information for 5.3.4 and the download links can be found here: https://forum.universal-devices.com/topic/33287-534-isy994-last-release-for-isy994/

The errors of "System -170001 [UDSockets] PSub:41 error:6" are infomrational in sorts for the ISY. According to Michel in another post (from 2019) this indicates that a socket isn't closing properly. Do you leave admin console open for long periods of time? And you also mentioned something about the web ui (is this through the portal?). Neither options are designed to be left open/connected for long periods of time. I woudl suggest you log out of everything if changes are not actively being made.

See here: https://forum.universal-devices.com/topic/28034-help-with-repetitive-errors/

Other items that would tend to slowdown admin console:

Memory usage of Java on your system. Look up how to set min/max memory settings in the Java console (configure java).

Looping programs - make sure in the program / summary tab that no programs are looping. Usually this would make admin console unusable, but just watch for any out of control programs. Look in the summary tab for any programs that are set to run at boot. Turn those off or disable the programs for now and reboot the system again.

Lastly, are you using any 3rd party apps to access the ISY994? I would make sure those are closed and/or disconnected from the ISY994 then power cycle the ISY994.

34 minutes ago, bwbeisne said:

Do you know the steps to clear out and fully reset the PLM?

This could be a drastic last step that I would suggest. If you do this make sure you have a current backup and perhaps even a backup from before these issues began. If the PLM is failing (again) making a backup now could include issues from the failing PLM. This is why you would want to be sure you have a (recent) backup from before the issue was noticed.

According to the PLM quick start guide - to factory reset the PLM -

To reset PowerLinc Modem to its original factory settings, unplug from wall outlet and wait 10 seconds. Press and hold Set button; while continuing to press and hold, plug back in. A long beep will sound; continue holding Set button until beep stops, then release.

What's strange is after the reboot you're having something logging into the device that's failing (-10104). Then you have some files that are failing to open (-110022) (you can see more about the error codes in the wiki).

It might be a problem with the SD card and that gets a lot more involved with fixing. Look in the wiki for replacing the SD card. Again, try running a backup now and see if you have any recent backups that you could try to restore depending on your next steps.

Thank you Geddy,

No I am never leaving the admin console or the web server open. All automation is internal, either time or condition based within the ISY. The only external interface is the Alexa portal subscription which has worked fine for a very long time. As far as memory goes, the ISY shows 20mb used 868mb free. I don't know but I assume the Java memory usage statement pertains to the admin console only correct? For this everything is default and has been working fine using the defaults since I started with ISY 10+ years ago. I have never had to do anything other than 'get java' from day 1. Plus this issue appeared and persisted a month or two before I logged back in to the admin console.

Yes, this is certainly starting to look like a hardware issue either SD card or PLM. Can we even buy PLMs any more? Are there any other, more useful logs of files I can share to help pinpoint this a little better?

Are these devices directly linked via scenes or controlling programs

I have 4 or 5 scenes driven from various keypads. I have 6-8 keypads directly linked to various target devices. Lamps nearby etc..