PDA

View Full Version : Sunrise scheduler has stopped working a few days ago



caseyp
August 30th, 2015, 08:31 AM
Hi Ron....or anyone else out there that can help,
I've been using the scheduler to automate some outdoor lighting for over a year now and it's been working flawlessly until the last 3 or 4 days. For some reason the sunset scheduler still turns them on but the sunrise one never turns them back off. I've restarted the computer and that didn't help. I do not see any errors in the logger. I can still manually turn them off with Girder. It's as if the scheduler no longer knows when it's sunrise. I've attached 2 screenshots of the scheduler.


Thanks for any help you an provide,
Casey

http://www.promixis.com/forums/attachment.php?attachmentid=6905&stc=1http://www.promixis.com/forums/attachment.php?attachmentid=6904&stc=1

Ron
September 7th, 2015, 09:20 AM
Strange. I tried your coordinates and offset here and it works. Can you send me your C:\Users\<YOURNAMEHERE>\AppData\Local\Promixis\Girder 6\plugin_235.cfg file?

caseyp
September 7th, 2015, 10:51 AM
Here's the cfg file Ron...


[
{
"device": 235,
"eventString": "Sunset+20",
"running": true,
"tasks": [
{
"begin": 0,
"end": 0,
"every": 1,
"id": 3,
"lat": 40.800800000000002,
"lng": -85.827200000000005,
"next": 1441671870,
"offset": 20,
"previous": 1441585620,
"randDist": 0,
"randMax": 0,
"randMin": 0,
"timezone": "America/New_York",
"type": 2
}
],
"uuid": "{8a63d2b2-3dd5-4db5-99fd-c73c196c1152}"
},
{
"device": 235,
"eventString": "Sunrise-20",
"running": true,
"tasks": [
{
"begin": 0,
"end": 0,
"every": 1,
"id": 3,
"lat": 40.800800000000002,
"lng": -85.827200000000005,
"next": 0,
"offset": -20,
"previous": 1440672360,
"randDist": 0,
"randMax": 0,
"randMin": 0,
"timezone": "America/New_York",
"type": 3
}
],
"uuid": "{7ad292f4-7377-4668-ae01-4f73a18e8471}"
},
{
"device": 235,
"eventString": "1050PM",
"running": true,
"tasks": [
{
"begin": 0,
"end": 0,
"every": 1,
"hour": 22,
"id": 3,
"minute": 50,
"next": 1441680600,
"previous": 1441594200,
"randDist": 0,
"randMax": 0,
"randMin": 0,
"type": 5
}
],
"uuid": "{d2c47b64-3bf6-437c-9ca2-00367d5a5200}"
},
{
"device": 235,
"eventString": "1049PM",
"running": true,
"tasks": [
{
"begin": 0,
"end": 0,
"every": 1,
"hour": 22,
"id": 3,
"minute": 49,
"next": 1441680540,
"previous": 1441594140,
"randDist": 0,
"randMax": 0,
"randMin": 0,
"type": 5
}
],
"uuid": "{dec6cb58-fe82-4506-9884-354c75912150}"
},
{
"device": 235,
"eventString": "Sunrise",
"running": true,
"tasks": [
{
"begin": 0,
"end": 0,
"every": 1,
"id": 3,
"lat": 40.800800000000002,
"lng": -85.827200000000005,
"next": 0,
"offset": 0,
"previous": 1440673560,
"randDist": 0,
"randMax": 0,
"randMin": 0,
"timezone": "America/New_York",
"type": 3
}
],
"uuid": "{e004a2ab-e120-4162-9d61-cf6616168211}"
}
]

caseyp
September 7th, 2015, 10:56 PM
Ron, I went ahead and deleted the existing tasks and recreated them and they look as though they may work because it's showing a "next" time which the others were not. This has worked fine for over a year so I don't know why it changed but I would think it about has to be a bug somewhere. I'll keep you posted.

Thanks,
Casey

Update: This worked. The lights shut off at the appropriate time today. I still don't have any idea why it quit working and this fixed it but hopefully it doesn't happen again.

Ron
September 8th, 2015, 11:28 AM
Thanks for reporting this one. I have found the bug and will release an update this week. There was a rounding error which was causing your coordinates at August 28, 2015 to create an invalid date for the sunrise.