All documentation
Fleet operations10 min

WUSP device management

Use authenticated telemetry and supported remote operations without exposing low-level transport choices.

Outcome

A capable endpoint reports current state and accepts only supported authenticated operations.

Before you start

  • A supported WUSP endpoint
  • An authenticated tunnel
  • A current capability snapshot

Start from live capability

  1. 1Confirm the WUSP session is current.
  2. 2Read supported selectors/instances before rendering controls.
  3. 3Use cached snapshots only as a marked fallback.
  4. 4Hide radio or mesh controls the endpoint did not advertise.

Run supported operations

  • Get reads typed values.
  • GetInstances enumerates objects.
  • Set/Delete change supported properties with request correlation.
  • Operate invokes an allowlisted action.
  • Upload/Download use bounded authenticated transfer sessions where implemented.
Operational note: Replay mutating requests safely and reject a reused identity with different action data.

Apply intent, then prove convergence

  1. 1Set topology policy through the supported contract.
  2. 2Read back persisted intent.
  3. 3Inspect real topology for convergence.
  4. 4Keep everyday UI focused on parent/operational relationships.

Verify the result

Capabilities are current.
A read returns a typed value.
A retry does not duplicate a mutation.
Real topology confirms intended state.

Common issues

UI shows a control but endpoint says unsupported.
Likely cause

The UI ignored the endpoint capability contract.

Fix

Refresh capabilities and hide unadvertised operations.

Policy saves but topology does not change.
Likely cause

Persisted intent has not converged.

Fix

Compare intent and real topology, inspect the offline path and wait for current telemetry.

Continue with

WUSP device management | Wantastic Docs