Local connection
Check credentials, association, backhaul and AP activation.
Integration at a glance
Internet uplink
A connected radio does not prove upstream reachability.
Reporting freshness
Use the last-confirmed time before treating missing reports as a local fault.
Target supported hardware and an enabled site. Your application retains its own health and recovery responsibilities.
Interpret connection state
Waiting for approval: ask the authorized business to review the device request. Denied or revoked: resolve local policy before investigating radio settings.
Authentication failed: inspect certificate validity, trusted server identity, platform support, and clock handling. Backhaul connected but AP inactive: inspect the satellite configuration acknowledgement.
Wi-Fi connected but Internet unavailable: inspect the gateway’s upstream connection. Not reporting: check the last confirmed time and management path before concluding the local link is down.
Freshness and outage behavior
The initial always-on reference integration reports every 30 seconds and considers observations stale after 90 seconds. These defaults are for qualified reference devices, not an assertion about sleeping sensors.
During an uplink outage the gateway can retain local observations for later synchronization. Established sessions may retain installed policy within its validity period; new authentication fails closed and retries automatically. Offline commissioning is not supported.
Initial compatibility matrix
Software target: Linux/OpenWrt clients with supported enterprise Wi-Fi and local key storage. Infrastructure target: GL-MT6000 gateway and single-hop managed satellite.
Qualification status: physical validation pending by the site operator after implementation. Do not treat the target list as a certified or production-qualified matrix.
Not initially supported: arbitrary third-party extenders, multi-hop mesh, shared-password-only IoT platforms, embedded adapters without qualification, or guaranteed external roaming.
Prepare a support request
Include the stable device identifier, site authorization context, software version, operation or event identifier, last-confirmed timestamps, and a redacted diagnostic summary.
Do not send passwords, private keys, bearer tokens, or unrelated network client records. Reproduce with one device in the authorized sandbox where possible.
Diagram and flow
- DEVICE OBSERVATION
Check link and uplink
Observe Wi-Fi and HTTPS reachability separately. Do not infer application health.
Health + time → Report observations - AUTHENTICATED API
Report observations
Send event ID and timestamp with the device reporting credential.
Compute → Evaluate the last report - FRESHNESS CHECK
Evaluate the last report
Compute current status from the observation and its validity window.
Expired → Mark not_reportingRecent → Show the observed state - RECENT EVIDENCE
Show the observed state
Keep authorization, connection and Internet checks distinct in your UI.
- EXPIRED EVIDENCE
Mark not_reporting
Show the last confirmed time. Silence does not prove the local link failed.
Read the diagram description
- DEVICE OBSERVATION — Check link and uplink. Observe Wi-Fi and HTTPS reachability separately. Do not infer application health.Health + time → Report observations.
- AUTHENTICATED API — Report observations. Send event ID and timestamp with the device reporting credential.Compute → Evaluate the last report.
- FRESHNESS CHECK — Evaluate the last report. Compute current status from the observation and its validity window.Expired → Mark not_reporting.Recent → Show the observed state.
- RECENT EVIDENCE — Show the observed state. Keep authorization, connection and Internet checks distinct in your UI.
- EXPIRED EVIDENCE — Mark not_reporting. Show the last confirmed time. Silence does not prove the local link failed.