@tholbear Try running it again tomorrow. For some reason when I run it, it hangs for me. When I hard code the date it works fine. I would try and reinstall it and try again.

@frosty_snow cool…

@lavolp3 I did try, and the forum said “spam detected” and wouldn’t post it. I do appreciate the quick responses and the help

Ok, thanks. Got that sorted now 🙂
Hopefully this will help others with the same dilemma.
I had read a post referencing the use of file://
notation which, apparently, is a red-herring.

Just for clarity to others, a local compliments.json
file should be located in /pi/MagicMirror/modules/default/compliments/ directory and referenced using only the file name in the config file.

e.g. remoteFile: 'compliments.json'

@tippon that code is in a weird place… it is asking for the part of the url to be added based on the configuration…

and for some reason it just abandons the work and returns… with garbage…

showDescription is the way you should enable/disable this, but it seems there is a bug in the current version of mm, see https://github.com/MichMich/MagicMirror/issues/2517

@sdetweil Once again, you are a superstar. It’s working, thank you 🙂

I thought I’d tried that the other night, but for some reason it didn’t work. I don’t know if I typed it in wrong, or if I messed it up when I tried to do it remotely through my phone. Either way, it’s working now, and I’m a happy bunny 😃

@chrizzz said in MagicMirror² v2.15.0 is available don't work.:

I do have some strange things after the update.

At first, the new weather module is just “loading” without displaying content. Even after 30+ minutes. Is there something wrong with the config? I saw that there is a minor issue with the data request which will cause it to load for ~10min (or to reduce the update interval).

{ module: "weather", position: "top_right", classes: "always", config: { // See 'Configuration options' for more information. type: "current", locationID: "YYY", appid: "XXX" } },

I checked this again with switching back to the old module and the old module works. The forcasting takes 10min (as expected) but the module itself works. I thought this might be something with the connection to the API. Any ideas?

@sdetweil This worked for me after my MagicMirror refused to start. Thanks!

@sdetweil thanks for the suggestion, I’ve putted the line in my config and for now every thing looks fine

Have you tried to contact your internet provider? You may need to make some configuration adjustments manually. I am from Spain, Benidorm webcam. And this is how I solved a similar issue. They guided me in real-time through all the necessary steps. Now all works properly, but I would not have done it on my own. Please tell us later how you managed to sort everything out.

@snille - you’re spot on. MMM-ModuleScheduler uses the cron module. The ranges for cron values can be found in the npm module documentation.

I’ve added an issue in the GitHub repository to update the documentation for the module.

@sdetweil Working!

@sdetweil ok, I understand. Then I have to update it manualy in future. Thanks again for your help.