English
EnglishEspañolFrançaisالعربيةDeutschPortuguêsItalianoفارسیBahasa IndonesiaاردوTiếng ViệtBahasa MelayuRomânăΕλληνικάहिन्दीNederlandsTürkçePolskiไทยУкраїнськаРусскийČeština한국어বাংলা日本語简体中文繁體中文FilipinoKiswahiliSvenskaעבריתSuomiDanskMagyarNorsk bokmålதமிழ்

Your country is detected for each new visit. You can choose your country and language.

Phones & messengers / Detailed guide

Somewear Hotspot: pairing, message route and tracking

Separate phone-to-Hotspot pairing, the message’s actual transport and shared-location updates. A message delivered over Wi-Fi does not prove the satellite path works; a phone’s current map position is not necessarily the last position shared with the team.

Applies to: Somewear Hotspot, original guide hosted in the manufacturer’s July 2023 directory. Not Node. Confirm current app labels and workspace/service configuration with the administrator.

Work through these checks

  1. Confirm the app’s device connection

    Read the existing app status pill for phone-to-Hotspot connection, signal and transmission state. A Pair button or disconnected state is a local connection finding; record it without resetting pairing or powering down a device carrying team traffic. The original pairing workflow is a setup operation, not proof that a satellite message was delivered. Observe the existing outward-facing logo/sky orientation from a safe position without moving operational equipment.

    What the result means: If the phone is not connected, preserve that state and ask the workspace administrator to resolve the local pairing path. An app open on the phone does not alone show a connected Hotspot, and repeating setup can disrupt the original evidence or an operating team.

  2. Read the message transport

    Page 4 says Smart Routing prefers available Wi-Fi or cellular and uses satellite off-grid. A satellite symbol on a message identifies satellite transport; its absence is consistent with Wi-Fi/cellular delivery. Save the message timestamp and icon with the network state. Do not disable the team’s working network just to force a charged satellite test; arrange a controlled check with the administrator.

    What the result means: Compare the icon on the exact message, not just overall phone connectivity. The original guide uses the satellite icon for messages sent or received by satellite; without it, the message used Wi-Fi or cellular. A successful terrestrial message therefore is not an observation of a successful satellite route.

  3. Compare current and shared position

    Page 6 distinguishes Current location from Last shared location and says tracking requires connection to the Hotspot. Check that connection and the intended tracking interval without changing team policy. Record the last shared timestamp and what the receiving workspace sees. A stale shared marker alone does not establish a phone-GPS failure. Download needed offline maps before departure, as the guide recommends.

    What the result means: The current-location icon and last-shared dot have different meanings. The map also distinguishes active blue tracks from historic white tracks; the guide describes a track becoming historic after inactivity. Keep the existing tracking interval and sender/receiver times rather than diagnosing a failed GPS or changing reporting policy from a stale marker alone.

When to stop and get help

Do not trigger SOS, disconnect a working team network to force satellite, restart an operational Hotspot, change tracking policy or install firmware for this check. Stop routine troubleshooting for an actual emergency and use the team’s established response procedure. Keep private messages and location history out of public reports.

What to tell support

Provide support the original hardware/app/workspace identity, status-pill connection result, existing message icon and time, network in use, current versus last-shared point and the receiving member’s timestamp. Record whether the map marker was active blue or historic white; do not publish messages, contacts or coordinates.

Common questions

Does this guide describe an automatic EMS call?

No. Page 9 of this original guide describes SOS alerts to the workspace in the app and email, and explicitly says EMS is not alerted. Confirm the current service and your team’s emergency-response arrangement before relying on it. Never activate SOS as a diagnostic test.

Does a white light mean the satellite connection is ready?

No. The original Hotspot guide, page 11, separates blinking white (powered on), roughly once-per-second blinking white (pairing mode), and steady white (fully charged). Red blinking means powered on with low battery; steady red means charging. These light states are not delivery receipts. Check the app’s connection and the message’s actual transport separately. This is original Hotspot guidance, not Node light behaviour.

Why did a workspace firmware update miss one Hotspot?

The original guide page 8 says only devices in range are updated. Its preparation requires the Hotspot off, charging and within range; Settings > Hotspots shows Update Available. Compare the serial-number list and reported completion for the missing unit instead of assuming every workspace device received it. Keep the connection intact during an authorized update. Do not change firmware flavour unless Somewear directs it, and do not interrupt team traffic to start an unscheduled update. Confirm current app and firmware instructions with the administrator; this original guide does not establish Node update behavior.

Original troubleshooting guidance based on the official sources below. Menu names can change. This is an independent guide, not a manufacturer service bulletin or a bench-tested repair.