Default Weather Module Stuck on loading.

sdetweil

@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 field

Show the messages

sdetweil

@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

fnmuffinman

@sdetweil so after messing around and trying out a new module (might change my problem here) but seems it still won’t load. I am still pretty green at troubleshooting modules so excuse my lack of knowledge here. I have a screenshot of the spot you asked but for the new module:

sdetweil

@fnmuffinman which module are you using

git remote -v

In the module folder

Tom’s is v3 api only

The original is v2.5 only

From Toms version readme

sdetweil

@fnmuffinman these modules use a helper so debug info is where you npm start , IF the author presents logging

fnmuffinman

@sdetweil alrighty so I got a bit further after a bit more testing and digging into the pm2 logs so here is where I am at.

I am using this module: https://github.com/Tom-Hirschberger/MMM-OpenWeatherForecast

Here is a screenshot of the current error I am seeing in the dev tools

I was seeing a 401 Unauthorized error for a bit but figured out the 3.0 API call thing. I did test the URL from the website with my lat and long with the API key it works. I no longer see those errors in my pm2 logs on the mirror. Here is a screenshot of my current config in the config.js as well

Sorry didn’t want to dox or give my api key :) also as further troubleshooting, here is a screenshot of the api.openweathermap.org URL to show it does work

appreciate the help! my first time truly digging into why a module isn’t working. I have alot more respect for coders lol

sdetweil

@fnmuffinman did you do the npm install in the module folder?

fnmuffinman

@sdetweil I was pretty sure I did but I ran it again and rebooted the mirror to the same results. Still the same error as the above screenshot in the dev tools console. Not sure if it matters, but I do have the mirror booting headless. I don’t remember exactly but it’s part of the startup script so when I reboot the pi, it automatically runs MM and loads it onscreen

sdetweil

@fnmuffinman what do you mean headless?

If no display here, you need to do
npm run server

And access from somewhere else
Make sure to enable config.js to allow other machine access

fnmuffinman

@sdetweil sorry wrong terminology. It is running on a pi connected to a display. I meant headless in I don’t have peripherals on it, just ssh into it from my pc