Skip to main content

Cloud Reader Setup Guide

This guide explains how to add and configure a cloud-managed reader in Tagnet. Cloud readers are RFID readers that cannot be directly accessed from the Tagnet application, typically because they are on a different network or behind a firewall. Instead of deploying configuration automatically, you'll manually configure the reader using its web interface.

Overview​

Cloud readers differ from on-premises readers in several ways:

FeatureOn-Premises ReaderCloud Reader
Configuration deploymentAutomatic via TagnetManual via reader web UI
Start/Stop controlAvailable in TagnetManual via reader web UI
Connection infoAvailableRequired for setup
Telemetry & scan dataAutomaticAutomatic (after manual setup)

Prerequisites​

Before starting, ensure you have:

  • Access to Tagnet with Contributor or Admin role
  • Network access to the reader's web interface (usually via VPN or direct connection)
  • The reader's IP address and login credentials
  • The reader's MAC address (found on the device label or in its web interface)

Zebra FX and ATR Readers​

Step 1: Add the Cloud Reader in Tagnet​

  1. Navigate to Devices in the main menu
  2. Open the Add menu and choose Device
  3. Choose Cloud managed

This opens a single form page, not a multi-step wizard: scroll through its sections (use the anchor rail on the left to jump between them), fill in what's required, and save once at the bottom. If your organization has more than one site scope, an Availability section leads the form; choosing the site there decides which device types and groups the rest of the form offers, and is skipped automatically on a single-site deployment.

  • Basics: Name (required, must be unique), optional Description, Reader model (e.g., Zebra Technologies FX7500), and Antenna count
  • Connection: MAC address (required for identification)
  • Reader configuration: antenna, power, and read settings for the model you picked; see Zebra FX Configuration for what each field does. Cloud readers can't be reached from Tagnet, so this configuration isn't deployed automatically, it's what you'll copy into the reader's own IoT Connector in Step 4 below
  • Organization: optional Device type and Device group, filtered to the site chosen under Availability
  • Scan event processing: how this reader's tag reads become scan events (processing mode, quiet period, max duration, and cooldown). With a device group chosen, each setting offers Inherit from group; without one, the defaults are Multi Tag Passage (5 second quiet period, 15 second max duration) and no cooldown. Choose Single Tag Passage for a reader that also sees tags that do not move; see Processing Modes. Quiet period and max duration are only editable when this reader stores its own passage timings, and choosing or clearing a group resets them to the group's values or the system defaults
  • Read point location: where the reader is, chosen from the site's locations, so a Move Inventory action can send items here. Leave it empty to inherit the group's location. See Read Point Location

Click Create reader at the bottom of the page. The form validates as you go: the anchor rail flags any section still missing something required, and the sticky footer explains what's outstanding if Create reader is unavailable.

Once created, the page switches to show the Ingest Endpoint and Operating Mode Config you'll need for manual setup of the reader. Keep this page open; you'll copy values from it during the steps below. If you navigate away, these same values are always available later from the reader's own Connection info tab.

Step 2: Configure the Reader's IoT Connector​

Important: Ensure the IoT Connector is stopped and disconnected in Communication > Zebra IoT Connector > Connection before making changes to the Configuration menu.

Access the Reader Web Interface​

  1. Open a browser and navigate to the reader's IP address (e.g., https://192.168.1.100)
  2. Log in with administrator credentials (default: admin/change)

Configure the Ingest Endpoint​

  1. Navigate to Communication > Zebra IoT Connector > Configuration
  2. Click Add Endpoint and enter:
    • Endpoint Type: HTTP POST
    • Endpoint Name: TAGNET-INGEST
    • Endpoint Description: Send tag data and telemetry to Tagnet
    • URL: Copy from the Endpoint section in Connection info
    • Authentication Type: BASIC
    • User Name: Copy from the Ingest credential section in Connection info
    • Password: Copy from the Ingest credential section in Connection info
  3. Click Add
  4. Set Tag Data Interface1 to TAGNET-INGEST
  5. Set Management Events Interface to TAGNET-INGEST
  6. Click Update

Step 3: Connect and Start the Reader​

The reader must be started before the custom operating mode can be applied in the next step.

  1. Navigate to Communication > Zebra IoT Connector > Connection
  2. Click the Connect button and wait for connection confirmation
  3. Click the Start button
  4. Wait for the confirmation message: Start Read Tags is Successful... Sending Data to the Endpoint TAGNET-INGEST

Step 4: Configure the Operating Mode​

  1. Navigate to Communication > Zebra IoT Connector > Operating Mode
  2. Select the Custom radio button
  3. In Tagnet, go to the Operating Mode Config section of the reader's Connection info tab
  4. Click Copy JSON to copy the entire configuration
  5. Paste the JSON into the Custom text field on the reader
  6. Click Save
  7. Wait for the message: Successfully mode configuration updated.

The reader is now configured and sending data to Tagnet.

Verification​

After completing the setup:

  1. In Tagnet, navigate to the Devices page
  2. Your cloud reader's status should change from Not Connected to Connected once telemetry is received
  3. Check the Ingest History to verify heartbeat messages are arriving
  4. Present RFID tags to the reader and verify scan data appears in Tagnet

Troubleshooting​

Reader shows "Not Connected" in Tagnet​

  • Verify the reader's IoT Connector is started and connected
  • Check that the endpoint URLs are correct (no typos)
  • Verify the username and password match exactly
  • Ensure network connectivity between the reader and Tagnet server
  • Check firewall rules allow outbound HTTPS from the reader

No scan data appearing​

  • Verify Tag Data Interface1 is set to TAGNET-INGEST
  • Check that the reader is in Started state
  • Verify the operating mode JSON was saved successfully
  • Present tags within range of the antennas

Authentication errors in reader logs​

  • Re-copy the username and password from Tagnet's Connection info
  • Ensure no extra spaces were copied
  • Verify the reader credential was generated (check Connection info shows credentials)

Operating mode won't save​

  • Ensure you selected the Custom radio button before pasting
  • Verify the JSON is valid (no truncation during copy/paste)
  • Check for any error messages on the page

Important Notes​

Device Configuration Changes​

Each device configuration in Tagnet includes the endpoint URL and operating mode settings. If you:

  • Change the device's configuration settings
  • Regenerate device credentials
  • Update endpoint configuration in Tagnet

You must manually re-apply these changes to the cloud reader's web interface using the updated Connection info. Please note that if there are any changes to the endpoint (URL, auth, etc.) the reader must be rebooted. If there are changes to the Operating Mode, the IoT Connector can be stopped and started (or reboot the reader).

Credential Security​

The Connection info tab displays sensitive credentials. Treat these values with the same security as passwords:

  • Don't share screenshots containing credentials
  • Navigate away from the Connection info tab when finished
  • Use the password visibility toggle only when necessary

Credential Rotation

Each cloud reader gets a single Ingest credential, used for HTTP Basic authentication on its tag data posts. Rotating the password is a two-step operation with a brief window of downtime:

  1. Choose Regenerate ingest password from the Actions menu on the device's page (admin only) and copy the password it shows
  2. Immediately update the corresponding credential in the reader's IoT Connector configuration

The old password stops working as soon as the new one is generated, so plan the rotation for a low-traffic window; the reader buffers reads locally and replays them once it's reconfigured and reconnected.

Admin Credential Management

Administrators can choose Manage credentials from the Actions menu on the device's page to:

  • View credential status and last-used timestamps
  • Resolve account lockouts caused by failed authentication attempts
  • Regenerate the Ingest credential's password
  • Delete a credential that's no longer needed (Tagnet blocks deleting the last active Ingest credential a device can still authenticate with, so a device can never be left unable to post data)

After regenerating a password, you must update the corresponding credential in the reader's web interface.

Multiple Devices​

When setting up multiple cloud readers, each device needs its own configuration in Tagnet with unique credentials. The MAC address is used to identify which device is sending data, so ensure it's entered correctly.

Quick Reference​

Tagnet LocationReader Web UI Location
Connection info > Endpoint / Ingest credentialConfiguration > Add Endpoint (TAGNET-INGEST)
Connection info > Operating Mode ConfigOperating Mode > Custom
Reader Web UI ActionMenu Path
Add endpointCommunication > Zebra IoT Connector > Configuration
Connect IoT ConnectorCommunication > Zebra IoT Connector > Connection
Configure operating modeCommunication > Zebra IoT Connector > Operating Mode
Start readingCommunication > Zebra IoT Connector > Connection > Start