Positioning settings reference
Complete reference for all positioning settings configurable per network.
Positioning profiles
The positioning_profile field selects a named preset instead of setting each value individually. See Positioning settings for guidance on choosing one.
| Setting |
API field |
Default |
Values |
Description |
| Positioning profile |
positioning_profile |
balanced |
fast, balanced, accurate, custom |
Named profiles are maintained by Blecon and resolve to tuned values at read time — retuned profiles apply automatically. custom means the record's own stored values are used. |
A request may set a named profile or individual tuning fields, never both. Setting any tuning field switches the record to custom, after materialising the values the previous profile was providing (so untouched settings keep their effective values).
Profile values
Network-level values resolved by each profile:
| Value |
Fast |
Balanced |
Accurate |
Collection window (positioning_window_seconds) |
30 s |
150 s |
300 s |
Movement threshold (positioning_movement_threshold_meters) |
10 m |
40 m |
75 m |
Heartbeat interval (positioning_heartbeat_seconds) |
300 s |
600 s |
1,200 s |
Instant positioning (positioning_instant_enabled) |
on |
off |
off |
Signal strength cutoff (positioning_rssi_cutoff) |
none |
-90 dBm |
-80 dBm |
Workspace-level filters resolved by each profile (Blecon Track):
Networks and workspaces configured before profiles existed follow the balanced profile automatically. Anything deliberately tuned is treated as custom and keeps its stored values.
Basic settings
| Setting |
API field |
Default |
Min |
Max |
Description |
| Positioning enabled |
positioning_enabled |
true |
— |
— |
Enable or disable positioning for this network. Positioning is available on Pro and Enterprise plans. |
| Coordinate system |
positioning_coordinate_system |
gps |
— |
— |
gps (lat/lon) or local (x/y/z meters) |
Update behaviour
| Setting |
API field |
Default |
Min |
Max |
Unit |
Description |
| Movement threshold |
positioning_movement_threshold_meters |
30 |
10 |
10,000 |
meters |
Minimum movement to trigger a position update |
| Heartbeat interval |
positioning_heartbeat_seconds |
600 |
60 |
86,400 |
seconds |
Periodic update interval (even without movement) |
| Instant positioning |
positioning_instant_enabled |
false |
— |
— |
— |
Update position immediately on a single strong, well-located signal, without waiting for the collection window |
| Signal strength cutoff |
positioning_rssi_cutoff |
unset |
-120 |
-20 |
dBm |
Ignore signals weaker than this when positioning; unset uses all signals |
Data collection
| Setting |
API field |
Default |
Min |
Max |
Unit |
Description |
| Collection window |
positioning_window_seconds |
90 |
30 |
3,600 |
seconds |
Time window for collecting measurements before calculating a position |
Quality targets
| Setting |
API field |
Default |
Min |
Max |
Unit |
Description |
| Target accuracy |
positioning_quality_target_accuracy |
20 |
— |
— |
meters |
Positions meeting this threshold are delivered faster |
| Target age |
positioning_quality_target_age |
120 |
60 |
3,600 |
seconds |
Positions calculated within this age of signal data are delivered faster |
System thresholds
These values are not configurable but affect positioning behaviour:
| Parameter |
Value |
Description |
| Good accuracy tier |
< 50 m |
Preferred hotspots for positioning |
| Acceptable accuracy tier |
50–100 m |
Used when no good hotspots available |
| Max hotspot location age |
~17 min (1,000 s) |
Hotspots with location data older than this are excluded |