End User Starter Kit Guide

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 authorized commands from the dashboard.

 

Field

Value

Document type

User guide

Version

1.3

Language

English

Prepared for

Urbit One dashboard users

Date

May 2026

Scope

Operational use of the dashboard environment, not installation or engineering design

 

  

The Urbit One dashboard environment gives operators a single place to verify kit health, inspect each device, review historical behavior, manage alarms, and send controlled commands. The practical goal is simple: detect operational degradation early, confirm the root cause, take the proper action, and verify recovery with data. Current status, historical context, and documented actions should be reviewed together.

The dashboard is organized by activity rather than by internal page names. Users normally start with the overall health view, open a device detail view when something needs attention, manage any alarms, and use command panels only when a corrective or configuration action is required.

User need

Where to work

Expected outcome

Know whether the kit is healthy

Overall health cards, active alarm table, and maps

Confirm that the Edge Node and field devices are reporting within expected intervals.

Investigate a device

Device detail view and historical charts

Compare current status against recent trends and configuration values.

Respond to alarms

Active alarm table and alarm detail panel

Acknowledge, assign, investigate, clear, and verify recovery.

Adjust customer-facing alarm behavior

Alarm settings panels for supported devices

Enable or disable selected alarms and update thresholds where available.

Send a command

Command panel for the selected device

Submit the command, wait for device delivery, and confirm the result through telemetry.

Escalate an issue

Support/help panel and alarm context

Provide the affected device, alarm, last activity, screenshots, and recent actions.

 

Operating principle
Always verify a corrective action with telemetry after it is submitted. A command confirmation only means the platform accepted the request; it does not always mean the field device has already executed it.

 

This document includes layout maps generated from the exported dashboard definitions. These maps show the relative location and purpose of dashboard elements. Because the export files do not contain live rendered screenshots from the running ThingsBoard instance, screenshot placeholders are included where customer-facing images should be inserted before release.

Use the same workflow every time. This reduces missed alarms, duplicate commands, and inconsistent operational handling.

 

 

Step

Action

What to verify

1

Open the overall health view.

Confirm that the alarm count, device cards, and map are visible. Check the selected time window.

2

Review active alarms first.

Prioritize Critical or Major alarms, unacknowledged alarms, and alarms on the Edge Node.

3

Check the Edge Node health.

The Edge Node should be active, recently reporting, charging or adequately powered, and using an expected backhaul.

4

Check each field device card.

Confirm last activity, battery or electrical values, location where applicable, and signal quality.

5

Open the affected device detail view.

Use current status, configuration, and historical charts to determine whether the issue is new, recurring, or expected.

6

Acknowledge and assign alarms.

Mark reviewed alarms as acknowledged and assign responsibility if your workflow requires it.

7

Send commands only when needed.

Use the correct command panel, submit once, and wait for telemetry or status confirmation.

8

Clear alarms only after recovery.

Clear the alarm after the condition has returned to normal or the operational decision has been documented.

 

 

 

Figure 1. Overall monitoring view layout map derived from the dashboard export.

 

The overview is the operational landing area. It summarizes the kit, shows the main devices, displays active alarms, and provides map context. Use it to decide where to drill down, not to perform a full diagnosis.

Element

How to read it

Healthy condition

Kit summary

Shows high-level counts and operating status for the solution.

All expected devices are present and no critical alarms are active.

Edge Node card

Shows Edge Node identity, online state, battery or power condition, charging state, backhaul/location indicators, and last update.

Active, recent last activity, battery adequate or charging, expected backhaul active.

Tracker card

Shows tracker identity, battery, location, last activity, and event indicators.

Active, recent uplink, usable battery, no active SOS/fall/press event unless intentionally tested.

Smart Plug card

Shows relay state, voltage, current, power, energy, power factor, and last activity.

Active, relay state expected, electrical values within expected range, no outage alarm.

Active alarms table

Lists current alarms across the kit.

No Critical or Major alarms. Any warning is acknowledged and under review.

Map or trip map

Shows current and/or historical location context for devices with location data.

Location is plausible and recent. Route history matches expected device movement.

Support/help panel

Provides the support entry point or reference information.

Used when a condition cannot be resolved through the standard workflow.

 

Most device cards provide an action menu or button. The exact icons may vary by user permissions, but the operational logic is consistent:

·       
Open history/details to inspect current status, configuration, and trends for the selected device.

·       
Open commands when a controlled action must be sent to the selected device.

·       
Open alarm settings when customer-facing alarm toggles or thresholds need to be changed.

·       
Open edit information only to update descriptive metadata, such as label, brand, model, or description, when permitted.

Time window check
If a chart or map appears empty, verify the selected time range before assuming the device has failed. Historical charts only show data inside the selected period.

 

 

Device detail views combine three types of information: status, current configuration, and historical trends. Use the current status to see what is happening now, the configuration to understand how the device is expected to behave, and the charts to prove whether the behavior changed over time.

The Edge Node is the health anchor for the kit. If the Edge Node is offline or unstable, field devices may continue operating locally, but dashboard visibility and command delivery may be affected.



Figure 2. Edge Node detail layout map derived from the dashboard export.

 

Data shown

Meaning

Operational interpretation

Active / last activity

Indicates whether the Edge Node has recently reported to the platform.

If inactive or stale, investigate power, backhaul connectivity, antenna placement, and recent restarts.

Battery percentage and charging

Shows local power availability and whether the device is charging.

A declining battery while not charging points to power-source or charger issues.

Latitude / longitude and GPS fix

Shows device position and whether location data is valid.

Missing or stale location may indicate poor GPS visibility or disabled/stale location reporting.

Active backhaul / link mode

Shows the current communication path, such as WiFi, cellular, satellite, or another configured route.

If active backhaul differs from preferred backhaul, the device may be using fallback connectivity.

Firmware 

Shows current firmware and target firmware when available.

A mismatch may indicate a pending or failed firmware update.

LoRaWAN mode

Shows the local radio or LoRaWAN operating mode reported by the Edge Node.

Unexpected values may affect field-device uplinks and downlinks.

Reporting interval and inactivity timeout

Shows how often the device is expected to report and when it is considered inactive.

Use these values to judge whether a last activity gap is normal or abnormal.

Data consumption

Shows traffic by supported backhaul where available.

Unexpected increases can indicate excessive reporting, retries, or unstable connectivity.

 

·       
Confirm the Edge Node reports before investigating downstream field-device issues.

·       
Check battery/charging trends before sending restart or firmware commands.

·       
Compare preferred backhaul against active backhaul to detect fallback operation.

·       
Review temperature/health and GPS fix history when the device is installed in a remote or unattended location.

The tracker detail view is used to validate location, movement, battery, LoRaWAN signal, event reporting, and geofence behavior.

 

Figure 3. Tracker detail layout map derived from the dashboard export.

 

 

Data shown

Meaning

Operational interpretation

Active / last activity

Shows whether the tracker has recently sent an uplink.

A stale tracker can indicate battery depletion, radio coverage issues, or that it has not reached an uplink window.

Battery

Shows tracker battery level over time.

A steady decline is normal; a sharp drop requires investigation.

Latitude / longitude

Shows reported location coordinates.

Coordinates should be plausible for the asset. Stale coordinates can occur when GPS is unavailable or location mode changes.

RSSI and SNR

Shows LoRaWAN signal strength and signal-to-noise ratio.

Compare against the normal baseline. Worse RSSI or low/negative SNR can explain missed uplinks.

Distance to Edge Node

Estimates distance between the tracker and Edge Node where available.

A growing distance can explain weaker LoRaWAN signal or delayed downlinks.

Event status text

Shows readable event information such as SOS, press, fall, or other tracker events.

Treat safety-related events as high priority even if telemetry otherwise looks normal.

Geofence status and distance from center

Shows whether the tracker is inside or outside a configured area.

An outside-geofence condition should be correlated with route history before clearing.

Work mode, positioning strategy, SOS mode, intervals

Shows how the tracker is configured to report and detect events.

Configuration changes affect battery, update frequency, and location precision.

 

·       
Check event status before focusing on signal or battery; SOS/fall/press events are operationally more urgent.

·       
Use the route map and coordinate history to confirm whether movement is expected.

·       
Use RSSI/SNR trends to distinguish device failure from coverage degradation.

·       
If a command was sent, wait for the next uplink window before assuming the tracker ignored it.

The smart plug detail view is used to validate relay state, power availability, electrical behavior, alarm thresholds, and LoRaWAN signal.

 

Figure 4. Smart plug detail layout map derived from the dashboard export.

 

 

Data shown

Meaning

Operational interpretation

Active / last activity

Shows whether the smart plug has recently reported.

If stale, check power availability, LoRaWAN coverage, and whether the Edge Node is healthy.

Relay status / state

Shows whether the controlled outlet is on, off, or in another reported state.

Relay state should match the operational expectation and any recently sent command.

Voltage

Shows measured line voltage.

High or low voltage should be compared against configured thresholds and local electrical expectations.

Current

Shows current draw.

Unexpected high current may indicate abnormal load behavior.

Power

Shows real-time power use.

Unexpected power draw can indicate a load left on, fault, or configuration mismatch.

Energy

Shows accumulated or delta energy where available.

Use trend behavior, not a single point, to understand consumption.

Power factor

Shows load efficiency behavior.

A low power factor can trigger an alarm if the low power factor alarm is enabled.

RSSI and SNR

Shows LoRaWAN radio quality.

Weak or noisy signal can delay relay command confirmation and telemetry updates.

Startup relay state

Shows how the relay should behave after power recovery.

Review this setting before using the device on equipment where unexpected energizing is unacceptable.

 

·       
Compare relay status against the expected physical state of the load.

·       
Review voltage, current, power, and power factor together; one value rarely tells the full story.

·       
Do not repeatedly send relay commands. Submit once, wait for the next uplink or confirmation, then verify status and electrical values.

·       
For outage alarms, correlate last activity, voltage, relay state, and Edge Node health before clearing.

Figure 5. Alarm lifecycle and recommended operator actions.

Figure 6. Placeholder for a live alarm table and alarm detail screenshot.

 

Alarms are the main operational control point. The dashboard supports reviewing alarm details, searching/filtering, acknowledging, assigning, and clearing alarms. The objective is not to make the table empty; the objective is to leave the system healthy and the operational record clean.

Status

Meaning

Correct use

Active

The alarm condition is still present or has not yet been cleared by rule or user action.

Investigate and monitor until the condition is resolved.

Cleared

The alarm is no longer considered active.

Use only after the condition is no longer present or after an authorized operational decision.

Unacknowledged

No user has marked the alarm as reviewed.

Treat as new or not yet triaged.

Acknowledged

A user has reviewed the alarm.

Use after reading details and starting investigation; acknowledgment is not a fix.

Assigned

Responsibility has been assigned to a user or group when supported.

Use for follow-up ownership and escalation control.

 

Step

Action

1. Identify priority

Sort or filter by severity and creation time. Review Critical and Major alarms first, especially alarms affecting the Edge Node.

2. Open details

Review alarm type, device, severity, creation time, current status, and recent activity.

3. Acknowledge

Acknowledge the alarm once you have reviewed it. This tells other users the alarm is being handled.

4. Assign if needed

Assign the alarm to the responsible person or group when your workflow requires ownership.

5. Diagnose

Open the affected device detail view. Check last activity, status, configuration, and trends.

6. Act

Take the appropriate action: adjust configuration, send a command, inspect power/connectivity, or escalate.

7. Verify recovery

Confirm through telemetry, status cards, and trend charts that the condition has returned to normal.

8. Clear

Clear the alarm only after recovery is verified or after an authorized decision that the alarm is no longer actionable. Must of the alarm are mark as cleared automatically when the condition did not longer exist.

 

Important
Acknowledging an alarm does not mean the problem is solved. Clearing an alarm without verification removes operational visibility and makes root-cause analysis harder later.

 

Alarm condition

Likely meaning

First checks

When to clear

Device inactive or not reporting

The device has not reported within the expected inactivity window.

Last activity, reporting interval, battery/power, Edge Node health, LoRaWAN signal, backhaul.

After new telemetry confirms recovery or the device is intentionally offline.

Low battery

Battery level is below the configured threshold.

Battery trend, charging state, power source, reporting interval.

After battery returns above threshold or the power issue is resolved.

SOS / press / fall event

The tracker reported a safety or manual event.

Event status text, route map, latest coordinates, user confirmation.

After the event has been handled and documented according to procedure.

Geofence alarm

Tracker is outside the configured area or distance limit.

Map, coordinate history, distance from center, expected movement.

After the tracker returns inside area or the movement is confirmed as authorized.

High or low voltage

Smart plug measured voltage outside configured limits.

Voltage trend, load behavior, site power condition, threshold value.

After voltage returns to normal or the threshold is corrected.

High current or high power

Measured load exceeds configured current or power limits.

Current/power trend, relay state, connected load, threshold value.

After load normalizes or the threshold is corrected.

Low power factor

Power factor is below configured threshold.

Electrical values trend, connected equipment, threshold value.

After value normalizes or the condition is accepted by operations.

Outage

Expected electrical availability or reporting is lost.

Voltage, relay status, last activity, Edge Node health, site power.

After power/reporting is restored and values are stable.

Backhaul or link change

The Edge Node changed active communication path or link mode.

Active backhaul, preferred backhaul, data consumption, last activity.

After connectivity is stable or fallback operation is accepted.

Firmware mismatch or update issue

Current firmware differs from expected or update did not complete.

Firmware fields, connectivity, battery/power, update command history.

After the expected firmware is reported or rollback/deferral is accepted.

 

Use filtering when the alarm table grows. Recommended filters include severity, device, acknowledged/unacknowledged status, active/cleared status, and creation time. For daily operations, focus first on unacknowledged active alarms, then on alarms that remain active for longer than expected.

·       
Do not clear an alarm only to remove it from the table. Clear alarms only after the condition has been resolved, accepted, or identified in accordance with the operating procedure.

·       
Do not clear an inactive-device alarm until the device reports again or the offline condition is accepted.

·       
Do not clear an electrical alarm until voltage/current/power values are back in range or a threshold correction is approved.

·       
Do not clear a safety event until the event has been handled through the agreed operational procedure.

·       
After clearing, check whether the alarm reappears. A recurring alarm usually means the root cause was not resolved.

Note: Most alarms are automatically marked as cleared when the condition no longer exists.

Figure 7. Tracker alarm settings layout map derived from the dashboard export.

 

Figure 8. Smart plug alarm settings layout map derived from the dashboard export.

 

Supported alarm configuration panels allow authorized users to enable or disable customer-facing alarm behavior and update thresholds for selected devices. Configuration changes should be intentional, documented, and verified. Thresholds that are too restrictive can generate excessive alarms; thresholds that are too permissive can hide real operational problems.

·       
Confirm which device you are configuring before saving changes.

·       
Change one category at a time when possible, then verify behavior.

·       
Use units consistently. Voltage, current, power, and power factor thresholds must match the dashboard fields.

·       
Email notification settings affect how notifications are delivered; they do not necessarily prevent alarms from appearing in the dashboard.

·       
Alarm configuration changes do not rewrite historical alarm records.

·       
If an alarm is already active, update the threshold, then verify whether the alarm clears or re-triggers according to the rule’s behavior.

Setting

Purpose

Operational guidance

Email Notifications

Controls whether customer email notifications are sent for supported tracker alarms.

Keep enabled for operational users who must be alerted outside the dashboard. Disable only when notifications are intentionally paused.

SOS Alarm

Enables alarm generation for tracker SOS events.

Normally enabled. Disable only for controlled tests or a documented business reason.

Press Once Alarm

Enables alarm generation for a single button press event.

Use when a manual check-in or alert button press is operationally meaningful.

Fall Alarm

Enables alarm generation for fall detection events.

Use when the tracker is carried by a person or attached to an asset where fall detection is meaningful.

 

·       
Open the tracker alarm settings action from the selected tracker.

·       
Confirm the entity name shown in the configuration panel.

·       
Enable or disable the required alarm toggles.

·       
Decide whether email notifications should be active for customer-facing alerts.

·       
Save the settings.

·       
Verify that the device detail view still shows current tracker telemetry.

·       
If this was a test, generate only one controlled event and verify alarm creation and notification behavior.

Setting

Purpose

Operational guidance

Email Notifications

Controls whether customer email notifications are sent for supported smart plug alarms.

Keep enabled when electrical conditions require active notification.

High Voltage Alarm / Threshold

Triggers when measured voltage rises above the configured high limit.

Set according to the expected site voltage and tolerance. Too low will generate noise.

Low Voltage Alarm / Threshold

Triggers when measured voltage falls below the configured low limit.

Use to detect brownouts, power instability, or site power problems.

High Power Alarm / Threshold

Triggers when measured power exceeds the configured limit.

Use to detect unexpected or excessive load.

Low Power Factor Alarm / Threshold

Triggers when power factor falls below the configured limit.

Use when load efficiency or abnormal electrical behavior matters.

High Current Alarm / Threshold

Triggers when current exceeds the configured limit.

Use to protect against abnormal current draw or load changes.

Outage Alarm

Enables outage-related alarm behavior.

Use when loss of electrical availability must be surfaced immediately.

 

Smart Plug alarm configuration procedure

·       
Open the smart plug alarm settings action from the selected smart plug.

·       
Confirm the device name before editing values.

·       
Enable the alarm categories that matter for the site.

·       
Enter thresholds using the same units shown in the electrical values cards and charts.

·       
Save the settings.

·       
Return to the device detail view and confirm that voltage, current, power, and power factor are still updating.

·       
Review the active alarm table after the next report to confirm whether the new configuration behaves as expected.

Threshold sanity check
For high alarms, the alarm normally triggers when the measured value is above the threshold. For low alarms, it normally triggers when the measured value is below the threshold. Power factor is the exception that often feels backward: lower values are usually worse.

 

 

Figure 9. Command delivery model and verification requirement.

 

Figure 10. Edge Node command panel layout map derived from the dashboard export.

Figure 11. Tracker command panel layout map derived from the dashboard export.

 

Figure 12. Smart plug command panel layout map derived from the dashboard export.

 

Commands are operational actions sent from the dashboard to the Edge Node or field devices. Use them deliberately. Repeated submissions can create duplicate requests, confusing status changes, and unnecessary radio traffic.

Target

Delivery behavior

What the user should expect

Edge Node

Commands are sent to the Edge Node when it is connected to the platform.

Execution can be near real time when backhaul is active, but reboot, firmware, and network changes may temporarily interrupt reporting.

LoRaWAN Class A field device

Downlinks are queued and delivered during the device receive window after an uplink.

The result may not be visible immediately. Wait for the next uplink/report before retrying.

LoRaWAN Class C field device

Downlinks can be received more immediately when the device is listening.

Still verify through telemetry because network and device state can affect execution.

Offline device

Commands may remain pending or fail depending on platform and device state.

Restore connectivity first or wait until the device reports again.

 

·       
Open the selected device detail view and confirm the status.

·       
Check active alarms and recent telemetry so you understand the current condition.

·       
Open the command action for that same device.

·       
Review command parameters before submitting.

·       
Submit the command once.

·       
Wait for the expected delivery path: next uplink window for Edge Node and LoRaWAN devices.

·       
Return to the status and history charts to confirm the result.

·       
If the result is not visible, check the last activity and signal before sending the command again.

Command category

Purpose

Precautions

Verification

Restart Edge Node

Reboots the Edge Node to recover from a software or communication condition.

Avoid during firmware updates or when battery is low. Expect a temporary reporting gap.

Last activity updates again; active state returns; field-device uplinks resume.

Firmware upgrade

Starts or supports the Edge Node firmware update process.

Use only with stable power and connectivity. Do not interrupt during update.

Current firmware matches expected firmware; no firmware alarms remain active.

Set reporting interval

Changes how frequently the Edge Node reports status.

Shorter intervals increase traffic and may affect power usage.

The interval field updates and telemetry cadence changes accordingly.

Configure radios

Updates radio-related settings used by local field-device communication.

Incorrect radio settings can disrupt LoRaWAN device communication.

Field devices continue reporting; LoRaWAN mode/status looks correct.

Set WiFi settings

Updates WiFi network connection parameters.

Incorrect credentials or network data can disconnect the Edge Node from WiFi.

Active backhaul and last activity confirm reconnection.

Set WiFi channel

Changes WiFi channel behavior where supported.

Use only when instructed or when resolving interference.

Connectivity remains stable after the change.

Request temperature / health

Requests diagnostic health information from the Edge Node.

Low risk; used for troubleshooting.

Temperature/health telemetry updates in the detail view.

 

7.4 Tracker commands 
*Consult the manufacturer's documentation

Command category

Purpose

Precautions

Verification

Reporting interval

Adjusts periodic or event-based reporting cadence.

Short intervals can reduce battery life and increase radio traffic.

Periodic interval or event interval values update; uplink cadence changes.

Work mode

Changes tracker behavior profile.

Use only when the operational mode is understood.

Work mode field reflects the requested setting after device report.

Positioning strategy

Changes how the tracker determines location.

More precise modes can consume more battery or require better signal conditions.

Location behavior and strategy field match expectation.

SOS mode

Changes how SOS behavior is handled.

Do not disable safety behavior unless approved.

SOS mode field updates; controlled test event behaves as expected.

Motion/static thresholds

Adjusts motion detection sensitivity and static timeout behavior.

Overly sensitive thresholds can create excess events; loose thresholds can miss movement.

Motion-related event behavior matches test conditions.

Temperature/light event settings

Adjusts environmental event sampling and thresholds where supported.

Short sampling intervals can affect battery life.

Environmental event fields update and event cadence changes.

WiFi scan / uplink interval

Controls scan behavior and uplink cadence where supported.

Scanning can consume battery and may not be needed in all deployments.

Settings are reflected after the next report; battery trend remains acceptable.

 

7.5 Smart Plug commands
*Consult the manufacturer's documentation

Command category

Purpose

Precautions

Verification

Relay control

Turns the controlled outlet on or off where permitted.

Confirm the connected load is safe to energize or de-energize. Do not use on critical equipment without authorization.

Relay status/state changes and electrical values reflect the new state.

Startup relay behavior

Defines the relay behavior after power restoration where supported.

Wrong startup behavior can energize equipment unexpectedly after an outage.

Startup relay state configuration updates.

Reporting or monitoring parameters

Adjusts how frequently the device reports electrical telemetry.

Short intervals increase traffic and may affect battery/traffic planning.

Telemetry cadence changes after the device reports.

Electrical limit parameters

Updates device-side electrical limits where exposed by the command panel.

Coordinate with alarm thresholds to avoid contradictory behavior.

Configuration fields and subsequent alarms match the intended limits.

 

Command retry rule
Do not retry a LoRaWAN field-device command until the device has had a reasonable chance to report again. If the device is Class A, the downlink depends on the next uplink window.

 

Figure 13. Solution health interpretation model.

The dashboard should be read as a system, not as a set of isolated numbers. A smart plug alarm may be caused by electrical behavior, but it may also be explained by an offline Edge Node, a poor LoRaWAN signal, or a stale time window. Correlation is cheaper than dispatching someone to the wrong place.

Signal

Good pattern

Warning pattern

Action

Last activity

Updates within the expected reporting interval plus tolerance.

No update beyond inactivity timeout.

Check device power, signal, Edge Node health, and selected time window.

Active flag

Active/online for expected devices.

Inactive/offline unexpectedly.

Open device detail and inspect last activity and alarms.

Battery

Stable or slowly declining; charging when expected.

Fast decline, very low level, not charging when expected.

Inspect power source, charger, solar/power input, and reporting interval.

Backhaul/link mode

Active route matches preferred or approved fallback.

Unexpected fallback, frequent changes, no active path.

Check coverage, credentials, antennas, and data consumption.

RSSI/SNR

Stable near normal baseline.

Sudden degradation, low SNR, repeated weak signal.

Check distance, antenna orientation, obstructions, and Edge Node health.

Location

Plausible and recent.

Stale, impossible, or missing location.

Check GPS fix, positioning strategy, and device placement.

Events/geofence

No unexpected safety or boundary events.

SOS, fall, press, or out-of-geofence event.

Follow operational procedure and confirm with route/history.

Voltage/current/power

Within expected operating range.

Outside threshold or abrupt change.

Inspect load, relay state, site power, and alarm thresholds.

Power factor

Within acceptable range for the connected load.

Below configured limit.

Check load behavior and threshold configuration.

Firmware

Current version matches expected version.

Mismatch or repeated failed update.

Use firmware workflow only with stable power/connectivity.

 

·       
Look for trend changes, not just single points. A single bad value can be noise; a persistent slope is behavior.

·       
Compare chart changes against alarms and command times. If the change follows a command, the command may be causal.

·       
Check whether data gaps align with Edge Node connectivity gaps. If yes, the issue may be backhaul-related rather than sensor-related.

·       
For battery and electrical data, trend direction matters more than a snapshot.

·       
For RSSI and SNR, use the device baseline. Absolute values vary by installation, antenna, distance, and environment.

·       
Confirm that the selected time window includes the movement or event you want to inspect.

·       
Use the latest coordinates for the current position and the route/trip history for movement behavior.

·       
If a tracker reports a geofence event, correlate the event time with map position and distance from center.

·       
If location is missing, check the GNSS fix, positioning strategy, battery, and whether the device has recently reported.

Check

Pass condition

Action if failed

Active alarms

No unacknowledged Critical/Major alarms.

Open details, acknowledge, assign, and investigate.

Edge Node

Active with recent last activity and acceptable power/backhaul.

Check power, backhaul, restart only if justified.

Tracker

Recent uplink, adequate battery, plausible location, no unexpected safety event.

Review signal, battery, location mode, and event history.

Smart Plug

Recent report, expected relay state, electrical values within range.

Review relay state, voltage/current/power trends, thresholds.

Maps

Latest location and route are plausible.

Check GPS fix, time window, and positioning settings.

Email/notifications

Notification behavior matches current operating policy.

Review alarm notification toggle for supported devices.

 

·       
Review recurring alarms and identify devices or thresholds causing repeated noise.

·       
Review battery trends and charging behavior before batteries become urgent.

·       
Review backhaul changes and data consumption to detect unstable connectivity.

·       
Review LoRaWAN signal trends to detect changes in placement or obstructions.

·       
Review firmware versions and pending maintenance actions.

·       
Confirm that alarm thresholds still match the operating environment.

·       
Record what was changed and why.

·       
Confirm the setting is visible in the device configuration section after the next report.

·       
Watch the affected charts over at least one reporting cycle.

·       
Confirm whether the related alarms have cleared, remain active, or retrigger.

·       
Return settings to the approved baseline if the change created unintended behavior.

Symptom

Likely causes

Recommended steps

No data visible in charts

Wrong time window, no recent telemetry, device inactive, permissions issue.

Expand the time window, check last activity, open device detail, verify active alarms.

Device card shows inactive

No report within inactivity timeout, dead battery, loss of power, poor LoRaWAN signal.

Check last activity, battery/power, signal charts, and Edge Node health.

Edge Node inactive

Power issue, backhaul down, antenna/coverage issue, firmware/restart in progress.

Check battery/charging, active backhaul, last activity, data consumption, and recent commands.

Tracker does not update location

No GPS fix, positioning mode, low battery, no uplink, poor placement.

Check last activity, battery, positioning strategy, GPS/location fields, and route map time window.

Tracker command not reflected

Class A downlink waiting for next uplink, device offline, weak signal.

Wait for next uplink, check RSSI/SNR, avoid repeated commands.

Smart plug relay command not reflected

Downlink delay, device offline, weak LoRaWAN signal, load/power issue.

Check last activity, RSSI/SNR, relay status, voltage/power after next report.

Electrical alarm keeps returning

Threshold too tight, real power issue, load behavior abnormal.

Review voltage/current/power trends and adjust threshold only if operationally approved.

Alarm does not send email

Email notifications disabled, recipient setup outside dashboard, notification service issue.

Confirm email notification toggle, check active alarm table, escalate with alarm details.

Map location looks wrong

Stale coordinates, no GPS fix, old time window, positioning strategy changed.

Check timestamp, GPS fix, coordinates history, and positioning strategy.

Firmware update does not complete

Unstable connectivity, insufficient power, device reboot, incorrect expected version.

Do not retry repeatedly. Verify power/backhaul, check firmware fields, then escalate if needed.

 

The following fields are commonly displayed on the dashboard. Labels can vary slightly depending on device model, firmware, and permissions.

Field

Meaning

active

Whether the device is considered active by the platform.

lastActivityTime

Most recent time the platform received activity for the device.

RepInt

Reporting interval or expected reporting cadence.

inactivityTimeout

Time threshold used to consider a device inactive.

name / label / description

User-facing identification and descriptive metadata.

firmwareVersion / expectedFirmwareVersion

Current and expected firmware versions.

hardwareVersion

Reported hardware version.

 

Field

Meaning

percentage

Battery percentage or power level indicator.

isCharging

Whether the Edge Node is charging.

Latitude / Longitude

Reported Edge Node coordinates.

gpsFix

Whether the device has a valid GPS fix where supported.

preferredBackhaul

Configured preferred connectivity path.

activeBackhaul / LMD

Currently active connectivity path or link mode.

lteIccid

Cellular SIM identifier where configured.

satelliteImei

Satellite modem identifier where configured.

wifiSsid

Configured WiFi network name where applicable.

lorawanMode

LoRaWAN operating mode reported by the Edge Node.

hubVersion

Reported local hub or Edge Node software component version.

temperature

Reported device temperature where available.

 

Field

Meaning

battery

Tracker battery level.

latitude / longitude

Reported tracker coordinates.

rssi

LoRaWAN received signal strength indicator.

snr

LoRaWAN signal-to-noise ratio.

distanceToGateway

Estimated distance to the Edge Node where available.

eventStatusText

Readable tracker event status.

eventStatus

Raw or encoded tracker event value where shown.

geofenceStatus

Whether the tracker is inside/outside the configured geofence.

distanceFromCenterMeters

Distance from geofence center where configured.

workMode

Tracker operating mode.

positioningStrategy

How the tracker determines location.

sosMode

SOS behavior configuration.

tempLightEnabled

Whether temperature/light functions are enabled where supported.

 

Field

Meaning

relayStatus / state

Current relay state reported by the smart plug.

relayStartupState

Configured relay behavior after startup/power recovery.

voltage

Measured voltage.

current

Measured current.

power

Measured power.

energy / power_sum_delta

Energy consumption or energy delta where available.

factor

Power factor.

voltageLowThreshold / voltageHighThreshold

Configured voltage limits.

overCurrentThreshold

Configured current limit.

overPowerThreshold

Configured power limit.

rssi / snr

LoRaWAN signal indicators.

 

Term

Definition

Acknowledge

Marks an alarm as reviewed. It does not resolve the condition.

Clear

Marks an alarm as no longer active or actionable.

Backhaul

The communication path used by the Edge Node to reach the platform, such as WiFi, cellular, or satellite.

Downlink

A command sent from the platform toward a field device.

Uplink

A message sent from a field device toward the platform.

LoRaWAN Class A

Device class where downlinks are normally received after an uplink receive window.

LoRaWAN Class C

Device class where downlinks are normally received immediately after the Edge Node receive it, without waiting for an uplink window.

RSSI

Radio signal strength indicator. Use trend and baseline for interpretation.

SNR

Signal-to-noise ratio. Low or negative values can indicate noisy radio conditions.

Geofence

A virtual geographic boundary used to detect whether a device is inside or outside an expected area.

Relay

The smart plug output switch that controls power to the connected load.

Threshold

A configured value used to decide when an alarm should be generated.

 

Before considering the solution healthy, confirm the following:

·       
The Edge Node is active and reporting recently.

·       
All expected field devices are visible and reporting within expected intervals.

·       
No unacknowledged Critical or Major alarms remain active.

·       
Any active Warning or Minor alarm has an owner or documented reason.

·       
Battery, power, link mode, signal, and electrical values are within expected operating patterns.

·       
Commands sent during troubleshooting have been verified through telemetry.

·       
Alarm settings and thresholds match the current operating policy.

·       
Support has been contacted for conditions that cannot be resolved from the dashboard.

End state
A healthy solution is not one with perfect numbers. It is one where expected devices are visible, current data is flowing, alarms are understood, commands are controlled, and abnormal conditions have an owner.

 

    • 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 ...

    • 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 ...

    • 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 ...

    • 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 ...