Edge Device Status

Summary

Lux Sync can publish live edge, device, gateway, or remote-worker status to a control-plane UI without requiring a full telemetry pipeline for current-state visibility.

Buyer phrase: “I need to see whether devices, edge workers, or gateways are online and what their current state is, but the live UI should not depend on a heavy queue or telemetry stack.”

Buyer Problem

Edge and device systems often have two different data needs:

• durable telemetry and history;
• current operational status.

The durable stream might go to a time-series database, data lake, or device-management platform. But the UI often needs a compact live projection: online/offline, mode, temperature, active job, version, location, or alert state.

Lux provides a fast active-state broker for the current view.

Lux Architecture

An edge agent, gateway, device proxy, or backend collector writes compact status state to Lux. Operators subscribe through a control-plane UI.

Data path:

1. Edge agent observes current device status.
2. Agent writes status JSON to the broker.
3. Lux stores current state in memory.
4. Control-plane UI receives status update over WebSocket.
5. Durable telemetry remains in the buyer’s existing telemetry system if required.

Example State

{
  "device": "edge-17",
  "status": "online",
  "temperatureC": 36,
  "source": "edge-agent",
  "summary": "edge-17 online 36C"
}

Implementation Shape

Use one document per device, gateway, site, or fleet summary:

device-edge-17
gateway-us-west-2a
fleet-summary-prod
site-atlanta-03

Agent update:

curl -X PUT "$BROKER/api/lux/device-edge-17" \
  -H "Authorization: Bearer $LUX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data":{"device":"edge-17","status":"online","temperatureC":36}}'

Control-plane UI subscribes to the document and renders the state.

AWS Estate Proof

Scorecard: /mnt/data/ubuntu_data/code/lux/artifacts/usecase-scorecard-aws/20260617T221800Z/scorecard.md

Proof string: edge-17 online 36C

Result:

• CLI proof: PASS
• Browser Playwright proof: PASS
• PUT ack observed from external operator machine to AWS EC2: 152.440 ms
• WebSocket delivery observed from external operator machine to AWS EC2: 391.809 ms

Timing boundary: this external AWS estate timing includes public network latency.

Customer Data Handling

For buyer-deployed brokers, edge/device status payloads stay in the buyer environment. The buyer controls broker placement, network ingress, authentication, and retention. Voxell does not need to receive device status payloads.

Good Fit

Use Lux for:

• current online/offline state;
• device heartbeat projection;
• edge worker mode;
• gateway status;
• fleet summary state;
• live control-plane views;
• lightweight alert panels.

Poor Fit

Do not use Lux alone as:

• a long-term telemetry lake;
• a device command reliability system;
• a guaranteed delivery bus;
• a high-volume sensor ingest pipeline.

Lux can sit beside those systems as the live control-plane projection.

FAQ

Can Lux show live device status?

Yes. A device agent or gateway can publish current status to the Lux broker, and a control-plane UI can subscribe over WebSocket.

Does Lux replace telemetry storage?

No. Lux is for current active state. Buyers should keep durable telemetry history in their existing observability, time-series, or data platform.

Can Lux run near edge workloads?

Yes. In the buyer-deployed model, the buyer can place the broker near the workloads or control plane that need low-friction synchronization.

Does Voxell receive device data?

For buyer-deployed brokers, device status sync payloads remain inside the buyer environment.