@jlloyd_UD , please report back your progress. I have to believe there are others similarly affected.

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.

@IndyMike : I tried factory resetting the main devices that are culprits here and they still randomly and occasionally turn on. It is mostly three or four bathroom fans that I find on with no explanation as to why they are on. it is possible that they are the ones that I'm finding on because the lights get turned off by someone else in the house (I have four kids and a wife). about a week ago, quite a few items went on and one of them was the master bedroom light at around 5am while my wife was sleeping. needless to say that didn't go over well.

any other suggestions as to how to fix this problem?

59 minutes ago, someguy said:

@IndyMike : I tried factory resetting the main devices that are culprits here and they still randomly and occasionally turn on. It is mostly three or four bathroom fans that I find on with no explanation as to why they are on. it is possible that they are the ones that I'm finding on because the lights get turned off by someone else in the house (I have four kids and a wife). about a week ago, quite a few items went on and one of them was the master bedroom light at around 5am while my wife was sleeping. needless to say that didn't go over well.

any other suggestions as to how to fix this problem?

Are you using Alexa or Alexa+ ?

If so, delete the 'ISY Optimized for Smart Home V3' skill in your Alexa app as well as your Alexa spokens in your portal. If the offending devices stop 'offending' for a few days, add back the ISY skill to Alexa, then add each of your spokens slowly one at a time (each day or so) to see which one is the offending one(s).

Edited Saturday at 02:11 PM2 days by Athlon

I am getting a high number of unexpected device activations as well. I can find no programs running at the time of the a uncommanded actions. As near as I can tell, all the unexpected device activations are Instagram Insteon. I don't think any types of devices are affected. I see nothing in the log to suggest any command is causing this. I think I have also ruled out the possibility that it is related to scenes. I have also reset many of the offending devices. My current working theory is that it has something to do with motion sensors or combinations thereof. We have a lot of unusual activity due to some visiting cats. They are triggering a lot of motion sensor detects. I am going to see whether their departure in a couple of days reduces the number of light triggers.

Edited yesterday at 01:11 PM1 day by oberkc

Motion sensors can certainly add to irregular triggering. Adding cats to the mix steps that up another few notches!

I have not yet tried to "fix" my Alexa skill and zero base my "spokens." I do plan to do that. My laptop fried its motherboard on Christmas day and have been dealing with restoring my many files and folders. I have seen mention of motion detectors creating spurious triggers to other unintended devices. Does anyone have a cure for that ill?

26 minutes ago, jlloyd_UD said:

I have not yet tried to "fix" my Alexa skill and zero base my "spokens." I do plan to do that. My laptop fried its motherboard on Christmas day and have been dealing with restoring my many files and folders. I have seen mention of motion detectors creating spurious triggers to other unintended devices. Does anyone have a cure for that ill?

Fresh batteries would be step#1

10 hours ago, someguy said:

@IndyMike : I tried factory resetting the main devices that are culprits here and they still randomly and occasionally turn on. It is mostly three or four bathroom fans that I find on with no explanation as to why they are on. it is possible that they are the ones that I'm finding on because the lights get turned off by someone else in the house (I have four kids and a wife). about a week ago, quite a few items went on and one of them was the master bedroom light at around 5am while my wife was sleeping. needless to say that didn't go over well.

any other suggestions as to how to fix this problem?

@someguy , from what I remember, you did not have any Alexa communication in the event viewer file that you provided. You also had only 1 link in your affected device link table (to the PLM). That really doesn't leave many options.

Since you do have a PLM link in the device, the PLM (EISY) can still turn on the device. That includes any REST device (alexa and other). You might try disabling (unplugging) your network connection to eliminate external commands. @oberkc mentioned that he has been having issues with Instagram communications - I have no experience with that but it sounds like it could be a player.

The other possibility would be an "all-on" event. Your older devices are susceptible. The newer device (71.C2.58) should not be. Not sure what this device is - please post back and confirm.

You can test to determine whether your devices respond to the "all-on" command from the admin console. From the "my lighting" tab in the admin console tree, hit the "all-on" button. After activating you'll need to visually inspect for devices that have responded. Newer devices will not respond (command removed). Older devices will respond. Very curious about your 71.C2.58 device.

@Athlon I am using alexa (not alexa plus). Also, many of the devices that go on randomly are not ones that I have a spoke for in the portal.

@IndyMike I think (I hope) that @oberkc meant insteon instead of instagram. I hope there is no way for instagram to directly control our homes. 😄

just this morning, I had an event occur where I had a number of devices turn on. Some of the devices that went on were the same and as yesterday and are frequent offenders. some of the devices were not usual offenders. also: many of the devices that went on this morning are fairly new or very new dual band switchlincs.

any other suggestions?

@someguy , now that I've re-read the post, you are probably correct about "Instagram" being a typo. You might be surprised to learn that there is an Instagram add-on for Home Assistant...

There's a lot of conflicting information here.

You're symptoms are following the "random on" events that have been attributed to communication collisions or PLM to EISY serial errors (pointed out by @kclenden ).

The Event log that you provided earlier did NOT show any PLM to EISY serial errors that I could find. @kclenden is far more experienced at screening for these. I would welcome his input on the issue.

Questions and things to try:

1. Your newer devices should not be susceptible to an all-on command from the PLM. Please verify that this is true by executing an ALL-ON from the MY Lighting Admin console and then physically which devices turn on. Devices like the IOLinc were not updated the last I checked.

2. When you find a light on unexpectedly, does the ISY have knowledge of the Light State? If it does it could point to a Rest command telling the ISY to turn devices on (the ISY knows it sent an on command in response to a Rest request). Try disconnecting the ISY from the Lan to interrupt Rest communication. You'll likely need to leave the system disconnected over a couple of nights to verify any improvement.

3. Manually linked devices can activate devices outside of the ISY's knowledge. I've had this happen previously when visitors were in the house and accidently put devices into linking mode. Scan the device link tables and restore if necessary.

4. The link table that you provided earlier showed only a link for your PLM. Only your PLM (or another controller) should be able to activate this device. If nothing above has helped eliminate the problem - disconnect your PLM. That should prevent any device direct communication.

5. Check for "other" controllers. In the past I've had HouseLinc running on a separate PLM. A PLM can control your devices even with NO links in the device table (just verified this AM). Make sure you don't have any other controllers capable of issuing device direct commands to Group 0.

6. If things are still acting up, we are down to X10 communication or local power upsets. You've already factory reset some of your devices - that should eliminate any programmed X10 addresses. If you factory reset a device and leave the link table blank (do not restore) the only device that should be able to activate it would be a PLM using a device direct command. An all-on command should NOT turn the device on. If the PLM is disconnected, there shouldn't be any controllers capable of turning the device on. If it does, there's something very next level going on.

Please report back your findings for the all-on test.

Edited yesterday at 12:41 PM1 day by IndyMike

2 hours ago, someguy said:

@ I think (I hope) that @oberkc meant insteon instead of instagram.

He did, but forgot to proofread after autocorrect. That is a good catch.