Install & Setup

Device Tracker 5.0

Overview

Device Tracker is a cloud-based solution that consists of:

  • A cloud-based server that is hosted and managed by Zebra.
  • A client software that runs on Zebra Android devices.

Installation on the device is required for the device to communicate with the server and for devices to be tracked by the solution. This section discusses how to install and enable Device Tracker on the mobile device. Contact Zebra services for access to Device Tracker cloud and to procure licenses prior to installation.


Important Note

Backward Compatibility - Device Tracker Cloud Server v5.0 or above supports Client software versions 4.0, 4.1 and 4.2. Starting on January 1, 2023, Device Tracker Cloud Server will no longer support Device Tracker Client versions 4.0, 4.1 and 4.2. The device must be upgraded with Device Tracker Client version 5.0 or above. See the Zebra Support Portal for the latest Device Tracker client.


Requirements

Device Requirements

Requirements for Device Tracker client on the device:

  • Supported Devices - See compatible devices table on the Zebra support portal.
  • Operating System - Only supported on select Android 8 Oreo, Android 10 and Android 11 GMS devices. See Device Tracker Support on Zebra support portal for compatible devices.
    Note: For Android 11, all LG updates (including upcoming releases) support Device Tracker except for LG update 11-20-18.00, which requires the April 2022 hotfix for support. For A11 LG updates, see the respective product page in Zebra support portal.
  • Optionally, Secondary BLE allows a device to be located if it loses battery power or is powered off. This is a hardware feature available on select supported devices with special batteries that are capable of secondary BLE; see the device compatibility table. Also see Secondary BLE Configuration for instructions to enable this feature.
  • Device licenses are required for Device Tracker to operate. Contact a Zebra reseller to procure licenses.

Network Requirements

Network requirements for communication between the device client app and the cloud server:

  • Open HTTPS port. By default, port 443 is typically used for HTTPS communication. However, this may vary based on network configuration.

  • For admins to access the web portal, allow the web portal URL through the firewall or proxy (supplied by Zebra during onboarding).

  • For device access and communication to the server, allow the following domains through the firewall or proxy.

    • If the firewall or proxy supports wildcards, add the following domains to the allow list:

      • connectivitycheck.gstatic.com
      • *.googleapis.com
      • *.firebaseio.com
      • *.cloudfunctions.net
      • [ProjectID].firebaseapp.com 1
    • If the firewall or proxy does not support wildcards, add the following domains to the allow list:

      • connectivitycheck.gstatic.com
      • www.googleapis.com
      • firestore.googleapis.com
      • cloudfunctions.googleapis.com
      • us-central1-[ProjectID].cloudfunctions.net 1
      • [ProjectID].firebaseio.com 1
      • [ProjectID]-default-rtdb.firebaseio.com 1
      • s-usc1c-nss-XXXX.firebaseio.com 2
      • [ProjectID].firebaseapp.com

    1[ProjectID] is supplied by Zebra services during the onboarding process. An XML file is supplied, which contains a string similar to:

    <parm name="ProjectId" value="<customer name>-dtrk-na-p" />
    

    The "value" field contains the ProjectID. In this example, the project ID is: <customer name>-dtrk-na-p

    2XXXX represents a dynamic range of numbers from 0000–9999. The domain name and range are controlled by Google and can change at any time. To retrieve the latest URLs associated with this domain name, create a script to regularly look up the URLs using https://[ProjectID].firebaseio.com/.settings/owner.json and update the rules accordingly.

If the password is reset, an email is sent from zdtrksupport@zebra.com.

Web Portal Requirements

The web portal allows adminstrators to configure Device Tracker, manage users and view licenses.

To access the web portal, in a supported browser enter the URL provided by Zebra during onboarding. The supported browsers are:

  • Chrome
  • Edge
  • Safari (v14.0 and later)

For first-time use, the administrator must set their password by clicking Forgot Password in the web portal and entering their email address, which is registered as a user in the system. An email will be sent to the administrator describing how to set the password in order for the administrator to login.

Licenses

End-user licenses are required for Device Tracker to operate. Additionally, separate BLE licenses are required for secondary BLE operation, allowing devices to be tracked even after losing battery power. See Licensing.


Install Manually

Steps to manually install Device Tracker client app on the device:

  1. Open the required ports and allow the domains specified in network requirements for the device to communicate to the cloud server.
  2. Connect the device to a Wi-Fi network that can access the cloud server based on the network requirements.
  3. Enable Bluetooth and Location services on the device to allow device tracking.
  4. Download Device Tracker client from Zebra support portal and install it on the device.
  5. Launch Device Tracker app. Grant all permissions when prompted. For Android 11 and higher, when granting Location permissions, choose option “Allow all the time”.
  6. Launch StageNow client and scan the barcode from the .PDF file provided by Zebra during the onboarding process. This configures Device Tracker with the cloud server settings.
  7. Optionally, enable secondary BLE to allow devices that support this feature to be located even when powered off. Follow instructions in Secondary BLE Configuration to enable and configure secondary BLE.

Install through an EMM

For mass deployment, install Device Tracker client on devices through an EMM. A server connectivity XML file is provided by Zebra services to configure Device Tracker with the server settings.

Installation Steps

To install and configure Device Tracker through an EMM:

  1. Open the required ports and allow the domains specified in network requirements for devices to communicate to the cloud server.
  2. Connect the device to a Wi-Fi network that can access the cloud server based on the network requirements.
  3. Enable Bluetooth and Location services on the device to allow device tracking.
  4. Download Device Tracker client from the Zebra support portal and deploy it onto the device through EMM. Grant the following permissions through EMM, such as creating a permissions profile:
    • android.permission.READ_PHONE_STATE – Required to read the device serial number and register devices with the Device Tracker server for tracking.
    • android.permission.ACCESS_BACKGROUND_LOCATION – Required to find devices using the Bluetooth proximity meter.
    • android.permission.ACCESS_FINE_LOCATION – Required to find devices using the Bluetooth proximity meter.
  5. Download and deploy Device Tracker MX XML file. This grants permissions to display over other apps, disable battery optimization and starts the tracking service.
  6. Download and deploy the server connectivity settings XML file provided by Zebra during the onboarding process.
  7. Optionally, enable secondary BLE to allow devices that support this feature to be located even when powered off. Follow instructions in Secondary BLE Configuration to enable and configure secondary BLE.

Installation Notes

  • When installing Device Tracker client on a device through an EMM, some EMMs do not grant all the permissions required for the app to run in the background. Alternatively, an XML file granting all permissions can be generated from a StageNow profile and consumed by the EMM.
  • Deployment with XML may vary between different EMM systems. Refer to the EMM guide.

Upgrade

Any previous version of Device Tracker below v5.0 must be uninstalled before installing this version. Starting with v5.0, a change was required to the app package name and app signature, resulting to new MX XML and server connectivity XML files. Follow the updated installation instructions to generate the new deployment package.


Uninstallation

To uninstall Device Tracker from the device, remove the Device Tracker client app manually or through an EMM.

Termination

To terminate Device Tracker Cloud, contact Zebra services. This removes the cloud server instance and deletes all data stored.


See Also