jason0x43

That should be doable, but it will involved editing some Go code. The command that shows the "Weather for XXX" Alfred item needs to be updated to send an argument rather than doing nothing (which is what it does now). That argument would then tell the workflow to stop rather than trying to get forecast data from the alfred-weather binary. You're welcome to try your hand at that, or I could probably look into it in a couple weeks.

I have a paid Apple developer account. So far as I've been able to determine, it's not possible to notarize something with a free account.

Version 1.6.1 is now available on the project releases page. No new features, but it's digitally signed and notarized, so macOS shouldn't raise any security warnings when the workflow is installed.

I'll try to get a signed version of the workflow up in the next few days. That won't do anything for you if you've done the right-click + Open trick, but it will at least nix this problem for new users.

The most recent release (on github) shouldn't have this issue.

Interesting, I hadn't seen that setting before. You learn something new every day! 😄

@pulgalipe Do you mean that the temperature, etc. values aren't visible until you highlight a particular item? If that's the case, it could mean that your color scheme is misconfigured (specifically, the "result subtext" color might be the same as the default background color).

I tested the workflow with ClimaCell this weekend, and I couldn't reproduce any issues (which doesn't mean there isn't a problem, just that it didn't show up for me). One thing to do is run `wtr options` and verify that your ClimaCell key matches what's in your account at developer.climacell.co.

Hmmm...the 403 implies that either the API key is invalid, or they've changed an API. I'll try to take a look this weekend.

Try opening up Alfred's preferences, then go to Workflows -> Toggl, and click the "debug" icon in the upper right of the preferences window. Try getting the status of your active timers (`tgl timers`) and look at the messages that show up in the debug pane. Testing myself (which may not say much since I haven't use Toggl in a while so I have no active tasks), the GET request to toggl.com to load the timers takes 1-2 seconds. Using `tgl timers` again within a short time should use the cache and not make a new GET request. Is the GET request taking a long time, or does it look like it might be something else?

I haven’t looked at this in quite a while, but I imagine it won’t work for new users since Google killed the “works with Nest” API. I believe they plan to open a new developer API later this year, though.

Version 1.6.0 is out with support for a couple of new APIs. Since Weather Underground has been gone for a while and DarkSky is on its way out, I added support for ClimaCell and OpenWeather.

Run `wto`, select one of the *Key options (e.g., DarkSkyKey), hit enter, paste your key, and hit enter again.

Apparently this has been an issue for a number of users. A short term fix is described here.

@Cicilia Thanks for letting me know. I created #55 to track that.