Connect to a CollarID device via Bluetooth to configure schedules and radio settings.
⚠ Requires Chrome or Edge — Web Bluetooth is not supported in Firefox or Safari.
⚠Some Windows users have reported issues with the BLE scan and USB DFU flashing flows — we're tracking it. macOS or Linux is recommended in the meantime.
Not connected
Offline CONFIG.CSV mode.
Build a schedule and radio config, then Export CSV and copy the file to the SD card root as CONFIG.CSV.
The file replaces the device's entire configuration on next boot — including LoRaWAN keys, which the browser can't fetch (they're tied to the device's identity).
If you're only changing the schedule, Import the card's existing CONFIG.CSV first so the correct keys are preserved.
No device connected
Click "Scan for Devices" above to find nearby CollarID collars.
Battery
—
SD Card
—
Firmware
—
System
—
GPS
—
Live Sensors
Awaiting update…
Status updates arrive automatically via BLE notifications.
Connect to a device to load schedules.
System
Disengaged
● unsaved
Order matters. When two schedules could run the same hour on the same day, the one higher in the list wins. Put a "weekends only" or dated schedule above the everyday one it overrides — use the ↑ ↓ buttons.
Overlapping schedule windows
On any given day, each hour can belong to at most one schedule. Higher in the list wins when two schedules share an hour on the same day — so a "weekends only" or dated schedule goes above the everyday one it overrides. Fix the conflicts before sending to the device.
Who runs when
Each cell is one hour of one day, coloured by the schedule that will run it. When two schedules could run the same hour, the one higher in the list wins. Hours are UTC; the lower axis shows
No schedules. Add one with the button above.
sh = solar-hours per day: the equivalent hours of direct, full-intensity sunlight (1000 W/m²) needed to offset daily energy use. See the Power tab for a breakdown by lighting conditions.
GEOFENCE ZONES
Zones are delivered over the air at the collar’s next check-in — not over this Bluetooth link. Manage them here or on the Remote Schedule page.
Connect a collar, then press Refresh to read its zones.
Delivered and verified over this Bluetooth connection in a few seconds — no LoRaWAN needed. The collar applies the same safety rules as a radio push. A detach zone puts the release unit into a faster check-in mode (higher battery use) until it fires, expires, or you delete it.
Bench test a location:(bench firmware only — production builds ignore test fixes)
MAGNETOMETER CALIBRATION
Corrects the compass for the collar’s own battery, metal and electronics. Do it before each deployment
and after attaching or removing an add-on. Takes
about a minute of turning the collar in your hands. The recorded data stay raw; the SD Card viewer applies
the calibration.
FACTORY RESET — BEFORE SHIPPING
Erases everything recorded during evaluation and returns the collar to stock, over this Bluetooth connection:
all recorded data (audio, accelerometer, GPS, METADATA.CSV), geofence zones, the uplink replay ring and LoRa
session state, and every setting (disengaged, default schedules, no radio credentials). The paired release
add-on and the service logs are kept. Takes up to a couple of minutes on a full card.
Connect to a device to load radio config.
LOST-MODE BEACON ENCRYPTION…
Optional. With a key, the collar’s lost-mode beacon carries its position encrypted: anyone can still hear
which collar it is and home in on its signal, but only a receiver holding the key (the
Handheld Receiver page with your sign-in, or your own receiver with the exported key)
reads the position in the beacon. Without a key the beacon is plaintext, as it has always been. Regular LoRaWAN uplinks are
encrypted either way. See the manual.
Optional. With a key, everything the collar sends over the direct radio is encrypted: its regular reports and
its lost-mode beacon. Anyone can still hear which collar it is and home in on its signal, but only a
receiver holding the key (the Handheld Receiver page with your
sign-in, or your own receiver with the exported key) reads what it sends. Without a key both are plaintext, as
they have always been. Regular LoRaWAN uplinks are encrypted by LoRaWAN either way; this key is not added to them.
See the manual.
Provisioning asks the server for this collar’s key (derived from your organisation’s master at the next
generation), writes it over this Bluetooth connection, checks the collar’s echo against what the server issued and
records the result on the server. Rotating the organisation’s generation is an administrator’s step on the
Admin page: every collar in the organisation is then stale until it is re-provisioned over Bluetooth, and each
keeps its old key until it is.
On a collar older than the MkII Mesh version of the collar, the key goes over in one step instead: that collar
cannot answer over Bluetooth, so it confirms on its next network report (only while it is switched on and
recording), and this card shows the result once the server has it.
Local Devices
Add-ons paired with this collar — detachment mechanism, and more to come.
Add-ons announce themselves when they check in with the collar. Magnet-wake an unpaired one nearby, then Refresh to see it and pair it — pairing is what makes it a scheduled add-on.
Thread add-ons are disabled: the next CONFIG.CSV you push carries thread_checkin_interval_s,0 and the collar opens no rendezvous windows.
Both hours are inclusive — the end hour is fully counted.
Days
Only between dates
From
Until (inclusive)
Overlapping time window
GPS
GPS
Fix everymin
Accuracy
Accuracy is the fix radius the collar waits for before it stops searching:
Low ≈ 30 m,
Medium ≈ 20 m,
High ≈ 5 m.
A tighter radius holds the GPS on longer per fix, so it costs more battery.
Dynamic sampling (activity-based)
Adjusts fix rate by movement intensity. The interval above is used when the animal is still. Enter thresholds in 0.01 g units (e.g. 20 = 0.20 g).
Behaviour
Typical VeDBA (g)
Threshold value
Resting / standing
< 0.05 g
< 5
Slow walk / foraging
0.05 – 0.20 g
5 – 20
Brisk walk / trot
0.20 – 0.50 g
20 – 50
Run / active flight
> 0.50 g
> 50
Medium VeDBA threshold
Medium interval (min)
High VeDBA threshold
High motion interval (min)
Sensors
Light
Environmental
Light sample everymin
Environmental sample everymin
Environmental sampling is fixed at 5 minutes.
Particulate (PM)min
Particulate sensor is not installed on this device.
Microphone
Microphone
Record continuously
Recordmin everymin
Continuous recordings are split into separate files on 60-minute boundaries.
Storage
Sample rate
Microphone gain
Low bits dropped
Accelerometer
Accelerometer
Sample rate
Range
Magnetometer
Magnetometer
Sampling
Sample everymin
Radio (per schedule)
LoRaWAN
Uplink everymin
Transmit on every new GPS position
LoRa and LoRaWAN share one radio — only one can be active per schedule. Raw LoRa is the direct link to a Handheld Receiver; deployments on the CollarID network use LoRaWAN.
Raw LoRa
Transmit everymin
Transmit on every new GPS position
When Transmit on every new GPS position is off, GPS fixes are batched and sent together on each scheduled transmit to save power.
Saved Schedules
Save current set
Add at least one schedule before saving.
Owner
Your saved schedules
No saved schedules yet.
Log in to save and load schedules.
Edit Radio Config
LoRaWAN
Region
Auth Method
Dev EUI (16 hex chars)
Join EUI (16 hex chars)
App Key (32 hex chars)
Nwk Key (32 hex chars)
Dev Addr (8 hex chars)
Nwk S Key (32 hex)
App S Key (32 hex)
F Nwk S Int Key (32 hex)
S Nwk S Int Key (32 hex)
LoRa (P2P)
Spreading Factor
Bandwidth
Coding Rate
Sync Word (hex, e.g. 12)
Frequency (MHz)
Listen after transmit
Opens a brief receive window (~250 ms) right after each LoRa
transmission so a nearby Handheld Receiver can reply. The radio never listens at any other time;
battery cost is negligible at normal transmit intervals. Off = today's transmit-then-sleep behavior.
Lost Mode
After the activation time passes, the collar transmits recovery beacons at the interval below.
Enable Lost Mode
Tx Interval (min)
Activation Time
Mortality Detection
Flags every transmission and sends an extra report at the interval below once the animal has been motionless for the trigger window. The rest of the collar's schedule is unchanged, and the flag clears by itself if movement resumes.
Enable Mortality Detection
Keeps the accelerometer running continuously so movement is always being watched. Nothing extra is written to the SD card, and any accelerometer schedule you have set still records exactly as before. Budget a small, constant power draw — the same one dynamic GPS sampling already uses.
Trigger After (hours motionless)
Report Interval (min)
Heads up
Calibrate the magnetometer
Away from metal and electronics: not on a steel bench, not next to a laptop or phone.
Press Start, then turn the collar slowly through every orientation: a few slow figure-8s, then a full roll about each axis.
Keep turning until the ring is full, usually 30–60 s. The collar gives up after 2 minutes. If the Bluetooth link drops, keep turning: the collar carries on by itself.
Starting…
On the collar: the LED pulses cyan while it collects, faster as the ring fills; two green flashes, then blue, when it is done; two red flashes if it failed or was stopped.