I am not seeing some insteon devices updating in my Administrative Console, and program IF statements are not triggering.  I read a thread with the exact same behavior and also after a isy994i conversion, and for that thread a 'Restore Devices' operation fixed the issue.  I have tried the 'Restore Devices' twice and also rebooted my Eisy and still have the issue.  Query pulls the device status,   And setting On or Off works.  The previous thread asked for Event Viewr level 3 logging.  I cleared the log and change state of one of my switches twice,  Log below

Fri 10/10/2025 11:47:58 : Create REST U7 [/rest/profiles/ns/0/connection]
Fri 10/10/2025 11:52:56 : Create REST U7 [/rest/profiles/ns/0/connection]

Please advise.

 

How old is your PLM? There's a sticker on the back with a 4 digit number, what is that number.

While you have the PLM unplugged, leave it unplugged for 10 seconds and then plug it back in and retest one of your scenarios

@cchandler12011

What's your ISY firmware and UI versions?

Try clearing your java cache, checking all 3 boxes, then download the IoX Launcher from here:

https://isy.universal-devices.com/start.jnlp

 

 

Edited October 10Oct 10 by Techman

Thank you all for the responses and support.  Here is additional information.  I am traveling so please excuse the latency. Went through all the suggestions and still having the same behavior.

PLM,

bought from the emergent Insteon.  

1223   Revision 2.6

Firmware and UI versions

Clear Cache / Download

This was a new laptop but cleared the cache anyway.  From the UD link getting  IoX finder : Not Found.  Tried entering in IP address and also http://192.168.xx.xx and these are not valid. does not provide guidance for desired input / format.  Devices on the same network. Ping works and can connect with my previous jnlp

Unplugging and Scene (Restore)

I unplugged PLM for a couple of minutes to get the 4 digit and revision numbers.  Still not was not receiving device events.  Rebooted the Eisy and still not receiving device events.  Queries and state change operations still work. Don't think I use scenes (versus programs) so did another Restore Device with no change.  I will create a polling / query routine for some devices near term.  but have 50 or so devices and have not researched network bandwidth and power implications.  

Going to be a couple of weeks before the next chance to troubleshoot.  But further suggestions appreciated and I will go through them when I get back to it.

 

On 10/10/2025 at 12:57 PM, cchandler12011 said:

I cleared the log and change state of one of my switches twice,  Log below

Fri 10/10/2025 11:47:58 : Create REST U7 [/rest/profiles/ns/0/connection]
Fri 10/10/2025 11:52:56 : Create REST U7 [/rest/profiles/ns/0/connection]

How did you change the state of your switch? The log shown above is not consistent with changing the state of the switch from the Admin Console. Were you changing the state by manually pressing the switch?

On 10/10/2025 at 12:57 PM, cchandler12011 said:

Query pulls the device status,   And setting On or Off works.

These would be commands that the eISY is sending to the device. Since they work, it implies that at least one half of the link combination between the eISY and device is intact. The fact that you're not receiving status updates from the devices when they are manually activated implies that the other half of the link combination between eISY and device is not intact.

When you add a device to your eISY network, at least four links are created. The first two links allows the eISY to control the device. The other two links allow the device to control the eISY.

One link stored in the PLM tells it that it can control the device. This is called a controller link. A corresponding link is stored in the device that tells it that the PLM is allowed to control it. This is called a responder link. The exact same thing happens with the device. One link (controller) is stored in the device that tells it that it can control the PLM. Another link (responder) is added to the PLM that tells it that it can be controlled by the device.

Depending on the type of device (e.g. keypad, motion sensor), many more links will be created between the PLM and device. Also, when you add devices to scenes, links are added to both the PLM and device.

The fact that you can query and turn on/off devices from the eISY tells you that the PLM has a controller link for the device and that the device has a responder link for the PLM. Since you're not receiving status updates from the device it implies that either the device is missing a controller link that allows it to control the PLM or the PLM is missing a responder link that tells it that it can be controlled by the device.

Since you're having problems with more than one device, it seems more likely that the missing links are in the PLM as opposed to several devices. If the PLM is missing links, it can be caused by many things, but generally falls into several areas.

• The PLM hardware is failing - Replacing or repairing the PLM fixes this.

• An electrical anomaly caused the PLM to corrupt its links table - Using the restore PLM command should fix this.

• Too many devices have been added to the eISY Insteon network or to scenes. The PLM links table can only hold so many links (~1000). If the PLM links table is full when a new device is added or a device is added to a scene, sometimes links for existing devices/scenes are overwritten by links for the new device/scene. The fix for this is to either remove Insteon devices from the eISY network, or to reduce the number of scenes being used, or reduce the number of devices that are included in scenes.

I'd recommend doing "Tools->Diagnostics->Show PLM Links Table" followed by clicking the "Start" button. You want to do this at a time when nothing else is happening on the eISY or Insteon devices as activity can cause the link listing to abort. Because of this, you'll want to list the PLM Links Table several times so that you know you got a complete listing.

When you have a complete listing, click "Save" and save the listing to a text file. This will allow you to use a text editor to search for the appropriate links for the devices that are not reporting status updates.