Dashboard

Watch out

• The banner "Active Clients" and the "Active clients" row of the Clients & Billing panel count the same accounts as the Active chip on the Clients page: status active and not expired (an account on the free package counts; pending, disabled, suspended and expired accounts do not). /api/system/info still returns the total of all accounts as clients, next to active_clients. The panel's "overdue" and "due ≤7d" alerts follow the same rule: an account on the free package is never overdue nor due, and "due ≤7d" counts the same accounts as the "Expiring in 7 days" chip on the Clients page (whole days on the server's calendar).
• The banner "Tuners Online" and the System Health "Tuners" row are both the enabled/total adapter count from the dvb_adapters table, not tuners that have signal lock. Open Monitor › System for real lock state.
• "Peak today" is not peak concurrency — it is COUNT(DISTINCT client_id) from watch_events since UTC midnight, i.e. how many distinct accounts started watching today.
• "Failed starts (1h)" counts any watch_events row shorter than 10 seconds in the last hour. Normal channel surfing inflates it; amber above 3, red above 10.
• Kicking is not a ban: the delivery loop re-checks that the connection row still exists about once a second and then stops sending, but a player that auto-reconnects simply opens a new session.
• Opening a page no longer cleans the connection table (2.9.402): a background job every 30 seconds archives a session into the viewing history and deletes it once nothing was heard from it for 3× the stale-connection window (at least 5 minutes), the same rule as the playback reaper, and purges watch_events older than 90 days (a fixed figure; the nightly housekeeping under Backup → Database maintenance applies its own rule, also 90 days by default). A held-up heartbeat during a long database write therefore never ends a live stream.
• "Check source signal" opens a fresh subscription to the channel. If it cannot open the stream or captures under 100 KB you get "Could not capture the source stream." — which on an all-tuners-busy box means the check failed, not that the source is bad.
• The Disk row's colour comes from the alert_disk_threshold setting (default 90%): red at or above it, amber from 10 points below it.
• The red "N pending account deletion(s)" banner above the KPIs jumps to Clients and selects the Pending Deletions tab; it is not dismissible from the Dashboard.
• The legend says "Hover a card for thresholds" but the KPI rows carry no tooltips — the thresholds are only in the dot colour.
• A "Live Events On Air" table appears above the streams table only while an event is broadcasting; when nothing is on air the panel renders empty rather than showing an idle state.
• Apps & stores (2.9.388): the card shows what the License server reports (read every hour): the version people get in each store: Google Play, the website download (/app, also how Fire TV gets the app: Amazon does not list it), the Apple App Store, LG, Samsung and Vidaa. Nothing is edited on the card: store lines and alerts are on the License server. A failed read keeps the last good one and says so. See Settings → Messages → "License server (app versions)".
• Recent Activity groups (2.9.376): a run of the same line one after another (the same event for the same account or stream, e.g. 11 × "Security: source observed — demo" within a few minutes) is one row "… ×11", with the time span under it ("14–17m ago") and the newest time on the right. Click the row or the ×11 (or Tab to it and press Enter or Space) to list its events, each with its time and detail (such as the IP); click again to close it. Only lines next to each other in time merge, so whatever happened in between still shows where it happened. The card shows 20 rows, a group counting as one; a group lists its newest 50 events, then "N more not listed". A single event looks as before, and the account name in a group is still the link to what that user watched.