Read the statement by Michael Teeuw here.
MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast
-
@chris1971 so looking at MMM-GoogleMapsTraffic , it uses very old stuff (5 years) in its dev dependencies section of package.json
sadly there is no way to get rid of the error messages without a tiny change
when u install a module using npm you can ‘omit’ installing the development stuff… BUT, it STILL goes thru all the WORK to check them out (I don’t know why this is stupid)
anyhow, the ONLY fix is to trick the installer to not FIND any dev dependencies…
edit package.json
and change this
"devDependencies": {
to this
"devDependencies1": {
notice I added the ‘1’ at the end… when npm install runs it will look for “devDependencies”
and not find it… and skip all the junk (You are not going to be developing on the module anyhow…so no loss and the stuff eliminated is formatting tools anyhow)now, that said,
I installed the module
copied the default config entry from the readme
fixed the text typo (missing trailing comma)
added my apikey from google dev console andworked like a champ…
i did this on two separate systems
my linux desktop
and a pi4 w 7in screen
-
@chris1971 you can also use Winscp or bitvise ssh clients
these give you an ssh terminal AND a file browser over the PI files…just click and double click,
I use notepad++ on my windows system to edit the config and css files.
and the ssh terminal to install mm and modules (where to run commands)
and start/restart via pm2 or npm start -
@sdetweil Thanks for this outstanding support!!!
I learned o lot - I have installed the MM some years ago and was a little bit concerned if I can do this again…Now the best: The MM is running with Openweather and Goggle Maps - I tried several times install/ deinstall and found your modified script for Maps - maybe this was a solution at the end. I still see some errors in the strting script - but MM is running now with the weather module after shutdown the Darksky service - this was the only reason for me to change the system again…
Thanks again!!!
-
@chris1971 glad you got it running
-
Hello there!
Unfortunatly It’s arrived the moment: “… on March 31st, 2023 the Dark Sky API will no longer be available.”, as recalled by the Dark Sky Team in this post: Infos from the Dark Sky TeamIn fact today morning MMM-DarkSkyForecast stopped working!
I tried to install its replacement MMM-OpenWeatherForecast, but it didn’t work!
On terminal i hve this error:[MMM-OpenWeatherForecast] 2-Apr-23 17:23 ** ERROR ** Error: Request failed with status code 401
I have already try to regen the API key on OpenWeatherMap site but the problem persist.
I’m using MagicMirror: v2.22.0
For now i’m using the simple configuration:
{ module: "MMM-OpenWeatherForecast", position: "top_left", header: "Forecast", config: { apikey: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", //only string here latitude: 45.072870, //number works here longitude: 7.558791 //so does a string } },
Has anyone had this problem before?
Can you help me?Thanks.
-
@Egnos see https://github.com/jclarke0000/MMM-OpenWeatherForecast/issues/23
new openweather api version is 3.0, code is hard coded to 2.5
-
Hi @sdetweil thanks for answering me!
I had read this post but I didn’t understand what I have to do.
I have to update the node_helper.js version 2.5 to 3.0?Can you help me?
Thanks.
-
@Egnos yes,
just edit the file and change 2.5 to 3.0
-
@sdetweil said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:
edit the file an
In the file “node_helper.js” I have modify:
this https://api.openweathermap.org/data/2.5/onecall?
with this https://api.openweathermap.org/data/3.0/onecall?but I have the same error:
[02.04.2023 17:58.05.910] [LOG] [MMM-OpenWeatherForecast] 2-Apr-23 17:58 ** ERROR ** Error: Request failed with status code 401
Where am I doing wrong?
-
@Egnos i’ve seen a number of these…
something to do with registering correctly with version 3 onecall
someone else said
I used the API keys from the website as the one sent in my email did not work.