Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ISY lost communication with all device - PLM issue?

Featured Replies

Posted

I’ve got an ISY-94i/IR Pro with approx. 45 devices, which has been working fine for maybe 15 years. Firmware version 4.5.4.   Been having issue the past week or so where some devices were not turning on/off at scheduled times and others would not respond in my MobiLinc Pro app or from Amazon echo through the ISY portal. It seemed syncing Mobilink with ISY would bring back some devices where I could control them, but within a few days that would no longer work and all devices were not responding. Everything appears in the console, but all devices show offline which is apparent when I restart the console and get Failed Communicating With…  each device.  Restarted ISY as well as power cycling the 2413S PLM.. Here’s a snippet of the Event log after restarting ISY:

---------------------------------

Fri 10/10/2025 08:35:03 AM : [  16 12 86 1]      ERR   1

 Fri 10/10/2025 08:35:25 AM : [  16 12 8D 1]      ERR   1

 Fri 10/10/2025 08:35:43 AM : [INST-TX-I1  ] 02 62 16 14 4D 0F 19 00

 Fri 10/10/2025 08:35:43 AM : [INST-ACK    ] 02 62 16.14.4D 0F 19 00 06          LTSREQ (LIGHT)

 Fri 10/10/2025 08:35:47 AM : [D2D EVENT   ] Event [16 14 4D 1] [ERR] [1] uom=0 prec=-1

 Fri 10/10/2025 08:35:47 AM : [  16 14 4D 1]      ERR   1

 Fri 10/10/2025 08:35:47 AM : [INST-TX-I1  ] 02 62 16 14 CC 0F 19 00

Fri 10/10/2025 08:35:47 AM : [INST-ACK    ] 02 62 16.14.CC 0F 19 00 06          LTSREQ (LIGHT)

 Fri 10/10/2025 08:35:56 AM : [INST-TX-I1  ] 02 62 16 14 CC 0F 19 00

Fri 10/10/2025 08:35:56 AM : [INST-ACK    ] 02 62 16.14.CC 0F 19 00 06          LTSREQ (LIGHT)

Fri 10/10/2025 08:36:05 AM : [INST-TX-I1  ] 02 62 16 14 CC 0F 19 00

Fri 10/10/2025 08:36:05 AM : [INST-ACK    ] 02 62 16.14.CC 0F 19 00 06          LTSREQ (LIGHT)

Fri 10/10/2025 08:36:09 AM : [D2D EVENT   ] Event [16 14 CC 1] [ERR] [1] uom=0 prec=-1

Fri 10/10/2025 08:36:09 AM : [  16 14 CC 1]      ERR   1

---------------------------------

And the error log (IP address is my PC I’m working in):

 Fri 2025/10/10 08:35:38 AM System             -170001             [HTTP:0-31-5] 192.168.10.189:53802->89 

Fri 2025/10/10 08:35:38 AM System             -170001             [HTTP:0-31]: POST[1]-->/services             

Fri 2025/10/10 08:35:38 AM System             -170001       <s:Envelope><s:Body><u:GetSystemStatus xmlns:u=        

Fri 2025/10/10 08:35:38 AM System             -170001             [HTTP:0-31-5] 192.168.10.189:53803->89 

Fri 2025/10/10 08:35:38 AM System             -170001             [HTTP:0-31]: POST[1]-->/services             

Fri 2025/10/10 08:35:38 AM System             -170001       <s:Envelope><s:Body><u:GetSystemStatus xmlns:u=        

Fri 2025/10/10 08:35:56 AM System             -170001             [HTTP:0-31-5] 192.168.10.189:53804->89 

Fri 2025/10/10 08:35:56 AM System             -170001             [HTTP:0-31]: POST[1]-->/services             

Fri 2025/10/10 08:35:56 AM System             -170001       <s:Envelope><s:Body><u:GetSystemStatus xmlns:u=        

Fri 2025/10/10 08:35:56 AM System             -170001             [HTTP:0-31-5] 192.168.10.189:53805->89 

Fri 2025/10/10 08:35:56 AM System             -170001             [HTTP:0-31]: POST[1]-->/services             

Fri 2025/10/10 08:35:56 AM System             -170001       <s:Envelope><s:Body><u:GetSystemStatus xmlns:u=        

Fri 2025/10/10 08:35:56 AM System             -170001             [HTTP:0-31-5] 192.168.10.189:53806->89 

Fri 2025/10/10 08:35:56 AM System             -170001             [HTTP:0-31]: POST[1]-->/services             

Fri 2025/10/10 08:35:56 AM System             -170001       <s:Envelope><s:Body><u:GetSystemStatus xmlns:u=        

Fri 2025/10/10 08:35:57 AM System             -170001             [HTTP:0-31-5] 192.168.10.189:53807->89 

Fri 2025/10/10 08:35:57 AM System             -170001             [HTTP:0-31]: POST[1]-->/services          

--------

After reading a lot of posts on here, I’m thinking the issues is my PLM. I do have a new spare one that I can try, but should I go through the reset to factory default on the current one first? From what I’ve read, after reset I would select the Restore Modem ( PLM), is this correct? I do have multiple backup available if the ISY both before I started having issues.

 

Thanks,

Mark


 

    

ISY-Events-Log.v4.5.4__Fri 2025.10.10 08.58.41 AM.txt

Is the green led on your PLM lit

What is the 4 digit date code on your PLM

If you click on TOOLS | DIAGNOSTICS | PLM INFO STATUS, does it show as connected?

If you click on TOOLS | DIAGNOSTICS | SHOW PLM LINKS TABLE, what is the link count. You should run this test when the ISY is least busy

The issue most likely could be with either a failing PLM or the SD card. Don't do a reset until you narrow down the problem

 

  • Author

Is the green led on your PLM lit - Yes

What is the 4 digit date code on your PLM - 1514

If you click on TOOLS | DIAGNOSTICS | PLM INFO STATUS, does it show as connected? - Yes

If you click on TOOLS | DIAGNOSTICS | SHOW PLM LINKS TABLE, what is the link count. You should run this test when the ISY is least busy - Zero

 

Your PLM is over 10 years old and most likely needs to be replaced. It lost all of its link tables.

You can try doing a restore PLM which will write the link tables stored in you ISY into the PLM.  

 

If Link count is 0:

  • Go to file | Restore Modem (PLM) ... this will attempt to recreate all the links in the PLM
  • Once Restore Modem (PLM) is completed, count the number of links in the PLM again using the procedure outlined above
  • If the link count is still 0, then in all likelihood the PLM is dead and has to be replaced
  • Author

Thanks for the information. I have an interesting development. I unplugged the PLM so I could get you the date code. Plugged it back in and I was hearing a repeating buzz that lasted for a few seconds off and on. I unplugged/plugged it back in and the buzzing stopped. I was looking at the console and noticed one of the devices was back on-line. I then went and queried the next active device and it came online and I was able to control the light through the console. I then repeated this for all of the enable devices, (discovered I probably could have done this by going to Network View and selecting Query) and now everything seems to be fully functional from MobiLinc and Amazon Echo. I really didn't do anything different - I had unplugged the PLM at least four times during my initial troubleshooting. 
But I still don't see anything when I go to the PLM Links Table and select Start then Count - still shows zero. What does storing storing the links on the PLM actually do in the communication process between ISY and the devices? I'm sure this is basic knowledge here, but I should know this for troubleshooting in the future.
Even though it appears to be working now, should I still perform the Restore PLM process? No downside to this? 

Appreciate your help,

Mark

Edited by msteelefl

Do you have the older 2412S PLM? If you do is your ISY controller powered by a wall wart? The 2412S PLM had power on the cable between the PLM and controller. The presently sold 2413S PLM does not have that power. So it needs a wall wart supply if you do not have one now.

Checked the Insteon site and the 2413S is in stock. 

Edited by Brian H

2 hours ago, msteelefl said:

What does storing storing the links on the PLM actually do in the communication process between ISY and the devices?

The PLM is really just another Insteon device.  Every Insteon device has a Links Table.  This table tells it who it will respond to, and who it can control.  When you add an Insteon device to your ISY two* links are added to the PLM Links Table (a controller and a responder link) and two links are added to the device Links Table (a controller and a responder).  Without these links, the PLM and device would simply ignore each other and your ISY would not be able to control or receive status messages from a device.

 

* It's possible more links are added depending on the type of device.  For example, a 6-button keypad will have links added for each button.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.