Urbit ONE Admin Dashboards Manual v1 2

Urbit ONE Admin Dashboards Manual v1 2

Urbit ONE Administrator Dashboards Manual | v1.2

Administrator Dashboards Manual

Urbit ONE Starter Kit - Evaluation Kit, Edge Node, Tracker T1000, and Smart Plug WS523

Prepared for administrator users responsible for monitoring, configuration, alarm management, and operational validation.

Revision v1.2 - Dashboard order updated




Document Structure

This version follows the operational flow used by an administrator: first the complete Evaluation Kit view, then the Edge Node, then the Tracker T1000, and finally the Smart Plug WS523. The modal command and alarm-setting windows are documented as operational subsections, not as primary dashboards.

Section

Dashboard / Topic

Purpose

1

Purpose and Scope

Defines the intended administrator audience and operational scope.

2

Administrator Role Overview

Explains the administrator responsibilities for monitoring, configuration, and escalation.

3

Dashboard Navigation and Common Controls

Explains the shared controls available across the dashboards.

4

Evaluation Kit Dashboard - With History States

Provides the Starter Kit overview and confirms all kit components are reporting.

5

Edge Node Dashboard

Covers connectivity, firmware, battery, backhaul, hierarchy, and Edge Node commands.

6

Tracker T1000 Dashboard

Covers location, distance, battery, events, alarms, and tracker settings.

7

Smart Plug WS523 Dashboard

Covers relay state, electrical values, consumption, signal, alarms, and commands.

8

Alarm Operations

Explains acknowledge, clear, assign, comment, and review activities.

9

Command and Configuration Operations

Explains administrator use of command dialogs and configuration controls.

10

User and Customer Administration

Explains the administrator tasks related to users and customer access.

11

Data Export and Historical Review

Explains how to use history, filters, export, and fullscreen functions.

12

Support and Escalation

Defines when and how to escalate operational issues.


1. Purpose and Scope

This manual explains how an administrator uses the Urbit ONE Management Center dashboards included with the Starter Kit. It focuses on operational monitoring, device visibility, alarm management, command execution, and basic administrative workflows.

The manual does not replace installation procedures, device datasheets, or low-level protocol specifications. Its purpose is to give administrators a clear operating guide for day-to-day use. No magic, no smoke, just dashboards doing their job.

Dashboard order: The correct reading and operating order is: Evaluation Kit, Edge Node, Tracker T1000, and Smart Plug WS523.


2. Administrator Role Overview

An administrator is responsible for validating that the Starter Kit components are visible, reporting data, generating alarms correctly, and accepting operational commands when required.

  • Confirm that all expected devices are reporting in the Evaluation Kit dashboard.
  • Review Edge Node connectivity, backhaul, battery, firmware, and device hierarchy.
  • Monitor Tracker T1000 location, battery, event status, and geofence-related indicators.
  • Monitor Smart Plug WS523 relay state and electrical telemetry.
  • Acknowledge, assign, comment, and clear alarms according to internal operating procedures.
  • Export historical data when evidence, troubleshooting, or reporting is required.

3. Dashboard Navigation and Common Controls

All dashboards follow a consistent visual structure: a left navigation menu, a top action bar, a main content area, device cards, historical widgets, alarm tables, maps, and command buttons where available.

Control

Use

Search

Filters rows or alarm entries containing specific text.

Filters

Limits visible data by device, state, alarm type, severity, or configured dashboard context.

History / Realtime time window

Changes the period used by historical widgets and maps.

Fullscreen

Expands a widget or dashboard area for detailed review.

Export

Downloads chart or table data for external analysis or documentation.

Entity selector

Selects the device or entity whose telemetry is shown in the current dashboard.

Action buttons

Open command, firmware, or alarm-configuration dialogs.


4. Evaluation Kit Dashboard - With History States

Figure 1. Evaluation Kit Dashboard - With History States.

The Evaluation Kit dashboard is the administrator starting point. It provides the operational summary for the complete Starter Kit and validates that the Edge Node, Tracker, and Smart Plug are reporting.

Area

Administrator interpretation

Kit Status

Shows whether the overall kit is operational. A healthy state means the expected components are visible and reporting.

Last Seen

Shows the latest communication timestamp for the kit. Use this to detect stale data quickly.

Active Backhaul

Shows the backhaul currently used by the Edge Node, such as cellular, Wi-Fi, or satellite.

Edge Node Battery

Shows the current battery level of the Edge Node.

Trip Map

Shows the reported location of the Edge Node and Tracker. It is the fastest visual confirmation that geolocation data is available.

What's in the Kit

Lists the components included in the Starter Kit and their current online/offline state.

Alarms

Shows active alarms affecting the kit or any of its components.

Device cards

Provide direct operational summaries for the Edge Node, Tracker, and Smart Plug.


4.1 Recommended validation flow

  • Start with the device reporting counter. The expected Starter Kit state is three reporting devices.
  • Confirm that the Kit Status is OK before moving into individual dashboards.
  • Check the Active Backhaul and Edge Node Battery values.
  • Review the map for plausible location data.
  • Check the alarm table before running commands or changing thresholds.
  • Open the individual dashboards only after the overview confirms which component needs attention.

5. Edge Node Dashboard

Figure 2. Edge Node Dashboard.

The Edge Node dashboard is the operational view for the device that orchestrates local field communications and backhaul connectivity. Administrators use it to review current health, backhaul state, firmware, device hierarchy, historical battery behavior, data consumption, and alarms.

Widget / Area

Administrator use

Device Profile

Confirms identity, brand, model, firmware version, satellite IMEI, and enabled radios.

Operational Snapshot

Shows current status, battery, charging state, active backhaul, last activity, location, and temperature.

Battery History

Shows battery trend over the selected time window and helps identify charging or power problems.

Map

Shows the reported Edge Node location.

Alarms

Shows active alarms associated with the Edge Node.

Telemetry table

Shows historical raw telemetry fields for technical review.

Hierarchy

Shows the parent-child relationship between the Edge Node and its field devices.

Data Consumption

Breaks down traffic by backhaul type, useful when satellite or cellular usage must be controlled.


5.1 Edge Node commands

Figure 3. Edge Node Commands dialog.

The Edge Node Commands dialog centralizes administrative actions. These commands can affect connectivity, reporting, firmware, and local behavior. Use them only when the target device is correct and the operational impact is understood.

Command

Typical use

Restart Gateway

Restarts the Edge Node when it is responsive but needs a clean reconnect.

Gateway Temperature

Requests or reviews the Edge Node temperature condition.

Set Reporting Interval

Changes how frequently the Edge Node reports health or telemetry.

Set WiFi Settings

Updates Wi-Fi connectivity parameters.

Set WiFi Channel

Changes Wi-Fi channel when the Edge Node is operating in access point mode or as configured.

Configure Radios

Enables or disables communication interfaces according to the deployment plan.

Firmware Upgrade

Starts a firmware update workflow. Confirm device readiness before using it.


Operational caution: Do not change radio or reporting settings during a live test unless the expected behavior is documented. Connectivity misconfiguration is the kind of problem that politely waits until everyone is watching.


6. Tracker T1000 Dashboard

Figure 4. Tracker T1000 Dashboard.

The Tracker T1000 dashboard provides historical and current visibility for mobile or field-location telemetry. It is used to validate position, battery level, LoRaWAN signal, distance to the Edge Node, events, and alarm configuration.

Widget / Area

Administrator use

Device Profile

Shows tracker identity and configuration fields such as DevEUI, AppEUI, firmware, work mode, positioning, and sensor options.

Operational Snapshot

Shows active state, battery, last activity, latitude, longitude, RSSI, geofence distance, and last event.

Distance to Edge Node

Shows tracker distance trend relative to the Edge Node, useful for geofence and proximity validation.

Map

Shows the tracker position for visual confirmation.

Battery History

Shows battery percentage across the selected window.

LoRaWAN Signal

Shows RSSI history and helps identify coverage or placement issues.

Alarms

Shows active tracker alarms.


6.1 Tracker alarm settings

Figure 5. Tracker Alarm Settings dialog.

The Tracker Alarm Settings dialog controls customer-facing alarm behavior for the tracker. The available switches include email notifications, SOS alarm, press once alarm, and fall alarm.

  • Enable Email Notifications only when the customer expects operational alerts by email.
  • Enable SOS Alarm when the tracker button event must create an operational alarm.
  • Enable Press Once Alarm when a single button press should be treated as an event requiring attention.
  • Enable Fall Alarm when fall detection is part of the operational use case.

6.2 Tracker command handling

Use the Send Command action to send supported commands to the tracker. Before executing any command, confirm that the entity selector shows the intended tracker and that the device has reported recently. For Class A LoRaWAN devices, some downlinks are delivered only after the next uplink window, so patience is not optional.

7. Smart Plug WS523 Dashboard

Figure 6. Smart Plug WS523 Dashboard.

The Smart Plug WS523 dashboard provides visibility into electrical telemetry, relay state, energy consumption, LoRaWAN signal quality, command access, and alarms. Administrators use it to validate power monitoring and remote load control behavior.

Widget / Area

Administrator use

Device Profile

Shows Smart Plug identity and configuration fields such as DevEUI, DevAddr, model, serial number, LoRaWAN class, and alarm-related settings.

Operational Snapshot

Shows active state, relay status, power, current, voltage, power factor, RSSI, and last activity.

Power History

Shows active power and energy trend over the selected time window.

Electrical Values

Shows voltage, current, and power factor history.

LoRaWAN Signal

Shows RSSI trend for connectivity quality review.

Relay State

Shows relay ON/OFF history.

Alarms

Shows active alarms associated with the Smart Plug.


7.1 Smart Plug commands and alarm settings

The Smart Plug includes action buttons for Send Command and Alarm Settings. The command workflow is used for supported remote control operations such as relay-related actions. Alarm settings are used to enable or tune alert behavior for electrical conditions such as voltage or power thresholds, depending on the configured rule logic.

  • Review current relay state before sending any control command.
  • Check voltage and current values before treating a zero-power condition as a failure.
  • Use historical charts to distinguish a short event from a persistent condition.
  • Confirm alarm thresholds with the customer operating policy before changing them.

8. Alarm Operations

Alarm tables appear in the Evaluation Kit, Edge Node, Tracker, and Smart Plug dashboards. An administrator should treat alarms as operational records. A cleared alarm is not deleted; it is closed as part of the operating history.

Action

Meaning

Recommended administrator use

Acknowledge

Marks the alarm as reviewed.

Use when the alarm has been seen and responsibility has started.

Assign

Assigns the alarm to a user.

Use when a specific operator or technician owns the follow-up.

Comment / Activity

Adds operational notes.

Use to document evidence, field actions, or customer communication.

Details

Opens the alarm record.

Use to review timestamps, status, severity, and comments.

Clear

Marks the alarm as resolved or no longer requiring action.

Use only when the condition has been corrected or classified as normal.

Export

Downloads visible alarm data.

Use for reports, support tickets, or incident evidence.


9. Command and Configuration Operations

Command dialogs are operational tools, not decorative buttons. Administrators should confirm the selected entity, device status, last communication time, and expected command effect before submitting changes.

Before sending a command

Reason

Confirm selected entity

Prevents sending commands to the wrong device.

Check last seen time

Avoids assuming immediate execution when a device is not currently reporting.

Review active alarms

Prevents confusing an existing failure with a command result.

Understand delivery model

Some LoRaWAN commands may wait for the next uplink receive window.

Document the action

Creates a traceable operational record.


10. User and Customer Administration

Administrators may manage users, customer access, and notification behavior depending on their assigned permissions. Access must follow least-privilege principles: users should receive the minimum permissions required for their operational role.

  • Use valid email addresses for account activation and alarm notifications.
  • Assign users to the correct customer or group before sharing dashboards.
  • Use read-only roles for users who only monitor dashboards.
  • Limit command-capable access to trained administrators.
  • Review inactive users periodically and remove access that is no longer required.

11. Data Export and Historical Review

Historical widgets and tables can be reviewed in realtime or over selected historical windows. Use the time-window control before drawing conclusions from charts; a wrong window can make healthy data look suspicious and suspicious data look innocent.

Task

Recommended approach

Review recent behavior

Use realtime or last hour windows.

Analyze a known event

Use a fixed historical range around the event timestamp.

Compare device health

Use the same time window across related widgets.

Prepare support evidence

Export chart or table data and include screenshots when useful.

Check stale data

Compare Last Seen, Last Activity, and chart timestamps.


12. Support and Escalation

Escalate to Urbit technical support when a dashboard shows persistent offline status, unexpected backhaul changes, repeated firmware update failures, command failures, missing telemetry, or alarms that cannot be explained by site conditions.

Escalation item

Information to include

Affected dashboard

Evaluation Kit, Edge Node, Tracker T1000, or Smart Plug WS523.

Device identifier

Edge Node ID, DevEUI, DevAddr, or displayed device name.

Time window

Exact period when the issue occurred.

Observed values

Last Seen, battery, RSSI, backhaul, location, relay state, or electrical values.

Alarm details

Alarm type, severity, status, and comments.

Actions already taken

Commands sent, settings changed, or field checks performed.


Support contact: For additional assistance, contact Urbit Support at support@urbit.us.


Appendix A - Dashboard Data Dictionary

Field

Meaning

Active / Status

Whether the entity is currently considered active or online by the platform.

Last Seen / Last Activity

Most recent timestamp or elapsed time since communication.

Backhaul

Communication path used by the Edge Node to reach the Management Center.

Battery

Reported battery percentage.

Charging

Indicates whether the Edge Node is charging.

Latitude / Longitude

Last reported position.

RSSI

Received signal strength indicator, commonly used as a radio quality indicator.

SNR

Signal-to-noise ratio for LoRaWAN radio quality.

Distance to Edge Node

Calculated distance between the tracker and the Edge Node.

Event Status

Human-readable event summary for the tracker.

Relay State

Smart Plug output state, typically ON/OFF or open/closed as configured.

Active Power

Instantaneous power in watts.

Energy / Power Consumption

Accumulated consumption in Wh or kWh depending on widget configuration.

Power Factor

Ratio between real power and apparent power.


Appendix B - Administrative Checklist

Frequency

Check

Daily

Confirm Evaluation Kit status is OK and all expected devices are reporting.

Daily

Review active alarms and assign ownership when required.

Daily

Check Edge Node battery and active backhaul.

Weekly

Review signal trends for Tracker and Smart Plug.

Weekly

Export or archive relevant operational data if required by the customer.

After changes

Document commands, configuration changes, firmware actions, and observed results.


Private & Confidential - Urbit

    • Related Articles

    • Starter Kit - Quick Registration Reference

      Starter Kit - Quick Registration Reference Initial Admin User Registration Thank you for acquiring the Urbit One Starter Kit. This kit includes a Quick Registration Reference to activate the initial administrator account required to access the Urbit ...

    • End User Starter Kit Guide

      End User Starter Kit Guide Monitoring, alarms, commands, and operational health Audience This guide is written for end users and operators who monitor the Urbit One Starter kit, review alarms, adjust customer-facing alarm behavior, and send ...

    • Edge Node Wake-Up Procedure

      Quick Reference Edge Node Wake-Up Procedure Urbit One Starter Kit Important: The Edge Node is shipped in Stop Mode. This low-power shipping state protects the unit during storage and transportation. Before using the Starter Kit, the Edge Node must be ...

    • Urb-IoT Edge Node Datasheet

      Urb-IoT Edge Node – Technical Datasheet Physical & Environmental Specifications · Operating temperature: −20°C to +85°C · Humidity: 0–95% non‑condensing. · Shock-resistant polycarbonate housing. Power · Internal 60.48Wh battery for up to 72 hours of ...