Watching people and assets

/admin/monitor/entity: Monitor → Entity Tracker

This guide is for the people who watch a building day to day: security, facilities, the operations desk. It covers four questions:

• Where is this person or this thing right now?
• Where has it been today, and over the last few days?
• What happened on a particular day, in order?
• Has anything gone wrong that needs someone to act?

Everything here works on entities: the forklift, the cleaner, the oxygen cylinder, each with a tag attached. If you have not set any up yet, start with People and assets. A tag that is not attached to an entity still appears on the device pages, but only by its MAC address.

All times on these pages are in your organisation's local time, whatever time zone your own computer is set to.

Before you start: what Omaya can and cannot see

Omaya knows where a tag is because gateways hear its radio signal. That has three effects you will see on every page below.

Every answer on these pages comes down this chain. A wrong room is a positioning question; a stale or offline card is a question about the tag and the gateways around it.

Omaya never sees anyone leave. It only stops hearing them. A stay ends at the last moment the tag was heard in that zone. If the next sighting is in another zone, the person has moved. If there is no next sighting, Omaya can only say the tag went quiet.

"Not heard" does not mean "gone". A tag goes quiet when it leaves the site, but also when it is somewhere no gateway covers, when its battery dies, when it is in a drawer, or when a model that sleeps while still has stopped sending. The pages say not heard and not left for that reason.

A zone is the answer, not a dot. Omaya decides which zone a tag is in. On the maps the marker is drawn at the middle of that zone, or at the gateway that heard it when the zone has no shape drawn. Do not read the marker's exact spot as an exact position.

Find where someone or something is now

1. Open Monitor → Entity Tracker.
2. Type part of the name or the identifier (staff number, plate, asset tag) into Search name or ID…. The cards narrow as you type.
3. Read the card. The room, in large type beside the pin icon, is where it is. The line under the name tells you how fresh that answer is.
4. Click the card for the entity view, described in The entity view below.

Check it worked. The card you are left with shows the right name, and its status line says Online with a time a few seconds ago.

From anywhere in Omaya, the search box in the top bar also finds an entity by name, identifier, label or the tag it carries; choosing the result opens this page with that entity's panel already open.

For example, at 21:40 Kumar Selvam, the Security Supervisor, wants to know where Hafiz Ismail is on his round. He types Hafiz and the one card left says Online · 8s ago, Car park entrance with Level 1 under it, Here for 3m, Moving now.

The page refreshes itself every 15 seconds. The badge at the top right says Live · just now, or how long ago it last refreshed. If a refresh fails, the page keeps what it last knew and says so in a yellow banner: Could not refresh — showing what was known at 10:42. Retrying. Nothing on screen is wiped by a failed refresh, so if you see that banner, treat the cards as a few minutes old.

The figures across the top

On the left are four status tiles, All, Online, Stale and Offline, each with its count. Each tile is also a filter: click Stale to see only the stale entities, and All to see everyone again.

Beside them are four facts about the site right now:

Fact	What it counts
people on site	People heard on site (online or stale). Anyone outside on GPS is not counted.
assets on site	The same, for assets.
moving now	Entities whose tag's motion sensor moved in the last 90 seconds.
low battery	Entities with a tag at 20% battery or less.

The tiles and the facts follow the filters below them, so with All labels set to Night shift they count the night shift only.

Narrowing the list

Control	What it does
All / Online / Stale / Offline tiles	Show one status. Each tile's count is for everything your other filters allow, so picking Online does not hide the size of the other groups.
All types / People / Assets	Show only people or only assets.
All locations	Show one site.
All labels	Show entities carrying a particular label, such as Night shift or Contractors.
Sort	By status (the default), name, zone, time in zone, or battery (low first).
Clear filters	Appears once any filter is set; puts everything back.
Cards / List buttons (top right)	Switch between cards and a dense table. Your browser remembers which you chose.

Only active entities are listed. An entity set to inactive keeps its history but drops out of this page.

If your role is limited to some labels (Entity access on System → Roles), this page, the entity view and the names on Right Now show only the entities carrying those labels. See People and assets.

Online, stale, offline

Status	Meaning
Online	Heard in the last 2 minutes.
Stale	Last heard 2 to 15 minutes ago. Often just a gap between sightings; worth a second look if it lasts.
Offline	Not heard for over 15 minutes, or no tag attached at all.

Someone outside on GPS stays Online for 15 minutes between positions, as a tracker on the move reports less often than a gateway hears a tag. The page opened from Entity in the menu uses a wider window, 5 minutes for Online and 15 for Stale, so it can still say online while the Entity Tracker already says stale.

In card view the entities are one flat list, not grouped by floor or room. Online and stale entities come first under On site, as full cards with an edge in their status colour: green for online, amber for stale. Anyone outside on GPS follows under Outside (see Indoor and outdoor). Offline entities are last, under Offline, as a compact strip of small tiles, so a quiet evening is not buried under a wall of empty cards. The section headings appear only when there is more than one group to show.

Reading a card

An on-site card shows, top to bottom:

• Who: the photo, initial or asset icon, with a dot on it in the status colour. Beside it the name, then Person or Asset and the identifier, then the status line: Online · 12s ago, Stale · 6m ago. No tag bound means the entity has no tag and cannot be tracked.
• Where, as the headline: the zone in large type, and under it the floor and the site.
• Two figures, always in the same place:
  • Here for: how long since the current stay in this zone began.
  • Last moved, for a tag with a motion sensor: how long since the tag's own motion sensor last moved, or Moving now (under Movement) when it moved in the last minute and a half. This comes from the motion sensor, not from the position changing, so a trolley can be Moving now inside one room. A tag with no motion sensor shows Last heard instead: how long since a gateway last heard it.
• Along the foot: signal strength, the tag's battery (red at 20% or lower) and, where a sensor in that zone reports it, the temperature where the entity is. At the right end, a small label saying how Omaya placed it; see the Placed by row in the entity view below.

If the entity has more than one tag, the battery shown is the best of them.

A card that says Not placed in a zone yet is being heard, but positioning has not put it in a zone. That is normal for the first minute or so after a tag wakes up. If it lasts, see Troubleshooting.

An offline tile is a single line: the name, then where and when it was last heard, for example Sales area · 2d ago, and the battery. Hover over it for the full wording. Not heard this month means there is no sighting in the current or the previous month.

Every card and tile has a small play button. It opens Movement Replay for that entity.

The entity view

Click any card, tile or list row. The entity opens in a large view over the list: the floor plan on the left, the facts on the right, and the day strip and timeline across the bottom. On a narrow screen it is one column.

At the top: the name, its type and labels, its status, and one line saying where it is, such as In Director Room · Level 5 · for 23 min · moving. The buttons are Movement replay, Edit (this entity on the Entity page, if your role can see it) and Attendance for a person or Utilisation for an asset.

Control	What it does
‹ › or the ← → keys	The previous or next entity, in the order the list shows them, without closing the view. Use them to go through everyone quickly.
↗ Open as page	The same view as a page of its own, in a new tab, for a bookmark or to send someone the link. Closing it there shows the list.
× or Esc, or a click outside	Close the view. The list is exactly as you left it, filters and scroll included.

The sections, in order:

Floor Plan. The floor the entity is on, with gateways drawn as squares, the gateway hearing it now outlined in blue, and a red pin for the entity. The legend says where the pin came from: Entity (zone centroid) (the middle of its zone), Entity (gateway proximity) (next to the gateway that hears it), or Entity (live position). When there is no pin, a line under the plan says why: never detected at any site, heard but not in a zone, in a zone with no shape drawn, or not heard for more than 10 minutes.

Under the where-line at the top: Here for (hover for when the stay began), Last heard, Last moved (from the tag's motion sensor; no motion sensor means it cannot report movement) and, where the zone reports it, Temperature. The top follows the live feed while the view is open; the sections are loaded when you open the view. The floor plan and the day strip under it stay in view while you scroll the facts on the right.

Today. One line: when it first turned up today, how many rooms it has been in, and the time tracked (silences not counted), such as In 10:41 · 4 rooms · 1h 14m tracked. Under it, against its usual first arrival over the last 14 days (at least three days seen): About the usual time, Later than usual or Earlier than usual, more than 30 minutes either way, with the usual time. In since before today means it was already on site at midnight.

How it is placed. The tag and its battery (with the 24-hour low when it differs), the gateway that placed it in its room and at what signal, and the gateway its last packet came through and how long ago. The two gateways can differ: the room comes from the gateway that has been steadily strongest, while any gateway that hears the tag can carry its latest packet.

Toilet Status. Only when the entity is in a zone set up in the Toilet Hygiene app: the toilet's dirty score against its target and when it was last cleaned.

Outside · last 24 h. Only when the tag has a GPS position in the last 24 hours, from a GPS tracker or a phone running Omaya Scout. While the entity is indoors and the phones only placed it at one place (typically the office itself) with no trips, this is one line, Only at office campus (placed by phones) — no trips, and Show map opens the map. Otherwise a street map shows the route with each stop numbered, then the stops and trips, newest first. Replay on the map opens the journey in GPS Replay. See Indoor and outdoor.

For a person, time at the place where they spend the night reads At home, with its times and no position, marker or route. Omaya finds that place from their tracker's positions at night; nobody enters it. See How Omaya knows someone is at home.

Day strip (under the floor plan). Where it was across the day as coloured blocks, from 08:00 to 20:00 (wider when it was seen earlier or later), with a line at the current time and the rooms and their totals underneath. Hover a block for the room, the time it arrived and how long it stayed. Today, Yesterday and the earlier dates switch the day.

Timeline · last 5 days. See the next section.

Read the Timeline

The Timeline is the entity's movement over the last five days, one row per zone visit, newest first.

Omaya never sees anyone leave; it only stops hearing them. A visit ends at the last sighting in that zone, and a silence of five minutes or more is shown as what it is — a stretch of time when nobody heard the tag.

Column	Meaning
Arrived	When the visit began.
Dwell	How long it stayed. The visit happening now carries a now badge and keeps counting.
Zone	Where. A grey · no zone after a floor name means it was on that floor but outside every drawn zone. A site name after the zone means a different site from the usual one.

Each day starts with a bold heading: Today · 01-Oct-2026, Yesterday · …, then plain dates. The newest day is open. Older days are folded to one line with a count, such as 28-Sep-2026 · 14 visits. Click a day heading, or select it with Tab and press Enter, to open or fold it.

Two rules shape the rows:

• Short breaks in one zone are one visit. Sightings in the same zone less than 5 minutes apart are joined. Otherwise a person sitting still at a desk would show as dozens of tiny visits.
• Silences of 5 minutes or more show as a row of their own, for example Not heard · 1h 20m. That row is the honest answer to "where were they between 12:10 and 13:30?": Omaya does not know.

Replay a day (Movement Replay)

Movement Replay plays an entity's day back on the floor plan, like scrubbing through CCTV. It replaced the older Trail Replay.

Open it

1. Open Monitor → Entity Tracker.
2. Click the play button on the entity's card, tile or list row. Or open the entity view and click Movement replay.

The replay opens on the latest day the entity was heard: today if it is still around, otherwise the last day it was seen. For today it starts at the current stay, which is where the entity is now. For an earlier day it starts at the first stay of the day.

Pick a day

3. Use the ‹ and › buttons beside the date to step back or forward one day, or click the date to pick one. You cannot step past today.

A day is your organisation's day, midnight to midnight. A stay that began the day before and carried on past midnight is included, and its start shows the earlier date and time.

Across the top, small figures sum up the day: how many stays, how many zones, and how long the entity was heard in total.

Play it

4. Click Play. The marker moves from zone to zone and the list on the right highlights the current stay. Click Pause to stop.
5. Choose a speed: 1 min/s, 10 min/s (the default) or 1 h/s. That is how much of the day passes per second of playback.
6. Use the Previous move and Next move buttons on either side of Play to jump to the start of the stay before or after.

Playback skips the stretches when nobody heard the entity, because there is nothing to watch. It stops at the end of the last stay.

Jump to a moment

• Drag along the timeline at the bottom, or click anywhere on it. Hovering shows the time and the zone at that point, or not heard.
• Click a stay in the list to jump to its start.
• Whole day shows midnight to midnight. Fit to movement zooms the timeline in to the part of the day that has stays in it, which helps when someone was only on site for two hours.

Key	Does
Space	Play or pause
← / →	Previous or next move
Esc	Close the replay (and then, pressed again, the entity view)

Read what it shows

The card in the corner of the map follows the playhead. It shows the time to the second, the zone, since 09:12 (1h 4m), and the gateway that heard it with the signal strength. In a gap it says Not heard and Last heard in Pantry at 12:10. Before the first sighting of the day it says Not seen yet.

On the floor plan, the current zone is filled in and the gateway that heard the entity at that moment is highlighted in blue. The marker sits at the middle of the zone. When the entity changes floor, the map changes floor with it. No floor plan for Level 3 means that floor has no plan uploaded yet. The stay list and the timeline still work.

On the right:

• Time by zone: a bar for each zone, longest first, with the total time spent there that day.
• Stays: each stay with its colour, its zone, its time range and its length. A stay that runs to the current moment ends in now; one that runs past midnight ends in midnight. Silences of 5 minutes or more appear between stays as Not heard · 25m.

Merged and Raw

Above the stay list are two buttons.

• Merged (the default) joins sightings in the same zone that are less than 5 minutes apart, giving one row per zone visit. This is the view to read.
• Raw shows every piece positioning recorded, which can be many short rows when a tag sits near the boundary between two zones.

A stay marked brief lasted under two minutes and sits between two stays in the same other zone, for example Office, Corridor (brief), Office. That pattern is usually the signal moving rather than the person: the tag was near a wall and a gateway in the next room heard it better for a moment. In Raw view the day's figures also count how many brief stays there were.

Replaying a single device instead

To replay one tag rather than an entity, open Monitor → Live Monitor, go to the Sensors tab, click the device, open its Movement tab, choose a range, and click Replay. That opens a separate Movement Replay page for the device, with a date range and a Load button. The dates on that page are whole days in your organisation's time. For a tracker with GPS it also draws the route outside on a street map, with your geofences — see Indoor and outdoor.

Being told instead of watching

Nobody watches a screen all day. To be told when Floor scrubber 2 leaves Level 3, or when anyone labelled Contractors enters the plant room, make a rule that watches the Person / asset or the Label with Entered / left a place. See Your first rule.

Who was in, and for how long (Attendance)

/admin/report/attendance: Reports → Attendance

The Timeline answers "where was Hafiz", one person at a time. When the question is "who was in on Saturday", "what time did the cleaning team arrive this week" or "who is still here", open Attendance instead. It reads the same stays as the Timeline, for every person on the Entity page at once, and gives for each person and day:

• First in and last out, on your organisation's clock.
• Time on site: the person's stays joined up, so two rooms, or two tags on one person, are never counted twice. A silence shorter than Gap that ends a visit (15 minutes, 30 minutes, 1 hour or 2 hours; 30 minutes unless you change it) is taken as a walk down a corridor no gateway hears, and counts as on site. A longer one starts a new visit.
• Time on each floor, counting only the time actually heard there, so the floors can add up to a little less than the day.
• Time outside on GPS, for someone carrying a GPS tracker, shown separately and never counted as on site.

Narrow it with Location, Floor and Group (tag), which lists the labels on the Entity page, such as a department, a shift or a contractor firm. Click a name for that person's days and every stay behind them. Export CSV downloads what you are looking at.

Read it with the same limits as the rest of this page. Assets are not listed, only people (for assets, see Reports → Asset Utilisation). A tag counts for whoever held it on that day, so a badge handed from one person to another is not credited to the wrong one. Someone not carrying their tag is not seen. A tag left on a desk overnight keeps its owner on site, and a day that runs through midnight is marked ↤ or ↦. A day on which the gateways sent nothing says no data rather than showing everyone absent.

Attendance shows named people's times, so it has its own permission, View Attendance Report: your administrator can give it to the people who run the register without giving them the rest of Reports. See How many were here for how it differs from the counting reports.

Right Now

/admin/monitoring/right-now: Monitor → Right Now & Live Alerts

Right Now is the page to leave open on a wall screen. It answers three questions without a date picker: which zones have someone in them, is that more or less than a moment ago, and what has just fired. It is also where you see each zone against its capacity: the separate Zone occupancy page has been folded into it, and its old address opens Right Now.

1. Pick a Venue, or leave it on All venues.
2. Pick a Time window: 5m, 10m (the default), 15m, 1h, 6h or 24h. A tag counts in a zone if it was there at any point in the window.
3. Optionally pick one or more Zones.

Your browser remembers these choices. Clear filters resets them.

Check it worked. The line at the end of the filter bar names what you picked, for example Filtered: venue: Level 2 · last 15 min, and the Zone occupancy heading shows the same window.

The page shows:

• The big number: how many were detected in the window, across the zones you picked. The line under it says who that is, for example 3 people · 6 tags not assigned to anyone · last 10 minutes.
• Four tiles: In zones now (the same count, split the same way), Active zones (out of how many are configured), Alerts (last hour) and Low battery (tags below 20%). Without View Anomalies there are three: Alerts (last hour) is left off.
• Zone occupancy, one section per floor. Each venue is a floor, and the floors are in building order by level. A floor's heading shows its short label (such as L4, G or B1), its name, how many of its zones are in use, a strip showing which of its zones have people in them, and the floor's count. Click a floor's heading to fold it away; your browser remembers which floors you folded. With more than one floor, a row of floor chips above the sections, each with its count, jumps to that floor (and opens it if it was folded). A floor's count is normally its zones added up. When a badge system reports the whole venue, or every way in and out of it is counted at the doors, the heading says building count or door count and uses that figure instead.
• Inside each floor, a tile per zone with its count and a trend against the window before, so with the 10-minute window it compares with the 10 minutes before that. ↑ or ↓ shows a change of more than 5%; flat means no change. A zone counted by a radar or counting sensor says people · radar and how many of them carried a tag. Every other zone counts tags: it says people when every tag is assigned to a person or asset, and tags when some are not, with a line underneath that splits it, for example 1 person · 2 tags not assigned to anyone. Assign the loose tags to an entity under Entity to have them counted by name.
• On each tile, a zone with a capacity says how full it is: Empty, Normal, Busy (half of capacity or more), At capacity or Over capacity, its bar turns from green through amber to red, and the line under the bar reads 3 of 20 capacity · 15%. A zone with no capacity set says No capacity set; set it on the zone under Space. A zone with an area also shows people per 100 ft². On the right of that line, the next expected peak from the forecast (~5 at 14:00, red when it reaches capacity), and under it the window in twelve bars.
• Live alerts: rule firings (Rule fired, or Rule failed when none of its actions went out) and device status changes (a device going offline or coming back), grouped as Critical, Warning, Info and Success. Click a group heading to fold it, and an alert to open its detail. The feed keeps the 50 most recent. Without View Anomalies this panel is left off and Insights takes the full width.
• Insights: short observations, such as a zone far busier than the rest or activity dropping across several zones.

Monitor → Last 24 hours has been retired. A zone going over capacity and back under, and a battery falling to low or critical, are now System events on the Activity Log (System → Activity Log); see Who did what. Everything else it listed is on Monitor → Central Alerts and the Activity Log.

Click any zone tile to open its panel. The top shows the count against capacity; four tabs underneath:

Tab	What it shows
Now	Who is in the zone: each entity by name with the tag it carries, then any tags not attached to an entity, under Not assigned, with their signal, battery and last sighting
History	The last 24 hours, one bar per hour, each the busiest moment of that hour. Blue bars were counted by a sensor (everyone); grey bars from tags (tag carriers only)
Forecast	The expected count for the next 24 hours with its likely range, the expected peak, and the capacity line. A zone needs a day of history before it has one; forecasts refresh hourly
Compare	Pick another zone and 7 days or 30 days: how many different tags were in each zone, day by day, and which was busier

Zone counts refresh every 3 minutes; the countdown under Refresh now shows when. Click Refresh now to update immediately. Alerts refresh every 10 seconds.

Who can see it. The page needs the View Monitor (overall) permission, the same as the rest of the Monitor menu. The Live alerts panel and the Alerts (last hour) tile also need View Anomalies, the permission that guards the alert feed. The standard roles (Admin, Manager and Viewer) have both. Before 3 October 2026 the menu item followed View Dashboard instead, so a role with only that saw the item and then an empty page.

How people are counted

Each occupant counts once:

• An entity with two tags is one person, not two.
• Someone who walked from one room to another during the window counts in the room they were in last, not in both.
• Beacons and fixed sensors are fittings, not occupants, and never count.

These rules apply from 27 September 2026. Before that, counts could be higher and steady rooms often showed ↑100%, so do not compare today's figures with notes or screenshots from before then. For which number to trust in a room, see Occupancy: which number is which.

Live Monitor

/admin/monitor: Monitor → Live Monitor

The engineer's view: every gateway and every device, rather than every person. Use it when the Entity Tracker shows something odd and you want to know whether the hardware is the reason.

Across the top: Gateways (Online means a packet in the last 5 minutes, Stale 5 to 30 minutes, Offline longer or never), Sensors (Registered and Active /5m), and Today's Activity. The page refreshes every 30 seconds. Refresh updates it now. If a refresh fails, the time at the top right says Refresh failed at 10:42 — showing earlier data instead of pretending to be current.

The tabs:

Tab	What it is for
Gateways	Each gateway, its status, packets and devices heard in the last 5 minutes, with a health strip for gateways whose signal is slowly getting worse (recomputed daily), so you can replace them before they fail. Click one for its detail: Info, Detected Sensors and Packet Feed.
Sensors	Each device with its zone, the gateway hearing it, signal and battery. Click one for its detail.
Floor Plan	Each floor with its gateways and devices. Open a floor to see lists of Sensors and Entities on it.
Rules	A summary, not every run. Today, by rule: how many times each rule fired, when last, its channels, and all sent or how many did not go out. Did not go through: each recent firing with an action that was skipped (something it needs is not set up) or failed (the provider refused it), with the reason, such as telegram · skipped — No active Telegram connector. Not checked today: scheduled checks that could not be made, with why. The tiles count today's firings, how many went out cleanly and how many failed. Links go to Rules, Central Alerts and Rule & Alert Effectiveness for the longer history.
Temperature	Each temperature sensor now, with today's low and high, and one line across all of them. Environment has the hourly history.

The filters above the table change with the tab: status, type, tag, location, venue, zone, dates and a search box.

A device's detail has five tabs: Info, Payloads, Gateways, Movement and Tracking. A Why here? button opens a page explaining why Omaya has put the device where it has: what each gateway hears, which floor the signal favours, and each time the device was challenged to move and stayed.

A link to a particular tab opens on that tab. Links to the tabs that were removed open where their content now lives: the old Gateway Health and Predictive links open Gateways, Enter/Exit opens the Enter/Exit report and History opens Sensor Trail.

Alerts and anomalies: who can act

Two pages hold things that need someone to act.

• Monitor → Anomalies (titled Device Anomalies) is the maintenance queue: devices that have gone Silent, are Heard less than usual, show Battery drain, or have a Configuration problem. See Reading Device Anomalies below.
• Monitor → Central Alerts is every alert the platform raises, from every module, in one feed. It opens on Needs a look (still open, or raised in the last day), and folds the same alert repeating from the same place into one row that says why it repeats. See Central Alerts.

Reading Device Anomalies

The page is laid out like the rest of the Monitor menu.

1. Read the card across the top, Unacknowledged anomalies: Critical, Warning, Info and Total. These always count every anomaly nobody has acknowledged yet, whatever the filters below show.
2. Pick a status tab over the table: Active (the default: open and not yet acknowledged), Acknowledged, Recovered (the device was heard again and the anomaly closed itself) or All.
3. Narrow it with the filters beside the tabs: All severities (or Critical, Warning, Info), All types (or Silent, Heard less than usual, Battery drain, Configuration) and the time, All time by default, or Last 24h, Last 7 days or Last 30 days.

The table has Device, MAC, Type, Severity, Score, Description, Detected at, Status and Actions. Refresh at the top right reloads it.

Check it worked. With Active and All time, the number of rows matches Total on the card above.

Who can change them

Anyone whose role can see these pages can read them, filter them and export them. Only roles that can manage devices can acknowledge or delete anything. With the standard roles that is Admin and Manager; a Viewer sees the same lists without the buttons. On Anomalies that also means no tick boxes and no Acknowledge selected bar. If a colleague says the buttons are missing, that is their role, not a fault.

What each action does

Action	Where	What it does	Undo?
Acknowledge	A row's Acknowledge button on Anomalies (asks you to confirm); on Central Alerts a row's Acknowledge, the button on a repeat row (all of that repeat), or Acknowledge in an alert's detail	Marks it as handled, with your name. The device is not changed. The row stays in the list with status Acknowledged, and drops out of the Active tiles; on Central Alerts it moves to Done.	No
Acknowledge selected	Anomalies, after ticking rows	The same, for every ticked row. Asks you to confirm.	No
Acknowledge shown	Central Alerts, beside the filters	Acknowledges every alert in the list as filtered that can be acknowledged here. Asks you to confirm.	No
Delete	Central Alerts, Delete in an alert's detail (click the row)	Removes the alert for good. Asks you to confirm.	No
Clear → Clear acknowledged	Anomalies	Deletes every acknowledged anomaly. Open ones are kept.	No
Clear → Clear all	Anomalies	Deletes every anomaly record, open or not.	No

One click is one action. Each button acts once, on the rows you see.

What can be done on Central Alerts depends on the kind of alert:

Kind	Acknowledge	Delete
Anomalies, battery alerts	Yes	Yes
Button presses	No (a press is an event; there is nothing to acknowledge)	Yes
Webhook failures	No	Yes
Gateway, coverage, rule, emergency	No; these are the notification bell's messages, one row per event	No
Toilet and Security Watch incidents	No; handle them in their own app	No
Everything else (connectors, Data Centre, Warehouse, capacity, OAIA, compliance, radar, requests)	No; the row links to where it is handled	No

A button acts only on the alerts that accept it: Acknowledge shown with a mixed list acknowledges the anomalies and battery alerts and leaves the rest, and an alert's detail shows only the buttons that alert accepts. Every row links to where it is handled.

Acknowledge, delete or wait?

• Acknowledge when someone has seen it and is dealing with it. The record stays, which is what you want when someone later asks "did anyone notice?".
• Wait on a silent device you expect back. When it is heard again, its anomaly closes itself as Recovered. You do not need to do anything.
• Delete only noise, such as a test button press or a webhook failure already dealt with elsewhere. A deleted alert cannot be brought back.

The four figures at the top of Anomalies (Critical, Warning, Info and Total) always count every unacknowledged anomaly, whatever the filters below show.

Troubleshooting

"The entity is offline"

Offline means not heard for over 15 minutes. Work through these in order.

1. Read the tile. Sales area · 2d ago tells you where it was last heard. If that is the exit or the car park, it has probably left.
2. Check the battery. The tile shows it. In the entity view, How it is placed also shows the lowest level in the last 24 hours, which catches a tag that dropped off a cliff.
3. Check for No tag bound. An entity without a tag is always offline. Attach one on the Entity page.
4. Check the gateway. Open Monitor → Live Monitor → Gateways. If the gateway that covers the last zone is offline, every tag in its area goes quiet with it.
5. Remember tags that sleep. Some tags stop sending while they are still. A parked trolley can be offline all night and fine.

"It is in the wrong room"

1. Open the entity view and read How it is placed. Presence (the same thing the Health tab and Why here? call Loudest gateway) means only the nearest gateway decided, and the answer is the zone that gateway sits in. A room with no gateway of its own often shows up as its neighbour.
2. Open the replay and switch to Raw. A run of brief stays between two rooms means the tag is near the boundary and the gateways disagree. That is the signal, not the person, moving.
3. For a device, use Why here? on its Live Monitor detail. It shows what each gateway hears and why Omaya has not moved it.
4. If one tag model is consistently wrong, its transmit power may need measuring. See The calibration bench.

"There is a gap in the Timeline"

A Not heard · 40m row is a period when no gateway heard the tag. The usual reasons:

• The person went somewhere with no gateway: a stairwell, the car park, outside.
• The tag was in a bag, a pocket against the body, or a metal cabinet.
• The tag sleeps when still.
• A gateway was offline. Check Live Monitor → Gateways, or Monitor → Central Alerts filtered to Gateway outages.

Gaps under 5 minutes are not shown. They are the normal spacing between sightings.

"Here for and the Timeline disagree"

Here for counts from the moment the current stay was recorded as starting. The Timeline joins visits to the same zone that are less than 5 minutes apart, so its Dwell for the latest visit can be longer than Here for. Both are right; they answer slightly different questions. The Timeline is the better guide to "how long have they been in there".

The Toilet Hygiene app's Live page uses the same figure as Here for, so the two agree.

"Today says In since before today"

The entity was already on site at midnight, in a stay that began the day before. This is normal for parked assets and for anyone on a night shift.

"Replay opened on an old day"

The replay opens on the last day the entity was heard. If that is not today, the entity has not been heard today. Use › to step forward, or pick a date.

"Session expired"

If a page or a button answers Session expired. Please refresh your browser and try again. (ERR: CSRF token), the page was left open longer than your session lasts. Reload the page, sign in again if asked, and repeat what you were doing. Nothing is wrong with your account.

"Counts went down after an update"

From 27 September 2026, an occupant counts once per window and only in the zone they were in last, and beacons and fixed sensors no longer count. Counts on Right Now (and on the Zone occupancy page, since folded into Right Now) and on the dashboard dropped where people moved between rooms or carried two tags. The new figure is the correct one.