Date Format?

General Discussion
1

I checked around but couldn’t figure this one out. I have a SmartApp that calls location.currentValue(“sunsetTime”). It refreshes every few minutes. Sometimes, the output is in PDT and sometimes in UTC, also GMT?

Why would that be? I’m guessing it doesn’t hurt anything – but it seems weird. This is straight from my logs:

b23404f4-5752-4a77-a53b-14ed58f51dbf  3:44:23 PM: debug SUNSET: Fri Oct 30 22:48:00 PDT 2015 : SUNRISE: Fri Oct 30 12:21:00 PDT 2015
b23404f4-5752-4a77-a53b-14ed58f51dbf  3:44:23 PM: debug SUNSET: Fri Oct 30 22:48:00 PDT 2015 : SUNRISE: Fri Oct 30 12:21:00 PDT 2015
b23404f4-5752-4a77-a53b-14ed58f51dbf  3:42:36 PM: debug SUNSET: Fri Oct 30 22:48:00 UTC 2015 : SUNRISE: Fri Oct 30 12:21:00 UTC 2015
b23404f4-5752-4a77-a53b-14ed58f51dbf  3:42:36 PM: debug SUNSET: Fri Oct 30 22:48:00 UTC 2015 : SUNRISE: Fri Oct 30 12:21:00 UTC 2015
b23404f4-5752-4a77-a53b-14ed58f51dbf  3:42:36 PM: debug SUNSET: Fri Oct 30 22:48:00 GMT+08:00 2015 : SUNRISE: Fri Oct 30 12:21:00 GMT+08:00 2015
3 Likes
2

I’d be willing to bet its a server build consistency issue. As different servers are most likely handling your request, if their time is setup differently that would report it back differently.

The sad part is, Time is VERY important to a server. I would not be surprised if this isn’t causing other issues as well… like timed events, scheduler, sunrise/sunset failures.

2 Likes
3

Thought the same, the other day when my current time was recorded in EST and the next runin was in PDT.

4

I think this might be resolved very shortly, if not already done.
It’s an issue with the JVM’s and the previous ability to change the default TZ for the entire JVM. I’m guessing this will go away very very soon.

2 Likes