Sensors now include an attribute that stores the associated gamertag for an active or recently-active platform. So, now a dashboard can display “Name (Gamertag)”, if desired.
New Feature
Added gamertag attribute to sensors for PSN, XBL, Steam, and Discord. On the master sensor, it shows the gamertag for the current or most-recently-played platform. Upgrade to Gaming Status Cards v4.2.6+ for easy display options.
Bug Fixes
Fixed an issue where a player profile name could potentially prevent the PC and Master sensors from detecting statuses properly if it contained multiple special characters in a row.
Adjusted device deletion so that it won’t sometimes leave orphaned devices behind after deleting a player profile.
I just updated to Home Assistant 2026.8.3. It does NOT yet include the necessary fixes for Steam for players who do not have fully configured Steam profiles. Removing affected friends from my list DOES work to restore functionality, although I am not yet sure if the re-authentication issues have been fixed which were previously causing me to need to re-enter my Steam API Key nearly every day.
Please note that if an underlying integration is not functioning properly (Steam, Xbox, PlayStation), then Gaming Status will be impacted until a bug fix is issued for the official integration. I unfortunately have no control over that.
Added a safety limit so a custom “Title Cleanups” text pattern you write can’t accidentally freeze the integration if it’s a poorly-formed pattern.
Stopped a few frequently-changing sensor values (including the new gamertag fields) from being written to Home Assistant’s history database on every update, cutting down unnecessary database growth.
Fixed a small memory leak where entries for games that were never found on SteamGridDB could pile up forever instead of being cleaned out.
Fixed a bigger memory leak where renaming a player or changing which account feeds a platform would leave the old, no-longer-used sensor data sitting in memory forever instead of being cleared out.
Made the Discord bot only pay attention to the players you’ve actually configured, instead of processing every single member of your Discord server every time it reconnects.
Cleaned up some redundant lookups in the PC status sensor and the Discord tracking logic so they don’t fetch the same information multiple times per update.
Removed a duplicate piece of text-cleanup code in favor of reusing the existing one.
Made sure a Steam connection error can no longer accidentally leak your API key into the logs.
Locked down notifications so they can only ever be sent through Home Assistant’s notification services, not any arbitrary service.
For now, I am slowing production on this integration (and the companion cards) since I am out of new feature ideas or improvements to existing ones. I have looked into integrating Nintendo game status, but I’ve not yet found a viable solution for that. If anyone has anything else they’d like to see added or changed, please let me know! You can post it here or submit it as an issue.
With nearly 3,000 views on this post, I hope at least a few people are actively using this integration now, but I have no way to track the installation numbers. I only know of maybe 4 or 5 people so far, but I love to think it’s in the 100’s anyhow since that’s better for my ego.
I will still actively maintain this integration and squash any bugs that surface, but I can’t think of much else that is feasible to add to it without adding bloat. I’m sure 5 minutes after I post this, I’ll think of something. If you don’t see any new releases or posts for a while, just know that I haven’t forgotten about it but rather it’s working fine for me and I don’t have anything to add or fix!
I just updated to Home Assistant 2026.9.0, and it seems as if the Steam integration issues related to unconfigured profiles may now be resolved. Hopefully the fix for the issue of continually needing to re-enter the API Key was also included.
It seems as if the Steam issue I was having with having to re-enter my Steam API key nearly every day may have been caused by my integration sending too many API requests when it would refresh the game library. This version (hopefully) fixes that.
Improvement
Added a per-cycle library scan limit to Steam to help prevent flooding the API when a user is tracking a lot of Steam players and/or has a very large library. If you were finding that you had to periodically re-authenticate Steam, this will hopefully fix that issue.
Update: The fix seems to be working for me so far. The only downside is that a large library now may take a few days to fully refresh. Recently-played games will still update live, so this shouldn’t be too big of a disadvantage.
I assume most everyone who is using this integration is also using Gaming Status Cards as well (available on HACS). I have recently added some screenshots to the README for some of the newer card options. I am including them below in case you haven’t seen them yet. As always, if you have any great ideas for new options, please let me know!
Note: Some of the times indicated in this screenshot are not correct since I haven’t allowed it to cycle full a full week yet. This is shown only to represent the new formatting options.
Improvements
Reformatted weekly report and added an option to show hours for the top 1-5 games for each player.
Added first-run backfill for weekly report to fill in missing data (first week will not be 100% acurate).
Added a button to the Gaming Status Hub device for manually sending a weekly report (good for testing).
Moved Notification Artwork to its own sub-menu.
Added per-player achievement/trophy and library scan toggles instead of a global-only setting.
Adjusted the Steam scan-budget divisor to only count players who are actually opted into library scanning. This should improve library scanning speed overall.
Bug Fixes
Adjusted weekly breakdowns to be true Sunday - Saturday weeks, as intended, instead of Monday - Sunday.