Read the statement by Michael Teeuw here.
Weather not working
-
@KI6UVE the doc for openweathermap provider uses a different term for the key
-
@KI6UVE currentweather and weatherforecast have been replaced by weather, with type:‘current’ or type:‘forecast’
-
I changed it from appid to apiKey and the other module names to just “weather”, but still just black space where it should be in MM. Did I miss anything else?
-
@KI6UVE looks like weather via openweathermap takes lat/lon, not location
i recommend reading the doc, linked to from the MM github page
-
@sdetweil
I read that doc and I changed weatherEndpoint to “/onecall” and put in the lat and lon variables, but now I get a parsing error: unexpected token “lat” -
@KI6UVE don’t change the endpoint, missing a comma on the line before?
-
@sdetweil
I took out the endpoint line and that fixed the parsing error, but still no weather. I rechecked my api key and it is correct. Any other ideas? Thanks!! -
@KI6UVE open the developers window, ctrl-shift-i, then select the console tab and put weath in the filter field
is this an openweather v 3 apikey, that u had to provide a credit card to get?
if so, add
apiVersion:'3.0',to the weather config section
-
@sdetweil
No luck. I noticed you used ‘ ‘ instead of “ “ for the ‘3.0’. I used “ “ for all my other variables, such as type: “forecast”. Is that correct?The doc file doesn’t have any notation for how the lat/Lon is presented. Should that read…lat: ‘33.3025’ or nothing as it would imply in the doc file, I.e., lat: 33.3025
-
@KI6UVE lat and lng are numbers, so no quotes. either type is ok as long as they match
