Pairing and Assigning BreakPoint Wearables to Workers

Pairing a BreakPoint wearable is a two-step handshake: first you register the physical device with your Console so the platform knows it belongs to your organization, then you assign it to a specific worker so every signal it transmits is attributed to the right person. The entire process takes about three minutes per device and requires only a browser and the device itself — no app download, no Bluetooth pairing on your phone, no command-line tools. This guide covers unboxing, pre-charge, pairing, assignment, and sync verification, plus troubleshooting steps for the most common issues you may encounter.

​

What’s in the Box

Each BreakPoint wearable ships in individual packaging that contains everything you need to get a single device live:

• BreakPoint Wearable Device — the sensor unit with integrated UWB radio, optical heart-rate sensor, GPS, and tap button
• Magnetic Charging Dock — a puck-style charger that attaches to the back of the device via magnets; connects to any USB-A power source
• Clip Attachment — a reinforced badge-style clip for attaching the wearable to a vest, lanyard, or collar
• Quick-Start Card — a small reference card with a QR code that links to this documentation and a printed serial number for manual entry

Keep the quick-start card accessible during the pairing process — the QR code on the card is the fastest way to register the device in the Console.

​

Step 1: Charge the Device Before First Use

BreakPoint wearables ship with a partial charge sufficient for the pairing process, but you should bring each device to a full charge before handing it to a worker for a full shift.

1. Align the magnetic charging dock to the back of the wearable. You will feel a gentle magnetic snap when it is correctly seated.
2. Connect the dock’s USB-A cable to any standard USB power source (laptop port, wall adapter, or multi-port charging station).
3. The device’s status LED turns solid amber while charging. A solid green LED indicates a full charge.
4. Allow approximately 90 minutes for a full charge from empty. A fully charged device provides up to 14 hours of continuous operation.

​

Pairing and Assignment Flow

​

Troubleshooting

Device does not appear in the Console after pairing

If the device row does not appear within 60 seconds of completing the pairing wizard, try the following steps in order:

1. Hard refresh the Console (Ctrl+Shift+R on Windows/Linux, Cmd+Shift+R on macOS). The Devices page does not always auto-refresh in older browsers.
2. Confirm the serial number. Go to Devices → Add Device and re-enter the serial. If the Console returns a “Device not found” error, the serial may have been transcribed incorrectly — check the physical label on the back of the device.
3. Check your organization’s device limit. Free trial accounts are capped at five devices. If you have reached your limit, you’ll see a quota warning in the pairing wizard. Contact your account team to increase your limit.
4. Confirm the device is powered on. The LED should be lit. If it is not, hold the button for two seconds to power on, or place the device on the charger for five minutes and try again.

Device shows red Offline status after pairing

A red offline status means the wearable cannot reach BreakPoint’s cloud. Common causes and fixes:

1. Cellular coverage: If the deployment site has weak or no cellular signal, the device cannot transmit over cellular. Check BreakPoint’s coverage map for your region, or contact your account team about deploying Bluetooth gateway hubs that relay device data over your site’s Wi-Fi.
2. Outdated firmware: A device running significantly outdated firmware may fail to connect. Bring the device within range of Wi-Fi or a BreakPoint gateway hub and trigger a manual update from Devices → [Device Name] → Update Firmware.
3. Hardware fault: If the device LED is red immediately on startup before it has had time to search for a signal, the device may have a hardware fault. Contact BreakPoint Support with the serial number for a replacement.

Low battery warning appearing immediately after full charge

If the Console shows an amber low-battery status on a device that was just fully charged, the amber LED should have gone green before the device was removed from the charger. Verify the following:

1. Check the charging connection. Reconnect the magnetic dock — misaligned magnets can create the appearance of charging (the dock is connected) without actually delivering current.
2. Check the USB power source. Some low-power USB ports (particularly on older laptops) do not provide enough current to charge the device. Use a USB wall adapter rated at 5V / 1A or higher.
3. Battery calibration. On a new device, the battery indicator can be miscalibrated. Run the device down to automatic shutdown, then perform a full charge from empty. This resets the battery gauge.

Worker's taps are not registering in TimeKeeper

If a worker’s clock-in or break taps are not appearing in the TimeKeeper attendance record:

1. Confirm the device is assigned to the correct worker profile. Go to Devices → [Device Name] and check the assigned worker. If the device is listed as “Unassigned,” tap events are discarded.
2. Confirm the worker has an active shift schedule. TimeKeeper only logs tap events for workers who have a shift schedule configured at their assigned location. Go to Team → Workers → [Worker Name] → Shift and verify a schedule is set.
3. Check the tap gesture. A clock-in requires a double-tap on the front face of the device within one second. A single tap triggers only a vibration confirmation with no data event. Have the worker practice the gesture.
4. Check for sync lag. Tap events buffer on the device when cellular signal is weak and upload in bulk when connectivity is restored. Events timestamped during a connectivity gap will appear in TimeKeeper retroactively once the device syncs — typically within a few minutes of returning to coverage.

​

What Comes Next

With your devices paired and assigned, your team is ready to go live. Consider these next steps to complete your deployment: