Appearance
Your things and your spaces
Where hardware, people, assets and the shape of the building are set up.
Set these up in this order: spaces first, then devices, then the things you want to follow. A gateway with no venue has nowhere to report; a zone with no shape cannot contain anything; a tag with no entity is a MAC address with no meaning. Most "nothing is showing up" questions are one of those three in the wrong order.
See how your building is described for the shape the space pages are building.
Nearly every page below is permission-gated. If a colleague cannot see one, that is their role rather than a fault — Roles is where to look.
Entity
/admin/manage/entity
The people, vehicles and assets you want to follow, each with the tag or tags assigned to it.
When you would open it. Giving a MAC address a name. Until a device is attached to an entity, every report about it is a report about a piece of hardware rather than about a thing you care about.
Before it has anything on it. Registered devices to assign. An entity can hold more than one tag, which is how a vehicle keeps its identity when its tag is replaced.
Device
Gateway
/admin/manage/gateway
Every gateway: where it is, whether it is online, what it can hear and when it last spoke.
When you would open it. The first page to open when a whole area goes quiet — one offline gateway explains an entire floor of missing data.
Before it has anything on it. A gateway must be placed on a venue before anything it hears can be positioned. Three or more online in a venue is what positioning needs; below that, devices fall back to nearest-gateway presence.
Sensor
/admin/manage/device
Every sensor, tag and beacon you have registered, with its model, battery, last reading and the zone it was last seen in.
When you would open it. Adding hardware, and checking one device when you suspect it. The model you pick decides how its packets are decoded and what the device can contribute.
→ Devices and what they report
Bulk Import
/admin/manage/device/import
Registering many devices at once from a spreadsheet.
When you would open it. A rollout. Typing two hundred MAC addresses by hand is how two of them end up wrong.
Sensor Onboarding
/admin/manage/device/onboarding
A guided way to teach Omaya a sensor it has never seen: point it at the device, let it collect real packets, and work out what the payload means.
When you would open it. When you have bought hardware that is not in the model list. The result can be saved to your own library, so the next unit of the same model is recognised immediately.
Before it has anything on it. The device powered on and within range of a gateway you select, and the page left open while it collects — the capture runs in the browser session, not in the background.
Custom Decoders
/admin/manage/device/custom-decoders
The payload decoders your organisation has defined, and the field-by-field specification behind each one.
When you would open it. Reviewing or hand-editing what onboarding produced, and adding a decoder straight from a datasheet when you would rather not sniff packets.
Space
Location
/admin/space/location
Your sites, and the buildings inside them.
When you would open it. The top of the tree. Create a location before anything else; every venue, gateway and report rolls up to one.
Before it has anything on it. Buildings are optional. If a location has none, the level is hidden entirely and the hierarchy reads Location → Venue → Zone.
→ How your building is described
Venue
/admin/space/venue
The mapped spaces: each one holds a floor plan, its scale and calibration, its operating hours and its cost per m².
When you would open it. Uploading a floor plan and setting what the space is worth. A floor is expressed here too — as a label and an ordering on the venue, not as a level of its own.
Before it has anything on it. A floor plan image with its real-world dimensions set, or nothing positioned inside it will land in the right place.
Zone
/admin/space/zone
The areas you draw on a venue’s floor plan — rooms, desks, entrances, restricted corners — and their capacity.
When you would open it. Zones are what almost everything is reported against. Draw the ones you would name in conversation, not every architectural subdivision.
Before it has anything on it. Capacity is set here and nowhere else. The meeting-room app reads this value, so there is deliberately no second place to type it.
Zone Type
/admin/space/zone-type
The categories you can label zones with — meeting room, workspace, corridor, washroom.
When you would open it. Grouping zones across venues so a report can say "all meeting rooms" without you listing them.
This list is read from the admin menu itself, so it cannot fall behind it.