jlloyd_UD

As I was preparing to start deleting and readding"spokens" from the Alexa skill ( recall that I had upgraded to eisy in August from ISY994i and soon thereafter had upgraded to Alexa plus but decided to revert to sort out problems without adding more; in fact, I cannot refute that my upgrade to Alexa plus did not precipitate my random experiences; if it did the damage remained), I got excited as I learned that there were several changes to the version of the eisy (I was still on version 6.0.0 since August. I used my UD mobile to upgrade my eisy and rebooted the eisy and synchronized everything after the reboot. I am now successfully on version 6.0.3. I hoped the new tweaks to the version would have resolved my random lighting. Unfortunately, it did not. I hope I am not imagining things, but I think the frequency has decreased although it seems illogical that the resets would continue but at a reduced rate. I will report progress as I start to unwind my Alexa V3 portal integration.

Thank you. Yes, I was talking about the portal subscription. I will begin the task of eliminating and adding back the spokens.

Sorry, I was not explicit enough. I was not concerned about my Prime subscription; I was referring to the fee paid (to UD?) for using the skill with the eisy. As I recall, it was either $20 or $40 per year this last cycle before I upgraded to the eisy.

Thanks for the direction. I was thinking the same approach, but also do not know how to do it most effectively, i.e., how would I terminate with less than extreme prejudice as I desire not to lose any subscription I paid to renew this past year. I suspect there is a way to do this so I do not risk the subscription; I am likely registered somewhere, and I will investigate that first. As I recall, I paid a premium for renewing this year since, at the time of renewal, I renewed using my ISY994i, and since it was no longer supported, the Alexa integration subscription cost more. I would first access the vocal mapping to create a paper copy so it will be easier to recreate it (or at least recreate my table without missing any vocal commands that I have created over the years). I am being careful to avoid going back to the beginning if I can avoid it! :>) I hope not to have to open a ticket if the process is already documented somewhere.

I am the originator of this thread and am revisiting the string of comments to determine if anyone has suggested fix for my random lights. I see that at leat one person indicates with some degree of certainty that my reset commands are coming from Alexa. I do use Alexa extensively for vocally commanding my Insteon switches, and I am getting the random lights on on most all of the switches. I have used Instaon switches for a long time, and I have replaced several over the years with the newest versions as recently as several months ago. I have one keypad_linc relay v36 that is wonky and probably needs resetting. I do have a I upgraded to eisy and have the latest integration of Alexa installed. None of these random events happened until after I upgraded to eisy as my Alexa integration (ISY Portal Amazon Echo Integration v3) was running trouble-free until then (with the ISY994). I recently tried to troubleshoot by removing my Amazon hardware until none were powered on. It did not affect the random lighting... it happened as if nothing had changed. My eisy was connected through a switch, and I changed that to be directly connected to the modem. Nothing changed. So, how do I determine the source of the random resets thought to be from Alexa echo devices? I am thinking they are actually emanating from the eisy/PLM pairing but would like to exonerate this belief. Is it time to factory reset the Alexa integration? How? Will I need to rebuild the vocals? If it persists, do I factory reset my eisy? Will that require I rebuild all the links from zero base? I posted my problem on the Alexa forum. I received a response stating that it was beyond their skill and knowledge base to troubleshoot and fix, even after it was escalated to a higher level. It seemed like they did not want to deal with it. I was hoping there might be a version change to my eisy that would be a magic bullet, but so far, nothing. Most comments are beyond my skill level to fully understand. I am at a point where I remove the eisy when I go to bed and sometimes power back up in the morning, and deal with the random events by using my vocal commands to extinguish the lights. It seems like a neanderthal approach to dealing with this problem. . (My wife likes the automation but has resorted to using the manual switches when she wants the lights to be on or off. It negates the benefit of having home automation I would prefer not to have to rebuild my links, but maybe it is the only way forward unless someone has a better idea. I appreciate the forum's thoughts on resolving my problem. It seems several others are also experiencing random commands of the switches. I have filters on my lines. Maybe I need to reposition them? If anyone has a structured approach for tracing down the origins of these random events, I would appreciate the details. I have lost the full benefit of the investment I made in upgrading my controller back in August. Thank you to all who have contributed here. Happy holidays!

I am a neophyte when it comes to network concepts and lingo, but I understand at a basic level what is being done to troubleshoot. I have been dabbling with UD and Insteon for about a decade with some degree of achievement. I have enjoyed the back and forth, but if my troubles are Alexa-based, I have not heard anything that would allow me to correct/eliminate the random lights on situation. If someone has provided a suggestion or a solution, I apologize if I have missed it and would appreciate a few ideas on how to proceed. I have been commanding Alexa using "vocals" to turn off the uncommended lights when they (too frequently) happen and disconnecting my eisy from the lan during bedtime. It would be nice to return to normalcy! I would not mind closing this lengthy thread if I could obtain a solution that I can easily apply. My household has become too reliant on Alexa's vocal controls. 🙃

My random lights on (not All ON, but 5 or 6 lights randomly) started only after recently upgrading my isy994 to an eisy, and then not immediately. It seemed to start after I "upgraded" Google Alexa to a "smarter" version. I reversed the upgrade to Alexa without any change in the "individual lights on randomly" case. I have resorted these past few weeks to unplugging my eisy from the network while asleep at night to stop the seemingly random and unprovoked, by me, command activity. Initially, commenters suggested my PLM was approaching the "end of life," but the situation with Alexa, if not totally coincidental, has me wondering. I want to get to the root cause, but I am not proficient in tracing individual commands. My eisy seems to work properly otherwise. My Alexa also responds to vocals like it should. I use it to shut off the errant lighting when it happens, but it annoys me to have to do that every 30 minutes or more often throughout the day. I have a serial PLM that worked perfectly with the isy994, so I don't want to "throw parts" at the problem yet. I have already purchased the special serial cable to retrofit the old serial PLM. The PLM is around 8 years old. What can I do to help you pursue your plan to isolate the source of this problem so it can be resolved? I can certainly send you the logs and the duration of logging you need to troubleshoot.

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.