joeria Posted March 3, 2023 Posted March 3, 2023 I have been trying to troubleshoot a random occurence of an event that turns a number of, but far from all, my insteon devices on. It appears to affect the same devices each time, a handful of dimmers and a few (2 or 3 out of individual buttons on three separate keypads. This seems to happen when no one is cotrolling any connected devices and it doesn't appear to coincide with any program executing. When this occurs the devices that turn on remain listed in ISYas in the prior (off) status and no action is recorded in the logs. So far in terms of troubleshooting: I have no motion sensors in the network I have reviewed and modified any programs so that I do not have a control IF statement executing a scene with the device in the IF statement being updated, or in the couple of cases that exists, I've added 3 seconds delay prior to executing the command. - In any case I can't trace the occurrence to the execution of any program. I've swapped out the PLM in case it was getting flaky - had an event after the swap. Does anyone have any suggestions? Thanks much!
DennisC Posted March 3, 2023 Posted March 3, 2023 Try right clicking on each device one at a time and selecting Diagnostics - Show device link tables. After the process runs, click on compare. This should tell you if any clinks have been mis-matched. If there is a mis-match or if you want to skip the first step, right clicking on each device involved and select restore device. That will re-write the data in the ISY's memory.
joeria Posted March 3, 2023 Author Posted March 3, 2023 Thanks @DennisC. I've tried restore device on several of the devices, I'll try on the rest. Had one device that wouldn't fully restore after PLM change. I've subsequently replaced it (after last event) as it was a significantly older device.
SMuddiman Posted May 30, 2023 Posted May 30, 2023 Did you ever figure out what was causing the random “Fast On” events? I have been having the same issue and have not been able to figure it out.
hart2hart Posted May 30, 2023 Posted May 30, 2023 Did you ever figure out what was causing the random “Fast On” events? I have been having the same issue and have not been able to figure it out.I just got created a situation that would cause them multiple times in an hour. Diagnosed and fixed it this weekend. It was caused by way I was using a specific node server. Which if any do you utilize?
joeria Posted May 30, 2023 Author Posted May 30, 2023 19 hours ago, SMuddiman said: Did you ever figure out what was causing the random “Fast On” events? I have been having the same issue and have not been able to figure it out. So, it has subsided, but my solution/answer is not straightforward. I first tried restoring from IOP the links on all devices that would turn on. That did not solve the issue. I also went through all my programs looking for situations where an "on event" on a device would trigger an "on event" for a scene in which the device was a member as this was a known cause. I either eliminated those situations or put a substantial (several second) delay before executing the scene on. This also did not resolve for me. I note these 2 solutions appear to have helped others. Finally, knowing that the devices that the devices impacted appeared to be older and likely had an "all on" bit in their code, I would take on or two off the network (air gap or unplug) at a time and see if that would stop it. Doing this, I found a couple of old devices that would not air gap or would not take a restore device. I changed these out and have not had an occurrence since. Cost me replacing about 5 devices that appeared to be working fine, but stability is king.
Techman Posted May 30, 2023 Posted May 30, 2023 (edited) INSTEON Random All On Events Random All On events are related to INSTEON commands being sent to the PLM from ISY and, on the other hand, one (or more) INSTEON devices sending events to the PLM at the same time and thus causing packet collision. RF/dual band devices increase the likelihood of this event since they send two packets for each signal. The combination of the following technique will dramatically reduce the likelihood of All On events: You don't have any programs that use Control for a device and then send a Scene command to a scene which includes the same physical device. So different buttons from the same KPL are considered one device Don't Use a Control for a device which is already a Controller for some Scene and then have the program send other INSTEON commands to other devices/scenes. This basically causes two or more events arrive at the PLM at the same time In addition, motion sensors with low battery, sometimes go crazy and start sending sequences of on/off every second or so. As such: Check Tools | Log for sequences of motion sensor on/off every few seconds and in succession If you do have those, change the motion sensor battery NOTE: All on events won't appear in the ISY log because they didn't originate from the ISY. Powerline noise and/or a defective device can also contribute to an on event. Edited May 30, 2023 by Techman
Recommended Posts