A Home Assistant custom integration for tracking gaming PC usage statistics per user. Monitor power consumption, session time, and electricity costs — with a full custom sidebar panel, historical graphs, push notifications, and more.
- Multi-User Tracking: Individual statistics per user, configurable via UI
- Live Session Monitoring: Real-time power (watt gauge), time, cost, and live kr/time tracking
- Cost Breakdown Views: Average kr/time per user (Statistik tab) and kr/kWh comparison over time (Historik tab) — see whether a costly day comes from more playtime or a pricier electricity rate
- Robust Price Handling: Falls back to the last known valid electricity price if the price sensor is temporarily unavailable, instead of silently counting that period as free — with an Admin tab health indicator showing fallback status
- Monthly Summaries: Automated monthly statistics per user
- Historical Graphs: Daily bar charts for the last 30 days per metric (time / energy / cost / kr-per-kWh)
- Leaderboard: Monthly ranking with 🥇🥈🥉 medals
- Push Notifications: Configurable rules with test and repeat support
- InfluxDB Integration: Long-term data storage for historical analysis
- Custom Sidebar Panel: Full-featured UI built directly into Home Assistant
- Dark/Light Theme: Automatically follows your HA theme
- Multi-Language Support: English and Danish translations included
| Metric | Unit | Description |
|---|---|---|
| Session Time | seconds | Active PC usage time for current session |
| Session Energy | kWh | Power consumption for current session |
| Session Cost | DKK | Electricity cost for current session |
| Monthly Time | seconds | Total usage time for current month |
| Monthly Energy | kWh | Total power consumption for current month |
| Monthly Cost | DKK | Total electricity cost for current month |
- Home Assistant: 2024.1 or newer
- InfluxDB: Running and accessible (v1.x)
- Required Sensors:
- User login sensor (returns current username as state)
- Power consumption sensor (PC wattage in W)
- Energy price sensor (DKK per kWh)
- (Optional) Device self-consumption sensor (only needed for plugs that expose it separately)
- Copy the
custom_components/pc_user_statistics/folder to your HA/config/custom_components/directory - Restart Home Assistant
- Go to Settings → Devices & Services → + Add Integration
- Search for PC User Statistics
- Enter your InfluxDB connection details
HACS submission pending
| Field | Example | Description |
|---|---|---|
| Host | a0d7b954-influxdb |
InfluxDB hostname or IP |
| Port | 8086 |
InfluxDB port |
| Database | homeassistant |
Database name |
| Username | homeassistant |
InfluxDB username |
| Password | •••••••• |
InfluxDB password |
The integration will verify the InfluxDB connection, confirm the database exists, load existing monthly data, and start tracking immediately.
After setup, open the 🔧 Konfiguration tab in the sidebar panel to:
- Edit all 4 sensor entity IDs without touching any files
- Add, edit, or remove user mappings (sensor state → user ID)
- Reorder sidebar tabs via drag-and-drop
Changes are saved instantly and trigger an automatic integration reload.
The integration adds a 🎮 PC Statistik entry to your HA sidebar with 6 tabs:
- Live session cards (tid, energi, pris)
- Donut-diagram med månedlig fordeling per bruger
- Månedlige totalkort per bruger
- 🏆 Leaderboard med guld/sølv/bronze ranking
- Aktiv bruger med LIVE-badge
- Oversigt over alle konfigurerede brugere og sensor-mappings
- Konfigurer modtagerenheder (HA Companion app)
- 4 premade regler klar til brug:
- ⏱️ Pausepåmindelse — gentages hvert 60 min
- 🌙 Lang session — advarsel efter 3 timer
- 💰 Prisgrænse — notifikation ved 10 kr
- 🌅 PC glemt tændt — gentages hvert 30 min ved inaktivitet
- Opret egne regler med valgfri trigger, besked og repeat-interval
- Test-knap sender øjeblikkelig push
- SVG søjlediagram — daglige totaler de seneste 30 dage
- Skift mellem Tid / Energi / Pris
- 7-dages tabel med mini-søjler per bruger
- Rediger sensor entity IDs
- Administrer bruger-mappings
- Omarranger tabs via drag-and-drop
- System-info og version
- InfluxDB write buffer status
- Bruger-mappings oversigt
The integration requires a smart plug with power monitoring. The plug's watt sensor is read every 60 seconds to track energy consumption and cost.
| Hardware version | 1.0 |
| Firmware version | 1.2.6 |
| HA integration | TP-Link Smart Home (built-in) |
| Local control | Yes — no cloud account required |
| HA polling | Every 5 seconds |
The HS110 exposes a current_consumption sensor (W) that is used directly for watt tracking. It does not expose a separate device self-consumption sensor — the "Plug self-power" field in the configuration should be left empty when using HS110.
⚠️ Do not update HS110 firmware. Firmware version 1.1.0 on certain hardware revisions broke local Home Assistant access. Version 1.2.6 on HW 1.0 is stable.
Entity IDs created by HS110 (example device name gamer_pc_power_monitor):
| Sensor | Entity ID | Unit |
|---|---|---|
| Current power | sensor.gamer_pc_power_monitor_current_consumption |
W |
| Total energy | sensor.gamer_pc_power_monitor_total_consumption |
kWh |
Any smart plug that exposes a watt (W) sensor in Home Assistant will work. The "Plug self-power" field is optional and only relevant for plugs that report their own power draw separately (e.g. Shelly Plug S/Plus).
HASS.Agent runs on the Windows gaming PC and reports the currently logged-in Windows username as a HA sensor state.
| Platform | Windows only |
| Sensor type | Logged In Users / Windows User |
| State example | Konge, Lukas, Sebas |
| Entity example | sensor.flemming_gamer_satellite_loggeduser |
The sensor state is matched to a user ID via the mappings configured in the 🔧 Konfiguration tab.
Any sensor returning a float value in DKK per kWh is supported. For Danish users, Energi Data Service (available via HACS) provides real-time spot prices including tariffs.
sensor.statistics_hub_current_usersensor.statistics_hub_current_session_timesensor.statistics_hub_current_session_energysensor.statistics_hub_current_session_cost
sensor.statistics_flemming_monthly_timesensor.statistics_flemming_monthly_energysensor.statistics_flemming_monthly_cost
(Same pattern for each configured user)
Measurement: pc_usage
Write frequency: Every 60 seconds (when user is active)
| Field | Type | Description |
|---|---|---|
power |
float | Current power in watts |
time_delta |
float | Seconds since last write |
energy_delta |
float | kWh since last write |
cost_delta |
float | DKK since last write |
Tags: user (string)
-- Total energy per user this month
SELECT SUM("energy_delta") AS "total_energy"
FROM "pc_usage"
WHERE time >= now() - 30d
GROUP BY "user"The integration uses a DataUpdateCoordinator with a 60-second polling interval.
| Event | What happens |
|---|---|
| State change (user/power sensor) | async_track_state_change_event triggers immediately |
| Every 60 seconds | Coordinator polls, calculates deltas, writes to InfluxDB |
| HA startup | Monthly totals loaded from InfluxDB with exponential backoff (30s / 60s / 120s) |
| InfluxDB write failure | Point buffered (FIFO, max 100) and retried next poll |
| 5+ consecutive failures | RepairIssue raised in HA UI — visible under Settings → Repairs |
Deltas (time, energy, cost) are only written to InfluxDB when a user is actively logged in and the power sensor reports a positive value.
If the configured electricity price sensor becomes temporarily unavailable or unknown (common with forecast-based price sensors around midnight rollovers or brief integration reloads), the integration no longer treats that period as free electricity. Instead, it falls back to the last known valid price:
| Situation | Behavior |
|---|---|
| Price sensor reports normally | Used directly, cached as "last known valid price" |
| Price sensor unavailable/unknown/unparsable | Falls back to the last known valid price instead of 0.0 DKK/kWh |
| No valid price has ever been read (e.g. right after HA startup) | Falls back to 0.0 DKK/kWh until the sensor reports |
Fallback usage is counted per month and visible as a health metric ("Prissensor") on the ⚙️ Admin tab, and a rate-limited warning (at most once per 5 minutes) is logged so a prolonged sensor outage is discoverable instead of silent. The fallback cache also survives a Home Assistant restart (persisted in the session snapshot, discarded if older than 6 hours).
Every coordinator restart (a full Home Assistant restart, or an integration reload triggered by any configuration save) re-fetches the current month's totals from InfluxDB via a SUM() query. If InfluxDB happened to be missing recent writes at that exact moment — for example because they were still sitting in the write-retry buffer during an outage — the fresh sum could come back lower than what had already been tracked and displayed, silently erasing real time/energy/cost from view.
The integration now protects against this with a persisted baseline: monthly totals are saved to the config store every 60 seconds, after every successful InfluxDB load, and on shutdown. On the next load, InfluxDB's sum is only ever allowed to raise the total, never lower it — and if InfluxDB is completely unreachable after 3 retries, the integration falls back to the last known baseline instead of resetting to 0. The baseline is correctly cleared at the start of a new month.
If you notice monthly totals that seem lower than expected, check the 📈 Historik tab's daily breakdown against another independent source (e.g. Microsoft Family Safety screen time, if configured) — the ⚙️ Admin tab's "Manuel korrektion" form can be used to add a one-off correction for a specific date if a gap is confirmed.
Alongside the monthly tracker, the integration also maintains a daily ("today") total per user — a full parallel to the monthly tracker with the same InfluxDB-load, baseline-floor protection, and periodic persistence. This powers a fair "today vs. today" comparison against Microsoft Family Safety's screen time on the 📊 Statistik tab (previously this compared MS's daily figure against the PC's whole-month total by mistake).
Both the monthly and daily rollover, and the InfluxDB query windows behind them, are computed in Europe/Copenhagen local time rather than UTC — using UTC directly would shift the rollover moment by up to 2 hours during CEST (summer time).
- InfluxDB v1.x only — InfluxDB v2.x / v3.x is not supported
- Single PC — one integration instance tracks one PC; multi-PC requires multiple config entries (planned for v3.0.0)
- DKK currency — electricity cost is calculated in Danish Krone (DKK); other currencies require a matching energy price sensor
- No historical import — data tracking starts from the moment the integration is installed; existing InfluxDB data from other sources is not imported
- HA Companion app required for push notifications — standard HA notify services are not supported in the notification UI
Check that all required sensors exist and are working. Verify entity IDs in the 🔧 Konfiguration panel tab, or check HA logs filtered by pc_user_statistics.
Verify InfluxDB is running and accessible. Check that the pc_usage measurement exists. Reload the integration: Settings → Devices & Services → PC User Statistics → ⋮ → Reload
- Install the Home Assistant Companion app on your phone
- Open the 🔔 Notifikationer tab and select your device
- Enable at least one rule and use the 📨 Test button to verify
Expected when PC is idle — the integration clamps negative values to 0.
Restart Home Assistant fully (not just reload). If the panel JS file was updated, clear your browser cache.
pc-user-statistics-tablet-card (v2.6.12+) auto-detects a narrow host width (<700px) and switches from its two-column tablet layout to a single stacked column. If you're on an older cards.js version, either update to 2.6.12+, or use pc-user-statistics-user-card (one card per user) on mobile dashboards instead — it's designed for narrow widths from the start.
- Backup any automations/dashboards using old entity IDs
- Delete old integration (Settings → Devices & Services → Spille PC Statistik → Delete)
- Install new integration and configure with your InfluxDB details
- Update entity ID references (see CHANGELOG.md)
Your historical data in InfluxDB is not affected.
MIT License — see LICENSE for details.
- Home Assistant community for integration guidelines
- InfluxDB for time-series data storage
- Issues: GitHub Issues
- Discussions: GitHub Discussions
Made with ❤️ for the Home Assistant community