Floor plans and positioning

Overview

This chapter covers everything that decides whether Omaya can report which room a tag is in rather than which building. The parts form one chain and are described together: the scale makes the plan mean metres, the walls make the estimate physical, the gateway positions and heights make the distances true, the calibration walk measures how each gateway really hears, and the Indoor Positioning settings decide how readily a tag is moved.

• For the order of work on a new building, see Setting up a site. This chapter is the detail behind steps 3, 5 and 6 of that guide.
• For a tag that is already shown in the wrong room, see A tag shows in the wrong room.
• For trackers with GPS, and for a person who walks out of the building, see Indoor and outdoor.

How a tag becomes a room

A tag does not know where it is. It sends a short radio message a few times a second, and every gateway in range reports how loudly it heard it. At a fixed interval Omaya re-reads all of those reports (a sweep) and decides where each tag is. The installation default is one sweep every 10 seconds; the platform operator can set a different interval for an organisation. The Speed tab of the Indoor Positioning settings shows the interval that applies.

Every wrong room has a stage it went wrong at, and the fix lives beside that stage. A wristband shown too far from every gateway is stage 2 (its model was never measured); a person shown upstairs is stage 4; two neighbouring rooms trading a still tag is stage 5 or 6. Most of the settings on the right are switches in System → Configuration → Indoor Positioning; the floor plan ones are on each venue's Floor Plan.

Two consequences explain most of the configuration in this chapter:

• A distance is only as good as the figures it is computed from: the signal a gateway sees at one metre, how fast signal fades on the floor, the heights of the gateway and the tag, and how loudly that kind of tag transmits. None of these can be looked up; the calibration walk and the calibration bench measure them.
• A room can only be named if it is drawn. Rooms are zones on the floor plan. A space that is not a zone cannot be reported, however good the radio coverage.

Calibration types

Three different functions are called calibration:

Function	Where	What it fixes	How often
The scale line	Map editor, Floor setup, step 2 Scale line	What a metre is on this plan	Once, when the plan is loaded
The calibration walk	The Calibrate gateways page (the Calibrate gateways button at the top of the Map editor)	Where the gateways really are, how signal fades on this floor, and the radio map	Once per floor, and again when gateways move
The calibration bench	Device > Tag Power > Measure	How loudly each tag model transmits compared with the tag used on the walk	Once per tag model

They depend on each other in that order. The walk solves positions in the plan's coordinates, so if those coordinates are not metres, neither is the result; and the bench compares every tag with the tag the walk was carried with.

Access to floor plans

SPECIFICATION

• Opening a floor plan (Map editor, 3D view, coverage check, wall designer): view-spaces (shipped roles: Admin, Manager, Viewer).
• Changing a floor plan (saving rooms, walls, gateway and sensor positions, the picture or the scale, importing a drawing, the wall designer) and the whole Calibrate gateways page: manage-floorplan, shown under System > Roles as Manage Floorplan Calibration (shipped roles: Admin, Manager).
• Adding rooms from the Map editor: create-spaces (Admin, Manager).
• System > Configuration > Indoor Positioning: manage-settings-general (shipped role: Admin).
• Device > Tag Power: manage-devices (Admin, Manager).

Without manage-floorplan the plan opens read-only with You can view this floor plan but not change it. Clicking a room, gateway or sensor shows its details; the Import menu, the Calibrate gateways button, the drawing tools and the save buttons are not shown.

Map editor

Choose Space > Venue, then click Floor plan on the floor's card. The Map editor opens: the venue's name at the top, the floor list on the left, the plan in the middle, and a details panel on the right whenever an item is selected.

Controls across the top of the editor:

Control	Function
Floor chip	Shows the floor's size, ceiling and north (for example 24.0 × 18.5 m · ceiling 2.7 m · north 15°), or Finish floor setup while setup is incomplete. Click it to open Floor setup.
Import	A menu with Find rooms in the picture and CAD drawing (DXF). See Detecting the walls automatically and Importing a CAD drawing.
3D view	Walls, rooms and devices as a 3D scene.
Calibrate gateways	Opens the calibration walk for this floor.

Above the plan are three switches, Names (every room's name on the plan), 1 m grid and Coverage (the coverage check), and the zoom buttons. Scroll to zoom; hold Space and drag to pan.

The floor list holds the groups Rooms, Gateways, Sensors and Walls, doors and furniture, with a search box, Find a room, gateway, sensor or wall.

Key	Effect
Z, G, S, W	Open the Rooms, Gateways, Sensors or Walls group
F	Open Floor setup
H	Open or close the coverage check
Ctrl+Z	Remove the last corner while drawing
Ctrl+S	Save the outline or shape being drawn
Esc	Stop drawing or placing without saving

Setting the scale

Applicable versions / plans

SPECIFICATION

• Permission: manage-floorplan (Admin, Manager).
• Picture formats: JPG, PNG, WebP.

Requirements

Aisha Rahman is preparing Level 3 of Northwind Tower. The architect has supplied a PNG of the floor, and the east corridor wall has been measured on site at 20.0 m.

• The plan picture is loaded and trimmed to the floor.
• Metres on the plan match metres on site.
• The ceiling height, the tag carrying height and north are recorded.

Restrictions

• Picture: JPG, PNG or WebP. A wrong file type is refused with Only JPG, PNG, or WebP allowed. At most 20 MB; a larger file is refused with Image too large (max 20MB).
• Floor setup has three numbered steps; each shows a tick once it is done. A floor with no scale line opens straight into floor setup.
• The scale line is the source of metres: every position, zone area and wall length is measured from it, not from the width and depth typed in step 3. Once the line is set, Width and Depth are read-only (Measured from the scale line in step 2.).
• A longer line is more accurate. A 2 cm slip on a 3 m line is a 0.7 % error on every distance in the venue; on a 20 m line it is 0.1 %.
• Ceiling height: 1.5 to 20 m, or blank. Tags carried at: 0 to 10 m, or blank. North: −360 to 360 degrees.

Set the scale before drawing anything

Zone areas, density per m², the cost-of-idle-space column and every distance a rule tests are all derived from the scale line. Changing it later rescales the meaning of everything already recorded against the venue.

Configuration roadmap

(1) Upload the floor plan picture and trim it to the floor.

(2) Draw the scale line and type its real length.

(3) Set the ceiling height, the tag carrying height and north.

Procedure

1. Choose Space > Venue and click Floor plan on the floor's card. Click the floor chip (or press F) if Floor setup is not already open.

2. Under step 1, Floor plan picture, click the box (Drop a picture here or click to browse) or drag the plan onto it. A high-resolution top-down view is best.

3. If the plan has a title block or a white margin, use Floor area in the picture: Draw area (drag a rectangle round the floor), Find edges (detect the floor's edges) or Reset (use the whole picture).

4. Under step 2, Scale line, click Set the scale line (Adjust the scale line once one exists). The bar above the plan reads Setting the scale line.

5. Drag A and B onto two points that can be measured on site, such as opposite corners of a room, a corridor or a wall.

6. Set the line's length and save:

   Configuration Item	Value	Note
   A to B	20.0	The real distance between A and B, in metres.

   Click Save. The page reloads so that every distance uses the new scale.

7. Under step 3, Size, heights and north, set the fields:

   Configuration Item	Value	Note
   Width × Depth	(measured)	The floor's real size in metres. Read-only once the scale line is set.
   Ceiling height	2.7	Storey height, used by the 3D view and radar heights. Blank means unknown, and the 3D view states that it is estimating.
   Tags carried at	1.1	How high tags are carried on this floor. See Gateway and tag heights.
   North	15	Which way the plan faces. Drag the dial so the needle points to real north, or type a bearing; Not known clears it. Used for the walking direction in the visitor app and for anything geographic overlaid on the plan.

8. Click Save size, heights and north.

9. Click Done, back to the floor to return to the floor list.

Verification

• Step 2 shows a tick and Set: … m between A and B. After saving, the console shows Scale saved. Reloading....
• With no distance typed, the editor shows Enter the real-world distance between A and B.; a failed save shows Failed to save calibration.
• Step 2 places the two scales side by side, Floor size from this line and Size typed in step 3, with the Difference. If they disagree it shows These disagree, and positioning follows the line, so every distance is out by that ratio: re-measure the line, or correct the typed size, whichever is wrong. When they agree it shows The line and the typed size agree.
• The floor chip shows the floor's size, ceiling and north.

Detecting the walls automatically

Omaya reads the plan picture and proposes the walls and rooms it can see, using the scale already set to return them in metres.

Applicable versions / plans

SPECIFICATION

• Permission: manage-floorplan (Admin, Manager).
• Requires a floor plan picture and a scale line.

Requirements

Aisha Rahman wants the walls and rooms of Northwind Tower Level 3 created from the plan picture rather than traced by hand.

• Walls and rooms are proposed from the picture.
• Each proposal is reviewed before anything is saved.

Restrictions

• Detection looks for dark, continuous structure in the image. Two errors are common on real drawings:
  • Thick walls can come back as two thin parallel walls, with a gap that a position estimate can slip through.
  • Furniture, hatching and dimension lines are promoted to walls, especially on architectural drawings with heavy annotation.
• Nothing is saved until Save all is clicked.
• Running detection a second time does not duplicate the floor: walls, doors and rooms already saved are skipped, and corrections made by hand are kept.

Configuration roadmap

(1) Open Find rooms in the picture.

(2) Review the walls and rooms found.

(3) Save, then tidy the result in the Map editor.

Procedure

1. In the Map editor, choose Import > Find rooms in the picture. The Find rooms in the picture page draws the walls (red lines) and rooms (coloured shapes) over the picture, with a Summary and the Walls found and Rooms found lists beside it.
2. Review every wall and room against the drawing. Click Run again to repeat the detection.
3. Click Save all.
4. Click the arrow beside the page title to return to the Map editor, and correct the result as described in Drawing walls, doors and furniture by hand.

Verification

• The walls appear in the Walls, doors and furniture group and the rooms in the Rooms group of the floor list.
• If nothing could be read, the lists show No walls detected. and No rooms detected.

Importing a CAD drawing

A CAD drawing of the floor is more accurate than any picture of it: it already contains every wall and every metre.

Applicable versions / plans

SPECIFICATION

• Permission: manage-floorplan (Admin, Manager).
• File format: ASCII DXF, up to 48 MB. DWG, IFC and Revit files are not read directly.

Requirements

The architect of Northwind Tower has supplied the Level 3 drawing as a DXF in millimetres.

• Rooms are created from the drawing's wall layers.
• The drawing becomes the floor's picture, already to scale.

Restrictions

• Drawing (.dxf, up to 48 MB). A binary DXF is refused; save an ASCII DXF.
• Export one floor at a time. A whole building in one file makes rooms from every floor overlap.
• A large drawing takes up to a minute to read.
• Layers that hold block references (doors or walls drawn as reusable blocks) are marked, because blocks are not drawn yet. Check those areas by hand.
• An area label such as (2059 sqft) is never used as a room name. The outline of the whole building is left out automatically.
• If the floor already has a picture, the import replaces it only after confirmation. Rooms, gateways and devices placed on the old picture will not line up with the drawing and must be moved afterwards.
• Nothing is saved until Save is clicked, and a save that fails saves nothing.

Converting other formats to DXF (the page gives these instructions when such a file is chosen):

Source	How to obtain a DXF
DWG (AutoCAD)	In AutoCAD or BricsCAD, Save As and choose AutoCAD DXF. Without CAD software, the free Autodesk DWG TrueView converts it with DWG Convert.
IFC (BIM)	Export the floor's plan view as DXF from the BIM tool, or ask the architect for the DXF.
Revit model	Open the floor plan view, then File > Export > CAD Formats > DXF.
ArchiCAD	Open the floor plan, then Save As > DXF.

Configuration roadmap

(1) Upload the drawing with its units.

(2) Check the size, the wall layers and the rooms.

(3) Save, then check every room in the Map editor.

Procedure

1. In the Map editor, choose Import > CAD drawing (DXF). The Import a CAD drawing page opens.

2. Set the upload fields:

   Configuration Item	Value	Note
   Drawing (.dxf, up to 48 MB)	level-3.dxf	One floor, ASCII DXF.
   The drawing is in	millimetres	millimetres (default), centimetres, metres, inches or feet. Most architectural drawings are in millimetres.

3. Click Upload and find rooms.

4. Review the result:

   • Size and units: the floor's size in metres. If it is not the size of the floor (a 30 m floor shown as 30,000 m), the units are wrong: change Units in the Wall layers card and click Run again. If the file declares different units from the ones chosen, the page says so.
   • Wall layers: CAD drawings keep walls, doors, furniture and text on separate layers. Layers named like walls (wall, A-WALL, partition, drywall, glazing) are ticked automatically. Tick or untick layers and click Run again.
   • Rooms: each room found, named from the text in the drawing where there is one. Untick a room, or click it on the drawing, to leave it out; type over a name to rename it. Keep all and None tick or untick every room.

5. If the floor already has a picture, tick Replace this floor's current picture with the drawing. The box also states how many rooms, gateways and devices are placed on the current picture.

6. Click Save.

Reviewing detected rooms

CAD drawings vary a great deal. Treat the rooms as a first draft: check each one against the drawing, leave out corridors or shafts that are not wanted as zones, and correct shapes afterwards in the Map editor.

Verification

• The drawing becomes the floor's picture, already to scale, with no scale line to draw. The rooms kept become zones, and the walls and doorways are added as with Find rooms in the picture.
• Choose a .dxf file first. is shown when no file was chosen; Tick the box above to replace the current image. when the floor has a picture and the box is not ticked; This import has expired. Upload the drawing again. when the review was left too long; Nothing was saved. when the save failed.

A detected room is only a shape: whether a room is the lobby or a riser cannot be told from the drawing. Check each room's name and position before relying on it, then tidy the rest in the Walls, doors and furniture group. Walls are worth the effort: they stop an estimate placing someone inside a lift shaft, and they feed the 3D view.

Drawing walls, doors and furniture by hand

Applicable versions / plans

SPECIFICATION

• Permission: manage-floorplan (Admin, Manager).

Requirements

Daniel Lim reports that a glass partition has been installed beside the pantry on Level 3 of Northwind Tower.

• The partition is added as a wall with its thickness and material.

Restrictions

• A wall or door needs two points on the plan; furniture or other shapes need three or more. Too few points are refused with A wall or door needs two points. or An outline needs at least three corners.
• Name: at most 80 characters.
• Thickness: 0.02 to 2 m, or blank. Height: 0.1 to 20 m, or blank (blank means the full ceiling height).

Configuration roadmap

(1) Add the item to the Walls, doors and furniture group.

(2) Draw its shape on the plan.

(3) Set its dimensions.

Procedure

1. In the Map editor, click the heading of the Walls, doors and furniture group to open it (it starts folded). All, Walls, Doors, Furniture and Undrawn narrow the list, and Filter walls searches it.

2. At the bottom of the group, set the new item and click Add:

   Configuration Item	Value	Note
   Name, e.g. Pantry partition	Pantry partition	The item's name.
   (type)	Wall	Wall, Door, Furniture or Other.

3. Click the item in the list and click its points on the plan. Click Save shape in the bar above the plan.

4. Click the drawn wall (in the list or on the plan) to select it. The details panel shows its Length and, for a wall, these fields:

   Configuration Item	Value	Note
   Thickness	0.1	Metres.
   Height	(blank)	Metres; blank means the full ceiling height.
   Material	Glass	How much signal the wall absorbs: Glass 2 dB, Drywall / plasterboard 3, Wood 4, Brick 6, Cement / plaster block 8, Concrete 12, Reinforced concrete 18, Metal 20.

5. Click Save dimensions. Redraw shape draws the item again; Delete removes it.

Verification

• The item shows its length in the list and is drawn on the plan.
• Thickness should be 0.02-2 m, or blank. is shown for a thickness out of range.

Wall designer

When no usable plan picture exists, the wall designer is the alternative: click the layout icon in the heading of the Walls, doors and furniture group. Draw walls by length and angle (Draw wall, with Snap to grid and Snap to 45°), place furniture, click Find rooms to turn spaces enclosed by walls into rooms, and click Save as the floor plan picture. What is drawn becomes real walls and zones rather than a picture of them.

Drawing zones (rooms)

A zone is a room on the plan. The Map editor lists a floor's zones in the Rooms group of the floor list. A CAD import or Find rooms in the picture creates zones from the rooms that are kept.

Applicable versions / plans

SPECIFICATION

• Drawing outlines: manage-floorplan (Admin, Manager).
• Adding a room in the Map editor: create-spaces (Admin, Manager). The add form is shown only to roles that hold it.
• At least one zone type must exist (Space > Zone Type).

Requirements

Aisha Rahman needs the rooms of Northwind Tower Level 3 (Reception, Meeting Room 3A, Open Office and the corridor) as zones that cover the whole floor.

• Every room, corridor and open area is a zone.
• The zones are drawn edge to edge, without overlap.

Restrictions

• An outline needs at least three corners (An outline needs at least three corners.). A zone without three corners has no boundary and nothing can be placed in it; the list shows a pencil instead of a tick.
• A room cannot overlap another: This boundary overlaps with zone "…". Please redraw.
• New room name: at most 120 characters.
• A room added in the Map editor has no Capacity; set it on Space > Zone (see Managing zones on the Zones list).
• If no zone types exist, the group shows Add a room type in Space › Zone types first, then add rooms here.

Draw zones edge to edge

Room estimation only ever chooses among the zones drawn on a floor, and a tag that falls between zones has no room to be reported in. Corridors and open areas are zones too, if a person in them is to be reported there rather than in the nearest office.

Configuration roadmap

(1) Add the room in the Rooms group.

(2) Draw its outline.

(3) Set its capacity on the Zones list.

Procedure

1. In the Map editor, at the bottom of the Rooms group, set the new room:

   Configuration Item	Value	Note
   New room name	Meeting Room 3A	At most 120 characters.
   (zone type)	Meeting room	A zone type of the organisation.

2. Click Add room and draw it. The editor reloads with the new room ready to draw.

3. To draw a room that has no outline yet, click it in the list (the group count states how many are left, for example 3 to draw). The bar above the plan reads Drawing and the room's name.

4. Click the plan at each corner. Undo (or Ctrl+Z) removes the last corner, Clear starts again, and a corner can be dragged.

5. Click the first corner, or click Save outline (Ctrl+S).

To change a drawn room, click it in the list or on the plan. The details panel shows its Outline, Area and Colour, with Edit outline, Rename, Colour, Clear outline (keeps the zone, removes its boundary) and Delete room. Press Esc, or click the cross in the bar, to stop drawing without saving.

Verification

• After Add room and draw it, the editor shows Room added. Draw its outline.
• After saving the outline, the editor shows Outline of "…" saved., the row shows a tick and its area in m², and the room is shaded on the plan.

Managing zones on the Zones list

Choose Space > Zone to list every zone in the organisation.

• Tiles at the top (Zones, Not drawn on the plan, No gateway and Inactive) count every zone; click one to open that tab.
• Tabs (All, Not drawn, No gateway, Inactive) and the filters beside them: Find a zone, All floors, All types and All labels. Clear resets them.
• Columns: Zone (with its location and floor), Type, Used as, Capacity, Floor plan, Gateways, Labels and Status. In Floor plan, Drawn opens the zone selected in the Map editor, and Draw it opens the Map editor with that zone ready to draw.
• Click a row to open the zone's Zone Info panel: its location, venue, type, capacity, gateways and labels; links to Floor plan, Right Now, Space Utilisation, Room Usage, Heatmap and Environment; and Edit and Delete.

Creating a zone on the Zones list

1. Choose Space > Zone and click Add Zone.

2. Set the fields:

   Configuration Item	Value	Note
   Active	On	Leave on.
   Parent Location	Northwind Tower
   Parent Venue	Level 3	The floor.
   Zone Name	Open Office
   Zone Type	Office
   Kind of space	Work room / office	Also Meeting / training room, Toilet, pantry or service room, Desk, Phone booth / focus pod, Open area. Seats on Space Utilisation count work rooms, open areas and desks only.
   Capacity	40	Under Advanced Settings.
   Capacity Note	(optional)	Under Advanced Settings.

   The other fields under Advanced Settings (doorway counting, compliance profile, Labels, Description) are optional.

3. Click Save, then click Draw it in the zone's row to draw its outline.

Zone types

Zone types are kept on Space > Zone Type (or the Zone Types button on the Zones page). The list shows how many zones use each type, linking to the Zones list filtered to it. Click a type to edit or delete it. A type still in use cannot be deleted; the message states how many zones use it, for example 3 zones use this type. Give them another type first, or switch this one off instead.

Placing the gateways

Gateways are assigned to a venue on Device > Gateway. The Gateways group of the floor list shows the gateways that belong to the floor, so that each can be placed where it is physically mounted.

Applicable versions / plans

SPECIFICATION

• Permission: manage-floorplan (Admin, Manager).
• The gateway's venue must be set on Device > Gateway.

Requirements

Daniel Lim has mounted six gateways on the ceiling of Northwind Tower Level 3, at 2.7 m. Aisha Rahman records each one on the plan.

• Every gateway is placed where it hangs, with its mounting height.
• The gateways are spread around the floor so that it can triangulate.

Restrictions

• Height: 0 to 30 m, or blank (Mounting height must be between 0 and 30 m.).
• Tx: −100 to 0 dBm, default −59.
• Rx: −20 to 20 dB, or blank (Receive offset must be between -20 and 20 dB.).
• Three positioned gateways are the threshold for a position in metres. Below three, a floor cannot triangulate; it can still name rooms with Room estimation, or fall back to the room of the loudest gateway. Coverage and geometry keep improving above three, and a line of three gateways along one wall is worse than three spread around the room even though the count is the same. See Gateways.
• A gateway mounted where two or three rooms meet hears a tag beside it about equally in each of them, and tags near it tend to swap between those rooms. Mount gateways a metre or two inside one room where possible. Where that is not possible, the …but not beside a gateway on a room corner switch on the Rooms tab is intended for that gateway.

Place gateways accurately

The distance calculation solves for a point consistent with how strongly each gateway hears a tag. A gateway recorded three metres from where it hangs pulls every estimate near it towards a place where nothing is.

Configuration roadmap

(1) Select the gateway in the Gateways group.

(2) Place it on the plan.

(3) Set its height and save.

Procedure

1. In the Map editor, open the Gateways group. Its count states how many are left, for example 2 to place; a gateway not on the plan yet shows Place.

2. Click the gateway in the list (or its pin on the plan). The bar above the plan reads Placing (or Moving) and the gateway's name.

3. Click the plan where it is mounted, or drag its pin.

4. Set the fields in the bar:

   Configuration Item	Value	Note
   Tx	-59	The signal this gateway sees from the walk's tag at one metre, in dBm. Default −59. Leave it; the calibration walk writes it.
   Height	2.7	Mounting height above the floor, in metres. Set it for every gateway; blank means unknown.
   Rx	(blank)	Receive offset: how much louder (+) or quieter (−) this gateway hears than the others on the floor, in dB. Set it only for a gateway known to hear loudly; see One gateway pulls tags in from next door.

   For a direction-finding (AoA) locator the bar also shows Facing and LAN MAC.

5. Click Save. Cancel leaves the gateway as it was; the pin-off button takes it off the plan.

Verification

• The row shows the gateway's position in metres from the top-left corner of the floor, in amber if it sits outside the floor.
• The details panel shows Mounted at, or Height not set when the height is blank.
• Saving before placing shows Click on the map to place this gateway first.
• With no gateway assigned, the group shows No gateways on this floor yet. Set a gateway's venue on Device › Gateway.

Gateway and tag heights

The Height field of each gateway takes its height in metres above the floor; the floor's Tags carried at field (step 3 of floor setup) takes the height at which tags are carried.

Radio measures the distance from the tag to the gateway through the air: a straight line, usually diagonally downwards from a box on the ceiling. A floor plan is flat and needs the distance measured across the floor. Without both heights Omaya cannot tell the two apart, so it uses the diagonal as if it were the flat distance, and every tag sits further from the gateway than it really is.

The error is largest close to the gateway. A gateway at 2.7 m above tags carried at 1.1 m is 1.6 m higher than they are: a tag standing one metre away is 1.89 m from the gateway through the air, nearly double. Five metres away the same difference is worth about five centimetres.

1. Set Height on every gateway (see Placing the gateways).
2. Set Tags carried at in step 3 of floor setup: about 1.1 m for a wristband or a lanyard, lower for a tag on a trolley, higher for a forklift. One value per floor is enough; the correction is not sensitive to a few centimetres.
3. For a tag that does not travel with a person, choose Device > Sensor, open the tag, expand its Tag Power card and set Carried at. A trolley tag at 0.6 m is not a badge at 1.1 m.

Blank heights change nothing: positioning stays flat, as it behaved before these fields existed. Blank is better than a guess, because a wrong height moves every close-range estimate.

Set heights before the walk, not after

The walk measures how signal fades with distance, using whatever heights are set at the time. A floor walked with no heights has the height difference built into its fall-off figure; adding heights afterwards corrects for the same effect twice. Set the heights, then walk, or walk again.

The calibration walk

The walk turns approximate gateway pins into measured positions, and the default radio figures into the floor's own. The Calibrate gateways page shows the plan on the left and the walk panel on the right in three numbered steps, repeated along the top: Pick a tag, Walk and mark, Finish. The arrow beside the title returns to the Map editor.

One walk does the whole calibration. The two refusals are deliberate: gateways are not moved by a walk that never went near the corners, because the solve cannot be trusted to place them, and a fitted distance model is thrown away when it is no better than guessing each gateway's typical distance — on some floors signal strength simply carries little range information, and the fingerprint has to do the work there.

Applicable versions / plans

SPECIFICATION

• Permission: manage-floorplan (Admin, Manager), also needed to open the page.
• A registered tag that the floor's gateways hear.
• Optional: a phone, for the mobile walk.

Requirements

Daniel Lim walks Level 3 of Northwind Tower with a lanyard badge of the model most staff carry, during a quiet hour.

• Every room and all four corners of the floor are covered.
• The gateway positions, the distance model and the radio map are updated from the walk.

Restrictions

• The gateways must be placed and their heights set first. The walk measures them as they are.
• Use a tag of the kind most people will carry. It becomes the floor's reference (see Reference tag of the walk). Use the same kind of tag on every floor where possible.
• Allow twenty to forty minutes per floor, at a quiet time if possible. People standing between the tag and a gateway change what it hears.
• The phone link is valid for two hours.
• The radio map cannot name a room that the walk never visited.

Configuration roadmap

(1) Pick the tag and check that every gateway hears it.

(2) Start the walk and mark points across the floor.

(3) Finish the walk and read the report.

Procedure

1. In the Map editor, click Calibrate gateways (also Then calibrate them with a walk under the Gateways group, and Calibrate gateways with a walk in the coverage check).
2. Under Pick the tag you will carry, choose the tag from Choose a tag. What the gateways hear now then shows what each gateway hears from it. Check that every gateway on the floor is in the list before setting off.
3. Under Walk and mark points, click Start walk here. The walk is named by date (for example Walk 2026-10-19); there is nothing to type. The plan's badge reads Recording walk #….
4. Optional: click Continue on a phone to carry a phone instead of a laptop. The Mobile calibration walk window shows a QR code and a link valid for two hours; points from the phone go into the same walk.
5. Click Suggest points to drop numbered markers spread over the floor. Walk to them in order; Where next highlights the area covered least.
6. At each spot, stand still and click the current position on the plan. Omaya waits a few seconds for the readings to settle (Skip wait shortens this), then records what every gateway hears from that spot. Points marked counts them.
7. Cover every room and all four corners. Corners and opposite ends teach far more than many points in one region. The phone shows a checklist of rooms covered and warns before finishing if a room has no point.
8. Under Finish the walk, click Finish walk and confirm. The phone also warns if the walk is short of the recommended number of points.

Under More options, Abandon walk discards a walk: its points are kept, marked abandoned, and not used. A walk left unfinished (the browser closed, the phone switched off) shows as You have an unfinished walk here. on return; Clear it marks it abandoned.

Verification

Finishing the walk runs the whole calibration automatically, in this order, and reports each step:

Step	Function	When it declines
Coverage	Counts points, rooms and corners covered, and names the rooms not walked.	—
Gateway positions	Solves where each gateway really is and moves it, by up to 3 m from where it was placed. Low-confidence gateways and gateways pinned to the floor's edge are skipped.	When the walk has no point near every floor corner: the solve cannot be trusted to move placed gateways, so nothing is changed.
Distance model	Fits how fast signal fades on this floor and each gateway's signal at one metre (Tx).	When the fit is no better than guessing each gateway's typical distance. On some floors signal strength carries little range information, and the fit is not applied.
Fingerprint	Rebuilds the floor's radio map from the walk.	—
Room classifier	Trains the floor's room classifier on the walk and reports how often it names the right room on held-out readings.	When there is not enough data.
Check	Re-checks which positioning method the floor qualifies for, and scores the walk against the new calibration: median error in metres, and how often the room is right.	—

The report appears on the phone a few seconds after Finish walk, and on the desktop under Last walk report at the top of the Calibrate gateways page. While the calibration is still running, the card says so and fills in when it is done. It has one line per step, for example gateway positions: solved, none written together with no point near the top-left corner(s), which identifies what to walk next time. The card always shows the last walk finished on the floor.

Starting the phone walk before a walk has been started shows Start a calibration walk first.

Solving and refining by hand

These are rarely needed, because finishing the walk already does the work. Both are under More options in the walk panel:

• Solve positions opens Solved gateway positions: each gateway's Current (x, y) next to its Solved (x, y), with an RMSE and a Confidence. A value can be edited before clicking Apply to floor plan. Use it when the automatic step declined and the result is to be judged manually.
• Refine (Run refine) moves each gateway by up to 3 m using recent readings from devices with a known position. The placement stays the anchor; it is never replaced wholesale.

When to walk again

• A gateway moved, or was added. Moving a gateway by hand marks every earlier walk on that floor as out of date: the radio map and the fits stop using them, so a floor that was on fingerprint drops back to triangulation until it is walked again. This is deliberate: a map of where the gateways used to be is worse than none.
• Heights were set or changed (see Gateway and tag heights).
• The layout changed: walls moved, a room split, heavy shelving installed.
• A different tag becomes the reference.

Reference tag of the walk

The walk measures each gateway against the tag carried on the walk, and records the signal that gateway sees at one metre from that tag. The tag is therefore part of the calibration, not only a tool used during it.

A tag of a different model (a wristband where the walk used a card) is heard louder or quieter everywhere, and Omaya reads the difference as distance. Six decibels of difference makes every range 1.7 times too long; thirteen makes it three times. This is not noise and does not average out: one kind of tag simply sits in the wrong place.

Device > Tag Power > Measure corrects it once per model, on the calibration bench. Lay the tag to be measured beside one of the model the walk used, close to one gateway, and run a few short rounds, turning the tags between them: whatever difference remains between them is the radios. The bench counts only frames the gateway really heard again, and refuses to save a measurement that disagrees with itself, because that means the tags were not really side by side.

NOTE

• Different floors can have different reference tags. An offset belongs to the venue whose walk it was measured against; a floor walked with another tag needs its own.
• A single tag can be out of specification for its model. The Tag Power card flags tags of one model that do not advertise the same power. Such a tag needs its own override rather than a change to the model: choose Device > Sensor, open the tag and set This tag's own offset in its Tag Power card.
• Until a model is measured, it is treated like the walk tag. Nothing changes until something is measured.

Building a fingerprint

A fingerprint is a radio map. Instead of computing a position from signal strength and a fall-off model, Omaya records what the radio looked like at each place and matches live readings against that record. It handles reflective, partitioned and irregular buildings that distance calculation alone gets wrong.

Applicable versions / plans

SPECIFICATION

• Permission: manage-floorplan (Admin, Manager).
• Requires at least one calibration walk on the floor.

Restrictions

• Finishing a walk rebuilds the fingerprint. It is also rebuilt every night at 02:00 from the last seven days.
• A rebuild replaces the map with what it can see now. If a gateway was offline recently, wait for its data to refill before rebuilding.

Procedure

1. Choose Space > Venue, click Floor plan on the floor's card and click Calibrate gateways.
2. Under How this floor positions, below the walk, find the Fingerprint quality panel.
3. Click Rebuild fingerprint (Build fingerprint on a floor that has none yet) to rebuild it now.

Verification

The panel shows:

Figure	What to check
Cells	How many places the map holds.
Avg samples and Range	Readings behind each cell. A thin map gives a confident-looking wrong answer.
Zone-tagged	Cells that know which room they are in.
Last built	When it was rebuilt.
Gateway coverage	For each gateway, the share of cells that heard it. A gateway of this floor under 60 % has lost a reference. Gateways from another floor are expected to be partial and are marked rather than warned about.

A status of Needs re-walks for low-sample cells means parts of the floor were walked too briefly.

Calibrating from fixed sensors

A walk needs someone on the floor. For a floor that nobody can visit often, a sensor fixed at a known spot is standing ground truth: every gateway that hears it gives a known distance and an observed signal, the same kind of evidence a walk produces, sampled every ten minutes.

Applicable versions / plans

SPECIFICATION

• Permission: manage-floorplan (Admin, Manager).
• A permanently mounted sensor assigned to the venue. Tags cannot be references.

Requirements

Daniel Lim has fixed an environment sensor to the wall of the Level 3 server room at Northwind Tower, a room rarely visited.

• The sensor's readings contribute to the floor's calibration.

Restrictions

• The reference control appears only for a placed sensor, never for a tag: a tag moves, and a moving reference would teach the floor something false (Tags move, so they cannot be positioning references.).
• The readings feed the floor's radio map when it is rebuilt each night, and the distance fit the next time someone finishes a walk on the floor.
• No floor is fitted from reference sensors alone. A floor that is never walked keeps its default distance figures however many references it has: a fit from one or two sensors that never move cannot tell distance from a gateway's own loudness.
• A reference sensor says nothing about the rooms it is not in. It complements a walk rather than replacing one.
• Removing the sensor from the map retires it as a reference.

Procedure

1. In the Map editor's Sensors group, click the sensor. The bar above the plan reads Placing and its name.
2. Click the plan where it is mounted, or drag its pin, and click Save.
3. Click the target icon in its row, or Use as a positioning reference in the details panel.
4. In the Use as positioning reference? window, click Use as reference.

Verification

• The console shows Sensor is now a positioning reference.
• The foot of the Sensors group states how many references the floor has (… references calibrating this venue.).
• Trying it on an unplaced sensor shows Place the sensor on the floor plan before using it as a reference.

Positioning method

Every venue is classified independently, and the classification is re-checked rather than set once — add a third positioned gateway and the venue moves up a rung on its own. The trap is at the top: a handful of poor fingerprint cells is still "a radio map", so a venue can be promoted to fingerprint on data that is worse than the triangulation it just replaced. That is the case worth pinning.

Left on automatic, each venue uses the first method it qualifies for. The Positioning method card on the Calibrate gateways page, under How this floor positions below the walk, shows which one is in use, for example Automatic — currently using Triangulation, and allows it to be overridden.

Choice	Function
Automatic	Classify from what the venue has. The default, and correct in nearly all cases.
Presence	Nearest gateway only. No triangulation, no radio map.
Triangulation	Distances from the gateway positions, ignoring any fingerprint.
Fingerprint	Use the radio map, fused with triangulation.

With Room estimation on, the room is chosen by room estimation on every floor with zones drawn and a gateway placed, and the dot is drawn inside that room; the method on this card is used when room estimation cannot answer. The floor's coverage check, under What placed devices here, shows the split: Zone estimate, Triangulated, Fused, Loudest gateway and so on.

Applicable versions / plans

SPECIFICATION

• Permission: manage-floorplan (Admin, Manager).

Requirements

At Northwind Tower, Ravi Kumar notices that positions on Level 3 became worse after a test walk was abandoned half-way. The floor has three well-placed gateways and a proper calibration.

• The floor is pinned to triangulation until it is walked properly.

Restrictions

• The automatic choice is wrong in one specific way: the top rung only asks whether fingerprint data exists, not whether it is good. A venue that collected a few dozen poor cells (an abandoned walk, an experiment, a room rearranged afterwards) is promoted to fingerprint and stops triangulating, even where it has three well-placed gateways and a proper calibration. The symptom is positions that became worse after an improvement.

Configuration roadmap

(1) Open the Positioning method card.

(2) Choose the method and save.

Procedure

1. Choose Space > Venue, click Floor plan on the floor's card and click Calibrate gateways.
2. On the Positioning method card, choose Triangulation and click Save.
3. After the floor has been walked properly, set the card back to Automatic.

Verification

The card shows Pinned to … and continues to state what automatic would choose (Left automatic it would choose …), so that the override remains visible.

Coverage check

Click Coverage above the plan in the Map editor (or press H). The floor list is replaced by Coverage check, covering the last 7 days on this floor, and the plan shades each room: green where positioning can show it, red where it cannot yet.

• Rooms that can be shown, Gateways placed, Typical stay in a room and Flickers between rooms, with advice under them.
• Rooms: each marked has a gateway, by room estimation or cannot be shown.
• What placed devices here: the share of each positioning method.
• Settings: which positioning switches are on, with Change in Indoor Positioning.
• Receive offsets: Suggest from calibration proposes each gateway's Rx from the walk (requires manage-floorplan).

The refresh button checks again; Back to the floor (or Coverage again) returns to the floor list.

Indoor Positioning settings

Applicable versions / plans

SPECIFICATION

• Menu: System > Configuration, the Indoor Positioning card.
• Permission: manage-settings-general (shipped role: Admin). Without it the panel shows Not Permitted.
• The settings apply to the whole organisation, not to one venue.

Requirements

Aisha Rahman finds that tags on Level 3 of Northwind Tower flick between Meeting Room 3A and the corridor, and that the small rooms without a gateway are never shown.

• Room estimation is turned on after a trial on the last day's data.
• The coverage check is used to confirm the result.

Restrictions

• The panel has five tabs: Overview, Rooms, Floors, Speed and Stability & records.
• For a new organisation every switch is off except Ignore faint readings from another floor and Split long stays at midnight (and, under the floor vote's advanced thresholds, Grade each vote by signal strength). Turn a switch on when there is a symptom it explains, not by default.
• Changes apply from the next sweep after Save. Nothing needs restarting.

Configuration roadmap

(1) Read the recommendations on the Overview tab.

(2) Try a switch on the last day's data.

(3) Turn it on and save.

(4) Confirm the effect in the coverage check.

Procedure

1. Choose System > Configuration and click the Indoor Positioning card.
2. On the Overview tab, under What this site needs, click Try on on the last day (or Try off on the last day) beside the switch (see Trying a switch).
3. When the result is satisfactory, click Switch it on in the result box, or Apply beside the recommendation, or set the switch on its tab and click Save.
4. Open the floor in the Map editor and click Coverage.

Verification

• At a glance on the Overview tab shows the switch as On.
• The coverage check lists the switch under Settings, and Rooms shows rooms marked by room estimation.

Overview

What this site needs reads the organisation's own floors, gateways and the last 24 hours, and states, switch by switch, what it recommends and why. Where it disagrees with the current setting, an Apply button turns that switch on or off and saves immediately, together with any other change made in the panel. At a glance lists every switch as On or Off, plus the detection speed preset; click a line to jump to its tab.

Where coverage is thin lists what no setting can fix: a floor of a multi-storey building with no gateway or only one, and pairs of gateways on different floors that hear the same tags about equally, with how often they contested a tag in the last day and how close their readings were. A tag near such a pair can sit on the wrong floor, or a short visit can be missed, whatever the settings. If the two are mounted one above the other, moving one sideways, or adding a gateway on either floor further from that spot, gives a reading only one floor can produce.

The coverage check on each floor plan is the companion: it shows which rooms can be named, how steady tags are, and which of these switches are on.

Trying a switch

Each line under What this site needs has Try on (or Try off) on the last day. Omaya takes the last 24 hours of up to ten of the organisation's tags (tags with a recorded known floor or a walk first, then tags that report motion, then the busiest) and replays them through the live positioning code twice: once as configured today and once with that switch changed. A box at the top of the Overview then shows both side by side:

• Floor changes and Short visits to another floor (another floor for under three minutes, then straight back: a quick real trip, or a false change).
• Room changes, and Time on each floor.
• Tags with a known floor shown on it, and how each version did on any walks recorded by the organisation.

When AI is on for the organisation, it explains what the difference means for the building. Nothing is changed: click Switch it on (or Switch it off) in the box to apply it, or close the box. A trial takes a few minutes; the panel can be closed in the meantime. One trial runs at a time.

NOTE

A trial can only judge what happened on the previous day. If nobody changed floor, a floor setting shows no difference; if none of the tags reports motion, the motion switch changes nothing. Record a walk for a firm answer.

Rooms tab

Which room a tag is in.

Setting	Function	Use it when
Room estimation	Works out the room from every gateway on the floor, including what they did not hear, instead of taking the room of the loudest gateway. Needs zones drawn and at least one gateway placed.	Rooms without a gateway of their own are never shown, or tags flick between two neighbouring rooms
Also use triangulation as evidence	With three or more gateways heard, the distance fix counts towards the room, and rooms are held a little longer. Only acts while Room estimation is on.	Tags lying on a desk still bounce between rooms
…but not beside a gateway on a room corner	A tag very close to a gateway mounted where rooms meet is judged without the distance fix. Gateways well inside one room are not affected. Only acts while triangulation is used as evidence.	A tag beside a gateway on a corner or a shared wall keeps changing between those rooms
Hold the room while a tag lies still	For tags with a motion sensor: once a tag has not moved for 5 minutes, it keeps its room until it is picked up again. Tags without a motion sensor are not affected. Only acts while Room estimation is on.	Tags left on a desk appear to wander
Allow for gateways that hear louder than others	Takes each gateway's receive offset (Rx) out before comparing gateways, so a gateway that hears loudly stops winning tags that are nearer a quieter one. Has no effect until offsets are set, in a gateway's Rx field or from Receive offsets in the coverage check.	One gateway pulls tags into its room from next door
Fingerprint accuracy boost	Also called Find3 LR. Weighs the parts of the radio map that really tell rooms apart. Worth it on venues with 8 or more gateways and 100 or more fingerprint cells; no effect on venues with 1 to 3 gateways.	Fingerprint results are poor on a well-covered venue

Hold the room while a tag lies still

If the room was wrong when the tag was put down, it stays wrong until the tag moves, and the minute after a tag is put down is when the estimate is least certain. The switch is therefore off by default, and suits tags that are put down in a known place.

Floors tab

Which floor a tag is on. Signal leaks through slabs and stairwells, so a gateway upstairs can hear a tag downstairs.

Setting	Function	Use it when
Pick the floor by majority vote	Every gateway that hears a tag votes for its own floor, weighted by signal; the floor with the most votes wins and the loudest gateway on that floor decides the zone. Without it, the single loudest gateway anywhere decides.	Devices appear on the floor above or below the one they are on
Ignore faint readings from another floor	Drops a reading heard by only a few gateways, all of them faint (by default: one gateway, weaker than −80 dBm). On by default.	A gateway on one floor briefly claims tags that are on the next
Weigh the floor over time	Keeps a running likelihood for each floor, fed by the same weighted votes, and moves a tag only when another floor clearly and steadily wins. One loud reading through the slab moves it a little; readings that keep agreeing win within a few sweeps, so a tag cannot stay on the wrong floor. While it is on, it alone decides floor changes; the room is then chosen within that floor.	Tags change floors repeatedly, or stay on the wrong floor for a long time
Change floor sooner while a tag is moving	For tags with a motion sensor: while the tag has moved in the last minute, the floor model accepts a new floor on less evidence, so a short trip to another floor is shown instead of being smoothed away. A tag lying still keeps the cautious setting. Tags without a motion sensor are not affected. Only acts while the floor is weighed over time.	Short trips to another floor are missing from the trail

Under the vote, How separated are your floors? offers three presets, Concrete slabs, Standard and Open plan, which set how loud a gateway must be to vote and how clearly one floor must win. Choose the preset that describes the building rather than typing values. Advanced thresholds holds the individual figures if there is a measured reason to change them:

Configuration Item	Default	Note
Full vote at or above	−65 dBm
Half vote at or above	−75 dBm
Ignored below	−80 dBm
Winning margin	0.3	How clearly one floor must win.
Grade each vote by signal strength	On	A vote grows evenly from nothing at Ignored below to a full vote, so a gateway at −66 dBm counts for more than one at −75 dBm. Off, votes fall into three fixed bands.

The faint-reading filter has two figures of its own: Heard by this many gateways or fewer (default 1) and …and all weaker than (default −80 dBm). A reading that meets both is dropped.

When Weigh the floor over time is on, Why here? mentions it by name ("…the floor model still places the device on…").

Floor level numbers

A gateway on another floor must be louder by the Extra to change floor margin for every level of difference. Two floors with the same Floor level (set on each venue), or levels in the wrong order, confuse every floor decision.

Speed tab

How quickly a move is shown. A tag is not moved the instant a gateway in a new room hears it; that would make tags near a wall flicker. The tab shows the result as a range of seconds until a tag that walks into a new room is shown there, together with the sweep interval (Sweeps run every … s.). That range is also the shortest visit that can be recorded: shorter visits are not written to the trail.

The range is the number of winning sweeps multiplied by the sweep interval, plus Hold before writing; the upper end adds one more sweep. The presets:

Preset	Suits	Sweeps to win in a row	Hold before writing	Shown after, 10 s sweeps	Shown after, 30 s sweeps
Stable	Desks, assets, equipment; fewest false moves	2	60 s	about 80–90 s	about 120–150 s
Balanced	Staff and visitor tags that move through the day	2	30 s	about 50–60 s	about 90–120 s
Responsive	Lobbies, wards, machine bays; notices arrivals first	1	15 s	about 25–35 s	about 45–75 s

The presets also set the other timing figures:

Preset	Settling hold at rest	Louder by, to take a tag	Louder by, to leave a room	Extra to change floor
Stable	30 s	8 dB	4 dB	6 dB
Balanced	15 s	6 dB	3 dB	6 dB
Responsive	10 s	5 dB	3 dB	4 dB

The preset also sets how firmly Room estimation holds a tag in its current room. Faster presets react sooner and record more room changes, almost all of them on tags in weak coverage. Measured on two days of recorded traffic from six tags, Balanced gave 21 % more room changes than Stable and Responsive 37 % more, and tags at a desk did not move under any of them.

The individual figures under the presets:

Configuration Item	Function
Sweeps to win in a row	How many sweeps in a row the new gateway must be louder. Ignores one-off reflections.
Hold before writing	Once the new room wins, how long it must keep winning before the trail records the move.
Settling hold at rest	Once a tag's motion sensor has been still this long, its gateway is held until it moves. Adds no delay to arriving; a gateway 10 dB louder always wins. 0 turns it off.
Louder by, to take a tag / Louder by, to leave a room	How much louder a new gateway must be. Below about 4 dB, tags move back and forth.
Extra to change floor	Added per floor of difference, because floors leak.

Leave a field empty to return to the installation default. None of these figures makes a gateway hear further: if a room is never detected, the remedy is a gateway in or near it.

NOTE

Settling hold at rest on this tab and Hold the room while a tag lies still on the Rooms tab are different. The settling hold applies to the gateway-by-gateway decision, adds no delay to arriving, and is overruled by a gateway 10 dB louder; the Rooms switch holds the room estimate itself for as long as the tag stays still.

Stability & records tab

Setting	Function	Use it when
Bermuda-style zone stability	Judges a move by the percentage change in signal rather than a fixed decibel margin. For venues with 4 or more gateways; no effect on venues with 1 to 3 gateways.	Tags still flip between zones on a busy, well-covered venue
Split long stays at midnight	A person's or asset's Trail tab and Reports > Sensor Trail show a stay that runs past midnight as one row per day, in the organisation's timezone: a trolley parked for three days is three rows, and selecting one day shows that day's part. Off, a stay is one row; on the Trail tab it then appears only on the day it began. Nothing stored changes, and the summaries (zone movement, entity summary, Entity Tracker) always count a stay once. On by default.	A multi-day stay is to be read day by day

If a trolley parked for three days is shown as one 72-hour stay, Split long stays at midnight is off.

When a tag's gateway goes quiet for a moment (a gateway restarting, a burst of interference), the tag is not handed straight to whichever other gateway still hears it faintly. With Bermuda-style zone stability on, the same other gateway has to win two sweeps in a row while the first stays silent; without it, the ordinary Sweeps to win in a row applies. A gateway that is really gone still hands its tags over, one sweep later. This is why a tag near a gateway that drops out does not jump to a distant room and straight back.

Platform-operator settings

Some parts of the chain are set by the operator of the platform, not on any page of the organisation's console. Contact the operator to have one changed.

Item	Reason
Sweep interval	How often every tag is re-read (installation default 10 s). It changes the timing of every preset on the Speed tab.
Measuring gateway hearing on the bench	It requires taking gateways off the ceiling. Rx can still be set by hand, or taken from the suggestions of a walk.
The filter for re-sent frames	Some gateways repeat the last message they heard from a tag for up to two minutes after losing it. Those copies are dropped from positioning automatically.

Configuration roadmap for a new floor

The following order has the fewest backtracks when a floor is set up from nothing:

(1) Upload the plan and set the scale line (Setting the scale).

(2) Find the walls (Import > Find rooms in the picture, or a CAD drawing), review and tidy them.

(3) Create the zones, set each one's capacity, and draw them edge to edge.

(4) Register the gateways and assign them to the venue and their zone.

(5) Place the gateways on the plan with their heights, and set Tags carried at.

(6) Walk the floor, covering every room and every corner, and finish the walk.

(7) Measure each tag model in use that is not the walk's model, on the bench.

(8) Turn on Room estimation, and review the coverage check.

(9) Check the Positioning method card, and override it only if the result is wrong.

Then choose Monitor > Live Monitor and walk the floor with a tag. Five minutes of watching a known tag's dot is the most direct check of the whole chain.

Troubleshooting

The coverage check says a room "cannot be shown". Cause: no gateway is in the room, and room estimation cannot tell it apart from its neighbours. Action: turn on Room estimation; if the room is still not shown, it needs a gateway in or near it. See A room is never detected.

After the walk, no gateway moved. Cause: the walk missed a corner. The walk report (Last walk report on the Calibrate gateways page) shows gateway positions: solved, none written with no point near the … corner(s). Action: walk again and include that corner, or use Solve positions to review and apply the result manually.

The walk report says "distance model: kept as is". Cause: on this floor, signal strength did not predict distance better than a plain guess. This is a property of the building, not a failed walk; the radio map and room estimation carry such floors. Action: check the fingerprint's Gateway coverage.

Positions became worse after the heights were set. Cause: the floor was walked before the heights existed. Action: walk the floor again.

A gateway is listed under Gateway coverage with a low percentage. Cause: it was offline, or moved, while the map was being learned. Action: fix the gateway, wait a day for readings to refill, then click Rebuild fingerprint.

The phone link stopped working. Cause: links last two hours. Action: on the desktop, click Continue on a phone again; when the link has expired the window shows This link just expired. and offers Re-issue.

The Image, Scale or Health tab cannot be found. Cause: the Map editor no longer has tabs. The picture, scale line and size are the three steps of floor setup (click the floor chip at the top, or press F); the health report is the coverage check (Coverage above the plan, or press H). Rooms, gateways, sensors and walls are groups in one floor list. Action: press Z, G, S or W to open a group, or use Find a room, gateway, sensor or wall.

A floor plan opens with no drawing tools. Cause: the role does not hold manage-floorplan; the plan shows You can view this floor plan but not change it. Action: ask an administrator for a role with Manage Floorplan Calibration. See Access to floor plans.

The Indoor Positioning panel shows Not Permitted. Cause: the role cannot change organisation settings (manage-settings-general). Action: ask an administrator who holds it.