Read the statement by Michael Teeuw here.
Openweathermap api works for 2 of my modules but not for Hourly
-
module: "weather", position: "top_right", header: "Hourly", config: { weatherProvider: "openweathermap", type: 'hourly', apiKey: "new api key", units: "imperial", maxEntries: 10, fadePoint: 0.12, showPrecipationAmount: true, AnimationSpeed: 1000, ignoreToday: true, colored: true, fade: false, timeFormat: 12, showFeelsLike: true, lat: 40.7128, lon: -74.0060, }
I’ve got a new api key, just replaced the old one. It was working fine. Any ideas why this might not be working?
-
@hengy hourly uses the /onecall endpoint, and I think the new apikey ONLY works with the v3.0 api on onecall
SO,
in config for hourly set
apiVersion :'3.0'
it defaults to 2.5 til next release
-
I’ve added it here. No luck.
{ module: "weather", position: "top_right", header: "Hourly", config: { weatherProvider: "openweathermap", type: 'hourly', apiVersion :'3.0', apiKey: "new api key", units: "imperial", maxEntries: 10, fadePoint: 0.12, showPrecipationAmount: true, AnimationSpeed: 1000, ignoreToday: true, colored: true, fade: false, timeFormat: 12, showFeelsLike: true, lat: 40.7128, lon: -74.0060, } }
-
@hengy I took your config (edited and added the code block and start/end {} in your post)
and my apikey
on version 2.27and got this
-
@sdetweil Maybe my mistake. I’m using the new ver 3 api. Should I be using the previous version I had running with no issues?
-
@hengy I don’t know. I am using my 3.0 apikey
-
@sdetweil possible they changed the plan. I’m using free.
-
@hengy yes that doesnt provide hourly, says so right there.
that is the plan that is going away. 2.5
you must provide a credit card for 3.0 onecall
first 1000 calls per day are no chargenote: 3 module instances is 3 calls
so only 333/ day. only 4 calls per minute each module -
@sdetweil
Thanks for your help, will do.