Read the statement by Michael Teeuw here.
NHL Module
-
@yawns thanks will give it a whirl tonight
-
@strawberry-3.141 turns out ESPN killed off their public API keys and I’m having a hard time finding a free nba API. Any chance you know where to find one?
-
I just installed this and all i get is “LOADING…”
-
This post is deleted! -
…I am having a bit of a problem…would you mind helping me…I knew I should have left this alone… I did what you said, but I am getting the following when I run magicmirror
please help…I have just under a week till my brother’s birthday and this is my big surprise for him… If you need any more pictures of anything to diagnose let me know
-
@Officeglen after my lectures today, I could help to debug this via teamviewer and fix it in time for your brothers birthday
@bbry do you get any errors in the terminal or electron console?
-
@Officeglen I made a possible fix for the error we couldn’t reproduce. I’m assuming that this was due to an unexpected/unhandled behaviour of the api.
@chieftainSupreme I was looking for a free api a couple of weeks ago, but couldn’t find one.
-
@strawberry-3.141 I got it working now. I removed the module from config.js, npm install(already was installed) in ~/MagicMirror/modules/MMM-NHL, then added the module.
-
@Officeglen Mine also does this. I’ve found that (at least in my case) its related to my internet connectivity. If I have MM loading up multiple modules that require the internet to update, while running my PC, tablet, cell phone, ps4 etc, that I get the infinite loading message. Can’t say its the same issue for yours, but Id guess that the module is loaded last, and times out therefore getting stuck on the ‘loading’ part. It hasn’t happened to me in quite some time, but my solution was to turn off a few devices, and to start the MM during off hours of NHL games. Now if I leave my MM on the module works just fine with updating scores and such
-
@SexyTrogg when your failure is related to the internet connection, then loading shouldn’t be there forever, but should stop on the next reloadinterval, which is 30 minutes by default
