jim_

Ok, so changes made ... now to wait for the event to occur in the next month ... maybe

Thanks larryllix for the reply I removed the "Run Program" line and you are correct, the decrement works With respect to "MS to send 'ON' only", is this the option ? (2844-222)

I tried looking through the forum, but could not locate anyone posting this scenario / problem ... I have a number of motion or switch activated scenes running for years and while they work perfectly 99% of the time, you hit the scenario where the timer has JUST expired and a new trigger occurs (less than a second) ... lights go off, then on, then off Example: basement stairs, motion triggers human, lights go on, human descends stairs, but does a turnaround trip ... the timer expires (light off sent) but within milliseconds of the off, human is detected, light goes back on for less than 1 second and then go off again ... stairs are dark I use a variable to reset the timer if there is a lot of traffic in the stairwell, this seems to work well. I've looked through Log to see if double Off is sent, but only see 1. Its like the perfect software race condition where the command "off" is sending and motion is triggering "on" to restart the script Anyone guide me on what I'm looking for ? CODE ------------------------------------------------------ Basement Stairs Trigger If 'Basement Stairs Mo' is switched On Then Set 'Basement Stair 3way' On $sBasement_Stairwell_Light_Timer = 60 ------------------------------------------------------ Stair Light Timer Decrement If $sBasement_Stairwell_Light_Timer > 0 Then Wait 1 second $sBasement_Stairwell_Light_Timer -= 1 Run Program 'Stair Light Timer Decrement' (If) Else Set 'Basement Stairs 3 Way' Fast Off ------------------------------------------------------ Basement Stairs Light Stop If 'Basement Stair 3way' Status is Off Then $sBasement_Stairwell_Light_Timer = 0 Set 'Basement Stairs 3 Way' Off Stop program 'Stair Light Timer Decrement' ------------------------------------------------------

Just FYI, with PLM's none existent, the fear is one of my three I have in service will die ... and the call came today from my kid ... ISY is dead Did normal reset etc ... PLM status showed NOT connected. Brought it to my house and tried several more resets, same status, ISY showed no PLM connected. Cracked the case and checked the capacitors, they all look good. A few years back I had my own failure, and read somewhere to reset the PLM x 3 in a row ... holding the reset a little longer after the buzzer stopped ... so I did and with luck this PLM works again Not sure if its on its last legs, but hopefully it lasts until PLM's are back in stock Just thought I would post this for anyone else who might have a "questionable" PLM ... its worth the extra few minutes to try

Solved .... lots of leg work / testing and NOT the expected AC noise one would typically encounter ... Moved to IOLinc to isolated circuit (known clean from noise ... basically beside the PLM ... still failed Factory reset the IOLinc / reloaded, failures still present, but random on reload Checked the power terminals (plug prongs) and electrical plug ... noted some corrosion (typical long term humidity exposure) Replaced electrical plug, steel wool the IOLinc plug terminals, apply protective electric grease on terminals ... Working ... Thanks to all who responded and read my post

I have 3 ISY-994 at different locations, all have i/o linc garage door modules and ALL show the same status ... You can write updates to the i/o linc all you want, they will always show the same status, yet have operated normally for years With respect to KPL, I have added, removed, factory reset several times with same result

I have 2 existing KPL / Buttons (separate modules) controlling the garage door [2450 i/o linc] I'm trying to add a NEW KPL / Button so there will be 3 appearances to open / close the door ... I added the 3rd button to match the existing and remembered to set Toggle to match the existing When the new button is depressed, it flashes twice and goes dark, the buttons on the other KPL's light up, door remains closed I'm not sure what info I need to post for assistance ... please suggest what I need to look at / for to debug ?? PIC attached - Rear KPL & KPL 8 Fam are existing, KPL2 Front is the new button cheers jim

I have done most units, did so methodically in line with killing each breaker circuit branch I still come back to why did the codes stop when daylight savings kick off March 13 .... something with a clock or corruption in program in ISY

I had to chuckle when I read this ... I pictured myself standing out on the street at 2am looking at the neighbors houses to see if lights were flashing I ran into similar problem with a new neighbors TV satellite, they were using UHF remote to change channels which would also change my SAT channel ... Fortunately, it was easy to diagnose ... new neighbor, new SAT install ...

Thank You for explaining ... My GDO (old tech) and Insteon controller has been installed for years Since the codes were only showing up in the middle of the night, I would rule this out ... also, when I killed the power to the garage, the codes still appeared

Negative

GDOs ??? Chamberlain models ???

Good thoughts ... but No neighbors have X10 or insteon ... actual none have home automation ... Same UPS for past 5 years and I did try connecting on standard power

I searched for over a month for any electrical device causing these mystery X10 codes .... finally gave up after a month having shutdown circuit breaker by breaker trying to isolate ... I needed to make an adjustment to a program and thought I would look at the logs tonight, and found the x10 codes stopped March 13, AKA daylight savings ... Since I have no X10 devices with any date control, I can only surmise this is related to ISY which does have date function .... Thoughts anyone ?

Thank you for the tip ... I'll sweep the house for all chargers and any other unnecessary electrical appliances