Asset Registry

Every physical tag you track (a tag attached to a forklift, a smart label on a pallet, a sensor on medical equipment) appears in Blecon Track as an asset. Assets give you a single view of where things are, where they've been, and what zone they're in, so you can make decisions based on real-time location data instead of manual checks.

For information about the physical hardware (tags, labels, hotspots), see the Hardware overview. To add new tags to your workspace, see Adding tags to Blecon Track.

What you see

Each asset shows:

• Current position: Where the tag is right now, displayed on the map.
• Last detected: When the network last detected the tag: a position, a sensor reading, or a sighting by a hotspot that gave no position.
• Last position: When the tag last got a confident position. A position needs a detection, but not every detection gives a position, so this time can be older than Last detected.
• Zone: Which zone the tag is currently in (if any).
• Status: Whether the tag is active (recently detected) or inactive.
• Trail: The movement path over a selected time period.

The assets list

The summary tiles across the top break your fleet down at a glance: how many tags are in a zone, how many haven't reported in over 24 hours, and how many have never been detected. Each tile is a shortcut — the counts that matter to you can be turned straight into a rule.

The assets list shows all tracked tags in your workspace. Devices running the Blecon Agent are listed on Devices, and anchors on Anchors, so neither appears here or in the counts above the list.

Narrow the list with the filter bar above it: by name, zone, zone keyword, team, type, keyword, custom field, last position and status. The filters stay set as you move to the map, trips, zones, alerts and statistics, and a set you use often can be saved. See Filters and saved filters.

Click any asset to open its detail page with position history, sensor data, and association information.

Exporting the list

Export sits beside the result count and downloads the list exactly as you have filtered it — every match, not the page on screen. Choose CSV or JSON. In a CSV file, each asset is one row, and each column has the name the asset list and the asset page use: Name, Asset ID, Type, SKU, Team, Keywords, Zone, Zone IDs, Registered, First Detected, Last Detected, Last Position, Latitude, Longitude, Accuracy (m), Status, Battery (mV), Scanned By and Last Scanned. Zones appear as both a name and an ID, because a zone can be renamed and the ID is what stays the same. Every custom field becomes its own column, named by its key, so you can open the file in a spreadsheet and match it against your own records on a field you already use, such as a purchase order number.

For JSON instead, click the arrow beside the button and choose it. The two files hold the same rows and the same columns; JSON keeps numbers as numbers, which suits feeding another system rather than a spreadsheet.

A large list takes a moment to prepare. The button says so and downloads the file when it is ready, so you do not have to keep the page open waiting for it to start.

If you are in a team, the file holds your team's assets only, the same as the list on screen.

Saved filters and regular updates

A filtered list you use often can be saved, applied again on any page with one click, and sent by email on a schedule. See Filters and saved filters.

Asset details

The detail page for an asset includes:

• Position history: A timeline of all recorded positions with timestamps.
• Last position from: The devices that detected the tag at its last position, newest first. These are the mobile devices that were within range the last time the tag was positioned, whether or not their sighting was the one that placed it: the first thing to check when an asset goes missing. A tag that stays still keeps this list current, because every sighting counts, not only the ones that moved the pin. Only devices registered in the workspace are named, and each links through to its own asset page. When another hotspot, such as a hub, has detected the tag more recently, the list shows Unnamed hotspot with the time of that sighting, so you can tell that the named devices did not detect it last. The missing-assets list carries the same information, and can filter by a device keyword, so "what did the night-shift devices last detect" is one query.

• Last Detected and Last Position: the two boxes at the top of the page, with an arrow from the first to the second. Under them the page says: "A position needs a detection, but not every detection gives a position."

  • Last Detected shows when the network last received any data from the tag: a position, a sensor reading, or a sighting by a hotspot. It turns red when the network has not detected the tag for 15 minutes or more, and shows Never when it has not detected the tag since it was added. The inactivity rule for the asset is in this box, because that rule uses the same time.
  • Last Position shows when the tag last got a confident position, then where that position is, and whether it is current or, for example, 3 h old in amber. Zones and alerts use this position. Beside the place name, the pin icon shows the coordinates when you point at it and copies them when you select it. Add rule under it adds a rule for that place, the same way Add rule on Last Detected adds an inactivity rule.

  The sensor readings, such as temperature, humidity and battery, are on the row below.

  When Last position is old but Last detected is recent, the network detects the tag but cannot work out where it is. When both are old, the tag is out of range of every hotspot, or the hotspots near it are offline.

  A tag has no GPS of its own. Its location comes from the hotspots that receive its data, so a hotspot must know its own location for the tag's location to be worked out. That is why a tag can report readings without a new location.

  A time with a dashed underline opens the Analysis panel. On the asset page that is the Last Position time, and Never under Last Detected. In the asset list, on the Missing page and in the map popup it is the last position time of every asset whose position is not current, and Never for a tag that has never been detected. For a position that is not current, the panel answers why the position is this old. It opens with how old the position is, for example No new position for 3 h, then the reason, then What to do. The reason has two parts. First, why the detections since the last position gave no new one, where the cause is known: for example, that the positions were less accurate than the accuracy filter, that the device which received the tag's data does not know its own location, or that positioning is turned off for the workspace. Second, when no hotspot has detected the tag for 15 minutes or more, for how long. What to do appears only when the cause shows what will fix it. For a tag that has never been detected, the panel shows how to activate that tag model instead, for example to peel off the backing of a smart label or to pull the activation tab, with a link to the tag's documentation. Select Get help with this tag to open a support request that already holds the asset, the state, the reason and the times.

  Select Details to see the rest: the hotspots that last gave the tag a location, and whether each one is online now (for the hubs and access points your account manages). When the position is current, select the Last Position time. The panel shows how the position was worked out, why it was shown as a new location (for example, that it was 23 m from the last one, more than the 15 m that counts as a move), and which zone it is in and which other zones competed. This part is a beta feature: it shows when beta features are turned on for the workspace. Each position in the history has the same button. When the asset has not moved, the panel says since when, and explains its latest position: the location on the map is then where the asset stopped, or the average of its positions since then. - Sensor data: Temperature, humidity, battery, and other sensor readings (when available). - Battery: The tag's supply voltage. Some tags also show an estimate of the battery life left, in weeks, with the voltage below it. The estimate comes from a model of that tag's cell, so it is approximate, and it never promises more than the tag's rated service life. Low means the cell is past the end of its useful voltage range. - Associations: Parent and child relationships with other assets. - Zone transitions: When the tag entered and left each zone. - Tags: Free-form labels you can add and remove inline (see below). - Custom fields: Key-value pairs set when the asset was added or updated.

Anchors

An asset can be designated as an anchor directly from its detail page in Blecon Track. Anchors are installed at known fixed positions and act as spatial anchors for indoor positioning: they tell nearby hotspots which area they're covering, enabling accurate location without GPS.

To mark an asset as an anchor, open the asset detail page and enable the anchor toggle. You can then set the tag's network zone and floor. The change takes effect immediately.

Asset types

Every asset can have a type: a single category like "vehicle", "case", or "pallet". Types are free-form: you type a value and it becomes available for other assets in the same workspace. The assets list shows a Type column and filter dropdown when at least one asset has a type set.

Types are useful when your assets fall into a small number of distinct categories that don't change often. For more flexible grouping, use tags.

Tags

Tags are free-form labels you attach to assets for filtering and grouping. Unlike asset types (one per asset), an asset can have any number of tags.

Examples: floor-2, high-value, maintenance-due, building-a, customer-acme

Adding and removing tags

On the asset detail page, you'll see a Tags row below the stats bar. Type a tag name and press Enter to add it. Click the × on any tag to remove it. Changes save immediately.

When adding an asset (via the Add Asset dialog or the API), you can set initial tags at the same time.

Filtering by tag

On the assets list, a Tags dropdown appears when any asset in your workspace has at least one tag. Select a tag to filter the list to only assets with that tag.

You can also click a tag chip on any asset row to instantly filter by that tag.

Tags via the API

Tags are a string array on the asset resource. Set them when creating or updating an asset:

# Add an asset with tags
curl -X POST https://api.blecon.net/tracker/api/workspaces/{workspace_id}/assets \
  -H "Authorization: Bearer {api_key}" \
  -H "Content-Type: application/json" \
  -d '{
    "asset_id": "urn:uuid:550e8400-e29b-41d4-a716-446655440000",
    "asset_name": "Forklift #3",
    "asset_type": "vehicle",
    "tags": ["warehouse-b", "high-value"]
  }'

# Update tags on an existing asset
curl -X PATCH https://api.blecon.net/tracker/api/workspaces/{workspace_id}/assets/{asset_id} \
  -H "Authorization: Bearer {api_key}" \
  -H "Content-Type: application/json" \
  -d '{"tags": ["warehouse-b", "high-value", "maintenance-due"]}'

# Filter the asset list by tag
curl "https://api.blecon.net/tracker/api/workspaces/{workspace_id}/assets?tag=high-value" \
  -H "Authorization: Bearer {api_key}"

# The same list with the counts the summary tiles show, from the same filters
curl "https://api.blecon.net/tracker/api/workspaces/{workspace_id}/assets?tag=high-value&include_stats=true" \
  -H "Authorization: Bearer {api_key}"

# List all tags in use
curl "https://api.blecon.net/tracker/api/workspaces/{workspace_id}/tags" \
  -H "Authorization: Bearer {api_key}"

The asset list returns tags only. Add entity_kind=agent to list devices instead, or entity_kind=all for both. Anchors appear only when you ask for them with is_anchor=true.

Setting tags replaces the entire tag list. To add a tag, include all existing tags plus the new one. To remove a tag, send the list without it.

Custom fields

Custom fields let you store your own key-value pairs on each asset: serial numbers, departments, purchase dates, or any other information your workflow needs.

Custom fields are set via the metadata object when creating or updating an asset:

curl -X POST https://api.blecon.net/tracker/api/workspaces/{workspace_id}/assets \
  -H "Authorization: Bearer {api_key}" \
  -H "Content-Type: application/json" \
  -d '{
    "asset_id": "urn:uuid:550e8400-e29b-41d4-a716-446655440000",
    "asset_name": "Forklift #3",
    "metadata": {
      "serial_number": "FL-003",
      "department": "warehouse",
      "purchase_date": "2024-06-15"
    }
  }'

Custom fields appear on the asset detail page under the Custom Fields heading. The keys are displayed as labels and the values alongside them.

You can also add and remove custom fields directly on the asset detail page. Click the edit icon next to the Custom Fields heading.

Filtering by custom field

The Custom field filter on the asset list appears as soon as one asset in the workspace has a custom field. Choose a field and type part of its value: department containing ware finds every asset whose department is warehouse. Leave the field as Any field to search every custom field at once. The filter is kept in saved filters like any other, so "every asset from purchase order 4471" can be one click.

The API offers the same, and more:

# Part of one field's value, case-insensitive
curl "https://api.blecon.net/tracker/api/workspaces/{workspace_id}/assets?metadata_key=department&metadata_search=ware" \
  -H "Authorization: Bearer {api_key}"

# Part of any field's value
curl "https://api.blecon.net/tracker/api/workspaces/{workspace_id}/assets?metadata_search=4471" \
  -H "Authorization: Bearer {api_key}"

# Exact value of one field
curl "https://api.blecon.net/tracker/api/workspaces/{workspace_id}/assets?metadata_key=department&metadata_value=warehouse" \
  -H "Authorization: Bearer {api_key}"

# Several fields at once; every pair must match
curl "https://api.blecon.net/tracker/api/workspaces/{workspace_id}/assets?metadata=department=warehouse&metadata=serial_number=FL-003" \
  -H "Authorization: Bearer {api_key}"

# The custom-field keys in use, for building a picker
curl "https://api.blecon.net/tracker/api/workspaces/{workspace_id}/metadata-keys" \
  -H "Authorization: Bearer {api_key}"

metadata_key on its own matches every asset that has the field, whatever its value. The search parameter of the asset list also reads custom-field values, so one search box covers names, IDs and fields.

Finding a tag

When you need to physically locate a tag, you can make it beep from Blecon Track. On tags with a built-in buzzer, the beep button is shown on the asset; sending it makes the tag beep and flash its lights so you can find it in a room, a vehicle, or a stack of pallets.

Because tags conserve power between connections, a beep is queued and delivered the next time the tag connects — usually within a few seconds, as Blecon Track asks the tag to connect promptly. While a beep is pending the button shows Cancel beep; it returns to Beep once the tag has connected and carried out the command, which is your confirmation that it was received. Cancel a pending beep at any time.

Archiving

Tags you're no longer using can be archived so they drop out of your live view without being deleted. Archived tags are hidden from the asset list, the map, and statistics, keeping your day-to-day view focused on what's in use. Use the Archived only or Include archived filter on the asset list to see them, where they carry an archived badge.

You can archive and unarchive a tag by hand from the asset list. Blecon Track can also archive tags for you: turn on auto-archive in workspace settings and set an inactivity period (1–90 days, default 30). Any tag with no position update for longer than that is archived automatically, and the check runs every hour.

Archiving is never permanent. Unarchive a tag manually at any time — and if an archived tag reports a new position, it is unarchived automatically and returns to your live view.

Related pages

• Hardware overview
• Registration Tools
• Map
• Asset associations
• History Store
• anchors
• Tracker API

---

Questions? Contact Blecon support — we're happy to help.