Local telemetry

Starlink local telemetry, explained for Mac users.

StarBar is built around local-network-first Starlink telemetry. That means it can be useful without asking for your Starlink account password, but it also means some fields depend on what your hardware exposes locally.

StarBar network screen showing local Starlink router and client telemetry on macOS
Router Reachable local network
Terminal Mini hardware context
Client Mac local device
Partial -- unexposed field

What to check, what it means, what to do next.

Signal What it suggests Check in StarBar Next step
Router reachable, terminal fields present Your Mac has a useful local telemetry path into the Starlink setup. Inspect status, latency, ping success, events, obstruction, hardware, and network clients. Use StarBar as the first-pass diagnostic surface before opening deeper support workflows.
Search result mentions Enterprise or Telemetry API The page may be about account/device management APIs, not the same local LAN telemetry path StarBar uses. Use StarBar for local status and diagnostics without treating it as an account-management client. Use official Enterprise or Telemetry API docs if you need account, fleet, or portal-style integration.
Router reachable, terminal fields missing The router may be reachable while dish/terminal telemetry is unavailable, partial, or blocked by topology. Look for partial data labels and which cards are unavailable. Check bypass mode, third-party router static route, mesh, or firmware/hardware limitations.
Everything local is unreachable The Mac may not have a route to Starlink local addresses or may be on another network. Confirm whether any hardware/client fields populate at all. Check Wi-Fi/Ethernet network, third-party router route, VPN, and router light state.
Specific field shows -- That field is not currently exposed or reliable for this hardware/firmware/setup state. Use the partial-data cue as information, not a bug by default. Diagnose with adjacent signals rather than inventing the missing value.

Run this local check.

  1. Open StarBar while connected to the same local network as the Starlink hardware.
  2. Check whether router, terminal, hardware, and client sections populate.
  3. Look for partial-data labels before assuming a metric is zero or normal.
  4. If using a third-party router, verify whether local Starlink status access needs a static route.
  5. Use account-level Starlink tools for billing, activation, plans, and official support.

Use the signal, then branch.

Does StarBar show router/client information?

Yes: The Mac can see at least part of the local network path.

No: Start with network selection, Wi-Fi/Ethernet, VPN, and router reachability.

Does StarBar show terminal/dish information?

Yes: Use local telemetry for status, events, obstruction, latency, and power checks.

No: Investigate topology: bypass mode, third-party router route, mesh, firmware, or local endpoint reachability.

Is the missing data account-related?

Yes: Use official Starlink account/support tools; local telemetry is not account authority.

No: Compare adjacent local fields and note the partial state.

Short answer

StarBar reads local Starlink telemetry exposed on your network when your Mac can reach the router or terminal. It is not the same as having full account-level API access.

What local telemetry is good for

Local telemetry is useful for status, latency, ping success, throughput, events, obstructions, hardware context, router clients, radio details, interfaces, and partial-data awareness when those fields are available.

Local telemetry vs official APIs

SERPs mix several concepts under 'Starlink API': local network telemetry, Starlink Telemetry API, and Enterprise/account APIs. StarBar is intentionally local-network-first for Mac diagnostics; it is not an account-management or fleet-provisioning console.

Why fields can be missing

Starlink telemetry can vary by hardware model, firmware, router mode, bypass/bridge setup, mesh configuration, and whether the dish or router is reachable from your Mac.

What local telemetry is not

It is not a guarantee of billing, activation, account status, plan details, official support status, or global outage state. Those require official Starlink account/support sources.

Why StarBar labels partial data

A diagnostic app should make uncertainty visible. When a field is not exposed locally, StarBar labels the partial state instead of guessing or pretending the data exists.

Quick answers.

Is there a public Starlink local API?

Starlink hardware exposes local telemetry in ways that can vary across hardware and firmware. StarBar focuses on presenting reachable local telemetry in a native Mac app rather than promising a stable public API contract.

Does StarBar need my Starlink account password?

No for core diagnostics. StarBar is local-network-first and reads telemetry from reachable hardware on your network when available.

Why does bypass mode matter?

Network topology can affect whether your Mac can reach router or terminal telemetry. Bypass, bridge, mesh, and third-party router setups may change what is reachable.

Keep Starlink visible from your Mac.

StarBar puts local Starlink status, latency, ping success, outages, obstructions, throughput, and power draw into a native macOS menu bar app.