Applies to: Tvheadend rolling official documentation read 2026-11-08; many examples are from 4.3-era builds; verify availability against installed build; no tuner or server tested; status API requires ADMIN; available fields vary by input and build
The useful distinctions
- The status functions require administrator privilege.
- Connections, subscriptions and inputs describe different active-state objects.
- For documented DVB inputs, signal and SNR may only be populated while the device is active.
- Not every input provides every statistic.
Capture during the reported action
An idle server is a different observation from a server handling the request that caused concern. Begin the authorized viewing or recording action, then collect the status snapshot while it is active. Write the action beside the snapshot. This gives a later reader enough context to understand whether an input was expected to be in use at the time of measurement.
Keep object types distinct
A connected client does not necessarily identify the particular media subscription you are investigating. Likewise, a populated input record does not alone tell the whole client-side story. Correlate the relevant objects and preserve their relationship in your private notes. The synthetic request list asks for these views without copying real account names, peer addresses or persistent device identifiers into an example.
Respect unavailable values
A missing or zero reading needs its active-state context and scale information before interpretation. Do not turn an idle device’s absent measurement into a numerical diagnosis of reception quality. This workflow collects application evidence; it does not certify hardware performance or establish a universal threshold. If a statistic is not supplied by a particular input, report that absence honestly and use the other available observations to frame the next investigation.
A focused way to proceed
- Prepare one authorized request and note its start.
- During that request, obtain the read-only connections, subscriptions and inputs snapshots.
- Match the active objects before interpreting their statistics.
- Retain the snapshot context and compare a second observation only under the same conditions.
Worked example · synthetic
Administrator read-only snapshot during one authorized action:
GET https://example.test/api/status/connections
GET https://example.test/api/status/subscriptions
GET https://example.test/api/status/inputs
Context note: action, active interval and relevant object relationshipRead the comparison
An unavailable idle-input statistic is not an active measurement of signal quality.
When to stop or ask for help
Provide the reviewed snapshot and action context to the server administrator; preserve unknown fields as unknown.