Console and Self-Service Onboarding

The console is the web entry point for devices, connection credentials, and data analysis. After sign-in, tenant users see only data belonging to their current workspace or explicitly shared projects.

Sign in with an email link, Google, or email and password. On the first sign-in, choose a workspace ID. That ID becomes part of device connection identities.

The console uses an account session. Devices and applications use separate connection credentials. Never paste a device key into the browser sign-in form, and never put an account password in device configuration.

2. Add a device or resource

Open Credentials → Device or resource credentials, then expand Add a device or resource:

Enter a device ID and display name.
Optionally enter device type, site, and map coordinates.
Select Create and generate device key.
Save the one-time device key and connect the device with one of the generated examples.

The device list shows online state, last-seen time, and latest data. Select View to inspect trends, recent messages, and command controls.

Device details also show active MQTT and WebSocket sessions. Each resource credential keeps one MQTT connection: a later connection takes over the previous one regardless of the client-supplied Client ID. If a key was copied, disconnect the session or rotate the resource key to invalidate it.

3. Create an application credential

For dashboards, scripts, or business services, open Credentials → Application credentials and select Create application credential.

An application credential can be limited by:

accessible data spaces;
data-only access or device/space management;
access to shared projects.

The secret is shown once. For rotation without downtime, create a new credential, migrate the application, and then revoke the old credential.

For MQTT, the application key already identifies its workspace. Configure an empty username for the default space (MQTT still requires the Username Flag when a password is present), or use only @production for a named space. Client ID may be omitted and generated automatically. Set a stable unique Client ID only for durable subscriptions or offline QoS messages.

4. View data

Data & Trends has two views:

All Data groups device reports, commands, credential changes, and settings changes into collapsed rows that update live;
Live Monitor shows newly arrived messages in every space the account may access and can be paused or resumed;

Device trends are part of Devices & Resources. Select View for a device and then select Trends in the right-hand detail to chart numeric fields such as temperature, power, and humidity.

Both monitoring views share one console WebSocket. Pausing stops table updates but keeps a bounded buffer. Resuming performs one durable-history catch-up and merges buffered records; it does not poll MongoDB continuously. Cross-device activity is ordered by platform receive time, while every message channel retains its own strict sequence.

Only JSON numeric fields are charted. Other fields remain available in message details.

5. Use AI analysis

Open AI Analysis to view stream labels. The platform uses message structure to identify likely telemetry, business records, control messages, or test data.

Labels only organize and filter data. They do not modify permissions, delete messages, or block ingestion. You can override an inaccurate label manually.

6. Manage data spaces

Use Data Spaces to isolate production, testing, or team data. Select the intended space when connecting a device or application.

If the account belongs to a shared project, its spaces appear on the same page but remain independent from the account's own workspace.

7. Connect to EarthMQTT or an external broker

The Connect page has two tabs:

EarthMQTT Connection shows the HTTP, MQTT over TLS, MQTT over WebSocket, and WebSocket endpoints available on the current deployment;
External Broker connects an MQTT service you already operate.

To connect an external broker:

Enter the MQTT service URL, username, and password.
Enter subscribed topics.
Choose whether the device ID comes from a topic segment or a payload field.
Save and connect.

External messages are synchronized into the current workspace and become available to Live Monitor, Trend Analysis, and AI Analysis.

Connection history in the connector list stores a separate timeline of bridge connections, disconnects, retries, recoveries, and errors. It describes the platform-to-broker link, not whether an individual device is online. Resource availability changes only through an explicit field/value mapping in an active data rule; the platform does not guess a vendor protocol from an LWT topic or familiar state words. Retained messages replayed after a reconnect are deduplicated and do not advance the resource's latest-data time.

Data freshness in resource details configures a per-resource silence window: disabled, 5 minutes, 30 minutes, 1 hour, 24 hours, or custom. When the window expires without explicit offline evidence, the resource is shown as Data stale, not Offline. A new non-retained report immediately restores Online. The policy is disabled by default so low-frequency resources are not misclassified. A disconnected, disabled, or removed external Broker still takes precedence and shows Offline.

A connector is read-only by default. With Commands ticked, commands for devices that came in through it are published to that broker on the topic and in the format set by the control profile or the command; without it, or without a topic, the command is still recorded and the platform says it will not arrive. The connector ignores its own commands when the broker hands them back, so data and commands may share a topic.

External broker messages are authenticated by the broker connection credential. A device connecting directly to EarthMQTT still needs its own resource key from Credentials → Device or resource credentials → Add a device or resource.