Weather skill does not account for timezone

I am in the US Central time zone. If it is Friday and I ask ‘MyCroft, what is the weather tomorrow’, I get the following

asking at 5:15 pm - The weather on Saturday is…
asking at 6:15 pm - The weather on Sunday is …

Looks like it is using UTC rather than the local date/time.

If I ask ‘What day is tomorrow’, MyCroft answers correctly at both times. seems to just be with the weather skill.

Thanks so much for reporting this, @tiredoftry.

We’re tracking a couple of location bugs with the front end of

I don’t suppose you’d be comfortable sharing your web_config_cache.json file with me?

Not a problem…


“name”:“Arad County”
“code”:“Fort Smith”,
“name”:“Fort Smith”
“name”:“Central Standard Time”,
“phonemes”:“HH EY . M AY K R AO F T”,
“wake_word”:“hey mycroft”,

Just so I’m diagnosing from the right starting point @tiredoftry, is your correct location Fort Smith in Arkansas?

Best, Kathy

Correct, Fort Smith, Arkansas.

1 Like

Additional data point: I just asked Mycroft about tomorrows weather and got a report for Wednesday.

Thanks so much for confirming, @tiredoftry.

I did a bit of digging into this, and I don’t think the timezone is the issue here. In the weather-skill code, when you use a day of the week or relative reference like Monday or tomorrow, this function converts that reference to an actual date.

My read of this is that the code does not take into account the timezone of the user - so if the user is in timezone GMT -0600, then it will treat 5.15pm as 11.15pm - ie tomorrow is Saturday, but will treat 6.15pm as 12.15am - ie tomorrow is Sunday.

This also explains why I get such interesting results - I’m in UTC +1000hrs near Melbourne, Australia. If I ask before 10am in the morning what tomorrow’s weather is like, I get today’s result :wink:

To resolve this I think it will take some re-factoring of the Weather Skill to take into account timezone when calculating relative days.