IndyMike

@RDoc , your query did NOT return an error - Your device responded correctly to the query with 2 Hops remaining (good communication). The ERR 0 notation is the EISY indicating that there is no error (or that it is clearing a previous error). Regardless, what you posted shows the device communicating normally. If you see an ERR 1 in the event viewer, that is typically a timeout error. [INST-TX-I1 ] 02 62 20 AB 28 0F 19 00 [INST-ACK ] 02 62 20.AB.28 0F 19 00 06 LTSREQ (LIGHT) [INST-SRX ] 02 50 20.AB.28 52.63.4C 2B 00 FF (FF) [Std-Direct Ack] 20.AB.28-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 [20 AB 28 1 ] ERR 0

@RDoc , can you run a query on one of your problem devices with the event viewer to to level 3 (and post it). I can remember others having similar issues with the EISY showing node errors where no problems existed. I'm thinking you are having the same issue (no actual communication error exists). I would NOT advise upgrading to a new PLM at this point. Doing so will require writing the new PLM address to all of your devices and will needlessly complicate things. If your old PLM works with the ISY994, it should work with the EiSY.

@SHM , since you are not using scenes, I am guessing that you are turning on multiple individual devices in a single program. That can cause issues where the PLM is bombarded by serial commands thereby causing errors. These errors can lead to uncommanded On/Off, PLM reset, etc. An example is shown in the link below. plm-problem-uncommanded-on-for-multiple-devices Not all devices are susceptible to the uncommanded On/Off. Newer Insteon devices have had the command removed. Fortunately, you can test if your devices are susceptible. Please not that the following will turn on/off ALL susceptible devices in your house. Not something to take lightly if you have motors/fans/garage doors/etc. controlled by Insteon. It will also issue commands to X10 devices (and possibly Z-Wave and Zigbee). I normally use an OFF command since it is less intrusive (try to run when other family members are away or asleep) - Manually turn ON devices you wish to test. Open your event viewer and place on Level 3 From the Admin Console tree - Select "My Lighting". From the My Lighting device window - Select "All Off" In the event viewer you should see the following I1 command from the Eisy to the PLM, and the PLM ACK. Devices that turn OFF have not had the command removed and are susceptible. Sat 10/31/2026 08:25:12 AM : [INST-TX-I1 ] 02 62 00 00 FF CF 14 00 Sat 10/31/2026 08:25:12 AM : [INST-ACK ] 02 62 00.00.FF CF 14 00 06 LTOFF-F(00) If you determine that your device are susceptible you have a few "preventative" measures you can take: Review the Wiki for program activation recommendations - INSTEON_Random_All_On_Events Insert wait commands between successive Insteon commands to prevent overloading the PLM If you have good communications, use scenes to turn your devices on/off.

Curious - I have seen posts regarding issues with the EISY-UI, but nothing regarding IOX. I would think if there were a bug in IOX you would have a lot of company with issues. Please do post back where this leads

@K-bert , your link table read produced gibberish for that device. I'm guessing that if you try this again with the event viewer open you will see poor communications and the data will be different. If you are still running your "test rig", try plugging it in close to the PLM. Edit: The PLM links you posted look correct. If the PLM sees a valid communication from the device it should register it (134 : 0086 : A2 01 71.FC.E9 02 2A 45). My guess is that your communication is so corrupted the PLM is not recognizing it.

@K-bert , please try performing a device link table read/compare (right click device on Console tree, select Diagnostics/Show device Links Table). Examples below. Bonus is you can have event viewer open on "Level 3" to record communications. Please post the resulting table and the event viewer contents. The Link table will show us whether you have the correct links in the device (Please provide current PLM address). The event viewer will show the communication progression, quality (hops remaining), and any errors encountered. The PLM also requires a link in it's table, but that's a little harder to come by. Please post the above and we'll see if a PLM table read is necessary. The examples below show a link table for a device that is linked ONLY to the PLM (53.BC.3A). It is the absolute minimum # of links for a device to function properly. Link Table Read Selection Link Table Contents Event Viewer Communications Tue 10/27/2026 09:47:12 AM : [INST-TX-I2 ] 02 62 18 93 83 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Tue 10/27/2026 09:47:12 AM : [INST-ACK ] 02 62 18.93.83 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Tue 10/27/2026 09:47:12 AM : [INST-SRX ] 02 50 18.93.83 53.BC.3A 2F 2F 00 (00) Tue 10/27/2026 09:47:12 AM : [Std-Direct Ack] 18.93.83-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 10/27/2026 09:47:12 AM : [INST-ERX ] 02 51 18 93 83 53 BC 3A 15 2F 00 01 01 0F FF 01 A2 00 53 BC 3A FF 1F 01 C2 Tue 10/27/2026 09:47:12 AM : [Ext-Direct ] 18.93.83-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Tue 10/27/2026 09:47:12 AM : [INST-TX-I2 ] 02 62 18 93 83 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA Tue 10/27/2026 09:47:12 AM : [INST-ACK ] 02 62 18.93.83 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA 06 (00) Tue 10/27/2026 09:47:13 AM : [INST-SRX ] 02 50 18.93.83 53.BC.3A 2F 2F 00 (00) Tue 10/27/2026 09:47:13 AM : [Std-Direct Ack] 18.93.83-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 10/27/2026 09:47:13 AM : [INST-ERX ] 02 51 18 93 83 53 BC 3A 15 2F 00 01 01 0F F7 01 E2 01 53 BC 3A 01 00 01 CA Tue 10/27/2026 09:47:13 AM : [Ext-Direct ] 18.93.83-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Tue 10/27/2026 09:47:13 AM : [INST-TX-I2 ] 02 62 18 93 83 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 Tue 10/27/2026 09:47:13 AM : [INST-ACK ] 02 62 18.93.83 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06 (00) Tue 10/27/2026 09:47:14 AM : [INST-SRX ] 02 50 18.93.83 53.BC.3A 2F 2F 00 (00) Tue 10/27/2026 09:47:14 AM : [Std-Direct Ack] 18.93.83-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 10/27/2026 09:47:14 AM : [INST-ERX ] 02 51 18 93 83 53 BC 3A 15 2F 00 01 01 0F EF 01 00 00 00 00 00 00 00 00 D2 Tue 10/27/2026 09:47:14 AM : [Ext-Direct ] 18.93.83-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Tue 10/27/2026 09:47:15 AM : [All ] Writing 0 bytes to devices Tue 10/27/2026 09:47:15 AM : [All ] Writing 0 bytes to devices

I don't have an Eisy, but you should see some activity in the Event Viewer (Level 3) when it tries to read the PLM. The 1st line [GET-LNK-RSP] is a must. If it is not displayed, the Eisy isn't trying to read the PLM. If the process is functioning correctly, the Eisy will continue issuing [GET-NEXT-LNK-RSP] commands until it hits the end of the PLM table. Sat 09/26/2026 05:05:07 PM : [GET-LNK-RSP ] 02 69 06 Sat 09/26/2026 05:05:07 PM : [LNK-DATA ] 02 57 E2 00 58 B0 78 01 20 45 Sat 09/26/2026 05:05:08 PM : [GET-NEXT-LNK-RSP] 02 6A 06 Sat 09/26/2026 05:05:08 PM : [LNK-DATA ] 02 57 E2 10 58 B0 78 01 20 45

@oberkc , I know you said this program worked previously, but... Shouldn't the sunset trigger be an "or" instead of "and"? Edit: Never mind, I get it now.

@DNewkirk , I'll start by saying that I'm using an ISY994 - things normally translate well, but there's always a caveat... I interpret the "Backlight" dropdown as "command only". It has no knowledge of the current state of your devices. As you indicated, it does have "stiction" allowing you to set multiple devices to the same level. For I2 KPL's. a query will return the backlight level of a device in D9 of a a "Extended Set/Get command - 2E" extended message . This will show the current setting of the actual device. The full sequence shown in the event viewer follows. The highlighted "09" being returned corresponds of an off level of 0 and on level of 9. Sat 09/19/2026 09:05:59 AM : [INST-TX-I1 ] 02 62 1C DF 01 0F 19 00 Sat 09/19/2026 09:05:59 AM : [INST-ACK ] 02 62 1C.DF.01 0F 19 00 06 LTSREQ (LIGHT) Sat 09/19/2026 09:05:59 AM : [INST-SRX ] 02 50 1C.DF.01 53.BC.3A 2B F6 00 (00) Sat 09/19/2026 09:05:59 AM : [Std-Direct Ack] 1C.DF.01-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 09/19/2026 09:06:00 AM : [D2D EVENT ] Event [1C DF 1 1] [ST] [0] uom=100 prec=0 Sat 09/19/2026 09:06:00 AM : [ 1C DF 1 1] ST 0 (uom=100 prec=0) Sat 09/19/2026 09:06:00 AM : [D2D EVENT ] Event [1C DF 1 1] [OL] [255] uom=100 prec=0 Sat 09/19/2026 09:06:00 AM : [ 1C DF 1 1] OL 255 (uom=100 prec=0) Sat 09/19/2026 09:06:00 AM : [D2D EVENT ] Event [1C DF 1 1] [RR] [28] uom=25 prec=0 Sat 09/19/2026 09:06:00 AM : [ 1C DF 1 1] RR 28 (uom=25 prec=0) Sat 09/19/2026 09:06:00 AM : [INST-TX-I2CS] 02 62 1C DF 01 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Sat 09/19/2026 09:06:00 AM : [INST-ACK ] 02 62 1C.DF.01 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Sat 09/19/2026 09:06:00 AM : [INST-SRX ] 02 50 1C.DF.01 53.BC.3A 2B 2E 00 (00) Sat 09/19/2026 09:06:00 AM : [Std-Direct Ack] 1C.DF.01-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 09/19/2026 09:06:01 AM : [INST-ERX ] 02 51 1C DF 01 53 BC 3A 16 2E 00 01 01 02 00 20 20 1C FF 09 C0 00 00 00 00 Sat 09/19/2026 09:06:01 AM : [Ext-Direct ] 1C.DF.01-->ISY/PLM Group=0, Max Hops=2, Hops Left=1 Changing the backlight to a max level of 7/15 results in the following (abbreviated): Sat 09/19/2026 09:07:51 AM : [INST-TX-I2CS] 02 62 1C DF 01 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Sat 09/19/2026 09:07:51 AM : [INST-ACK ] 02 62 1C.DF.01 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Sat 09/19/2026 09:07:52 AM : [INST-SRX ] 02 50 1C.DF.01 53.BC.3A 2B 2E 00 (00) Sat 09/19/2026 09:07:52 AM : [Std-Direct Ack] 1C.DF.01-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 09/19/2026 09:07:52 AM : [INST-ERX ] 02 51 1C DF 01 53 BC 3A 11 2E 00 01 01 02 00 20 20 1C FF 7F C0 00 00 00 00 The "LED brightness" button will show what the ISY "believes" the device back light "should be". It is based on a device Image retained in the ISY. It does NOT appear to respond to the device query. In other words, your actual device setting may be different. If they are different, a device restore should restore the ISY settings.

If you can Telnet into the ISY, here's another process: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card I just tried this, it does work on the ISY994.

New card not formatted properly or incompatible? Is it truly a new unformatted card? If it's the correct card size you could copy the files from the old card using a PC. Note that people have had issues initializing/copying files using a Mac.

Curious that Mobilinc works but you can't connect locally. When you do a manual "Add" in the IOX finder, what does it show you when you try to connect? You could also try to connect to the ISY shell via Telnet - https://docs.universal-devices.com/production/ISY%20Advanced%20Configuration%20Guide.pdf

If you can ping the ISY you should be able to manually add the address: Click the "Add" button and manually add the local address as shown. Also add an address for http ( http://xxx.xx.x.x/desc). After doing this click "save" and save the configuration to a local file for the Next time things are lost. Use the "Load" command from the file you created. My "saved" file is from 2022, still working.

@mmb , I second the opinion that performing a whole house query may be doing more harm than good. This is particularly true if your overall communication (and scene accuracy) is good - meaning that you don't benefit from the query. Why you ask? It turns out there are serial communication errors occurring regularly between the ISY and the PLM. Most of the time these are harmless and the ISY simply retries the command and we never know the problem occurred. Rarely, the corruption results in a valid command that the PLM puts on the powerline (think all-on/all-off). @kclenden was the 1st to document that these errors were occurring and could cause All-on/all-off events. Since that time I have see 1 case of a All-on and 1 instance of the PLM Reset due to corrupted communications. The communication errors are more frequent during periods of heavy communication - Device restores, Program activity with no delays, and system queries. I have found a mitigation on the ISY994 using the low level "CD" (configure delay) command through the ISY Shell interface (Telnet). This allows you to reduce the rate of successive commands that the ISY issues to the PLM. Unfortunately, I don't believe this exists on the EISY. This is why I would recommend eliminating the query-all if you can tolerate it. Another possibility would be to shorten/improve the quality of the serial/usb cable to the EISY. I have not found this to help on the ISY994, but the EISY is a different animal.

@MMAltair , I am starting to believe that your EISY filesystem was corrupted during the power outage. You will not be able to do much with only 10 devices in your PLM. You can try another PLM restore to see if that corrects the issue, but my guess is that the EISY image has been corrupted. BEFORE you perform the restore, open the Event Viewer on Level 3. The EISY will then show you exactly which device records are being written to the PLM as in the example below. If you wind up with a "short list" of devices, the EISY image is corrupt. To restore properly, you will need to find a good backup. Programs can be exported to save them. I have had mixed results with this. The best results were obtained by exporting each subfolder to a separate file (do not try to save "My Programs" itself). You can also export individual programs. I would suggest trying this (export/import) to make sure you understand the functionality prior to restoring the backup. You can import folders/programs as a test and then hit "undo changes". If you believe you have a good restore (all 41 of your devices) then you can start working through any remaining communication issues. PLM Restore Snippet Mon 07/27/2026 08:51:35 AM : [ 53 BC 3A 1] Restoring PLM Mon 07/27/2026 08:51:35 AM : [ 58 B0 78 1] Replacing PLM links (locally and in PLM) Mon 07/27/2026 08:51:35 AM : [ 58 B0 78 1] Replacing PLM links Successful Mon 07/27/2026 08:51:35 AM : [ 1A 5D C7 1] Replacing PLM links (locally and in PLM) Mon 07/27/2026 08:51:35 AM : [ 1A 5D C7 1] Replacing PLM links Successful Mon 07/27/2026 08:51:35 AM : [ C C2 32 1] Replacing PLM links (locally and in PLM) Mon 07/27/2026 08:51:35 AM : [ C C2 32 1] Replacing PLM links Successful Mon 07/27/2026 08:51:35 AM : [ 18 93 83 1] Replacing PLM links (locally and in PLM) Mon 07/27/2026 08:51:35 AM : [ 18 93 83 1] Replacing PLM links Successful Mon 07/27/2026 08:51:35 AM : [ 58 B0 74 1] Replacing PLM links (locally and in PLM) Mon 07/27/2026 08:51:35 AM : [ 58 B0 74 1] Replacing PLM links Successful Mon 07/27/2026 08:51:35 AM : [ 16 CD 80 1] Replacing PLM links (locally and in PLM) Mon 07/27/2026 08:51:35 AM : [ 16 CD 80 1] Replacing PLM links Successful Mon 07/27/2026 08:51:35 AM : [ 41 21 1 1] Replacing PLM links (locally and in PLM) Mon 07/27/2026 08:51:35 AM : [ 41 21 1 1] Replacing PLM links Successful Mon 07/27/2026 08:51:35 AM : [ 29 53 3C 1] Replacing PLM links (locally and in PLM) Mon 07/27/2026 08:51:35 AM : [ 29 53 3C 1] Replacing PLM links Successful