jason0x43

Hmmm...that was kind of a messy process I gave you there. Ok, let me make a couple more updates and I'll get back to you.

Ok, glad to hear it's working. I uploaded a new version of the workflow that does some debug logging in the background. If you install that one, it could help figure out narrow down the source of the problem if it comes up again.

Ok, I just uploaded a new version with some debug logging. That should make diagnosing the problem a bit easier. Just use the download link in the first post in this thread and install the workflow. First, try running "wset location" again. The workflow will create a new file in the workflow directory called "debug.log" that logs all the Weather commands you've run for the last hour, including exceptions. You can get to the file by: Open Alfred's preferences Click on Workflows at the top of the pane Select the Weather workflow Double click on one of the command boxes in the workflow area (any one of the ones with the stormy icon) Click on the "Open workflow folder" button at the bottom of the info pane that appears That will open a Finder window at the workflow folder. You should see a file called debug.log. Hopefully it will shed some light on the problem. Just paste its contents into a new message here.

Hmmm... Just to make sure, are you using a recent version? (Like, did you download it in the last day or two from this thread or from the github page?) I'm going to upload a new version with some debug code in a little while--I'll let you know when that's ready. That should make diagnosing this a bit easier.

Which command gives you that error?

Do other commands work, like "wset units" or "wset service"? If you type in "wset location washington dc" (exactly that, without the quotes), does it work?

It's never the easy answer. Ok, I'm looking into it. Could you tell me what version of Alfred you have?

Excellent, I'm glad you like it!

It sounds like the script that the workflow uses to query location data is crashing, or at least returning bad data. Hmm... Does the location you're trying to enter contain any non-ASCII characters, by chance?

The problem should be fixed now--just download and install it again. Basically I had upgraded one part of my code without updating the other parts that were using it. Sorry about that.

Hmmm...let me look into it a bit more and see if I can reproduce the problem. Could you tell me what version of Alfred you're using? And is this the first time you've tried this workflow, or are you upgrading from the previous version?

Just try any of the commands. The first time you try to do anything (get status, set temp, etc) the workflow will ask you for you login info.

Ok, I see the problem, Your service is defined as Weather Underground, but you only have a key for forecast.io. I'm not entirely sure how it got into that state, but you should be able to fix it by running the "wset service" command again. I've posted an updated version of the code that deals with this situation (by asking you to re-specify your service if the service key is missing).

I just posted a new version that fixes a small bug in the settings migration code. It would only have come up if you upgraded from the very first version of the settings to the current one. If you haven't had any problems, you aren't affected.

Hmmm...I've tried this with several older versions of my settings file but I can't reproduce this error. Could you open up your settings file (at /Users/<you>/Library/Application Support/Alfred 2/Workflow Data/jc-weather/settings.json) and either post it or see if it looks like this? It's OK if you have additional settings, like key.fio, but you should have at least the ones below. { "key.wund": "<your key>", "service": "wund", "icons": "grzanka", "days": 3, "time_format": "%A, %B %d, %Y %I:%M%p", "version": 3, "location": { "latitude": 34.0522342, "timezone": "America/Los_Angeles", "longitude": -118.2436849, "name": "Los Angeles, California", "short_name": "Los Angeles" }, "units": "si" }

Another update. The workflow is now timezone-aware. This is used to 1) fix a bug where you could get weird output if you were looking at the weather across the international date line, and 2) show the local time for your target location.

Just updated the workflow to support temperate range mode (heat/cool)

Thanks!

New version. There is now a "Get key" on the "Enter your API key" dialog that pops up when selecting your weather service. I thought this was a bit easier than having a separate "getkey" command; it's more where you need it than floating around on its own. You can also set a custom time format now with the "format" command.

Note: This workflow is no longer maintained. This is a really simple workflow that performs unit conversions. Conversion commands look like: u {value} {in units} > {out units} You can include a space after the u keyword, but it's not required. Units can generally be abbreviated or not, as long as the input is unambiguous. Here are some valid commands: u 5km > miles u 5km > mi u5km>mi You can also do unit math (again, spaces are generally optional): u 1cm * 1in u 1in^2 / 2mm^2 u1cm+2.5in-3mm>ft Just remember that units matter. You won't get any output if you try to do something like 1cm * 1in > in, because multiplying two lengths gives an area (like in^2). The calculator is called as you type, so it'll give you an answer whenever you type a query it can process. Actioning the result will copy the value (just the number) to the clipboard. That's it! Well, there are also a couple options you can configure. You can open the configuration file with the command u>. The options are: "separator" - what separator to use between the input value and output units "precision" - how many decimal digits to include in the output (set to null for unlimited) More info and source is available here. Download Update 2014/05/22: You can now use a space between a number and its units (e.g., "5 km" in addition to "5km"). Update 2014/02/06: Unit math is back! Update 2013/12/07: Add output precision option (see above) Update 2013/12/01 (again): Bug fix Update 2013/12/01: Added support for using "space" as the unit separator, so you can do queries like "1mile km". Update 2013/11/30: Added Euros to the currency list. I also added a couple extra commands, accessible with the 'u>' command, Update 2013/11/29: Currency conversion is back. Update 2013/11/25: At last, I pushed out an update that should have this back up and running. It's using a local library now, so it's faster and not subject to the whims of Google. Sorry it took so long. Update 2013/11/5: Google shutdown the API this workflow was using on November 1, so it's broken until I switch it to something else. Sorry about that. I'll have it back up and running in a day or two. Update 2013/10/11: Bugfix Update 2013/8/14: It should now work with Snow Leopard (Python 2.6). Update 2013/8/13: Now with Alleyoop support!

I just posted an updated workflow that should work properly again on pre-2.0.3 Alfred.

You do need an API key from either Weather Underground or forecast.io, but only to get the actual weather data. From your error message I'm guessing you haven't upgraded to Alfred 2.0.3 yet (it was just released in the last couple of days). I made a change to the workflow to take advantage of some new stuff in 2.0.3. It may have been a bit premature.

New version up. The workflow will now display weather alerts. You can action an alert to be taken to a details page (this only works in the US for Weather Underground). There's also a new command to set the format for displaying timestamps.

I just posted a new version--this one ties the key specification to the service selection, so there shouldn't be any more problems with key vs. service.

That's actually an error from the Weather Underground that they send back when your API key is incorrect. One thing to keep in mind is that you have to choose the service first, then set the key, because `wset key` sets the key for the current service (wunderground by default). I should probably make specific commands to set the key for forecast.io or wunderground, or maybe look at the key format or something.