Manage users, provision devices, and view all data.
Total Users
Total Devices
Online (2min)
Create User
ID
Username
Email
Role
Created
Devices
Actions
Device UID
First Seen
Last Seen
Firmware
Org
Provisioned To
Config
—
Online
—
Stale (>2h)
—
Offline (>24h)
—
Low Battery (<20%)
Device
Status
Battery
Last Seen
Temp (°C)
RSSI
SNR
Every collar with uplinks in the window, judged against its own verified schedule — the burn-in report for new hardware.
—
Checked
—
Clean
—
Warnings
—
Critical
Loading…
Fence tester — sends a pretend GPS position to a bench collar (test builds only; field collars ignore it)
Each click is one pretend GPS fix, delivered at the collar's next check-in. Zones need two fixes inside to switch on (send twice), and the collar logs every zone change to its SD card. Use with a "Test only" zone first.
ID
Name
Members
Created
Actions
Beacon encryption keys
Collar
State
Generation
KCV
Provisioned
Stale
Rotating moves the organisation to its next key generation. Every keyed collar then shows as stale until it is re-provisioned over Bluetooth from the Configure tool, one by one; each keeps sending under its old key until it is.
Assign User to Org
Assign Device to Org
Customer-owned gateways feeding our ChirpStack. Registering here creates the
gateway in ChirpStack (unknown gateways are silently dropped) and records
whose box it is. After registering, hand the customer the forwarder settings.
Register Gateway
Pre-flight checklist (before the customer points a gateway at us)
Forwarder mode must be the Semtech UDP packet forwarder — Basics Station cannot fan out to two network servers.
Region decides the port: us915 → 1701, eu868 → 1700, same port up and down.
EU868 only: two network servers sharing one gateway each track duty cycle alone — combined they can exceed the legal budget. US915 has no duty cycle.
Downlinks need a bidirectional gateway — uplink-only boxes receive fine but collars never get commands.
EUI
Label
Org
Region
Last uplink
Registered
Forwarder settings —
Customer-run ChirpStack connections. Creating one mints its ingest key (shown once),
stores their API token encrypted, and probes their instance. Full sequence with the
gotchas is in the Runbooks tab — the step this page cannot do for you:
assign their collars to their org (Devices tab) before their server carries them,
or the cross-tenant gate rejects the uplinks.
Connect a customer ChirpStack
Ingest key — shown ONCE, save it now
Paste into their ChirpStack → Application → Integrations → HTTP
Name
Org
Region
Transport
Status
Health
Last uplink
Set up
Devices
Actions
Loading…
Saved schedule presets across all users. Admins create presets in the
configurator;
here you can rename, delete, or assign them to any set of users and orgs
(assignees can load a preset in the configurator; only the owner and admins can edit it).