Skip to main content
A location signal is a network identifier — currently an IP range, with WiFi network matching planned for a future release — that you register against a location. When a device’s heartbeat arrives from a matching network, AssetGullak automatically records that location as the device’s Last Seen Location, without anyone manually updating anything. This is separate from a device’s Assigned Location (the location an admin has deliberately set). Last Seen Location is detected automatically and answers a different question — not “where does this device officially belong,” but “where does it actually appear to be right now.”

​
What location signals are used for

  • Answering “where is this device right now” without physically tracking it — useful when people and devices move between offices or project sites
  • Multi-site visibility — see at a glance which of your registered locations each device last checked in from
  • No manual upkeep — once a signal is registered, matching happens automatically on every heartbeat; nobody has to update a device’s location by hand

​
How matching works

  • Checked on every heartbeat a device sends
  • If the device’s current IP falls within one of your registered IP ranges, its Last Seen Location is updated to that location
  • If the IP doesn’t match any registered range — for example, someone working from home, or a client site — Last Seen Location is left unchanged, not cleared. It reflects the most recent confirmed sighting, not “current location this instant.” A device last seen at your Gurgaon office three days ago will keep showing Gurgaon until it’s next seen on a registered network, not flip to “unknown” the moment it leaves.
  • Two different offices can’t register overlapping IP ranges — if a range you enter overlaps one already registered elsewhere in your company, it’s rejected with an error naming the conflicting location, so a typo doesn’t silently misclassify devices later

​
Adding a signal

Under a location’s detail page, in its Network Signals section, click Add signal.

​
Writing a CIDR range

A CIDR range describes a block of IP addresses, written as address/prefix — for example 103.87.59.0/24. The prefix says how much of the address is fixed:
  • /32 — one single, exact IP address, nothing else. Use this if you only have one specific address to register, e.g. 103.87.59.234/32.
  • /24 — a typical single-office block, matching every address that shares the first three numbers (e.g. 103.87.59.0/24 matches 103.87.59.0 through 103.87.59.255).
If you’re not sure whether your office has a single static IP or a wider assigned block, check with whoever manages that office’s internet connection before registering a /32 — some connections rotate slightly within a range even when described as “static,” which would cause a /32 to silently stop matching.
WiFi Network signals aren’t active yet. The type exists so floor-level location detection (multiple WiFi access points mapped to different locations sharing one office IP) can be added without a schema change later. Creating one today won’t cause an error, but it also won’t do anything — devices don’t yet report which WiFi network they’re connected to. This will be documented separately once it’s live.

​
Editing or removing a signal

Each signal has an overflow menu (⋮) with Edit and Delete. Editing a signal’s value re-validates it the same way creating one does — an invalid CIDR or an overlapping range is rejected. Deleting a signal doesn’t affect any device’s current Last Seen Location; it just stops being checked on future heartbeats.
  • Locations — set up the location itself before adding signals to it
  • Devices — see Last Seen Location on a device’s detail page