@assassins Also with this module the request dependency is missing and needs to be installed manually.

cd ~/MagicMirror/modules/MMM-DynamicWeather
npm init -y
npm install request --save

This should solve it.

@mmrize Thanks a lot for your response!
After reading through my emails this morning, I deeply regret that you had to hand over ownership and maintenance of your modules. Apparently, your regrets are partially deeper than mine, when you see what happened to your babies.

Last night, after @swvalenti pointed me to the new owner’s forum, I opened there an issue and requested support. A very nice guy tried to help me late at night, but in the end the owner himself closed and locked publicly my issue in an unexpected, rude and passively aggressive manor (see last comment in thread), of course without solving the issue.

So, I solved quickly the issue by myself by kicking out the module from my config, as well as any other module maintained by the new owner. I am sorry, that it unfortunately hit your module, cause I liked it and I had it installed from the very beginning.

Anyways, live goes on :sun_with_face:

@swvalenti Thanks a lot for the link! I’m just wondering why someone sets up a separate forum for a bunch of modules where you need a further login to get support…My professor in maths said once „there are things you have to believe, you can’t understand them“…a wise man.

Hi,
i recently updated from 2.16.0 to 2.17.1 and MMM-Tools stopped being displayed on my mirror. All other modules are beeing displayed.

These are the errors I found in the log:

0|MagicMirror  | [04.10.2021 09:07.15.554] [ERROR] 
0|MagicMirror  | (node:13630) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE] [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received type number (1)
0|MagicMirror  |     at Object.writeFile (fs.js:1436:5)
0|MagicMirror  |     at /home/pi/MagicMirror/modules/MMM-Tools/node_helper.js:308:29
0|MagicMirror  |     at new Promise (<anonymous>:null:null)
0|MagicMirror  |     at Class.getRecordUptime (/home/pi/MagicMirror/modules/MMM-Tools/node_helper.js:295:12)
0|MagicMirror  |     at Class.startScan (/home/pi/MagicMirror/modules/MMM-Tools/node_helper.js:50:54)
0|MagicMirror  |     at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-Tools/node_helper.js:45:12)
0|MagicMirror  |     at Socket.<anonymous> (/home/pi/MagicMirror/js/node_helper.js:109:11)
0|MagicMirror  |     at Socket.emit (events.js:315:20)
0|MagicMirror  |     at Socket.emitUntyped (/home/pi/MagicMirror/node_modules/socket.io/dist/typed-events.js:69:22)
0|MagicMirror  |     at /home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:428:39
0|MagicMirror  |     at processTicksAndRejections (internal/process/task_queues.js:75:11)
0|MagicMirror  | (Use `electron --trace-warnings ...` to show where the warning was created)
0|MagicMirror  | [04.10.2021 09:07.15.557] [ERROR] (node:13630) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
0|MagicMirror  | [04.10.2021 09:07.15.562] [ERROR] 
0|MagicMirror  | (node:13630) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

On the author’s github (Bogsunet) there is no option to submit an issue. Can anyone help me further?
Thanks in advance!

@earnestrichards here you find RSS feeds of the two major French newspapers.
Le Monde
https://www.lemonde.fr/actualite-medias/article/2019/08/12/les-flux-rss-du-monde-fr_5498778_3236.html

Le Figaro
https://www.lefigaro.fr/rss

Just choose the feed you’re interested in and add it to the config of newsreader module.

@lkthomas you could setup a crontab to execute the removal of a specific module. But you’ll still have to remove it manually from config.js. What’s your specific use case for that? Just to understand your requirements.

@majorc Besten Dank! Das fiel mir auch kurz nach meinem letzt Post auch ein (hätte ich auch eher drauf kommen können). Die Meldung selbst hbe ich so gelassen und stattdessen das property noWarningText: im MMM-DWD-Warnweather angepasst. Jetzt muss ich nur noch das Häkchen loswerden ☺

@Jalibu Awsome, thanks for the quick fix!
As far as I can see the forecast for 30 min. works fine. At the moment I can’t discover any issues. I dunno how you found a way to pull those forecasts, but thanks for your effort!

Same here. This behaviour started about 2 weeks ago. Some times the feeds cycle as expected, but then all of a sudden they rush through.

@jalibu Thanks for the update, man! You rock!
I installed the update, but unfortunatelly no map is displayed at all. No matter if displayOnlyOnRain: is set true or false.
I opened an issue an github https://github.com/jalibu/MMM-RAIN-MAP/issues/12

@jalibu Klar, ist schon erledigt.

@ph1tch I’d assume that MMM-ModuleScheduler is the culprit…I have MMM-RemoteControl, too, and it causes no issues.
Curious to see if it works.

@jalibu Ich habe das Modul mal am Wochenende installiert und es funktioniert. D.h., wenn ich eine Warnung auf mein Handy bekomme, sehe ich sie auch im Modul.
Vorschlag:

• Wenn keine Warnungen anliegen, sollte lediglich “Keine Warnungen” als Nachricht erscheinen in #666 statt grün und ohne Haken davor. Das würde besser zu MMM-DWDWarweather Modul passen ☺.
• In der config würde ich noch die header: option angeben, die man sich nach Wunsch benennen kann. Ausserdem hat man dann auch eine schöne Headline über dem Modul.

@ph1tch Let me guess…you’re using MMM-pages, too? Then that might be the problem.
I filed an issue for that on the weekend and @Jalibu provided a fix a few hours ago. I tested it and it works now as expected. Try the fix and see if it solves your issue, too.

@jalibu Thanks for the update of the module! It works great! Also the displayOnlyOnRain option works now correctly. (just pulled the latest commit).

@tikkisean Great build and welcome to the club!

By now, unfortunately this module is still the best of its kind :-/

Word! (…and strike „unfortunately“…)

@matefits71 said in MMM-RAIN-MAP:

Basically the forecast are 2h old, it means it’s showing what happen and not what will happen,

Well, MMM-RAIN_MAP is based on the FREE Rainviewer API, which allows the use the radar data of the past.

How do you put the forecast to update for the next 2h?

Forecast is a central feature of RainViewers business model. The forecast function of RainViewer requires for the iOS-app (certainly for the Android app, too) a paid subscription. Thus, I strongly doubt, that someone can use a paid function for free via their API. If I read their basic API information correctly, you don’t even get as a patron or gold member of the paid API, the forecast calculations.

Also, is there any chance to add more fluidity (or fps) to the animation? For exemple the app raintoday (ios) does this perfectly. I’m not sure if we can get there API.

The API provides a radar snap shot every 10 minutes- Thus, you’ll meed to interpolate the precipitation images (intensity, direction, accuracy, etc.) which is not a trivial task and needs -depending on the used method and number of interpolations- quite some computational resources. which might not be available on an RPi.

@sdetweil True, that is far easier. Unfortunately I didn’t succeed in getting MMM-Config to work properly. Maybe I‘ll give it a 3rd try during my vacation.

@bdream I strongly guess that one of the 3rd party modules is not compatible vith MM2.16.0. I had the same issues with MMM-MyCalendar, which caused a black screen after starting MM. My approach is to disable all 3rd party modules by adding the line

disabled: true;

for each module and enable it one after the other by setting it to

disabled: false;

Taht might discover quicker, which module is the culprit instead of poking in logs (that is my personal approach!).

When you found the module, that causes issues, contact the developer on github, or look for an alternative fork which seems to be maintained.

Regarding the above mentioned MMM-MyCalendar module, I reverted to the default calendar module, which works just fine and delivers the same features.