MMM-MyScoreboard

[j.e.f.f]

@P-Bo726 Still thinking about the right way to do it. It needs a complete rearchitecture in order to make it happen. And If I’m going to do that, then I also want to rearchitect how I handle the data providers… Instead of a one-to-one relationship between sport and feed, I’d like to be able to take advantage of feeds that can provide multiple sports – e.g.: Using just the ESPN and Sportsnet scoreboard feeds can provide the data for all of the sports I currently support, plus a few more that I haven’t yet integrated. Even better is that Sportsnet gives me all sports it supports at once… so it significantly cuts down on the data pulls.

So it’s a long way of saying yes it’s in in the plan, but it won’t happen overnight.

[nevint]

@j.e.f.f Looking forward to it! I still haven’t got the API key approved, it seems they are ignoring the requests these days.

[j.e.f.f]

@nevint @P-Bo726 Just to give you an update, I have a branch with multiple instances working. Still needs quite a bit of testing, but here’s a sneak peek:

This is three instances of the module running simultaneously, and taking advantage of using feeds that supply scores for multiple sports, including CFL without the API key.

[P-Bo726]

Fantastic. Looks great!

[nevint]

@j.e.f.f Any luck with the CFL testing?

[j.e.f.f]

@nevint going well. I’m going to release it with V2 of the module, which also adds support for multiple instances and takes advantage of using providers for multiple sports. Plus a few new display goodies! I need a few more days of testing, as I’m ironing out some issues with the NBA feed. But otherwise it’s just about ready for release.

[nevint]

@j.e.f.f Awesome!! Thanks for all the hard work!

[j.e.f.f]

I’m excited to announce Version 2.0 of MMM-MyScoreboard! See the top of this thread for all of the new features, or just jump in and get the update.

When updating, be sure to run git pull in the MMM-MyScoreboard directory to get the latest source code, the run npm install to install the new dependencies. Optionally run npm prune to remove old dependencies that are no longer required.

Also note that some of the team short codes have changed, so be sure to check you config against the list of short codes in the README if your team is not showing up.

[P-Bo726]

Thank you for all the hard work.

[emlowe]

Getting some errors using the default config

I’m running node serveronly and I updated to MM 2.1.3

SyntaxError: Unexpected token function
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:542:28)
at Object.Module._extensions…js (module.js:579:10)
at Module.load (/home/elowe/MagicMirror/modules/MMM-MyScoreboard/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Class.loadModuleDefaultConfig (/home/elowe/MagicMirror/modules/MMM-Remote-Control/node_helper.js:254:17)
at /home/elowe/MagicMirror/modules/MMM-Remote-Control/node_helper.js:211:10
at FSReqWrap.oncomplete (fs.js:123:15)

And then :

TypeError: Cannot read property ‘indexOf’ of undefined
at /home/elowe/MagicMirror/modules/MMM-MyScoreboard/providers/ESPN.js:98:34
at Array.filter (native)
at Object.formatScores (/home/elowe/MagicMirror/modules/MMM-MyScoreboard/providers/ESPN.js:97:39)
at /home/elowe/MagicMirror/modules/MMM-MyScoreboard/providers/ESPN.js:75:27
at /home/elowe/MagicMirror/modules/MMM-MyScoreboard/node_modules/json-parse-async/index.js:20:14
at _combinedTickCallback (internal/process/next_tick.js:73:7)
at process._tickCallback (internal/process/next_tick.js:104:9)