Scheduling Behavior

[Chasewood]

I have simple program that turns two SwitchLinc Dimmers (2476D's) on half an hour after sunset.

 

One of the two switches turns on as required. The other seems to respond to the on program correctly, but also turns on at other times. Both switches seem to respond reliably to the off program.

 

I've combed through my other scenes and programs to make sure nothing else is triggering the switch and I've factory restored the switch to make sure there are no X10 addresses lying around.

 

The switches are less than three months old.

 

What am I missing here?

[LeeG]

Look at the ISY Log (not the event trace) to see if it reflects the errant actions of the device at the time they are occurring. The Log should reflect the device turning On or Off is the ISY is aware of the activity.

[Chasewood]

Looks like I can't enclose files with this message.

I haven't figured out how to copy programs into this message yet.

Here is the log of relevant activity from last weekend.

Haven't figured out how to format that correctly into this message yet, but the content is all here.

 

Outside Front Off 0 Sat 2013/06/15 01:00:00 Program Log

Outside Front Status 0% Sat 2013/06/15 01:00:00 System Log

Outside Front Status 100% Sat 2013/06/15 16:37:09 System Log

Outside Front Fast Off Sat 2013/06/15 16:37:46 Web Log

Outside Front Status 0% Sat 2013/06/15 16:37:46 System Log

Outside Front Off Sat 2013/06/15 16:37:47 Web Log

Outside Front On 255 Sat 2013/06/15 21:20:50 Program Log

Outside Front Status 100% Sat 2013/06/15 21:20:51 System Log

Outside Front On 53 Sat 2013/06/15 22:20:50 Program Log

Outside Front Status 21% Sat 2013/06/15 22:20:51 System Log

Outside Front Off 0 Sun 2013/06/16 01:00:00 Program Log

Outside Front Status 0% Sun 2013/06/16 01:00:00 System Log

Outside Front On Level 100% Sun 2013/06/16 14:19:42 System Log

Outside Front Ramp Rate 0.5 Sec Sun 2013/06/16 14:19:42 System Log

Outside Front Status 100% Sun 2013/06/16 14:19:42 System Log

Outside Front On Level 100% Sun 2013/06/16 14:19:42 System Log

Outside Front Ramp Rate 0.5 Sec Sun 2013/06/16 14:19:42 System Log

Outside Front On 229 Sun 2013/06/16 14:21:26 Web Log

Outside Front Status 90% Sun 2013/06/16 14:21:27 System Log

Outside Front Off Sun 2013/06/16 14:21:28 Web Log

Outside Front Status 0% Sun 2013/06/16 14:21:28 System Log

Outside Front Off Sun 2013/06/16 14:21:34 Web Log

Outside Front On 255 Sun 2013/06/16 21:21:12 Program Log

Outside Front Status 100% Sun 2013/06/16 21:21:12 System Log

Outside Front On 53 Sun 2013/06/16 22:21:13 Program Log

Outside Front Status 21% Sun 2013/06/16 22:21:14 System Log

[oberkc]

I claim no special abilities to read these logs, but it appears to me that something is causing your ramp rates and ON levels to change. I cannot help but continue to suspect there is some program somewhere that is causing this to happen.

 

I also see a "fast" command in there. I don't know how this would happen other than by direct physical activation or a program.

 

I know you have "combed" through the scenes, but select the device in question from your device tree. At the right side of that page is a view showing in which scenes that device is a controller and responder. Double check to see that there are none.

[LeeG]

What level ISY firmware are you using?

 

The device is being commanded by a Program(s) at times other than what you indicated

 

Outside Front Off 0 Sat 2013/06/15 01:00:00 Program Log

Outside Front Status 0% Sat 2013/06/15 01:00:00 System Log

Outside Front Status 100% Sat 2013/06/15 16:37:09 System Log

Outside Front Fast Off Sat 2013/06/15 16:37:46 Web Log

Outside Front Status 0% Sat 2013/06/15 16:37:46 System Log

Outside Front Off Sat 2013/06/15 16:37:47 Web Log

Outside Front On 255 Sat 2013/06/15 21:20:50 Program Log

Outside Front Status 100% Sat 2013/06/15 21:20:51 System Log

Outside Front On 53 Sat 2013/06/15 22:20:50 Program Log

Outside Front Status 21% Sat 2013/06/15 22:20:51 System Log

Outside Front Off 0 Sun 2013/06/16 01:00:00 Program Log

Outside Front Status 0% Sun 2013/06/16 01:00:00 System Log

Outside Front On Level 100% Sun 2013/06/16 14:19:42 System Log

Outside Front Ramp Rate 0.5 Sec Sun 2013/06/16 14:19:42 System Log

Outside Front Status 100% Sun 2013/06/16 14:19:42 System Log

Outside Front On Level 100% Sun 2013/06/16 14:19:42 System Log

Outside Front Ramp Rate 0.5 Sec Sun 2013/06/16 14:19:42 System Log

Outside Front On 229 Sun 2013/06/16 14:21:26 Web Log

Outside Front Status 90% Sun 2013/06/16 14:21:27 System Log

Outside Front Off Sun 2013/06/16 14:21:28 Web Log

Outside Front Status 0% Sun 2013/06/16 14:21:28 System Log

Outside Front Off Sun 2013/06/16 14:21:34 Web Log

Outside Front On 255 Sun 2013/06/16 21:21:12 Program Log

Outside Front Status 100% Sun 2013/06/16 21:21:12 System Log

Outside Front On 53 Sun 2013/06/16 22:21:13 Program Log

Outside Front Status 21% Sun 2013/06/16 22:21:14 System Log

[Chasewood]

I'm on 4.0.5. , Firmware and UI

 

I've been through all my programs again. The outside on and outside off programs are the only way these switches are accessed. Neither is in any scene.

 

Could there be a phantom program lurking somewhere unseen?

[LeeG]

These entries are too similar in time on Sat and Sun to be random events. What is in the Programs that are triggered at these times Sat 21:20:50, then Sat 22:20:50 one hour later. Followed by Sun 21:21:12, then Sun 22:21:13 one hour later? Could be a Program that is triggered, performs an Action, Waits 1 hour, performs another Action.

 

 

Outside Front On 255 Sat 2013/06/15 21:20:50 Program Log

Outside Front On 53 Sat 2013/06/15 22:20:50 Program Log

 

Outside Front On 255 Sun 2013/06/16 21:21:12 Program Log

Outside Front On 53 Sun 2013/06/16 22:21:13 Program Log

[Chasewood]

Program: Outside OFF

If

time is sunset +30 mins

Then

set "Outside Front" 100%

set "Outside Garage" 100%

wait 1 hour

set "Outside Front" 21%

set "Outside Garage" 20%

 

Program: Outside ON

If

Time is 1:00:00 am

Then

set "Outside Front" off

set "Outside Garage" off

 

The program turns two sets of outside lights on at full intensity shortly after sunset and dims them both one hour later. The off program turns both off at a fixed time (1 AM).

 

Like I say, these are the only two programs that control Outside Front or Outside Garage. They are in no scenes.

 

Yesterday evening (Monday) the "On" program worked fine, but the subsequent "Off" didn't work correctly - Outside Front was on at 21% this morning.

 

I wonder if it's a fault in the switch not recognizing the signal.

 

I've factory reset this switch a couple of times already to make sure there wasn't an X10 address lurking. The X10 switch I had in that position before I replaced it with this one was also unreliable and eventually would not respond to X10 commands. The circuit the switch controls has four 60 or 100 W bulbs, which doesn't seem excessive.

 

I guess I could try swapping the switch with one that works and see if the problem moves with it, but I'd rather exhaust other approaches before trying that.

[Chasewood]

By the way - these are the only programs I have that use the ISY Schedule.

[oberkc]

Yesterday evening (Monday) the "On" program worked fine, but the subsequent "Off" didn't work correctly - Outside Front was on at 21% this morning.

 

 

Your originally-stated problem was that one of your lights "turns on at other times". The problem quoted above is a different problem, possibly from a different cause.

 

Are you still getting the one light turning on at other times?

[LeeG]

I am as confused as oberkc as I thought the problem being tracked was the device turning On/Off at times not expected.

 

I added some annotation to the Log that was posted. Outside Front was turned On/Off with activity outside of the 'Program'. It was controlled by the paddle. It was controlled either with the Admin Console or an App.

 

Did the device turn On or Off at times not noted in the posted Log?

 

Outside Front Off 0 Sat 2013/06/15 01:00:00 Program Log - Program initiated Off as expected

Outside Front Status 0% Sat 2013/06/15 01:00:00 System Log

Outside Front Status 100% Sat 2013/06/15 16:37:09 System Log - device turned On at paddle

Outside Front Fast Off Sat 2013/06/15 16:37:46 Web Log - device turned Off using Admin Console or App

Outside Front Status 0% Sat 2013/06/15 16:37:46 System Log

Outside Front Off Sat 2013/06/15 16:37:47 Web Log

Outside Front On 255 Sat 2013/06/15 21:20:50 Program Log - Program initiated On as expected

Outside Front Status 100% Sat 2013/06/15 21:20:51 System Log

Outside Front On 53 Sat 2013/06/15 22:20:50 Program Log - Program initiated 21% On as expected

Outside Front Status 21% Sat 2013/06/15 22:20:51 System Log

Outside Front Off 0 Sun 2013/06/16 01:00:00 Program Log - Program initiated Off as expected

Outside Front Status 0% Sun 2013/06/16 01:00:00 System Log

Outside Front On Level 100% Sun 2013/06/16 14:19:42 System Log - device turned On by paddle

Outside Front Ramp Rate 0.5 Sec Sun 2013/06/16 14:19:42 System Log

Outside Front Status 100% Sun 2013/06/16 14:19:42 System Log

Outside Front On Level 100% Sun 2013/06/16 14:19:42 System Log

Outside Front Ramp Rate 0.5 Sec Sun 2013/06/16 14:19:42 System Log

Outside Front On 229 Sun 2013/06/16 14:21:26 Web Log - device turned 90% On with Admin Console or App

Outside Front Status 90% Sun 2013/06/16 14:21:27 System Log

Outside Front Off Sun 2013/06/16 14:21:28 Web Log - device turned Off with Admin Console or App

Outside Front Status 0% Sun 2013/06/16 14:21:28 System Log

Outside Front Off Sun 2013/06/16 14:21:34 Web Log

Outside Front On 255 Sun 2013/06/16 21:21:12 Program Log - Program initiated On as expected

Outside Front Status 100% Sun 2013/06/16 21:21:12 System Log

Outside Front On 53 Sun 2013/06/16 22:21:13 Program Log - Program initiated 21% as expected

Outside Front Status 21% Sun 2013/06/16 22:21:14 System Log

 

The failure to turn Off at 1 AM could be a comm issue, a device issue. Does the ISY Log show the 1 AM activity to turn the device Off?

[Chasewood]

The problem(s) does not occur every day.

I first became aware of the problem when I noticed that the outside lights were on during the day. That could have been due to them not turning off at 1:00 AM or turning on before an hour after sunset.

I assumed the latter because the former did not occur to me.

Since I've started paying more attention over the past couple of days, I've only noticed the "not off" phenomenon, which happened last night and the night before. The Outside Front lights were at 21% on both days.

I'm pretty sure (but not certain) the "spurious on" phenomenon has happened repeatedly also, I just haven't seen it happen over the past couple of days.

I've got the complete log going back to when I first started with the ISY, but since I can't remember when I used the AC to turn those switches on and off and I can't figure that out from the log entries (is there an explanation somewhere of what System Log, Web Log and Program Log mean?) I decided to stop using the ISY to turn the switch off and am only looking at those log entries where I'm reasonably confident I haven't injected confusing commands from the AC.

I've only been doing that since Lee first suggested that I look at the log.

If there is some way I can filter out useful data from the complete log I'd be happy to do that. There are 41732 rows in that unfiltered spreadsheet.

[apostolakisl]

First off, use the search function in the programs editing section and search the name of the switch (edit: also any scenes that is a member of) to make sure it only exists in the programs you specified. Obviously if it exists in an unintended location, delete it. If all looks good, then you will have to wait until the problem occurs again. If/when it does, go back and look at your log. Also use the programs summary page to see what programs ran, when they ran, and whether they ran true or false.

[Chasewood]

I've been out of town for a week. I've just checked the log and it looks like the programs ran perfectly while I was gone.

I'll come back if the problem recurs.