Hallo @santicoia ,
herzlich willkommen in der Community und danke für dein Interesse an meinen Modulen.
In deiner config.js fehlt ein Komma nach showNoWarning:true

Wenn man das ergänzt, dann funktioniert es bei mir wunderbar :-)

Hier mal ein erster Entwurf: https://github.com/jalibu/MMM-NINA
An der Optik müssen wir noch Arbeiten ;-)

Bin hier für Vorschläge (Mockups, etc) offen.

@v0rtex @MajorC
Is there still a need for this?
I just stumbled upon the Nina API (i.e. https://warnung.bund.de/api31/dashboard/082210000000.json for Heidelberg)

It should be very easy to implement a client module for MagicMirror

@ph1tch @swvalenti
woops… 🙈😇
My stupid mistake. This happens when you didn’t pay attention in the Boolean algebra lecture 😁

Please pull the latest release.

Thank you for your feedback.

Hi everyone,
I released version 2.0.0 of this module today. It is written 100% from scratch.

Changes

• The module is now much more leightweight and should consume less computing resources.
• Removed GoogleMaps support because the maintenance effort for both maps was too high and the code looked very untidy as a result.
• Configuration was redefined. Old module configurations are not compatible!
• Much more flexible options to set markers and alternating map positions
• The onlyOnRain feature was fixed and is now compatible with the MM’s default weather module and MMM-OpenWeatherForecast

If you do not require GoogleMaps, I’d recommend to switch on version 2.x as version 1.x won’t be supported in the future.

@itsdonj
Please check your symbols. The “undefined” error comes when there are invalid symbols in your list

Hi,
I did some maintenance/refactorings on that module.
Version 2.0.0 is currently available as Feature Branch and much more lightweight.
I also removed GoogleMaps support because the maintenance effort for both maps was too high and the code looked very untidy as a result.

So far known settings like “onlyOnRain” are missing, because I developed the module from Scratch. As soon as I have first feedback if the module runs stable, I plan to transfer all features of the old version into the new one.

The configuration to version 1.x is completely incompatible and must be adapted.

Are there any volunteer users here to please look at version 2.0 and run it for 1-2 weeks for testing?

thx @sdetweil for explaining.
It‘s nothing but a bug. I will fix that as soon as I find the time for some maintenance on that module.

thank you @matefits71 for your ideas and feedback and thank you @Fozi for your excellent answer about the reasons for all of the current limitations.

I am also not very satisfied with this module and already tried to refactor it with the windy.com API. First results looked okay but I wasn‘t able to get it to a stable state that did not hang up after a few hours on the Raspi due to its high resource consumption.

I am very open for any kind of contribution or ideas here and still think about a second try on the windy refactoring.

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

@oneartur unfortunately no.
The module uses rainviewer.com API. The free plan only offers history data.

I started to play around with windy.com and had good results on my MacBook for development, but windy’s map rendering is so heavy weight, that it did not really work stable on the raspberry pi.

I also find it a pity, that MMM-RAIN-MAP does not provide a forcast. Let me know, if you find a free dataprovider to enhance that.