I migrated from a ISY994 to eisy several months ago. I use eisy to control Insteon light switches with a simple program turning them on at sunset and off at a set time. Everything worked fine until recently. Initial problem was that a couple of switches would not turn on from the program It would be different switches on different nights. I could manually turn them on from the app but often had to press the "On" button several times. OFF program turned all devices off. I deleted both programs and set up the programs again. Last night - same issue with the ON program - 2 devices did not turn on. With the OFF program - 6 of the 10 devices failed to turn off at the prescribed time. I noted today that when I go into the Administrative console that 2 devices were not initially recognized (not the same 2 that did not turn on last night). I could query them and eventually they were recognized. I've had this issue in the past also. A new issue arose - periodically I would be asked to re-enter my user name and password.

Any thoughts - this is very aggravating

@sndflea Your first issue sounds like a potential Insteon traffic noise issue. If the program is unable to fire the devices at the time it runs it does not try again. If you find that through admin console you cannot turn devices on/off reliably then there's a possible Insteon noise issue. In admin console open Event Viewer and set it to level 3 and try to control the device from admin console, but also physically. Please post the results here (as a text or file - NOT screen shot). Other users have a lot more experience reviewing the event viewer and can potentially help with this. Are the devices that aren't turning on far away in the house? Are they older devices that might only be single signal devices?

Noise is a hard issue to diagnose. Often people think of it only as a "NEW" device added to the home, but we've learned through the years that it could even be as simple as a failing (or defective) phone charger block that's beginning to cause issues. Another noise maker is a garage door opener or appliance.

Some noise troubleshooting tips are in the wiki: https://wiki.universal-devices.com/INSTEON:_Troubleshooting_Communications_Errors

Also, this post by @MrBill gives a good method for chasing possible noise creators: https://forum.universal-devices.com/topic/35216-programs-not-working/#comment-330289

Another thing might be program corruption. Unlikely since the devices (sometimes) turn off. But if you'd like to check the program you can also post that here (please right click the program and select the last item in the menu "COPY to Clipboard" and then paste as plain text here (again, please NO screen shot!).

The last issue with having to re-enter user/pass for admin console is a computer/network issue. If you're on a wireless network and/or the eisy is connected via wireless network please be sure not to leave admin console open if not actively using it. Try to get on a wired network for both the eisy and computer if possible. What computer OS are you using? This issue would not (at least should not) be related to the program issue. These are (typically) two very different issues.

The event viewer log is attached. This morning I could not control any of the devices from the console. I could control them with the app.

Programs - I use separate programs for each device. The are all the same except for the random times. Sample for one of the devices willl follow. I have tried grouping all of the devices into one program but results aren't much better. Bakers Rack Light LL On - [ID 001C][Parent 0004]

If

Time is Sunset - 32 minutes

Then

Set 'Bakers Rack Light LL' Query

Wait 1 minute (Random)

Set 'Bakers Rack Light LL' On

Set 'Bakers Rack Light LL' On

Set 'Bakers Rack Light LL' On

Set 'Bakers Rack Light LL' On

Else

- No Actions - (To add one, press 'Action')

I added the following program due to the issues that I was having

All On - [ID 002B][Parent 001A]

If

Time is 8:30:00PM

Then

Set 'Back Door LL' Query

Set 'Back Door LL' On

Set 'Den LL' Query

Set 'Den LL' On

Set 'Dining Room LL' Query

Set 'Dining Room LL' On

Set 'Living Room Table LL' Query

Set 'Living Room Table LL' On

Set 'Outside Lights LL Module' Query

Set 'Outside Lights LL Module' On

Set 'Front Hall LL' Query

Set 'Front Hall LL' On

Set 'Living Room Chest LL' Query

Set 'Living Room Chest LL' Fast On

Set 'Front Door LL' Query

Set 'Front Door LL' On

Set 'Bakers Rack Light LL' Query

Set 'Bakers Rack Light LL' On

Set 'Sun Porch Table LL' Query

Set 'Sun Porch Table LL' On

Else

- No Actions - (To add one, press 'Action')

As respects the issue with the login - I am running an ethernet connection. OS in Windows 10

ISY-Events-Log.v6.0.5__Sat 2026.08.01 09.15.56 AM.txt

@sndflea , The Event Viewer output does not appear to match the programs that you posted - was that intentional?

The log shows that you attempted to turn off 10 devices using direct commands (device specific - no scenes). Direct commands require that the device respond with it's acknowledgment of the command. 3 of the devices did not respond (Err 1).

2 of the devices appear to be older based on their addresses (2C 36 41, 18 A0 D7) and may be powerline only devices. The third is more recent (47.E2.57) and would likely be dual band (unless it's a IOlinc).

Other than the errors, your communications aren't stelar, but they are not horrible either. From the statistics below, 72% of the commands used 1 Hop (good) with the remaining commands using 2 Hops (Fair).

It does appear that you are dealing with signal absorption or noise. The troubleshooting links that @Geddy supplied are applicable.

I find it interesting that all of the commands being issued are "rest commands" as if they originated external to the EISY. I am not that familiar with the EISY (I use the ISY994). Were these OFF commands generated by another controller or by a EISY program?

Sat 08/01/2026 09:14:07 AM : Create REST U7 [/rest/nodes/2C%2036%2041%201/cmd/DON/0/51]
Sat 08/01/2026 09:14:07 AM : U7 Rest:  submitCmd([2C 36 41 1],[DON],[<NULL>])
Sat 08/01/2026 09:14:07 AM : [INST-TX-I1  ] 02 62 2C 36 41 0F 13 00
Sat 08/01/2026 09:14:07 AM : [INST-ACK    ] 02 62 2C.36.41 0F 13 00 06          LTOFFRR(00)
Sat 08/01/2026 09:14:11 AM : [D2D EVENT       ] Event [2C 36 41 1] [ERR] [1] uom=0 prec=-1
Sat 08/01/2026 09:14:11 AM : [2C 36 41 1      ]           ERR   1

Event Viewer Statistics

Elapsed Time	0:01:41
Communications
TX-I1	10
TX-I2	0
INST-ACK	10
INST-SRX	7
INST-ERX	0
Total Comms	27
Errors
Unknown	0
ERR   1	3
Unexpected Response	0
Unexpected, Ignored	0
Failed	0
Hops
Max Hops=3, Hops Left=3	0
Max Hops=3, Hops Left=2	5
Max Hops=3, Hops Left=1	2
Max Hops=3, Hops Left=0	0
Max Hops=2, Hops Left=2	0
Max Hops=2, Hops Left=1	0
Max Hops=2, Hops Left=0	0
Max Hops=1, Hops Left=1	0
Max Hops=1, Hops Left=0	0
Hop Efficiency
0 Hops Used	0	0.00%
1 Hop Used	5	71.43%
2 Hops Used	2	28.57%
3 Hops Used	0	0.00%

I migrated from an ISY994 to eisy several month ago. All commands in the event log were generated by eisy. I'm not certain of the sequence of events that I went through this AM. I know I initially tried to access the devices through the dashboard. The off commands may have been generated through the Mobile App. I will review the trouble shooting links and see if I can figure out the issue. I guess that I could always go back to my ISY994 or the Insteon Director app:) When I migrated to eisy I a;lso updated my PLM Could that be an issue?

Thank you for your help.

43 minutes ago, sndflea said:

I migrated from an ISY994 to eisy several month ago. All commands in the event log were generated by eisy. I'm not certain of the sequence of events that I went through this AM. I know I initially tried to access the devices through the dashboard. The off commands may have been generated through the Mobile App. I will review the trouble shooting links and see if I can figure out the issue. I guess that I could always go back to my ISY994 or the Insteon Director app:) When I migrated to eisy I a;lso updated my PLM Could that be an issue?

Thank you for your help.

OK the mobile app would make sense for the rest commands.

I would not suspect the new PLM programming. That would result in consistent failures for a given device. That is not my understanding of your problem.

This really sound like a classic noise/signal absorption problem. You need to use a methodical process to isolate when/where the problem is.

• If the problem is always/frequently present, you can turn off breakers in an attempt to improve communications. Also inspect the circuit the PLM is on for any new or possibly failing devices.

• If the problem occurs at certain times of the day, try to alter the timing of events to improve communications (well pumps, heat pumps, photo cells, etc). These are the worst to locate. Noise/absorption related to certain devices turning on can be a horrible pain to isolate. They require a lot of patience and observation to pin down.

You can use the event viewer to monitor "hops remaining" in response to a system query to assess communication quality. If you find a problem device, you can use the "show link table" feature to interrogate the device table. This is a rather intensive read procedure that will show problems if communication issues are present.

As you acquire data, post it to the forum.

As an example - I had a variable speed heat pump/condenser installed a few year ago. For the 1st couple of years I had no issues. Then it got hot and the heat pump started hitting 80%+ speed levels. As soon as it did, my I1 (powerline only) devices near the electrical panel went offline. Took me quite awhile to pin down.

It's been pretty hot this year...

Working devices for even years. Can deteriorate and cause all kinds of problems. I have seen phone chargers working for years age and start making power line noise. Causing problems.