Push your reader to this URL.
Every POST /rfid/<token> from your reader appears live below — with the raw JSON payload, source IP, and parsed tag data. This session is private to this browser tab.
Dashboard
Overview of your reader webhook activity. Point your reader at the URL below and the live feed populates the moment data starts flowing.
Webhook health
— · waitingEvents / sec
last 60 sRecent activity
0 eventsWaiting for first event
Configure your reader to POST to the URL above, or click Send test event below to verify your connection.
Per-reader breakdown
0 readersNo readers seen yet.
Top tags
by reads, top 5No tags yet.
Test your webhook
verify connectivityFire a sample tag_read event at your webhook to verify the full path before connecting your reader.
Or test from a terminal
loading…
Live feed
Real-time events from your reader webhook, with parsed tags, raw JSON, and per-reader breakdowns.
Tags
0Events
0Waiting for first event
Configure your reader to POST to the URL above and you'll see it appear here.
Analytics
Throughput, tag discovery, gap distribution, per-reader breakdown, cross-reads, and activity heatmap.
Throughput
events per minute, last 30 minTag discovery
— unique tagsRead-count distribution
reads per tagInter-event gap
— gapsConnection health
— sessionPer-reader breakdown
0 readers| Reader | Events | Events / min | Unique tags | Total reads | Avg payload | Mean gap | Last seen |
|---|
Cross-reads
tags seen by 2+ readers| EPC | Readers | Per-reader reads |
|---|
Activity heatmap
reads per reader over timeTop tags
by read count, top 10| EPC | Reader(s) | Reads | % of total | First seen | Last seen |
|---|
QC check
Paste your expected EPCs and verify the reader covers your inventory — matched, missing, and unexpected tags in real time.
Expected tags
0 EPCsPaste the EPCs you expect to read — one per line. The list is matched live against incoming reads. Stored in this browser per session.
QC result
no reference listWebhooks
Each webhook is a unique URL your readers POST to. Create as many as you need — one per reader, one per test scenario, one per environment.
Loading webhooks…
Saved sessions
Snapshots of past test runs, persisted in your account. Load one to review its events, compare it against your current live session, or delete when no longer needed.
Readers
Org-wide registry of every reader that has sent data. Give each a friendly label, location, and notes — they're shared across all users, so "pda" becomes "CX1500N Handheld" for everyone. New readers register automatically.
| Reader (raw) | Label | Location | Notes | Last seen | |
|---|---|---|---|---|---|
| Loading… | |||||
Settings
Tune the platform to your deployment — timing thresholds, custom JSON fields to surface, and per-webhook integrations.
Timing thresholds
When tags / readers / events count as "stale", "present", "silent", or a dropout. Seconds.
Custom payload fields
Surface extra JSON fields your reader sends. One path per line — dot notation with [] for array wildcards. Shown on event rows and CSV export.
reader_name, event_data[].rssiAPI tokens
Long-lived tokens for programmatic access — use as Authorization: Bearer rs_… on any /api/* endpoint. The full token is shown once at creation.
| Name | Prefix | Last used | Created | |
|---|---|---|---|---|
| No API tokens yet. | ||||
Monitor
Everything across all users — live webhooks and saved sessions. Open any one to review it in real time, so you can see what's happening and help when needed.
| Status | Owner | Webhook | Events | Tags | Last event | Watching | |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Users
Invite teammates, change roles, reset passwords, disable accounts. Admins can manage everyone; regular users see only their own data.
Invite a new user
Pick a temporary password and share it securely; they should change it on first sign-in.
Existing users
All accounts on the platform. Hover for actions.
| Username | Name | Role | Last login | Actions |
|---|---|---|---|---|
| Loading… | ||||
Audit log
Append-only history of platform activity: sign-ins, user changes, webhook creates/deletes, configuration writes, share-link issuance.
| When | Who | Action | Target | Details | IP |
|---|---|---|---|---|---|
| Loading… | |||||
System health
Live process and platform metrics. Refreshes every 5 seconds while this page is open.
Object counts
Total rows in each persisted table.
Process
— · Node — · started —
Downloads
Identium ReaderSense desktop application — connect, configure, AI-test, and QC your Identium UHF readers. Installers below are hosted on this server; your download is logged for accountability.
Loading installers…
macOS prerequisite — install Mono first
The macOS build relies on Mono to run the .NET-based RFID bridge that talks to the reader. Open Terminal and run:
brew install mono
If the app shows "Identium ReaderSense is damaged and can't be opened", strip the download-quarantine attribute once with:
xattr -cr "/Applications/Identium ReaderSense.app"
Windows installer
SmartScreen may show "Windows protected your PC" — the installer isn't code-signed. Click More info → Run anyway. No prerequisites; everything bundles in the installer.
User guide
Everything you need to go from "fresh account" to "reader pushing tags into the platform". Six minutes from end to end.
What is ReaderSense?
ReaderSense is two things working together:
- Desktop application (Windows / macOS) — connects directly to an Identium UHF reader over the local network, lets you tune its settings, run inventory, and push tag data out as JSON webhooks. Includes AISense (auto-tunes reader parameters against your actual tags) and a 17-test QC module for production-line acceptance.
- This platform at
identiumone.com/ReaderSense/— receives the webhooks, visualises the live feed, provides analytics and QC checks, and stores named snapshots you can share with your team or customers.
Typical flow: install the desktop app on a laptop near the reader → point it at the reader → in Auto Mode, give it the webhook URL from this platform → log in here to see tags flowing live.
Install the desktop app
Open the Downloads module and grab the installer that matches your operating system:
- Windows 10 / 11 (x64) — double-click the
.exe; click "More info → Run anyway" if SmartScreen warns. No prerequisites. - macOS — Intel — open the
.dmg, drag the app into Applications. Install Mono first viabrew install mono. - macOS — Apple Silicon (M1 / M2 / M3) — same flow with the
-arm64.dmg. If you see "damaged and can't be opened", runxattr -cr "/Applications/Identium ReaderSense.app"in Terminal once.
Sign in to the platform
You're already here. Bookmark https://identiumone.com/ReaderSense/. If you're an admin, invite teammates from the Users module — each gets their own login and their own webhook tokens.
Change your password from the user menu (bottom-left of the sidebar) → Change password. The first admin password was set at deploy time and should be rotated immediately.
Create a webhook
Open the Webhooks module and click New webhook. Give it a friendly name (e.g. "Loading bay A" or "QA bench"). You get a URL of the form:
http://213.210.21.60:4612/rfid/<your-token>
This is plain HTTP intentionally — Identium readers can't speak HTTPS for outbound webhooks. The URL is public; the token in the path is what scopes incoming data to your session. Anyone with the token can post; the token isn't a secret per se, but a fresh one isn't discoverable without your account.
You can have as many webhooks as you need — one per reader, one per test scenario, etc.
Configure the reader
Open the ReaderSense desktop app:
- Connect — enter your reader's IP and click Connect. If you don't know it, the app's Discovery tool finds readers on your subnet.
- Inventory — verify the reader sees your tags. Use Settings → power and antenna config to dial in coverage. Or run AISense to have the app empirically pick the best settings against your real tags.
- Auto Mode — set the upload destination. Choose Wi-Fi or LAN as the upload interface, paste the webhook URL from this platform into the URL field, click Apply Configuration, then Start Auto Mode.
The reader will start POSTing tag-coming events. The very first one appears on the platform's Dashboard within seconds — the URL bar flashes to confirm.
Monitor the live feed
The Live feed module shows every event in real time with the parsed JSON, source IP, reader name, tag list, and HTTP headers. Click any event to see its full payload + a payload-validity report explaining anything that's off-spec.
The Analytics module aggregates throughput, tag discovery, gap distribution, per-reader breakdown, cross-reads, the activity heatmap, and the connection-health timeline. Useful for tuning antennas and detecting flaky links.
Run a QC test
Open QC check, paste the list of EPCs you expect the reader to read (one per line), and click Apply list. The page splits into matched / missing / unexpected in real time. Good for production-line acceptance ("did all 50 tags on this pallet read?").
For a printable sign-off, hit the Report button (Live feed → topbar). You get a clean branded HTML/PDF with summary, per-reader breakdown, QC result, connection health, and top tags.
Programmatic access (API tokens)
Open Settings → API tokens. Create a named token (shown once at creation — save it). Use it as a Bearer token on any /api/* endpoint:
curl -H "Authorization: Bearer rs_…" \ https://identiumone.com/ReaderSense/api/webhooks
Perfect for CI pipelines, monitoring scripts, or piping ReaderSense data into your own BI tools.
Troubleshooting
No events arriving. Check the reader is in Auto Mode and the URL it has matches the one on your webhook. The platform's Dashboard shows when the last event arrived; if "never", the reader hasn't POSTed yet. Confirm the reader can reach 213.210.21.60 on port 4612 outbound (firewalls sometimes block it).
"Reader silent" banner. The reader was sending and stopped. Common causes: network blip, reader rebooted, Auto Mode was disabled, or the reader's clock drifted enough to invalidate the session. Check the Connection health panel in Analytics for the dropout timing.
"Damaged and can't be opened" on macOS. Gatekeeper quarantine — run xattr -cr "/Applications/Identium ReaderSense.app" in Terminal once.
404 on download links. The platform server doesn't have the latest installer cached. Ask the admin to re-pull from the GitHub release.
Forgot your password. Ask an admin to reset it from the Users module.