Eternet Portal Documentation

Widget Dashboard Preview

Source

This route reads from the legacy-compatible /etr/GetFakeStreamData endpoint and normalizes returned schemas into shared widget models. The endpoint is explicitly named as fake stream data, so the page should be described as a preview/test workspace unless the source is replaced or validated as production telemetry.

Rendering

Schema normalization selects a widget type and constructs its configuration before rendering. A schema preview is not equivalent to a device-bound, live MQTT widget.

Using the preview workspace

The Widget Dashboard route is a focused place to load a collection of widget schemas and see how the shared renderer interprets them. It helps teams examine visual type, labels, bounds, units, and basic configuration without opening each resource separately. The data loader requests the legacy-compatible /etr/GetFakeStreamData API, normalizes the returned objects, selects a widget type, and builds a model configuration. This makes it useful for validating schema compatibility and catching layout or type issues before a schema is used elsewhere.

The endpoint name is intentionally explicit: “Fake Stream Data” signals that the route may be supplying demonstration or test values. Unless the configured backend has been independently verified to return production-bound telemetry, present this workspace as a preview or compatibility tool. A changing or populated widget here does not prove that a real device is publishing to MQTT, that a stream is persisted, or that a production dashboard is subscribed to the same source.

How to validate a widget schema

Start by comparing the schema with the expected data contract. Confirm the widget type, source entity, stream identifier, and value type. For numeric visualizations, use representative values at the lower bound, midpoint, and upper bound; also test values outside the configured range and missing values. For charts, confirm that the sample contains a sequence rather than a single scalar. For maps, ensure latitude and longitude are valid and that longitude is not accidentally supplied as latitude. For tables, ensure column names correspond to row fields and that empty results have a clear message. These checks distinguish visual correctness from data correctness.

If the endpoint returns no items or an unexpected shape, the loader normalizes common list wrappers such as data, results, items, schemas, and streams; it cannot recover information absent from the response. The route may render an empty state on an API failure. Troubleshooting should therefore begin with authentication and the response body, then inspect schema normalization and the shared renderer.

Customer communication

For a customer presentation, describe this route as a widget preview and schema-checking surface. Demonstrate how a configured model appears and explain which properties control its presentation. If the customer’s goal is live monitoring, move to a real entity dashboard and verify a telemetry message using the actual device identifier and stream. The distinction is valuable: previewing a schema lowers implementation risk, while production monitoring requires a working source, authorized API, and data freshness checks. The preview page does not itself create a production data subscription or persist a dashboard layout.