Zte History

Execute read-only history SQL

Execute a guarded SQLite SELECT/WITH SELECT query against history.db. Requires explicit LIMIT <= 2000, SQL length <= 16384 bytes, and allowlisted tables. This tool does not auto-inject router_id or event.scope filters; add them explicitly for router-scoped analysis.

Get domain context

Return domain context and operator-specific facts for ZTE 5G analytics: router identity/topology, event scope, deployment coordinates, RF interpretation rules, identities, metrics, relationships, pitfalls, uplink/MultiWAN semantics and query patterns.

Get history schema

Return DDL and descriptions for allowlisted history.db tables, including router_id and event.scope semantics where relevant.

Get router MultiWAN status

Fetch live read-only MultiWAN mode/composition status for a router through the unified daemon API. Returns router_id/router_id_defaulted, observed_at, mode/status/is_active and uplink_ids for cross-linking to uplink telemetry. Defaults to router_id=ultra for compatibility; pass router_id explicitly for any named-router or multi-router question. This is external I/O, not history.db analytics, and it is not the same as uplink telemetry.

Get router uplink status

Fetch live read-only uplink telemetry for a router through the unified daemon API. Returns router_id/router_id_defaulted, observed_at and backend-provided uplink legs such as mobile/wired state, addressing, raw rates and counters. Defaults to router_id=ultra for compatibility; pass router_id explicitly for any named-router or multi-router question. This is external I/O, not history.db analytics, and it is not the same as MultiWAN status.

List configured routers

Return configured router inventory from the daemon API: router_id, family, topology roles, deployment metadata, capability flags and latest known availability. Use this before selecting a router for multi-router questions. This does not perform a fresh router poll.

Refresh live router status

Perform an explicit live telemetry refresh for a router through the unified daemon API and return fresh router status, selected router_id/router_id_defaulted, resolved tower/sector context and configured router deployment metadata. Defaults to router_id=ultra. For current serving-cell / "сота" questions, the returned sector context is part of the expected answer, not optional decoration. This is external I/O, not history.db analytics.

Run known history report

Run an existing verified router-scoped history report and return structured JSON rows. Defaults to router_id=ultra unless router_id is provided. Reports: current-decision, decision-hints, combos, anchor-health, anchor-signal-history, tower-health, tower-anchors, tower-nr-coverage, tower-quality, tower-streaks, action-effectiveness. action-effectiveness summarizes recorded recovery action outcomes, not every self-recovery incident.