Jump to content
jason0x43

Weather workflow

Recommended Posts

Thanks for this awesome workflow Jason!

Unfortunately, the feelslike option seems too hard to figure out. I've tried everything, including using it as an argument, and searched in the options and even tried opening the sourc e(at that point, I think my technical understanding went moot lol)

 

How do I toggle, or see feelslike? As you indicated in a previous comment, it should be there.

 

Another thing is, if I scroll on the hourly, it shows no precipitation. But if I scroll on daily (wtd), it says light rain in evening. And also on Thursday (which on wth, it shows only Partly Cloudy)... any idea what's going on?

Screen Shot 2017-05-02 at 10.28.38 PM.png

Screen_Shot_2017-05-02_at_10_25_56_PM.png

Share this post


Link to post

The current version of the workflow didn't have support for apparent ("feels like") temperatures; I've added that to version 1.3.0.

 

Regarding the discrepancy between hourly and daily forecast, that happens sometimes. The workflow isn't actually interpreting the data to generate the forecast text; the text comes directly from the service (Dark Sky or Weather Underground). Sometimes the textual descriptions may not appear to agree with the hourly data. You can double check the workflow by visiting the relevant service (Dark Sky or Weather Underground) and double checking that what the workflow says agrees with a forecast for your location (or whatever location you were checking with the workflow).

Share this post


Link to post
12 hours ago, jason0x43 said:

The current version of the workflow didn't have support for apparent ("feels like") temperatures; I've added that to version 1.3.0.

 

Regarding the discrepancy between hourly and daily forecast, that happens sometimes. The workflow isn't actually interpreting the data to generate the forecast text; the text comes directly from the service (Dark Sky or Weather Underground). Sometimes the textual descriptions may not appear to agree with the hourly data. You can double check the workflow by visiting the relevant service (Dark Sky or Weather Underground) and double checking that what the workflow says agrees with a forecast for your location (or whatever location you were checking with the workflow).

 

Awesome, thanks Jason!

Share this post


Link to post
Posted (edited)

Hi,

 

Thank you for this workflow, it looks really cool, but i have not been able to get this to work. I got my API from Weather Underground here: https://www.wunderground.com/weather/api/, but i have not been able to use this workflow. It just sits on 'thinking' and that is it then it shows me the google search and nothing..

 

Using this: http://www.packal.org/workflow/weather

 

Any advice?

 

Thanks

 

Miguel

Edited by Miguel05

Share this post


Link to post
Posted (edited)

EDIT: seems to be working now. Occasionally "ERROR_OVER_QUERY_LIMIT" is displayed but I'm not sure what's causing this.

 

Question: the official screenshots display temperature, precipitation %, and sunrise/sunset as subtext underneath each day's heading, but I only see this information if select a manually scroll/highlight a specific day. Is this a configurable option?

 

------------------- 

 

I have the same problem as Miguel05 using Weather Underground. The debug panel shows the following:

 

Note: I redacted my API key and some other information.

 

[2018-04-26 18:28:55][input.scriptfilter] Queuing argument ''

[2018-04-26 18:28:56][input.scriptfilter] Script with argument '' finished

[2018-04-26 18:28:56][ERROR: input.scriptfilter] Code 2: [alfred] 2018/04/26 18:28:55 Alfred version: 3.6.1

[weather] 2018/04/26 18:28:55 Using config file /Users/XXXXXX/Library/Application Support/Alfred 3/Workflow Data/com.jason0x43.alfred-weather/config.json

[weather] 2018/04/26 18:28:55 Using cache file /Users/XXXXXX/Library/Caches/com.runningwithcrayons.Alfred-3/Workflow Data/com.jason0x43.alfred-weather/cache.json

[weather] 2018/04/26 18:28:55 loaded config

[weather] 2018/04/26 18:28:55 loaded cache

[alfred] 2018/04/26 18:28:55 set keyword to 'daily'

[alfred] 2018/04/26 18:28:55 tell: data=alfred.workflowData{Keyword:"daily", Mode:"tell", Mod:"", Data:""}, arg=''

[alfred] 2018/04/26 18:28:55 Adding items for 'daily'

[weather] 2018/04/26 18:28:55 Running DailyCommand

[weather] 2018/04/26 18:28:55 using configured location

[weather] 2018/04/26 18:28:55 getting forecast for main.Location{Latitude:XX.XXXXXXX, Longitude:XXX.XXXXXXX, Timezone:"", ShortName:"XXXXXX, XXXXXX", Name:"XXXXXX, XXXXXX"}

[weather] 2018/04/26 18:28:55 getting URL http://api.wunderground.com/api/XXXXXXXXXXXXXXXX/conditions/alerts/hourly/astronomy10day/forecast10day/q/XX.XXXXXXX,XXX.XXXXXXX.json

panic: runtime error: index out of range

 

goroutine 1 [running]:

main.(*WeatherUnderground).Forecast(0xc42011eb60, 0x40390870aebec4cc, 0x405e642fcdb88517, 0x0, 0x0, 0xc420077310, 0xe, 0xc420077320, 0xe, 0x0, ...)

/Users/jason/Documents/Programming/go/src/github.com/jason0x43/alfred-weather/wunderground.go:206 +0x12e8

main.getWeather(0x7fff5fbff9d1, 0x0, 0x40390870aebec4cc, 0x405e642fcdb88517, 0x0, 0x0, 0xc420077310, 0xe, 0xc420077320, 0xe, ...)

/Users/jason/Documents/Programming/go/src/github.com/jason0x43/alfred-weather/weather.go:114 +0x6c8

main.DailyCommand.Items(0x7fff5fbff9d1, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x18)

/Users/jason/Documents/Programming/go/src/github.com/jason0x43/alfred-weather/daily.go:31 +0x107

main.(*DailyCommand).Items(0x157fe38, 0x7fff5fbff9d1, 0x0, 0x0, 0x0, 0x1, 0x1, 0x0, 0x0, 0x0)

<autogenerated>:2 +0x6d

github.com/jason0x43/go-alfred.(*Workflow).Run(0x1563840, 0xc42011fe98, 0x4, 0x4)

/Users/jason/Documents/Programming/go/src/github.com/jason0x43/go-alfred/workflow.go:258 +0x5e6

main.main()

/Users/jason/Documents/Programming/go/src/github.com/jason0x43/alfred-weather/main.go:85 +0x6de

Edited by etm001

Share this post


Link to post
3 hours ago, etm001 said:

Occasionally "ERROR_OVER_QUERY_LIMIT" is displayed but I'm not sure what's causing this.

 

Almost certainly that means you’ve exceeded your allowed number of API calls. 

Share this post


Link to post
53 minutes ago, deanishe said:

Almost certainly that means you’ve exceeded your allowed number of API calls. 

 

It must have been too many calls per minute.

Share this post


Link to post
Posted (edited)

I have exactly the same problem with:

Quote

panic: runtime error: index out of range

error message in the debug panel with WU service. 

 

With DS service everything works just fine

Edited by RuslanI

Share this post


Link to post
Posted (edited)

So, it looks like maybe you're not getting astronomy data (which contains sunrise and sunset times).

 

Try accessing the API address from your debug log directly in the browser. (http://api.wunderground.com/api/xxxxxxxxx/conditions/alerts/hourly/astronomy10day/forecast10day/q/xx.xxxxxxx,yy.yyyyyy.json). You should get back a page full of JSON data that contains a section starting with

"astronomy10day": [
  {
    "day":0,
    "sunrise": {
        "date": {
          "epoch":1525688961,
          "hour":6,
          "mday":7,
          "min":"29",
          "mon":5,
          "pretty":"6:29 AM EDT on May 07, 2018",
          "sec":21,
          "tzname":"EDT",
          "year":2018

Is that section in there?

Edited by jason0x43

Share this post


Link to post

With the latest version, after adding my DarkSky API key and a location, I'm still asked to choose a service. Doesn't seem like that gets added to the json config file.

 

Share this post


Link to post
On 6/22/2018 at 12:27 PM, Hamlin said:

With the latest version, after adding my DarkSky API key and a location, I'm still asked to choose a service. Doesn't seem like that gets added to the json config file.

 

 

Did you set the service to Dark Sky?

Share this post


Link to post

Hi there, 

 

Trying to install this workflow and when I try to update the default location it shows "ERROR_OVER_QUERY_LIMIT" in the results. I just created the API key for Dark Sky AND have had no activity with this key yet, so curious on how to resolve this issue.

 

Thanks!

Share this post


Link to post

I believe you can get that error if you make requests too quickly (like, 5 a second for a couple of seconds), although that’s hard to do with the workflow. When you hit a transient limit (as opposed to the 1000 query per day limit) it should reset in a few minutes. Are you still seeing the issue?

Share this post


Link to post

The "ERROR_OVER_QUERY_LIMIT" appears to be an issue with the Google Location API lookup according to the GITHUB posts.  The workflow works but you cannot query other locations.  

Edited by mikedvzo

Share this post


Link to post

Did anyone fix this? It seems that there is a version with a fix for the Google Location API that has been created but no link to download it was provided on Github or here.

Share this post


Link to post

The problem is that Google stopped allowing requests to its Location API without an API key in June, and apparently I haven't used the location feature in a while. :) To fix it I'll either need to switch to some other location service or required all users to get a Google API key, which is a bit of a pain. It looks like OpenStreetMaps has an open location service API; I'll look into that. 

Share this post


Link to post

Ok, version 1.5.0 is out. I replaced uses of Google's Location API with OpenStreetMaps Nominatim, which seems to work OK, although it's a bit less intelligent than Google's. At least it works, though. :)

Edited by jason0x43

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×