Skip to content

Fortnite Stats v2.1.0 - Accurate Stats & Modernization

Latest
Latest

Choose a tag to compare

View all tags
@michaellunzer michaellunzer released this 07 Jul 07:37
v2.1.0
e3baccb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Fortnite Stats v2.1.0 — Accurate Stats & Modernization

This release fixes the long-standing "the numbers don't match" reports and modernizes the integration to current Home Assistant standards.

🩹 The big fix: stats now match fortnite-api.com / fortnitetracker.com

Previous versions had two problems that made the reported stats wrong:

  1. A mock-data fallback shipped by accident. On any API hiccup the integration silently served hardcoded placeholder stats (with random jitter), so you could be looking at fake numbers without knowing it. This is completely removed — the integration now reports real data or clearly shows itself as unavailable/needing attention.
  2. Per-mode sensors never populated. The individual platform/mode sensors were missing their value logic and always read unknown.
  3. Summed totals omitted Limited-Time Modes. The old aggregated sensors added up only Solo + Duo + Squad, which always read low versus your true lifetime totals.

What to use now: the new All Inputs / Overall sensors report the exact lifetime totals shown on fortnitetracker.com (verified: 674 eliminations from the API → 674 in Home Assistant, where the old summed approach showed 139).

Fixes #22, #23.

✨ What's new

  • All Inputs / Overall sensors (enabled by default) — the fortnitetracker-matching lifetime numbers, including LTM.
  • Per-input breakdowns for Console and PC are still available, now disabled by default — enable them from each entity's settings if you want them.
  • New stats: Deaths and Eliminations-per-Match, plus correct K/D computed from the API's real death counts.
  • Device grouping — all of a player's sensors now live under a single device.
  • Long-term statistics — counting sensors (eliminations, wins, matches, score, …) now feed Home Assistant's statistics engine, so you can graph them over time.
  • Re-authentication flow — if your API key expires, Home Assistant prompts you for a new one instead of silently failing.
  • Better setup validation — an invalid API key or misspelled username is now caught during setup instead of creating a broken entry.

🧰 Under the hood

  • Single API call per update via Home Assistant's shared HTTP session; proper UpdateFailed / re-auth handling.
  • Config entry runtime_data, full DataUpdateCoordinator pattern, typed and async throughout.
  • Added translations/en.json (required for the config UI and entity names).
  • Removed the accidentally-committed ha_test_aggregated/ duplicate tree and the empty services.yaml.

⚠️ Upgrade notes

  • Minimum Home Assistant version is now 2024.12.0.
  • Aggregated (summed) sensors are disabled by default and their entity IDs changed (now *_agg_*). If you used them on a dashboard, they may show as unavailable after upgrading — switch those cards to the All Inputs / Overall sensors, which are more accurate. You can re-enable the aggregated entities from Settings → Devices & Services → Entities if you still want them.
  • The individual per-mode sensors were non-functional before this release, so their entity IDs changing has no practical impact on existing setups.
  • No configuration changes are required — your existing API key and username carry over.

Closes / addresses

  • Fixes #22 — stats not matching fortnitetracker.com
  • Fixes #23 — comparison of API data to HA sensors
  • #16 — the old 'FortniteData' object has no attribute 'fplayer' crash was already resolved by the 2.0 rewrite (safe to close)
  • #15 — Trio stats: the API still does not expose trios; the new Overall sensor is the practical way to see combined stats

Full Changelog: v2.0.3...v2.1.0

Assets 2
Loading