someguy

I have a program running that checks to see if any of my offenders are on when ISY thinks they are off. I had three of my common offenders on at 8am yesterday. here is the log for the previous four hours. the offenders are: 15.A6.B2, 71.C2.58, and 15.A2.CC I don't see anywhere that these devices are being contacted by the system except at around 8am when I query them and then turn them off (with my program that does so). ISY-Events-Log.v6.0.0__Tue 2025.11.18 17.53.56.txt

@IndyMike I started my even viewer. I will only send it if I have an event occur, which happens about 2-3 times per week. my suspicion is that you'd just want the event viewer info surrounding the event. @Techman questions answered: yes, I have insteon motion sensors. no, I haven't had an "all on" event happen in recent years. my abnormal events are rare enough that it rarely is a witnessed event. I just come home and find something on when no one has been home and no program could have turned that device on. yes, I have some older non dual-band insteon devices installed. yes, I have power supplies plugged into some of my outletlincs (but those outletlincs haven't, to my knowledge, gone on (or off) in one of these events). because I almost never know, exactly, when these events occur, I haven't been able to find a program that could be causing them.

I've found a way to get rid of the duplicate items. it has been mentioned before. 1) create a group with the name, e.g. "kitchen lights" 2) upon creating the group you add in both the "devices" called kitchen lights and the "scene" that is called kitchen lights. Interestingly, when you look through the list to find the kitchen lights, there are dozens more devices that are available when using them normally. 3) once the group has been created, it should work just fine. somehow, as has been noted previously in this thread, groups take precedence over devices and scenes. this will solve the duplicate devices problem. but: I went a little further and found that if you mess around with the group, you can figure out which device and which scenes actually work and which are the broken ones (perhaps they are the ones connected to the V2 skill). you can then, while still modifying the group, deleted those devices or scenes...... BUT THE PROBLEM I had with doing this is the the V3 skill did not work consistently when using alexa+. (here is what I mean: if I said "turn the kitchen lights on" 10 times, it would work maybe 4 times and not work the other 6. I couldn't figure out any reason why it only worked part of the time.) Here is how I solved the “I can’t control the <device name> because its skill is disabled. You can find the skill and enable it again in the Alexa app" problem: I downgraded to remove alexa+ for now. I liked alexa+ but the problems with the voice controls weren't worth it.

I would like to continue to try to solve (if possible) this problem as I still have devices occasionaly going on for no obvious reason. most of what you kind fellows are saying in this thread goes over my head, unfortunately. is there any way I can contribute to try to solve this problem? is running my "event viewer" on level 3 going to help me (us) any?

FYI: I went into the isy.io access for alexa and found that my "devices" still worked as listed in the "amazon echo device list" but the "scenes" did not work. I then went into the alexa app and asked it (by typing "disable alexa+") and it did so and then, voilà: all of my scenes and devices all work without any problems! I'll just await this being solved and then re-enable alexa+.

I'd like to keep the alexa + capability but get rid of the sassy "... November 4..." responses. any suggestions?

when I added the V3 skill, I looked for the V2 skill to remove it and it was nowhere to be found. Perhaps there is a way to find it and remove it? and by the way; its actually "after November 4".

yes, I'm looking for my elk screen to show the status of lights as a percentage but also to have buttons right next to that that will allow me to turn the device on or off.

I am still working on this, in my spare time. I am still finding devices turned on when ISY thinks they are off. This has been happening for years, really. I previously figured that my ISY/Polisy/Eisy this was just a communication issue: the ISY would try to turn the device off and the device just didn't get the message. I am now noticing that they are on when it seems that no one (and no program) actually turned them on. as I look into this further, I find that they are all similar devices with similar Insteon Addresses: of note, the one called "BB Fan" is one that I swapped to a new switch and it hasn't happened since. My current thought is that something is sending an on to them and I haven't been able to confirm what it is yet. I theorize that it is an alexa, but I also wonder, although seemingly extremely unlikely, that it could be a miscommunication through the REST system. the reason I believe this is because of the similarity of their addresses. I made some programs to occasionally check the devices for being on when the Eisy thinks they are actually off and then I'll look in the "Error Log" as suggested above by @kclenden and see what I can figure out. any other thoughts?

here is the info from the error log for the same time. my light went on, according to the event log at "Monday 10/13/2025 04:59:20". Mon 2025/10/13 04:59:00 0 -170001 [HTTP:8-5] Mon 2025/10/13 04:59:00 0 -170001 [HTTP:8-5]: GET-->/rest/ns/1/nodes/n001_87521/report/status/CLITEMP/67 Mon 2025/10/13 04:59:00 0 -170001 [HTTP:8-5]: GET-->/rest/ns/1/nodes/n001_87521/report/status/HEATIX/67. Mon 2025/10/13 04:59:00 0 -170001 [HTTP:8-5]: GET-->/rest/ns/1/nodes/n001_87521/report/status/WINDCH/67. Mon 2025/10/13 04:59:00 0 -170001 [HTTP:8-5]: GET-->/rest/ns/1/nodes/n001_87521/report/status/CLIHUM/87. Mon 2025/10/13 04:59:00 0 -170001 [HTTP:8-5] Closing socket normally Mon 2025/10/13 04:59:02 0 -170001 [HTTP:7-5] ??J Mon 2025/10/13 04:59:02 0 -170001 [HTTP:7-5]: GET-->/rest/ns/14/nodes/n014_controller/report/status/ST/1 Mon 2025/10/13 04:59:02 0 -170001 [HTTP:7-5] Closing socket normally Mon 2025/10/13 04:59:03 0 -170001 [HTTP:9-5] Mon 2025/10/13 04:59:03 0 -170001 [HTTP:9-5]: GET-->/rest/ns/10/nodes/n010_controller/report/cmd/DON Mon 2025/10/13 04:59:03 0 -170001 [HTTP:9-5]: GET-->/rest/ns/10/nodes/n010_t531672041584/report/status/S Mon 2025/10/13 04:59:03 0 -170001 [HTTP:9-5]: GET-->/rest/ns/10/nodes/n010_t531672041584/report/status/V Mon 2025/10/13 04:59:03 0 -170001 [HTTP:9-5]: GET-->/rest/ns/10/nodes/n010_t531672041584/report/status/C Mon 2025/10/13 04:59:03 0 -170001 [HTTP:9-5]: GET-->/rest/ns/10/nodes/n010_t531672041584/report/status/G Mon 2025/10/13 04:59:03 0 -170001 [HTTP:9-5]: GET-->/rest/ns/10/nodes/n010_rs_j46n/report/status/ST/68.8 Mon 2025/10/13 04:59:03 0 -170001 [HTTP:9-5]: GET-->/rest/ns/10/nodes/n010_rs_f9s2/report/status/ST/69.7 Mon 2025/10/13 04:59:03 0 -170001 [HTTP:9-5]: GET-->/rest/ns/10/nodes/n010_rs_8qcz/report/status/ST/68.9 Mon 2025/10/13 04:59:04 0 -170001 [HTTP:9-5] Closing socket normally Mon 2025/10/13 04:59:43 0 -170001 [HTTP:8-5] Does this tell us "who" turned on the light?

okay, my light went on at around 5am, for unknown reason. here is a snip from my log. does this tell anyone why it turned on? the light that turned on was: 48.15.F2. also: my PLM is 71.17.AC by the way. Mon 10/13/2025 04:59:20 : U7 Rest: submitCmd([48 15 F2 1],[DON],[<NULL>]) Mon 10/13/2025 04:59:20 : [INST-TX-I1 ] 02 62 48 15 F2 0F 11 CC Mon 10/13/2025 04:59:20 : [INST-ACK ] 02 62 48.15.F2 0F 11 CC 06 LTONRR (CC) Mon 10/13/2025 04:59:20 : [INST-SRX ] 02 50 48.15.F2 71.17.AC 2F 11 CC LTONRR (CC) Mon 10/13/2025 04:59:20 : [Std-Direct Ack] 48.15.F2-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Mon 10/13/2025 04:59:20 : [D2D EVENT ] Event [48 15 F2 1] [ST] [204] uom=100 prec=0 Mon 10/13/2025 04:59:20 : [48 15 F2 1 ] ST 204 (uom=100 prec=0) Mon 10/13/2025 04:59:20 : [D2D-CMP 000B] STS [48 15 F2 1] ST Converted values Event=80 Condition=80 prec=0 I appreciate any help.

I kind of gave up. I'm selling my tesla in a couple of months. if you would like my help, then I'm happy to get back into trying to fix this (mostly because it may help you and other people). but if I'm the only one with this problem then I'll give up. FYI: I did try installing the nodeserver in a different slot and went through the process and it still didn't work.

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.

I only have one system that inputs devices into the alexa. it is the Eisy portal. if I delete everything off of the portal in the alexa settings, will that delete things from the Alexa? it doesn't seem to do so. I'd like to delete everything and start over from scratch to clean it up.

@DennisC I'm not sure that variables will tell me what I would want to know in the way I envision. I'll try emailing jimbo automates.