2 out of these things do not exist in Australia natively, and one of those is a myth. what were you on while there? I know the Aussies like a good wind up.
No problems. I wasn't blaming you for it.
So what URL do I need to use?
The one in your example just doesn't work.
And yes I just dumbly use the node with the city and country set.
I can/could get used to how you do it, but it is the URL that is catching me out.
Perhaps there are different OWM APIs and API keys?
All I can say is if I use the flow I posted with my real API key in global context, it retrieves a forecast:
I get code: 401 and this text:
Please note that using One Call 3.0 requires a separate subscription to the One Call by Call plan. Learn more here https://openweathermap.org/price. If you have a valid subscription to the One Call by Call plan, but still receive this error, then please see https://openweathermap.org/faq#error401 for more info.
Seems I am back to square 1 for now.
I get the same error message as you if my API key is incorrect.
Yeah, but if I then use the same key with the actual node, I don't get an error.
It works.
So we probably have different account types. 
OWM node Version 0.5.1 uses old api, so will work with you older api-key. As said V3 api you need to subscribe to get a new key, the One Call subscription plan. Same for OWM node v 1.0
2 Likes
If you search for "secret" in the flows library, there are a couple contrib nodes that will hold your api key in a way that they cannot be exported...
1 Like
Thanks. I'll investigate that.
Thanks Steve.
I'll look at those too.
(When I get home this afternoon)
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
