Read the statement by Michael Teeuw here.
Problems With Weather
-
@mykle1 pi@raspberrypi:~ $ pm2 stop MagicMirror
[PM2] Applying action stopProcessId on app [MagicMirror](ids: 0)
[PM2] MagicMirror ✓
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name │ mode │ ↺ │ status │ cpu │ memory │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ fork │ 6 │ stopped │ 0% │ 0b │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
pi@raspberrypi:~ $ pm2 start MagicMirror
[PM2] Applying action restartProcessId on app [MagicMirror](ids: 0)
[PM2] MagicMirror ✓
[PM2] Process successfully started
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name │ mode │ ↺ │ status │ cpu │ memory │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ fork │ 6 │ online │ 0% │ 2.4mb │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
pi@raspberrypi:~ $
Still no luck displaying forecast, thank you again for bearing with me this long -
Were there any errors when MM launched?
-
MagicMirror should have launched when you issued the
pm2 start MagicMirror
command -
@mykle1 No errors and yes MM launched, everything is displaying but the forecast
-
@mykle1 now it is displaying message: “Please set the correct openweather appid in the config for module: weatherforecast.”
-
I’m done for the night, mate. I would suggest you double check your appid at openweather. copy and paste it into your config entry for weatherforecast and make sure it is in quotes.
Perhaps someone else will continue to help you tonight.
Good luck
-
@mykle1 So I emailed Openweathermap for help and he said I should use the “One Call Api” https://openweathermap.org/api/one-call-api but I am having trouble figuring out how to incorporate the API call code into the weather forecast module?
-
@brendan_c23 said in Problems With Weather:
So I emailed Openweathermap for help and he said I should use the “One Call Api” https://openweathermap.org/api/one-call-api but I am having trouble figuring out how to incorporate the API call code into the weather forecast module?
Uhhh, I’m pretty sure the default weatherforecast module DOES use the One Call API.
I would try getting another api key using a different email. However, I suspect there might be something else going on there. Would you object to sending me your current openweather api key so I can test it here? If you agree, send it in a private chat message. I’ve sent you a chat. You can send your api key there if you agree.
-
weatherforecast: Your AppID does not support long term forecasts. Switching to fallback endpoint.
Totally not your fault, just so you know.
And I guess mine does not either, However, the module does load after a short delay but it only displays tomorrow’s weather. Same as when using my api key.
This is very odd as I tested your api key in another weather module that uses open weather and it is giving all the data and NO errors. SO, I’m guessing the weatheforecast module itself has some issues.
Are you dead set on using weatherforecast? There are many weather modules that provide you with forecasts and current weather. I’m fairly sure that some of them were built upon the openweather api and your current api key should work fine with them. Personally, I don’t use the default weather modules. I’ll be happy to give you a hand with them if you are willing to try them.
Edit:
I’ve just been informed that in the new MM release (April 1) both of those modules are being replaced by a newer version that does both current and forecast. Sheeesh
-
@mykle1 I see the edit but now I’m wondering if the issue you and Brendan are experiencing are related to this old bug that was fixed last year and maybe it came back? Or that code could be a workaround until the fix next month.