|
Scott Goffman Posts: 111
12/14/2014
|
Every since I updated to the latest Core Service yesterday, events (at least my most noticeable ones) haven't been firing. I can manually trigger the scenes/groups/devices connected to them, but the timed events don't seem to do anything.
I don't see anything reported in the Windows app logs or in errors.xml; what else can I do to debug this?
Thanks,
-Scott
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
12/14/2014
|
Hey Scott, that's really weird. Can you send me your configuration.xml and log.sdf files? I'll take a look and see if I can spot anything...
|
|
|
0
link
|
|
Scott Goffman Posts: 111
12/15/2014
|
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
12/15/2014
|
Your Sunrise, Midnight, and Sunset events are all scheduled to next run tomorrow. Your Bedtime event is scheduled to run at 11pm tonight. Assuming the bedtime event runs as planned, the question I have is why did it skip a day (assuming I'm understanding what happened correctly).
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
12/15/2014
|
Looking deeper, the Sunrise and Midnight events did in fact fire as scheduled, but it appears the Sunset event did not. Is that the one you noticed?
|
|
|
0
link
|
|
Scott Goffman Posts: 111
12/15/2014
|
>Looking deeper, the Sunrise and Midnight events did in fact fire as scheduled, but it appears the Sunset event did not. Is that the one you noticed?
That's the one I noticed tonight, but "Sunset" and "Midnight" didn't fire last night.
-Scott
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
12/15/2014
|
There are log entries for the event actions this morning... is it possible the event did fire, but the lights were reactivated for some reason?
One example:
edited by ccicchitelli on 12/15/2014
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
12/15/2014
|
| 12/14/2014 5:43 AM | Updated status of f2610f72-87d1-479d-b382-9c722387a256 to 0 | | 12/14/2014 5:43 AM | CMD Sent: 02 62 1D 95 DE 00 13 01 | | 12/14/2014 5:43 AM | Received: 02 62 1D 95 DE 00 13 01 06 | | 12/14/2014 5:43 AM | Received: 02 50 1D 95 DE 22 3F 0F 21 13 01 | | 12/14/2014 5:43 AM | CMD Match (2nd): 02 62 1D 95 DE 00 13 01 | | 12/14/2014 5:43 AM | Updated status of 9379d64d-1f1e-4118-9fd9-f4ca0810eae9 to 0 |
|
|
|
0
link
|
|
Scott Goffman Posts: 111
12/15/2014
|
I'm not sure what event that would be; I have a Sunrise - 10, which should be 6:47 am; Sunset - 20 = 4:23 pm; but nothing at 5:43 am that i'm aware of.
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
12/15/2014
|
There are also entries at 6:50, which was probably sunrise today. Tomorrow it will be 6:47 and so on...
|
|
|
0
link
|
|
Scott Goffman Posts: 111
12/15/2014
|
Looks like that 5:43 event was sunrise, since it's turning off device 1D.95.DE (which only happens at sunrise). Does the Core service just use the local Windows system time, or does it connect to an external time server?
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
12/15/2014
|
It uses the system time. Though it uses your zip code to pull the lat/long which is then used to calculate sunrise and sunset. Actually, that could be the issue. The most recent update was to update the weather (lat/long) to match a MSN service update. For about 24 hours it wasn't working, which means it may not have calculated the next run times for all events. All the scheduling appears to be right now though, I think you should be good going forward...
|
|
|
0
link
|
|
Scott Goffman Posts: 111
12/15/2014
|
Okay, I'll keep an eye on it for the next day/night cycle and report back.
Thanks for the help!
-Scott
|
|
|
0
link
|
|
Scott Goffman Posts: 111
12/15/2014
|
Update: For testing purposes, I added an action to the 11pm Event to email me. It did correctly fire at 11pm last night; but then also twice at 6:51 am (sunrise). Could DawnGuard be causing that event to trigger?
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
12/15/2014
|
Can you send your latest configuration.xml file?
|
|
|
0
link
|
|
Scott Goffman Posts: 111
12/15/2014
|
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
12/15/2014
|
Thanks Scott. Now we're in business. It looks like issue yesterday was as I thought - from the MSN weather service being offline for a day.
This issue is separate, it appears your 11pm event fired, then scheduled itself to run again next at 6:51am, ran again, then scheduled itself for 6:51am tomorrow. We did make a change to the next run date scheduler so that must be the cause of this, let me look into and it and I'll reply back here...
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
12/16/2014
|
Hey Scott, I've run a bunch of tests and trials and have not been able to replicate this issue. Can you confirm if this has happened again?
Thanks!
-Chris
|
|
|
0
link
|
|
Scott Goffman Posts: 111
12/16/2014
|
It did; the 11pm event failed to trigger last night (but did fire twice again this morning at sunrise). Config is unchanged, but I updated Log.sdf here: http://goffman.net/docs/CastleOS_Files/-Scott
|
|
|
0
link
|
|
Chris Cicchitelli Administrator Posts: 3390
12/16/2014
|
Tracked it down, will fix and post an update, thanks!!!
|
|
|
0
link
|