arzoo

That was one of the first things I checked and none of those four programs ran at 52 past. Their last run time was 55 past which seems close but probably just a coincidence. I'm pretty sure these programs are not the issue but it can't hurt to rule them out. The other thing I should mention is none of my programs had been updated prior to this issue starting.

Will do, and again, thanks for all your help with this!

It's also strange that a bunch of IR commands seem to fire when the issue occurs. Might have to pull the IR dongle and see if that makes any difference. Debugging this issue is SO slow because I can only try one thing at a time and then it can take a day or two before the issue re-occurs. And that in itself is strange; some days it's fine and others it can happen two or three times? But most often it seems to happen around 1am.

I removed the battery from the suspected sensor (14 72 B6 1) but the problem triggered again last night at 12:52. The fact that it's always around the same time has me thinking what programming I might have in place that's the culprit. The only programs I'm running with an hourly trigger are for monitoring the heartbeat signal on four Insteon water sensors. When the water sensors are working correctly, they send a heartbeat once about every 24 hours. I have programs that check every hour, incrementing a counter. If the counter exceeds 24 then I assume the battery is low. Anyway, I'll disable those programs and see if it makes any difference.

That's good to hear and will do when we get home! Thanks

14 72 B6 1 But the issue continues even with the sensor disabled. I'll have to try some of the other suggestions to continue debugging. I'll focus on the fact that it only happens at 52 minutes past the hour.

I'm back to thinking the one motion sensor is the culprit. Replacing the battery did not help, but I think it's actually malfunctioning/faulty. With that motion sensor disabled, the issue has not reoccurred for at least one day. I'll give it a few more, and then replace it with a new one.

Apparently the motion sensor was not the issue, 1:52 a.m. everything triggered again last night. Back to the drawing board. Just so odd that it's always the same time every night. I'll have to review all my programs and see if I have anything scheduled to run at that time, but I'm pretty sure I don't.

@IndyMike Thanks SO much for helping decipher the log! I'm on vacation for the week so I'll get back to this when I get home. I will say this, since replacing the batteries in the one suspect motion sensor, the problem has not reoccurred.

I do have a few older Insteon motion sensors, including the one I currently disabled. So far no crazy stuff but it typically happens overnight (?). Thanks again for the help.

I've attached a level 3 log that I ran a few days earlier. The craziness started around 12:51pm but the cause may have been prior? No I don't have any programs that run at x:52 on the hour, but I do have programs that remain running with a 1 hour wait state (I don't think they are the cause). My home automation network has over 100 devices, mostly Insteon switches (dimmer and keypad) and sensors (motion, wet, smoke, siren, etc). I've also got a few Z-wave devices and IR control. Some of the devices are pretty old (~15 years) and others much newer. I've replaced a lot of the Insteon stuff as it fails (including the PLM). As for programs I've got close to 200 and I've done some pretty extensive stuff (imo). After looking over the level 3 log I decided to start by disabling a motion sensor that seemed to trigger for no reason. But I still don't see how any one device could cause this behavior? Anyway, thanks for everyone's help with this! ISY-Events-Log.v5.7.1__Fri 2024.07.26 01.15.58 PM.txt

Here's the event viewer from last night at 4:52am. I'm not sure what the RR/OL/ST codes mean but looks like most every device triggered?

I've also looked over the log and it seems like all the buttons on all the Insteon keypads (4) are turning on and then off instantly.

The thing is, all of the programs that are triggering have different "If" conditions. There's literally no one device that could cause this behavior.

I have a very strange problem that recently started happening; many of the programs on my eisy have started triggering at the same time, always 52 minutes past the hour, but not every hour. Most of the programs affected seem to be related to my Insteon Keypads and eisy IR controller. I don't see how this could be a hardware failure (eisy or insteon or sensors) because it's always 52 minutes past the hour but on random hours. I'm totally stumped. Any thoughts or suggestions?

Hi All. I have an insteon keypad button configured in Toggle Off mode. When the button is pressed, it flashes twice (why twice?) and then should remain off. The button is a controller for a scene that handles all the lights in my basement. So the button can turn off all lights (but not on). I also have a program that triggers on the status change of any light in the basement. If one or more is light is on, a scene controlling the keypad LED is turned on, and if all lights are off, the keypad LED is turned off. So basically, if the keypad button LED is on it indicates one or more light in the basement is on and pressing the button turns them all off, and if none of the basement lights are on, the keypad button LED is off. This all works fine, mostly. Here's the strange behavior, some times when pressing the keypad button (when it's on), the LED will flash twice (which is normal) and then immediately after turning off, it turns back on and remains on? Pressing it again does the same thing. I've disabled the program that turns the LED on/off based on switch statuses, but that doesn't fix the problem, so it's not the program. I've looked over the event log but I don't see anything strange (I'm not an expert on reading the log). Any thoughts?

String variables would be very useful. That feature would help consolidate multiple scripts.

Bummer. Thanks.

Hi All, I just added a new Motion Sensor II (to replace an older motion sensor). This is the first time I've used the new model and I've noticed when motion is detected it sends the ON command twice, and the same for the OFF command (30 seconds later). Is this normal behavior? I've tried changing the sensitivity but that makes no difference. The double signals are a problem for some of my programs. I guess I could add a wait statement but I'm just not sure if this is normal or the sensor is defective? Thu 11/28/2019 11:36:23 PM : [ 4F A0 20 1] DON 1 Thu 11/28/2019 11:36:23 PM : [ 4F A0 20 1] ST 255 (uom=100 prec=0) Thu 11/28/2019 11:36:23 PM : [ 4F A0 20 1] DON 1 Thu 11/28/2019 11:36:59 PM : [ 4F A0 20 1] DOF 1 Thu 11/28/2019 11:36:59 PM : [ 4F A0 20 1] ST 0 (uom=100 prec=0) Thu 11/28/2019 11:37:00 PM : [ 4F A0 20 1] DOF 1

Any way to do that without losing all the references to the keypad buttons in programs?

Hi, I recently purchased and installed a 2334-2 keypad but the ISY admin console is missing the LED Brightness button for the keypad? I also noticed the device is listed as v.00 but my other keypad (with the LED Brightness button) is v.43. Is it possible I selected the wrong Insteion device when I added the keypad? I'm stumped.

Wow, I've been using the ISY for like 10 years now and never knew this! Thanks for the help!

Not sure I understand - I've only ever used the ISY to configure my insteon devices. Is there something else I need to do? I did write the changes to the devices.

Hi All, I have a scene which includes three Insteon switches. The scene is configured so that one switch is ON and the other two are OFF. So the scene only turns on one switch but always turns off all three switches. Using a 6-btn keypad, I have one of the (non-primary) buttons set as a controller for the scene. The issue is, pressing the button will turn on all three switches even though the scene is not configured that way? If I trigger the scene manually from the admin console it works as expected. Any ideas why I'm seeing this behavior?

We've been testing both Amazon Echo and Google Home to see which is more useful. AE works perfectly with our ISY. GH is useless; it links to the devices and works for a minute, hour, day, who knows? The next time we try to turn a light on it says "Universal Devices Unavailable" and has to be relinked. I've given up using GH to control our lights, but it is better at answering questions.