Proposal: tennis (ATP/WTA) support via a new provider

[bensynapse]

Disclosure up front: I run the Live Tennis API, so this is vendor-authored — judge accordingly. We also ship our own dedicated MagicMirror module (MMM-LiveTennis); contributing tennis to MMM-MyScoreboard reaches users who want one unified scoreboard rather than a second module, so there's no conflict from our side — just saying it openly.

Proposal: add tennis (ATP/WTA) as a league. There are currently no racquet sports, and your providers/ layer looks built for exactly this: a new providers/LiveTennisAPI.js implementing the same getScores(payload, gameDate, callback) contract as CPL.js/PWHL.js (own POLL_FREQUENCY, startDataPoll, normalize to the module's game object), registered beside the others in node_helper.js, plus a 'TENNIS' (or 'ATP'/'WTA') entry in the league map in MMM-MyScoreboard.js.

Two design questions I'd want your steer on before building:

1. Config shape. Tennis is player-centric, not team-centric. Cleanest fit seems to be reusing the existing teams array as player surnames (teams: ["Alcaraz", "Gauff"]) so no schema change is needed — or a players alias if you prefer explicitness.
2. Rendering. Tennis scores are per-set (6-4 3-6 2-1* plus current-game points and a serving indicator). Options: map completed sets won into the existing home/away score slots (zero renderer changes), or a small tennis-aware score string. I'd start with the zero-renderer-change version.

Honest API note: the free keyed tier is 30 req/min / 100 req/day — fine for development and for a mirror polling every ~15 min, but a CPL-style 60 s poll all day exceeds it; sustained fast polling needs a paid tier. The README entry would state that plainly next to the key-signup link, like your other provider caveats.

If you're open to it I'll build the provider + docs as a PR against your repo, matching your eslint config and provider conventions. Free-tier signup for testing: https://livetennisapi.com/subscribe/free

[dathbe]

I'm open to it. I don't follow any raquet sports, so I don't know how much this would require rebuilding the box score DIV. Others have recently made some pretty drastic changes to the MLB box score visuals, so I know it can be done sport-by-sport. As long as it doesn't affect users of the other sports (or improves their experience), I'm happy to add any additional features. And I'm happy to disclose API limits in the README. 100/day is better than 0/day, and maybe this steers you some business.

If you want, open a PR. If you have questions along the way, let me know. Please PR against the development branch as I'll merge there first for testing.

[bensynapse]

Totally reasonable concern — here's how it stays contained.

Nothing changes for existing sports. Tennis would come in as a new provider behind the same per-sport switch everything else uses, so MLB/NFL/NHL/etc. render exactly as they do today. If a user doesn't add a tennis league to their sports config, not a line of tennis code runs for them.

The box score is the only real design question, and it can be tiny. Tennis isn't a single number — a match is a set score plus the current game, and (live) who's serving. Two ways to land it:

1. Minimal, no DIV rebuild (my recommendation for v1): reuse the existing score cell and show a compact one-liner — e.g. Alcaraz 2 Sinner 1 for sets, with the live game underneath (6-4 4-5 •Alcaraz where the dot marks server). This slots into the current layout the same way a soccer score does; no changes to the shared box-score DIV, so zero risk to other sports.
2. Richer tennis box (later, opt-in): a set-by-set grid like a TV scoreboard. This one would touch a tennis-only DIV, but it'd be gated to tennis and never rendered for other sports — the same pattern whoever reworked the MLB visuals used.

I'd start with (1), get it correct and non-disruptive, and leave (2) as a follow-up if people want it.

On the data: I maintain the Live Tennis API (disclosing up front — judge it on the merits), which is a live-tennis match-state feed: live scores, sets/games/points, current server, and completion/retirement/walkover status across ATP/WTA/Challenger/ITF. There's a free tier — 30 req/min, 100 req/day, no card (key at https://livetennisapi.com/subscribe/free) — which is plenty for a MagicMirror polling a handful of matches. It's a data source only, not tied to anything else.

If the minimal approach sounds right, I'm happy to open a PR wiring tennis in as a new provider with the compact score cell, so you can see exactly how contained it is before deciding on anything fancier. No worries at all if you'd rather not add a sport you don't follow — just say the word.