Eternet Portal Documentation

Device Management

Device inventory

Browse and search the device inventory, open a device workspace, and switch between list and map presentations when location data is available.

Device workspace

The workspace brings together device properties, user access, stream definitions, dashboard widgets, historical values, and MQTT Explorer tools. The exact panels depend on the device record and available service responses.

Telemetry and MQTT

Incoming MQTT values are associated with the device and its configured streams to update supported live widgets and location displays. MQTT publication is a separate operation through the portal’s broker integration; it depends on valid topic, payload, permissions, and broker connectivity.

Historical data is requested through the configured API/time-series path and should not be confused with an in-memory live message.

Integrations and limits

Device records and stream metadata are served by Eternet APIs. Remote access panels may rely on MeshCentral. Map markers require valid latitude and longitude values; widget rendering requires a compatible widget schema and matching stream data.

How the device workflow fits together

A typical operator journey starts in the inventory, where the user narrows the list to the device that needs attention. Opening its detail view changes the task from fleet-wide discovery to entity-level operation. The page is designed to keep identity, properties, connectivity, streams, and visualizations associated with the same device record. This reduces context switching, but it also means the quality of the page depends on stable identifiers returned by the API. Names are useful for people; identifiers are what the portal uses to link stream definitions, history, map coordinates, widget cards, and remote access operations to the correct entity.

Properties describe the configured device rather than necessarily reporting its current physical condition. A configured publisher, topic, owner, or access grant should be distinguished from a recently received telemetry value. Likewise, a device may have a stream definition without any current messages, or it may have recent MQTT data that is not yet represented by a configured widget. During a customer demonstration, explain these as separate layers: registration tells the platform what the device is; stream metadata tells the platform what to expect; incoming messages provide observations; the widget schema determines how selected observations are rendered.

Telemetry lifecycle and troubleshooting

For a live value to appear, a publishing client must send a message to a broker topic that the portal or backend associates with the device. The message must be authorized and parseable, and the identifier or stream name in the payload must match the resource configuration. Numeric gauges and charts need values that can be interpreted as numbers; state widgets may accept text or boolean values; map markers need a valid coordinate pair or a supported location representation. If a value does not change, troubleshoot the chain in order: broker connection, publish acknowledgement, topic and QoS, payload shape, resource match, stream configuration, subscription/reconnect state, and finally the widget’s selected stream.

The portal may expose both live and historical views, but they answer different questions. A live event proves that a message was observed at a particular time; history proves that a backend stored and returned records for the selected range. A chart can legitimately be empty when historical storage has no records even while a current MQTT value is displayed elsewhere. Conversely, a historic chart is not evidence that a current device remains connected. This distinction helps operators avoid drawing conclusions from stale or partially available data.

Customer value and responsible presentation

For customers, the Devices module offers a single point to locate registered equipment, review the data it exposes, inspect operational history, and connect values to reusable visual components. It is useful for commissioning, routine monitoring, and first-line diagnosis. The portal does not replace firmware, a broker, the time-series store, or a remote-management platform. Device actions are only available when their corresponding integration is configured and authorized. Before a live demonstration, select a device with a known stream, verify that its API record and widget schema agree, send a controlled test message, and check both the visible value and timestamp. Avoid claiming universal widget support or guaranteed delivery; supported payload shapes and rendering depend on the device’s configured data contract.