Track Devices

Device Tracker 6.1

Overview

Device Tracker can block user access to the device with either of the following optional features for device checkout:

  • User barcode scan - If enabled, the end user is presented with the Checkout screen, prompting the user to scan their user barcode to gain device access.
  • SSO signin - If enabled, the user logs in with their SSO credentials to gain access to the device.

Device Tracker operation and functionality is based on the user role of the user logged in.

To find a device, the misplaced device must be marked for retrieval by the administrator or manager. The “finding” device (the device performing the search) is used to determine the distance the user is located in relation to the “misplaced” device (the device to be found) using the visual proximity meter. When a device is found, recommission the device to place it back into the active device pool. Alternatively, decommission the device if it needs to be removed from the active device pool.

image Procedure to find a device (download this Quick Start Guide).

The following options are available to facilitate device tracking:

  • Use Automation to configure rules that trigger the workflow of finding lost mobile devices.
  • A note can be added at any time to capture comments specific to the device (e.g. device screen damaged) to aid in tracking or identifying problems with the device. This feature is available only for administrators and managers.

An administrator dashboard and manager dashboard are accessible via the web portal to view devices, access points and sites and take action to track devices.

Licenses are required on the devices and may be transferred from one device to another or removed from a device.


Device Checkout

Device Checkout is an optional feature configured by the administrator to block device access until a user performs one of the following on the device:

  • Signs in with SSO credentials
  • Scans a user barcode

Checkin/checkout must be enabled. The following sections describe how to use checkout using either of the above options.

SSO

When single sign-on SSO is activated and Enterprise Login Screen (ELS) is installed on the device, the user signs in to the device using SSO login credentials.

Sign in

When SSO is activated and Enterprise Login Screen is installed on the device, users sign in to the device by entering their SSO login credentials. After successful sign in, the user is granted access to the device and is checked out with the user name returned by SSO for accountability.

To sign in using SSO:

  1. In the Enterprise Login Screen, tap Sign in.
  2. In the company SSO sign in screen, enter the user credentials and tap Sign in or the related button to signin.
image       image
Enterprise Login Screen       Company SSO signin screen

Passcode

If the user cannot sign in to the device, either due to an SSO signin failure or a network outage, the administrator can supply a passcode for the user to enter on the device to bypass the SSO login. The passcode is set with an associated passcode group name through SSO integration under the Enterprise Login Screen Mobile Client section.

To bypass the SSO signin screen, in the ELS screen tap the menu at the top right, select Sign in with Passcode and enter the passcode supplied by the administrator.

image

Enter bypass passcode

This grants the user device access and checks out the user as "passcode_" followed by the passcode group name as displayed in the Mobile Devices dashboard in the Checked Out By column.

image

Checked in user from entering passcode

Signout

To signout of ELS, in Device Tracker tap the top right menu and select Sign out of Device. The user is signed out and the ELS screen appears for the next signin session.

image

Signout of ELS

On successful signout of ELS, the device is checked in and accountability is removed from Device Tracker.

User Barcode

When using barcode scanning for checkout (SSO is not activated), the user is required to scan the user barcode at the start of their work shift to checkout the device, then checkin the device at the end of the work shift. The checkout screen blocks device access, preventing the user from accessing the device until checkout is performed. When a device is checked-out, the user is associated with the particular device until the user checks in the device.

By default, if no barcode prefix is defined all barcodes are accepted. Specify a checkout barcode prefix to restrict checkout only to barcodes that begin with the specified prefix.

Note:

  • For Android 10 and higher, if "Display over other apps" permission is not granted, the user must manually launch the app once and grant this permission for checkout functionality to work properly.
  • If any other app also uses a screen overlay, the checkin/checkout feature may conflict with the other app. For example, this feature cannot be used with Zebra’s MotionWorks Proximity application.
  • The checkout barcode can be scanned when the device is in the lock screen. If the Android lock screen appears after the checkout screen is displayed, a checkout barcode can be scanned while the device is in the lock screen. The device is checked out, as seen after unlocking the device.
  • When DataWedge is disabled, it prevents the scanning of barcodes. Upon device checkin, an error message is displayed indicating that barcode scanning is disabled on the device. During this state, the device cannot be checked out. To resolve this, decommission the device and re-enable DataWedge. Then recommission the device.

Checkout

Perform a device checkout at the start of a work shift as follows:

  1. Remove the device from power to automatically display the checkout screen or launch the app on the device.

  2. The checkout screen appears, prompting to scan a barcode. When in the checkout screen, the user is prevented access to the device until checkout is performed. imageDevice checkout

  3. Scan the barcode associated with the user by pressing the scan trigger or tapping on the barcode image on the screen. If the administrator has set a prefix string in the barcode prefix option, the barcode must contain the prefix specified for checkout to be successful.

  4. A message appears indicating the user is checked-out successfully. The app is placed in the background.

  5. The user is now associated with the device.

Note: If Checkout is enabled, after a device is rebooted the Checkout screen may take up to one minute to be displayed.


Check-In

Choose one of the following options to Check-In a device:

Option 1:

  1. Launch the app.
  2. Tap on the options menu from the top right and select Check-In Device.
  3. The user is checked-in. The checkout screen appears prompting to scan a barcode.

Option 2:

  1. Connect the device to power.
  2. The user is checked-in. The checkout screen appears prompting to scan a barcode.

Option 3:

  1. Reboot the device.
  2. The checkout screen appears prompting to scan a barcode.

Mark Device To Find

When initiating the process to find a device, the misplaced device must first be set to the To Be Found state by the administrator or manager. The finding device, or the device performing the search, is used to determine the distance the user is located in relation to the “misplaced” device, or the device to be found. Location must be enabled on the finding device to perform the device search.

A device must be marked To Be Found before a device search can take place.

To mark a device "To Be Found":

  1. From the device list, tap and hold the device card of the misplaced device to find. Select Set To Find. image Device action menu
  2. The status is changed to To Be Found and the device is now listed in the To Be Found category in the dashboard.
  3. To proceed to find the device, continue to the next section Find a Device.

Managers and administrators can alternatively mark a device To Be Found as follows:

  1. Open the device list.
  2. Tap on a device card.
  3. Tap Enable Finding. image Manager/admin view to mark a device "To Be Found"

Lost Device Nearby

Lost Device Nearby is an optional feature (configured by the administrator) that proactively sends alert notifications to a device when a lost device is detected within close proximity. This allows the lost device to be found by nearby users in addition to any users that may be actively searching for the device. The nearby user that receives the alert notification can promptly initiate the finding process, expediting device recovery by allowing the lost device to be found more quickly with its vicinity immediately known. Alerts are sent as one or a combination of the following: audio, vibration, LED, and/or Android notification.

When the notification message appears on the detecting device, it includes the device model and device name of the lost device. Tap on the notification to start the finding process. If there are multiple lost devices detected nearby, a notification is received from each lost device. If the detecting device is online (internet is available), the Device Tracker Device Details screen appears and the user can start the finding process by tapping the Start Finding button. The user proceeds to find the lost device with the proximity indicator and play sound features.

Enabling Lost Device Nearby triggers continuous BLE scanning to detect nearby devices and send notifications when devices are detected. This continuous activity consumes additional battery power on the device - review your use case and battery requirements before enabling this feature.

image

Notifications of lost devices nearby

Alert notifications are received even if the detecting device is offline, as seen in the notification message which displays "offline" status for the detecting device. In this case, tap on the notification to immediately start the finding process. The Device Tracker app appears for the user to find the lost device with the proximity indicator. The detecting device cannot mark the lost device as "Found" or "Cannot Find" until the detecting device is back online. However, this can be done in the web portal by the manager or administrator.

image

Notification received when detecting device is offline

When Lost Device Nearby is enabled, the "To Be Found" screen displays a Nearby tab, which filters lost devices that are marked "To Be Found" and are receiving Bluetooth beacons while within nearby proximity.

image

To Be Found - Nearby Devices

When the detecting device is offline (no internet connectivity), nearby devices can still be detected from the BLE beacons received. The nearby device is displayed as "Unknown" along with its beacon ID:

image

Offline detecting device displaying nearby devices

The detecting device receives Lost Device Nearby notifications when all the following requirements are met:

  • The device must be in the "In Service" state.
  • The device must neither be charging nor in a low battery state (based on the Low battery threshold).
  • If Checkin/Checkout is enabled, the device must be Checked Out by a user.

Note: Any Lost Device Nearby notifications are removed when Bluetooth beacons are no longer detected from the lost device for at least 5 minutes. This is due to the lost device no longer: (1) located within close proximity of the detecting device, (2) emitting Bluetooth beacons, or (3) in the "To Be Found" state.


Find Device

A device search is initiated from the To Be Found device list. For an associate, the To Be Found device list is displayed after starting the client app. For an administrator or manager, the To Be Found device list is accessible via the dashboard.

When ready to perform the device search, the first step is to use the finding device to find the access point (AP) that the misplaced device is connected to. This provides the general location of the misplaced device. The user walks toward the AP, then uses the Bluetooth proximity indicator on the finding device to identify how close or far the misplaced device is located in relation to the finding device. To further pinpoint the device location, on the finding device tap Play Sound and listen for the audio sound being played on the misplaced device. Walk towards the sound to locate the misplaced device.

Play Sound is also useful if the proximity indicator is not operational (e.g. Bluetooth is disabled). Audio alerts can be played during the search process even if the lost device is in Do Not Disturb (DND) mode, with exceptions.

Device Tracker can locate devices even when the device loses battery power or is turned off, if the device has a secondary BLE.

To start the search process:

  1. Initiate the device search. Perform one of the following in the To Be Found device list:

    • Tap and hold the device card for the misplaced device. Select Start Finding from the device action menu.
      imageDevice action menu
      Or
    • Tap on the device card for the misplaced device to open the Device Details screen. Tap Start Finding.
    image                 image

                  "Start Finding" Associate view               "Start Finding" Manager/Admin view

  2. The device tracking screen appears. The device state is changed to Being Found.

  3. Check the Connected AP on the tracking screen on the misplaced device. Walk towards the known location of the AP.

  4. Using the BLE proximity meter, walk towards the misplaced device. The BLE proximity meter identifies the overall trend on how far or how close the user is located in relation to the misplaced device. The closer the misplaced, the further the blue indicator bar expands to the right. As the finding device approaches the misplaced device, the numerical value on the meter decreases as it reaches “Close” or “0” value. image Tracking screen with proximity meter

  5. Tap Play Sound on the finding device. The misplaced device emits a chirping sound to help identify its location. Walk towards the sound. Continue this step until the device is found. Note: When playing the sound, by design the Pixie Dust tone is played on the device.

  6. If the misplaced device is found, tap Device found. Select one of the following based on the behavior encountered:

    • The device is changed to the Found state if no automation rules are configured.

    • If Automation rules are configured with option Automatically Mark Devices "To Be Found" enabled, a message appears prompting the user to take action based on the rule(s) selected and to check each checkbox after action is taken. It is important to execute ALL actions specified, otherwise the device will return back to the To Be Found state after it is marked Found based on the automation process. After all action is taken and all checkboxes are checked, tap Confirm. The device state is changed to Found if automation option Automatically place device "In Service" when marked "Found" is disabled. If this option is enabled, the device state is changed to In Service. image

      Sample screen of action to take after device is found

  7. If the device is found and the automation option Automatically Place Device "In Service" When Marked "Found" is disabled, manually recommission the device to place it back into the active device pool. Alternatively, decommission the device if it needs to be removed from the active device pool.

  8. If the device is not found, tap Cannot Find. The device state is changed to Cannot Find.

The device is listed under the corresponding categories as seen from the admin dashboard or manager dashboard.

Administrators and managers can add a note to capture comments specific to the device, such as hardware damage or reason for decommision.

Behavior when locating a misplaced device in different scenarios:

  • If Bluetooth is turned off on a misplaced device that is powered-on and a user initiates locating that device, Device Tracker automatically turns on Bluetooth in the misplaced device to allow that device to be located using the proximity indicator. However, if the misplaced device is disconnected from the server, Bluetooth will not be turned on.
  • If Bluetooth is turned off on the misplaced device while it is being found, that device cannot be located using the proximity indicator. However, if the device is powered off, it can still be located using secondary BLE (if supported).
  • A device is in the Disconnected state when it does not communicate with the server for approximately 12 minutes. During this time, if a device search is performed on a misplaced device that has lost connection with the server, that device cannot be located using the proximity indicator and any attempt to Play Sound is ineffective since audio cannot be emitted from the disconnected device.
  • If a finding device initiates a device search prior to the misplaced device becoming Disconnected, the misplaced device can be found using the proximity indicator.
  • If Bluetooth is turned off on the finding device while it is locating the misplaced device, the misplaced device cannot be located using the proximity indicator on that finding device.
  • If Android Location Services is turned off on the finding device, it cannot locate the misplaced device using the proximity indicator.

Secondary BLE

For devices with secondary BLE beaconing capability, Device Tracker can locate the device if it loses battery power or is powered off. The location of the device is detected by signals transmitted from the secondary BLE beacon. Attempts to locate the device must occur soon after the device loses power, prior to loss of power from the secondary BLE beacon. The secondary BLE radio of some devices is located in the battery. Such devices are subject to the behavior described in battery-based BLE behavior.

When locating a device based on its secondary BLE beacon, the Play Sound feature is disabled during device search since it cannot function due to the loss of device power. The Secondary BLE state is viewed from the Device Details screen.

Usage Notes:

  • Secondary BLE differs from the built-in device primary BLE used for device tracking, which cannot operate once the device loses power.
  • While finding a device, the values seen in the BLE proximity indicator may differ when finding a device that is powered on (primary BLE) versus a device that is powered off (secondary BLE), particularly if the Reference RSSI is not specified for the battery-based secondary BLE. This is due to varying location and orientation of the secondary BLE antenna. During the finding process, the user should rely on the trend reflected in the BLE proximity meter to navigate to the misplaced device.

Play Sound

To find a device that is close by, play a sound on the lost or misplaced device through the Find Device process. Alternatively, managers and administrators can play sound from the web portal through the Actions menu from either the Mobile Devices dashboard or Device Details screen.

Note: When playing the sound, by design the Pixie Dust tone is played on the device.

To play sound through the Mobile Devices dashboard:

  1. Log into the web portal as a manager or administrator.
  2. Go to Dashboard > Mobile Devices.
  3. Tick the checkbox to select the desired device(s) to play sound.
  4. From the Actions dropdown, select Play Sound. image

To play sound through the Device Details screen:

  1. Log into the web portal as a manager or administrator.
  2. Go to Dashboard > Mobile Devices.
  3. Click on the row of the desired device to play sound.
  4. The Device Details screen appears. From the Actions dropdown, select Play Sound. image

Do Not Disturb (DND) Mode

DND mode is an Android feature that silences the device - it mutes sound and stops vibration. Device Tracker has the capability to play audio alerts when DND mode is turned on in the lost device, with exceptions (see below).

Turn on DND mode by performing one of the following methods:

  • Press the hardware volume +/- key (on the side of the device) then tap the Silent icon in the Zebra Volume Control UI to turn on silent mode.
  • In Android Settings > Sound > Zebra Volume Control, tap the Silent icon in the Zebra Volume Control UI to turn on silent mode.
  • In Android Quick Settings, tap the Do Not Disturb icon to turn on DND.
  • In Android Quick Settings, tap the drop-down for the Do Not Disturb icon to select Alarms only.
  • In Android Quick Settings, tap the drop-down for the Do Not Disturb icon to select Priority only.
  • In Android Quick Settings, tap the drop-down for the Do Not Disturb icon to select Total silence.
  • In Android Settings > Sound > Default notification sound, select Silent to set the default notification sound to silent. (This silences the device without DND mode.)

When DND is turned on based on the methods above, Device Tracker can play audio alerts in all cases except for the last two bullet points. In the last two cases, Device Tracker can no longer play a sound during the finding process in the following scenarios:

  • When a user gains access to Android Quick Settings to completely silence the device (see the second to last bullet point above).
  • When a user gains access to the Android Settings app and modifies the notification sound to silent mode (see the last bullet point above).

To ensure full operation of Device Tracker, Zebra recommends to restrict user access and prevent users from completely silencing a device by setting both of the following options:


Disable Finding

After a device is marked To Be Found, if the device search needs to be terminated follow these steps (applies to only managers and administrators):

  1. Open the device list.
  2. Tap on a device card.
  3. Tap Disable Finding. image Manager/admin view to disable finding

The device is removed from the To Be Found list and placed back In Service.


Bluetooth Scanners

When tracking is enabled for Bluetooth Scanners, two tabs are seen in the To Be Found screen in the mobile app:

  • Mobile Device - displays a list of mobile computers that have been marked To Be Found after being reported lost or misplaced
  • Bluetooth Scanner - displays the following:
    • My Bluetooth Scanner - shows the Bluetooth scanner that is paired and connected to the host mobile computer. The following information is displayed: device friendly name, connection status (connected, disconnected), MAC address, and battery level (from the battery icon). Only one Bluetooth scanner can be connected at any given time. If there is no Bluetooth scanner paired with the mobile computer, no device is listed in this section.
    • Other Bluetooth Scanners - shows a list of Bluetooth scanners that have been marked To Be Found after being reported lost or misplaced

image

Bluetooth Scanners in Device Tracker client

Pair/Unpair Bluetooth Scanner

To pair and connect a Bluetooth scanner to the mobile computer:

  1. Launch Bluetooth Pairing Utility, pre-installed on the mobile computer by default. image
  2. Use the Bluetooth scanner accessory to scan the barcode displayed. image
  3. Select whether to allow access to contacts and call history, and tap Pair in the confirmation message. image
  4. In Device Tracker mobile app, tap the Bluetooth Scanner tab in the To Be Found screen. My Bluetooth Scanner displays the paired and connected Bluetooth scanner. image

This procedure automatically registers the Bluetooth scanner to the Device Tracker system. If lost, it can be marked To Be Found to initiate the search.

To unpair the Bluetooth scanner, place it in a powered cradle. This automatically unpairs and disconnects the Bluetooth scanner from its associated mobile computer and removes it from the My Bluetooth Scanner section. image Unpair Bluetooth scanner

Find Bluetooth Scanner

To find a Bluetooth Scanner:

  1. On the device, open Device Tracker client. The To Be Found screen is displayed. image

  2. Tap on the device tile under My Bluetooth Scanner. The device details are listed along with the button to begin finding the device. image

  3. There are 3 different scenarios when finding a Bluetooth scanner:

    • Within Bluetooth range - To find a Bluetooth scanner within Bluetooth range, tap Start Finding button. The Bluetooth Scanner is placed in the To Be Found state and the proximity meter is displayed with the option to Play Sound. image Note: When finding a mobile computer or Bluetooth scanner, the proximity values displayed may be different on each device even when they are in the same distance to the finding device.

    • Out of Bluetooth range - In the web portal, the When disconnected Beeaconing Rule must be enabled. To find a Bluetooth scanner out of range, under Other Bluetooth Scanners, tap on the device to find. The device details screen appears. When the device is moved within Bluetooth range, the proximity meter will appear and provide the ability to play a sound to locate the device.

      image              image
      Unpaired Bluetooth scanner              Finding unpaired Bluetooth scanner that is out of range
    • Located nearby - The Lost Devices Nearby notifications setting must be enabled in the web portal. When a Bluetooth scanner is set To Be Found and Bluetooth beaconing is enabled on the Bluetooth scanner, the Nearby tab in the To Be Found screen displays the Bluetooth scanners that are detected to be in close proximity to the mobile computer. image

Virtual Tethering

Virtual Tethering notifies the user if a paired Bluetooth scanner is moving beyond the effective Bluetooth range from its associated mobile computer. A pop-up notification appears on the mobile computer indicating that the Bluetooth scanner is moving out of range. Supplemental notifications in the form of beeping, LED flashing, audio tone, and vibration can occur on the Bluetooth scanner and mobile computer. These alert options vary depending on the device. Virtual Tethering and its options are enabled in the Bluetooth Scanners setting from the web portal.

image

Virtual tethering pop-up notification


Decommission/Recommission Device

Decommission a device to remove it from the active device pool and recommission it to place it back into the active device pool.

Decommission a Device

When a device is no longer in use or needs to be removed from the active device pool, mark it as Decommissioned to prevent any further reporting to the server. This applies to situations when the device is being sent for repair, the device is being replaced, or the device is deprecated and needs to be removed. When a device is decommissioned, the license is automatically deallocated from the device and returned to the license pool for it to be reallocated to another device.

If a device is decommissioned by a manager, the device is removed from the assigned site and therefore no longer visible in the manager dashboard. The device can be recommissioned only by an administrator.

To decommission a device (admin/manager access required):

  1. Perform one of the following procedures:
    From the device list, tap and hold on the device card. Tap Decommission from the device action menu displayed. The Device Details screen appears.
    Or,
    If already in the Device Details screen, tap on the top right menu and select Decommission.

    image              image
    Access Decommission from device card.              Access Decommission from device details.
  2. The status is changed to Decommissioned and the user is prompted to enter a note.

  3. If desired, add a note by entering text in the Note section to indicate the reason for the device decommission. See Add/Edit a Note section.

  4. Tap back. The note is saved and the device is placed in the Decommissioned category in the dashboard.

Recommission a Device

Recommission a device after it is found or when it is previously Decommissioned and needs to be placed back into the active device pool (e.g. returned from repair). Recommissioning a device restarts the device status reporting to the server and can only be performed by an administrator.

When recommissioning a device, if a license is available it is automatically allocated to the device. If no license is available, the device remains in the decommissioned state and a note is automatically added indicating there is no license available. This note overwrites any pre-existing note. When a license is available, the admin or manager must recommission the device to allocate the license and manually delete the note.

Steps to recommission a device (administrator access required):

  1. In the dashboard, scroll down and tap Decommissioned or Found to display the corresponding list of devices.

  2. Perform one of the following procedures:
    Tap and hold the device card and select Recommission.
    Or,
    Tap the device card to display the Device Details screen. Tap on the top right menu and select Recommission.

    image              image
    Access Recommission from device card.              Access Recommission from device details.
  3. The Status is changed to In Service, as seen in the Device Details screen.

  4. Tap the Note section to enter or edit text indicating the reason why the device is recommissioned.


Add/Edit Note

Administrators and managers can add a note to capture comments specific to the device to help in device tracking or identifying device problems. For example, a comment could be "device screen damaged".

To add or edit a note:

  1. From the device list of any category accessed from the dashboard, tap and hold the device card and tap Add a Note. If a note already exists, the option is provided to Edit a Note.

  2. The Note section appears in the Device Details screen prompting to enter in text. imageEnter a note or comment

  3. After entering text for the note, tap the back button.

  4. The note is saved and can be viewed in the Device Details screen.


See Also