Battery-powered wearable with SOS button — standalone (no phone, no BLE). Does it exist? Has anyone built one?
You have a budget per tracker? There are many options.
Mictrack MT710 support the SOS button:)
Hi trake-trace,
Thanks for the quick reply. Yes, we have a target, but the requirements matter more to us than the lowest price:
Target cost per unit (core module only, no enclosure):
Prototype stage: up to US$ [X] per unit for [5–10] units. We expect to pay more at this stage.
Production (first batch of [500–1,000] units): around US$ [Y] per unit.
Must-haves:
Works on its own with built-in GNSS and 4G LTE Cat 1 (Cat M1/NB-IoT coverage in Brazil is patchy). It shouldn't need a paired phone.
A physical SOS button that sends an alarm event right away.
Reports position plus the alarm to our own Traccar server. OsmAnd over HTTP on port 5055 is our first choice.
As small as possible. We'll design the enclosure and the disguise in Brazil, so from you we only need the board, antennas, battery and button.
Can be flexible:
Battery life: in standby it only needs to check in now and then. Continuous tracking is only needed during an alarm.
Extra sensors (motion, fall detection) are nice to have but not required.
If you can list the options with a rough price for each, we can quickly pick the one that fits best. Would a development kit be available for testing first?
Best regards,
Eduardo Tavares Ribeiro
Hi Mictrack,
Thanks for suggesting the Mictrack MT710. We're planning to order units for testing and have a few questions before we do:
Battery life in continuous tracking: Have you used the MT710 yourself? How long did the battery last in real-time mode (for example MODE,1 with reports every 10–30 seconds)? We know the 12-month figure is for one report per day, so we'd like to know what to expect in real use.
Setup support: Once our units arrive in Brazil, could you help us configure them to work with our Traccar server (APN, server/port, working mode and the SOS event)?
Cost: If we can't get it working on our own, how much do you charge for this support? Is it per hour, per device or a fixed fee, and would it be done remotely?
Thanks again for your help.
Best regards,
Eduardo Tavares Ribeiro
Hi everyone,
First, a thank you. Over the past weeks this forum answered things I could not have figured out on my own: that the Chinese 4G watches speak the watch protocol on port 5093 and that their SOS button arrives as an sos alarm; that BLE beacons cannot be separate devices and have to come in as attributes of the reader's position; and the current state of Apple Watch support. That saved me weeks of dead ends.
Context: I'm building a panic-button system on top of Traccar for people under threat, for institutional use (court security / judicial police response). The form-factor reference is invisaWear — a small discreet wearable, pendant or keychain, with a hidden button. The problem is that invisaWear and everything in that class is Bluetooth: the device is only a button, and all the location and connectivity comes from a paired phone. In my scenario the phone is precisely what gets taken, dropped or smashed, so a BLE-only button is worthless.
What I'm looking for is a device that:
has its own GNSS and its own cellular connection (Cat 1 or Cat M1, own SIM) — nothing depending on a paired phone;
has a physical SOS button that raises an alarm event, not just periodic positions;
runs on a rechargeable battery and is small enough to be worn discreetly — not a vehicle tracker, and not a wrist watch;
speaks a protocol Traccar already supports (gt06, gl200, osmand, …).
The closest I've found are the Queclink GL320M / GL320MG (personal tracker with SOS, gl200, port 5004) and the Concox/Jimi PT30 class. Those work, but they are "personal trackers" in the pocket-device sense, not wearables in the invisaWear sense. On the small side, the Mictrack MT710 is tiny but has no SOS button.
So, two questions:
Is there a device I'm missing? Small wearable form factor, own 4G + GNSS, SOS button, rechargeable battery, Traccar-compatible.
Has anyone here built one? I'm talking to a hardware house about a custom board (MCU + modem + GNSS + button, reporting over OsmAnd on port 5055). I'd much rather learn from someone who already went through it. The parts I expect to hurt are battery life with the modem registered while mostly asleep, antenna performance in a small plastic body worn against the body, accidental-trigger handling on the button, and time-to-first-fix after a long sleep.
Any pointer is welcome, including "we tried and it failed because X".
Thanks again for this project.