Read the statement by Michael Teeuw here.
Default Weather Module Stuck on loading.
-
Hello, my default weather module quit working after updating to the latest MagicMirror version (2.34.0). it was a few versions behind, so I am imagining that something changed in the request that I am missing in the config but I cannot seem to track down what it might be. The API request is getting a 401 error, and using the api key itself in my browser I am able to retrieve the information, but something in the module request is causing an error I believe.
My current config (a bit of a mess as I have been trying to troubleshoot for awhile)
module: 'weather', position: 'top_right', config: { weatherEndpoint: '/weather', apiVersion: '2.5', weatherProvider: 'openweathermap', locationID: '5946768', apiKey: 'xxxxxx', //lat: 53.5462, //long: -113.4937, roundTemp: true, degreeLabel: true, colored: true, fade: falsethis returns an error "GET https://api.openweathermap.org/data/2.5/weather?id=5946768&units=metric&lang=en&APPID=xxxx 401 (unauthorized)
In the few days prior to updating, the forecast was also showing the days as a string (01/10/26) rather than the day of the week as it had been doing previous. This is what prompted me to update to the latest version of MM in the first place.
-
-
my default weather module quit working as well, however my weatherEndpoint is Openmeteo. Is that one also relying on api calls as well and that’s why it stopped working?
-
@fnmuffinman no. I haven’t seen any limits on that provider
Weather is done all in browser
Open the browser developers window
ctrl-shift-i
Select the console tab
Put weath in the filter fieldShow the messages
-
@flyedge also, using the new v3 api settings
The location is specified using lat/lon (not long)
And the only weather types are current and forecast
And endpoint would not be needed, but if provided needs to be ‘/onecall’See
https://docs.magicmirror.builders/modules/weather.html#configuration-options
