Read the statement by Michael Teeuw here.
Weather module works for current, shows 'loading' for forecast
-
@sdetweil I created a new api key, and also commented out the ‘current’ module and no change. I brought up the console, but frankly I don’t know what I’m looking for.
-
@CliffordW put ‘fore’ (no quotes) in the filter field. You are looking for anything that seems like an error, or rejection
There are two consoles. The dev console from the UI part, and the terminal console from the node_helper. You would see the latter in pm2 logs, or the terminal window where u did npm start
-
@sdetweil This is the closest thing I can find reporting as an error. However, I commented out the forecast module, and this error is still reported.
-
@CliffordW that’s because custom.css isn’t there by default.
-
@sdetweil Still not working.Any suggestions how I might troubleshoot this?
I found this in the log:
Failed to load resource: the server responded with a status of 401 (Unauthorized)
A very long url to openweather is included.
I tried using the ‘current’ apikey for forecast, the error disappeared, but still no display.
-
I have the exact same problem.
@CliffordW Did you find a solution to solve the problem? -
@matpi did u get new apikeys from openweather?
-
@sdetweil no I use this key for some time know 2-3 years at least. But the key works when it is placed in the current weather module. So I do not think the key is the issue.
-
found the problem :). id did not set:
weatherEndpoint: ‘/forecast’,
now it works.
thanks
-
@matpi awesome. can u mark this resolved? 3dots to the right, click the menu
