Lights switch on at random times

[jlloyd_UD]

1 hour ago, IndyMike said:

Your earlier "Event Viewer" post showed that the EISY was receiving REST commands instructing it to turn on/off device  60.41.6B.

That is the EISY simply responding to an external command.  Not a fault of the EISY or the PLM.  It's a valid command that is being received through the network interface.  

I don't use Alexa or PG3 so I am not much help in troubleshooting.  I suppose you could try eliminating specific device links (60.41.6b) from Alexa to see if that corrects the behavior for that specific device.

You can also disconnect the EISY from your network during the night (rather than unplugging it).  Without a network connection, the Rest interface should not be operative.   

This is a partial summary of the things I have done.

Thanks for your further explanation/suggestions. When I posted the log, it was for only one instance of a random on, and it happened to be the I3 switch (60.41.6B).  After that, I factory reset the switch, but the behavior did not change.  About every Instean device (old switches, outlets, and the new I3 switch is randomly switching. (I also have another I3 switch I installed at the same time as 60.41.6B, which seems, so far, immune to randomly switching). I reset three Insteon devices, and the behavior continued. The three included an old switch, a new I3 switch, and an outlet. All of them continued errant behavior after factory resets. Would I "air gap" a switch to take it offline to see if it stops the undesired behavior?  And, if it did, what would be the remedy, as I suspect the origin of the REST command is still unknown?

When you suggest disconnecting the EISY rather than removing power, are you suggesting the removal of the USB cable connecting to the PLM?  I think I did that, but I will try it again. As I recall, it did not eliminate the undesired behavior.  I am suspecting that I will continue to lack the "smoking gun", i.e., the source of the REST command.

I have now also disabled all of my programs. I deleted some that I was not using.

general question for anyone. Is there some way to remove/reset the association between my eisy and my echo's? Is it included in the document entitled ISY Portal Amazon Echo Integration V3 - Universal Devices, Inc. Wiki? I have attached a copy that addresses the addition of the integration. I have not throughly read it yet.

I am posting a 7-minute level 3 communication log from my system at 11 am in case there are additional clues.  It has several REST commands.

 

ISY-Eventslevel 3 comm -Log.v6.0.0__Sun 2025.10.12 11.09.14 AM.txt ISY Portal Amazon Echo Integration V3 - Universal Devices, Inc. Wiki.pdf

[IndyMike]

13 minutes ago, jlloyd_UD said:

This is a partial summary of the things I have done.

Thanks for your further explanation/suggestions. When I posted the log, it was for only one instance of a random on, and it happened to be the I3 switch (60.41.6B).  After that, I factory reset the switch, but the behavior did not change.  About every Instean device (old switches, outlets, and the new I3 switch is randomly switching. (I also have another I3 switch I installed at the same time as 60.41.6B, which seems, so far, immune to randomly switching). I reset three Insteon devices, and the behavior continued. The three included an old switch, a new I3 switch, and an outlet. All of them continued errant behavior after factory resets. Would I "air gap" a switch to take it offline to see if it stops the undesired behavior?  And, if it did, what would be the remedy, as I suspect the origin of the REST command is still unknown?

When you suggest disconnecting the EISY rather than removing power, are you suggesting the removal of the USB cable connecting to the PLM?  I think I did that, but I will try it again. As I recall, it did not eliminate the undesired behavior.  I am suspecting that I will continue to lack the "smoking gun", i.e., the source of the REST command.

I have now also disabled all of my programs. I deleted some that I was not using.

general question for anyone. Is there some way to remove/reset the association between my eisy and my echo's? Is it included in the document entitled ISY Portal Amazon Echo Integration V3 - Universal Devices, Inc. Wiki? I have attached a copy that addresses the addition of the integration. I have not throughly read it yet.

I am posting a 7-minute level 3 communication log from my system at 11 am in case there are additional clues.  It has several REST commands.

 

ISY-Eventslevel 3 comm -Log.v6.0.0__Sun 2025.10.12 11.09.14 AM.txt 1014 B · 4 downloads ISY Portal Amazon Echo Integration V3 - Universal Devices, Inc. Wiki.pdf 179.28 kB · 0 downloads

@jlloyd_UD, Resetting your switches will not help.  Base on your event viewer, they are responding to valid communications from the PLM/EISY.  

The EISY is, in turn, responding to a valid REST command instructing it to turn ON/OFF an Insteon device.  

Your latest Event Log doesn't offer any new insight (at least for me). 

1. You have 3 reset "profile" commands that I can't identify. 
2. At 11:07:00 AM the EISY receives a valid Rest command to turn OFF device 40.16.5C (highlighted RED)
3.  The Violet Entries are the ISY/PLM/Device communicating the OFF command sequence.
4. The green entry is the ISY summarizing the OFF command communication.  Good news is that you have very good communication to this device.

When I suggested disconnecting the EISY, I was proposing disconnecting it from your network (RJ45 network connector) not the PLM.  This was intended to be easier then powering down the EISY completely.  It would allow your programs and other EISY events to run while eliminating Rest commands. 

 

un 10/12/2025 11:00:42 AM : Create REST U7 [/rest/profiles/ns/0/connection]

Sun 10/12/2025 11:05:32 AM : Create REST U7 [/rest/profiles/ns/0/connection]

Sun 10/12/2025 11:05:44 AM : Create REST U7 [/rest/profiles/ns/0/connection]

Sun 10/12/2025 11:07:00 AM : Create REST U7 [/rest/nodes/40%2016%205C%201/cmd/DOF]

Sun 10/12/2025 11:07:00 AM : U7 Rest:  submitCmd([40 16 5C 1],[DOF],[<NULL>])

Sun 10/12/2025 11:07:00 AM : [INST-TX-I1  ] 02 62 40 16 5C 0F 13 00

Sun 10/12/2025 11:07:00 AM : [INST-ACK    ] 02 62 40.16.5C 0F 13 00 06          LTOFFRR(00)

Sun 10/12/2025 11:07:00 AM : [INST-SRX    ] 02 50 40.16.5C 48.EC.F5 2F 13 00    LTOFFRR(00)

Sun 10/12/2025 11:07:00 AM : [Std-Direct Ack] 40.16.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=3

[IndyMike]

1 hour ago, someguy said:

I’m having a similar problem: my bathroom light goes on at random times in the middle of the night (which wakes me up). 
 

I recently upgraded to Eisy, I’m on 6.0.0 and I also upgraded to “Alexa plus”.  I’ve been following this thread to see what @jlloyd_UD figures out. 
 

i will run my event viewer at night at some point and see if i can figure out “who” is to blame.  
 

I have a comment for @IndyMike:  if I just go into the portal and remove a device from the Amazon echo list, does it instantly remove the echo/alexa control of that device?  I’m thinking not.  I’ve had many devices that have duplicates and many challenges with trying to remove these duplicate devices. 

@someguy, please do post any event viewer info that appears pertinent.  

Unfortunately, I am not knowledgeable on the Alexa control/integration.  I am simply reading the event viewer logs and interpreting what the EISY is receiving. 

@Geddy had earlier posted a link pertaining to the Amazon Integration. 

[jlloyd_UD]

1 hour ago, IndyMike said:

@jlloyd_UD, Resetting your switches will not help.  Base on your event viewer, they are responding to valid communications from the PLM/EISY.  

When I suggested disconnecting the EISY, I was proposing disconnecting it from your network (RJ45 network connector) not the PLM.  This was intended to be easier then powering down the EISY completely.  It would allow your programs and other EISY events to run while eliminating Rest commands. 

I thought the same about resetting the switches, but I was not sure. I am glad to hear the switches are properly responding to the mysterious origin rest (reset) commands. I determined that simply air gapping the switch probably disables comm but it also disables the capability of physically using the rocker to turn on/off the connected light! It places a permanent air gap in the physical wiring.

To be clear, disconnecting the eisy from the plm means removing (one end or the other) the special USB-RJ45 serial cable?  I presume it only needs to be connected if I add new devices, change settings on switches, add scenes or programming?  If so, that is good as I was fearing too much wear and tear on the small USB female power connector on the eisy. It is mechanically not overly robust and probably not something I want failing.

[jlloyd_UD]

3 minutes ago, jlloyd_UD said:

I thought the same about resetting the switches, but I was not sure. I am glad to hear the switches are properly responding to the mysterious origin rest (reset) commands. I determined that simply air gapping the switch probably disables comm but it also disables the capability of physically using the rocker to turn on/off the connected light! It places a permanent air gap in the physical wiring.

To be clear, disconnecting the eisy from the plm means removing (one end or the other) the special USB-RJ45 serial cable?  I presume it only needs to be connected if I add new devices, change settings on switches, add scenes or programming?  If so, that is good as I was fearing too much wear and tear on the small USB female power connector on the eisy. It is mechanically not overly robust and probably not something I want failing.

Oops. Disconnecting that cable negates the use of the Alexa portal (spokens). Maybe that is a solution for when I go to bed after putting all Alexa-linked devices to sleep. It's one small step better than unhooking the more fragile power connector; it would put wear and tear on connectors, as it needs to be done each night, and does not resolve the fundamental problem of the generation of unwanted reset commands originating from who knows where.

[Techman]

You can shut down/disable the eisy by pressing the button on the front until the led turns red, no need to unplug anything

Pulling out the set button on a device disconnects the a/c power to the device.

[IndyMike]

4 hours ago, jlloyd_UD said:

Oops. Disconnecting that cable negates the use of the Alexa portal (spokens). Maybe that is a solution for when I go to bed after putting all Alexa-linked devices to sleep. It's one small step better than unhooking the more fragile power connector; it would put wear and tear on connectors, as it needs to be done each night, and does not resolve the fundamental problem of the generation of unwanted reset commands originating from who knows where.

Correct - this was intended as a stopgap/troubleshooting step until you resolved the root cause.  It allows programs and schedules to run on the EISY while preventing Rest commands.

I would not call the RJ45 network connection fragile, but agree you would not want to disconnect/re-connect as a long term solution.  If you are concerned about this, most routers allow you to "pause" a network connection to specific devices.  

Either way, it's far better than continuously performing power cycles on the EISY. 

[jlloyd_UD]

2 hours ago, Techman said:

You can shut down/disable the eisy by pressing the button on the front until the led turns red, no need to unplug anything

Pulling out the set button on a device disconnects the a/c power to the device.

Thanks, my eisy came with a card with a QR code on it. I opened it and found nothing similar to an instruction pamphlet, but you are correct. If one looks closely at that tiny blue LED button on the front panel of the eisy, one will see that it illuminates a silhouette of a power switch symbol.  Like you said, if you press and hold it, the LED turns red but does not power down the eisy.  By the way, that button is called a multi-function button, and it has 6 functions depending on how many times it is pressed, according to https://www.universal-devices.com/eisy (there is no depiction of the eisy and description for the location of switch buttons or ports). To shut down the eisy, the button has to be depressed 6 times. Now I am concerned about eventual wearout on that button!  🙂 I am not sure what depressing the button once does.

There has to be a solution that renders my system functional once again.  Maybe the next firmware version update will resolve it?

Also, I saw elsewhere that the term "plug-in" replaced the term "node server."  It's "magic" reading the wiki.

[kclenden]

10 hours ago, jlloyd_UD said:

There has to be a solution that renders my system functional once again.

The log available via "Tools->Error Log" should be able to tell you the IP address of whatever device is sending the random "rest" commands.  After you save it, open it with a text editor and use the date/time to find the ON command that arrived via a "rest" command and the line above should show you the IP address of the device that sent the command.  Here's an example of when I used a "rest" command from the browser of my desktop to get the value of one of my state variables.

Mon 2025/10/13 06:32:58 AM      0       -170001 [HTTP:6-9] ::ffff:192.168.2.166:2259->64288
Mon 2025/10/13 06:32:58 AM      0       -170001 [HTTP:6-9]: GET-->/rest/vars/get/2/25
Mon 2025/10/13 06:32:58 AM      0       -170001 [HTTP:6-9] Closing socket normally