If you don’t see this in your navigation, your administrator can switch the module on under Administration → Modules, or it may not be included in your plan. The module is called Readers there, and is part of Sensors.


How it works
A visit opens once a tag has been read enough times in a row (Min Reads to Open), and closes once
it has not been seen for a while (Absence Timeout Seconds). If it turns up again within the grace
window (Reopen Grace Seconds), the same visit carries on — a forklift that stops in a doorway is
one arrival, not four. A tag is in one place at a time: opening a visit at one antenna closes any
other open visit for that tag.
How reads move assets
A visit on its own records where the tag was seen. To act on it, switch on Raises Events for the antenna, then write an automation rule on the asset that runs when a tag arrives or departs. Rules can:- move the asset to the place the antenna points at, so its location in the register follows it through the doorway;
- notify somebody — “tell me when it leaves the yard”;
- check conditions about the read: which antenna and its purpose, the reader’s code, the tag, how long it stayed, how many times it was read, and the strongest signal.
Which side of a doorway
Every reader log — All activity, Present, Reads, Unrecognised tags and a reader’s Recent visits — shows the side of the doorway an antenna stands for as in, out or checkpoint. On the asset register, Last in / out, Last reader, Last antenna and Last in / out date say when each asset last went through a doorway. A site with a single antenna at its gate can still count in and out: give the antenna the in/out gate purpose. One antenna cannot see direction, so each time an item passes it counts as the opposite of the last time it passed a gate at the same site — in, then out, then in. An item seen for the first time is going says which side the first pass counts as, and Seconds before the opposite side counts (60 by default) keeps an item that lingers at the gate from being counted as leaving. One missed read puts every later pass the wrong way round, so a pass through a gate shows Change to out (or Change to in) to people who may configure readers. The correction is marked corrected, and every later pass of that item at that site is worked out again from it.The header
New reader adds one. A banner appears when an antenna has stopped reading while its reader keeps
reporting — one cut cable on a four-port reader looks exactly like a healthy reader with a quiet
doorway.
Present
Where things are lists every recent visit by a recognised tag.
A visit appears the moment a reader sees a tag that the register says is on something. Until a tag is
registered, its reads land under Unrecognised tags instead.
Readers


Unrecognised tags


On each row, This tag is on… lets you pick the asset the tag is attached to — search the register,
or use the scan button beside it to read the asset’s printed label; the tag is then
registered against that asset and every later read is recognised. It needs permission to create
assets. Not ours stops the tag being asked about — it keeps being seen, it just stops appearing
here. It needs permission to configure readers.
Each antenna records unrecognised tags one by one up to its Unknown Tag Cap per hour, so a flood of
cartons never affects a registered tag.
Reads


All activity
All activity is everything the readers produced, newest first, in one list: every visit, every unrecognised tag (including those marked not ours or claimed), every kept read, and each reader’s last message and last error. It is the tab to watch while commissioning a doorway — did anything arrive just now, and what became of it. Until anything has, it says Nothing has arrived yet. Tag, asset, reader or antenna searches the list. A toggle for each kind of entry there is — such as here, arriving, left, unrecognised, read, message and error — and for in, out and checkpoint narrows it, and the count of entries shown sits beside them.
An error row is drawn in red.
Adding a reader


For MQTT, Add it is held until there is a broker, a port from 1 to 65535 and a topic, and the first
one missing is named under the boxes. Add it creates the reader and opens it. Nothing it sees means anything until its antennas are
added. Adding readers needs permission to add readers and antennas.
One reader


State
When reads land nowhere
A read is recorded against the antenna number it arrives on, and the antenna is what says where that is. A read with no antenna to land on is placed nowhere: no visit opens, nothing arrives anywhere, and the tags it heard are not shown as being anywhere. So the reader’s screen warns when Reads are arriving for antenna N, which this reader does not have, or when This reader has no active antenna, with how many reads have had no antenna so far and when the latest was. A BLE gateway reports every read as antenna 1, so it needs antenna 1 even though it has no antenna port. Its tags still show when they were last heard and their battery, which is why such a reader can look half-working. Add antenna 1 (or the port the reads arrive on) opens the antenna form with the port, a name and the reader’s site filled in.Antennas, and where they point
Each row has edit and remove buttons.
Adding an antenna


Reading the payload
Every brand of reader sends a differently shaped message, so the shape is configuration rather than code. For a Bluetooth gateway of a make the product already knows, Start from a preset saves writing the map yourself: choose the gateway — HPE Aruba access points, Kontakt.io telemetry stream or Minew gateway (G1, G2, MG3, MG4) — and press Apply. A preset replaces the map, the payload format and the tag format, and runs its example message through the new map so you can see the reads it produces; the broker, the password and how the reader connects are left as they are. It is offered to people who may configure readers. Where a message comes through a gateway, the reads it produces show a Gateway column too. The map says which fields of a message hold the tag, the antenna and the signal. Paste a real message into A message to try it on — or use use the last one received — and press What does this give? to see the reads the map produces. This runs the same mapper that live messages go through. Save the map saves it. It is held, with a sentence under the box, until the map is a JSON object with afields object that says which field holds the tag; an empty map is
allowed, for a reader nobody has seen a message from yet.
Broker credentials
For a subscribed reader: a User name and Password for the broker. Store it saves them encrypted; afterwards only the last few characters are shown. No password is a supported state — a broker on a site network often needs none.Posting to this reader
For a reader that posts its messages in, this section replaces the broker settings.- This reader’s own address is for a reader with one box for a server address. Point it there and it posts whatever it emits — JSON, a form or a line of text. Copy the address copies it; Issue a key for this reader creates the key to send with it.
- If the reader cannot connect to that address appears where your installation offers it. Some older readers cannot make a secure connection to the address above and give up before posting anything. This second address takes the same key and the same messages, on a port that accepts the older connection. It is also shown beside the key when the key is first issued, since that is the only time the key can be read.
- Through a relay or middleware gives a worked example of trading an API key for a token and posting the reader’s messages. Copy the push example copies it.
Publishing to our MQTT broker
For a reader that posts to us, Publishing to our MQTT broker shows the broker settings to type into a gateway or reader whose firmware publishes over MQTT and cannot post: the host, the ports, the reader’s code as User name, and a key issued for this reader under Issue a key for this reader as Password. It publishes on any topic, and every message is read by the map. Without TLS the password crosses the network as typed, so that port takes only a key issued for this reader; use TLS wherever the gateway can.Try it without hardware
Sends one message through the whole path — mapped, resolved, turned into a visit, with any rules run against it. Send it writes for real, so use it on a test reader or expect the visit to appear.Recent visits
The last visits this reader saw: What, Antenna, Status (here or left) and Last seen.Editing a reader
Edit opens Edit reader, the same settings the reader was added with, plus who is told when it goes quiet. The payload map is not here — it stays in Reading the payload on the reader’s screen — and neither is the device the reader is filed under.

Removing a reader
Remove reader asks you to confirm. The reader stops being listed and its reads stop being accepted — the doorway goes dark — but nothing is erased: its antennas and every read already taken are kept. In some organisations removing a reader needs approval; you are told either way.When a reader goes down
The product watches every reader for silence and tells somebody once when it is sure a reader is down, and once when it is back — not every time its connection flickers.Is it alive
The Readers list and each reader’s screen say where a reader stands against that rule, beside its state:
The reader’s screen spells out the rule under Alive check. A reader with a heartbeat set is
judged on it; one with none is judged by its messages alone — so a heartbeat of 10 seconds on a
gateway that uploads every five minutes is why such a reader never comes back.
Any message from a reader counts as a sign of life, including a keepalive with no tags in it. A
reader that only speaks when it reads a tag is judged by its device’s silence window instead, so a
dock door with no traffic overnight is no longer reported offline every night. Pausing a reader
closes any outage without a message, and switching it back on starts the clock again.
Who is told. Each reader can name a person to tell (Who is told) and a second person to tell
as well (Also tell), whoever covers when the first is away, together with how often it sends a
heartbeat (Heartbeat every (seconds), 10 to 3,600) and how many it may miss
(Heartbeats it may miss, 1 to 20, default 3). Where a reader names nobody, the alert goes to the
head of the reader’s site, and where the site names nobody either, to the organisation’s
administrators — so an outage is never announced to nobody. All four are set under Knowing it is
alive and Who is told in Edit reader.
On the Notifications screen these events are under Sensors and readers
and are addressed to whoever looks after it, which means the people worked out above. You can
change their channels, add subscriptions for a role, or switch an event off there like any other.

