jlloyd_UD

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.

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.

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.

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

I am returning to your comment about node servers. I will need to work my way through that since I really do not know what a node server is or what it does. Do I stop all the node servers, and then turn each one back on while waiting for a result, before turning the next one on? If I find a node server that starts the random lighting, I will note its identity and will need to know the next steps. Do I turn it off again? So, I clicked on the Administrative Console tab for Plug-ins and selected Launch Polyglot V3 (PG3). After successfully logging in, I see many pull-down tabs, but I see nothing explicitly about "node servers." Would it be called something different? Can you refer me to a document that discusses node servers? I am deeper into ISY than I have ever had to go, but I am willing to learn. In the meantime, even unplugging all of my physical echo devices does not stop the random commands from being issued. One of them just came back on with all echos disconnected, so the commands must be originating elsewhere.

I have unplugged my eisy for the past several evenings while sleeping. This effectively eliminated the random commanding of lights when the eisy was unplugged. When powered, the random commanding of lights returned.. Does this behavior tell me the eisy might be at fault? Does it also exonerate the PLM? Or is the eisy only reacting to commands even though there is no clear understanding of how the commands are being generated? I have an Alexa Connectivity tool as part of my Universal Devices account, where my devices/lights/outlets/scenes are linked with Alexa "spokens". The "spokens" are working properly. A commenter has expressed his belief that the random commands are coming from Alexa. [Note that several days ago, I reverted from Alexa + back to Alexa after I suspected that this random commanding problem started after I agreed to upgrade to Alexa+. The reversion did not resolve the random commanding problem.] Does this suggest the eisy might not be the source of the random commanding but only responding to spurious commands from the Alexa device? Is it logical, as a simple and uncomplicated diagnostic step, to unplug all the Alexa devices to determine if the random lighting stops or changes behavior? I have other thoughts, but will leave this comment until I learn the outcome of Alexa unplugging.

I reverted to the original Alexa. It's easy, all you need to do is ask Alexa to install (go back to) the original Alexa and it does revert. It lost something in the reversion as she no longer responds to the spoken changes to my Insteon devices; it simply beeps. That is not a big deal, as she does respond to more complex questions. However, random commanding of my Insteon devices has not abated with the reversion. Unfortunately, a simple reversion does not resolve the problem if, indeed, the problem is with Alexa Plus; back to scratching my head.

60.41.6B.1 is the address of the I3 switch for the light that is randomly coming on. I'm beginning to believe my upgrade to the Alexa plus service, which is closely coincidental with these random lights might just be the source. I am going to try to revert back to my less capable Alexa plug-in to see if that eliminates the spurious signals. Alexa plus is still in the advanced development stage, and it might have some bugs. Just guessing.

Here is the event viewer capture level 3 for a recent random illumination event. random actuation ISY-Events- Log.v6.0.0__Wed 2025.10.08 04.06.11 PM.txt

For example, I did the following on my I3 switch (I just repeated the factory reset again). The beeps did not occur (I have beeps set to zero on the I3) but the switch returned to normal brightness on the LED, and the controlled light turned on. Then I took an extra step to push in the set button again. A green LED started flashing, indicating it to be awaiting instructions, I believe. At that point I did a system restore from the admin console and after it processing for 20 seconds or so, I can control the switch from the admin console again. By the way, I followed the same procedure for the other devices, and each has experienced random actuations again.

Yes, when I transitioned to the eisy from the isy994, I was able to reinstall my Alexa links for the spoken commands. It worked as it did before. I should mention that after I reinstated the Amazon plug-in, I had an offer to upgrade to a more capable Amazon plug-in for free due to having an Amazon Prime account. I would not have done this had I had to pay for it, and I do not necessarily like the new version. I would not mind reverting to the older version to see if that resolves the problem. My wife and I have enjoyed the voice control, so I could not deal with eliminating it. I will see if disabling it for a short period makes a difference. Although I can pinpoint the exact day or time I upgraded Alexa, I'd be willing to bet the upgrade happened around the time I started having the glitches with the random lights so it is a good chance the problem started with the upgrade. I will try to capture the event viewer transmission as you have suggested. Thanks for your suggestion.

With the eisy unplugged overnight, the lights behaved (no random illuminations), but I had no events set during the overnight period that would have normally commanded a light. I believe I have a mix of single- and dual-band devices. I factory reset (air gapped) and system restored the following: I3 Switch v54, a Keypadlinc relay v36, and an on/off 2663-222 Outlet. Each of these was a source of random lighting. After the system restore, the I3 Switch exhibited random behavior again. After some time, I observed no random behavior on the other two devices, but I am not sure I waited long enough for the random behavior to return. I did purchase a new laser printer a few days ago (Sunday afternoon) and set it up for WiFi printing. I thought it might be adding spurious signals to the power line, so I disconnected it for a lengthy period during which the random behavior did not change. Moreover, the strange behavior began either Thursday evening or Friday, before the printer was added, so I do not think it was the source of the problems. The only other electronic device I have changed in the past month is an upgrade of my ISY994i to the eisy. The eisy ran perfectly for several weeks before the strange behavior started.

I have followed everyone's proposed solutions and diagnostic procedures, and nothing has changed the performance of my Insteon products as controlled by my newly installed UD eisy and my original, 7-year-old, Smarthome PLM. Am I at a point where I need to replace the PLM? [It is not an inexpensive device, especially after I just purchased the eisy and the required serial RJ-45/USB cable for the serial PLM, but it will be well worth the expense if it does fix the problem]. After I replace it and the random lights continue, what then? I would prefer to know the cause of the problem. It worked for better than 2 weeks before I started having these unexplained anomalies.

I received my weekly Ting power quality report, and it shows no surges or brownouts in the past week, so I am ruling that as the instigator of any recent upset to the eisy or the plm

The green light on the plm is on. The counter on the restore plm was a system busy moving bar signal, which disappeared after progressing to 2%. There was no other indication that the restore process had run or completed properly. I will unplug the eisy now and watch what results. Thanks.