Overview¶
What is SmartSafety?¶
Call for help … even if you can no longer do it yourself! Automatic monitoring & emergency call system for early detection of critical situations. Reduces rescue response times by up to 90%. With companion rescue navigation.
Why SmartSafety?¶
Every year, more than 20,000 people have accidents in the outdoor sector. It usually only becomes critical when friends and helpers do not become aware soon enough. Or do not know your exact position. Or no emergency call is possible at all because only 10% of the earth is covered by mobile phone networks. We deliver the missing 90% by satellite. And draw attention to you at an early stage. With your exact position.
SOS : What happens if…?¶
For each scenario (e.g. manual SOS or automatic crash/standstill alarm), different notification chains can be created with a 2-step escalation. Example: First SmartSafety reports your position via SMS/email to friends and team for comrade rescue. Upon their request or after a timeout, without reaction, professional rescue facilities such as mountain rescue or coast guard (via 112/GEOS) are then activated, which may communicate further with you or your stored emergency contacts.
How do I configure my SmartSafety?¶
Go to protegear.io à SmartSafety. A default setting is already available!
- profiles: set the monitoring scenarios for your activity
- tours: set the geofences (SAFE, DANGER and REST zones)
- notifications: store your alarm recipients (SMS, EMail, Telegram, …)
- trace: compile who is alerted, when and for which event Contacts: enter the emergency contacts who can be contacted by a rescue control centre such as GEOS in the event of an SOS or escalation!
Overview of alarm detections¶
Note on initial setup: All automatic alarms should be tested before real use to become familiar with them. Therefore, in the default setting, ESCALATION to the rescue control center is initially deactivated, so that alarms only go to your own emergency contacts.
All alarm types can also be combined with each other, so that for example with POSITION6D + MOTIONLESS, motionlessness only triggers an alarm if the device (and its wearer) are horizontal. Furthermore, this can be combined with ZONES (Geofences), so that depending on the location, other parameters automatically apply.
| Alarm Type | Features | Important to note | available for device types |
|---|---|---|---|
| MOTIONLESS | motionlessness (complete rest) for x minutes | to be worn on the body; is independent of GPS; is cancelled, if necessary, by the device going to sleep after 15 minutes (NOT-MOVING), if NOT-MOVING is activated as a pause | only A*LIVE |
| HALT | Motion less than x meters in y minutes | good GPS needed | all |
| CRASH | impact and/or free fall with and subsequent stop within y minutes and z meters | good GPS required if subsequent movement is to be detected | only A*LIVE and P99; P88 |
| ZONE | Inside DANGER Zone (Red Zone in TOURS/ZONES) | distinguished into REST (no alarm triggering except SOS); SAFE (no ZONE alarm); DANGER (position in DANGER Zone triggers ZONE alarm) | all |
| Floating Geofence: You can also assign a floating secure zone around a “Master”-Device to have team-devices be kept in range. | |||
| PROXIMITY | Proximity alarm when 2 or more devices are less than x meters apart, optionally in 3D with height information | good GPS required | all |
| DEADMAN | |||
| active deadman: | absence of a defined manual action on the device (e.g. preset message) for x sec. | all | |
| passive deadman circuit: | A) “Outdoor only”: Poor GPS reception triggers alarm after x sec | all | |
| B) “Indoor + Outdoor”: Signal loss since x sec. triggers alarm | all | ||
| This is the final alarm detection; when your device is “offline” for whatever reason (destroyed; battery dead; no connection; etc.) | |||
| Timeout is to be set large enough; so that any latencies due to poor network coverage do not trigger a false alarm | |||
| POSITION6D | position of the device in X/Y/Z axis | to be worn on the body; independent of GPS | only A*LIVE |
| HEIGHT | x meters above ground level (AGL) exceeded / below / within | all | |
| ALTITUDE | x meters above sea level (AMSL) exceeded / below / within | all | |
| SPEED / VSPEED | Horizontal or vertical speed exceeded | VSPEED only A*LIVE | |
| PAUSE | not an alarm; but a pause of the monitoring | PAUSE mode can be triggered by: | |
| Switching off (POWER-OFF) | only A*LIVE; P99/P88 | ||
| Tracking STOP | all | ||
| PAUSE (2x TRACK button on ALIVE or PRESET message PAUSE on InReach) | only A*LIVE and InReach* | ||
| Start-Charge (if activated in profile) | only A*LIVE | ||
| Not-Moving (if activated in profile) - device stays motionless for at least 5, 10 or 15 min | all | ||
| PAUSE mode is ended by: | |||
| Switching on | all | ||
| Tracking START | all | ||
| Movement outside PAUSE radius | all |
IMPORTANT for certain device types:¶
GARMIN INREACH / MONTANA / GPSMAP: Essential here is to trigger TRACKING Start to begin the monitoring, and Tracking STOP to end of the monitoring, giving the device at least 10 minutes in the open air to send this signal, otherwise false alarms (especially DEADMAN) may occur.
A*LIVE: Regular switching off ends the monitoring, here make sure that the switching off does not happen on an activated charging pad, as this triggers a RESET.
Telegram¶
Use Telegram Messenger to save on SMS costs.
-
Telegram app: Download the app from the AppStore or PlayStore. Create a new group with people who should receive the notifications. Then add our ChatBot with the name @ProtegearBot. Send “/chatid” as a message, a number will be sent as a reply, e.g. -986456487
-
protegear.io → SmartSafety → Expert mode - on → Notifications → + → Telegram; Create the notifications, enter the ChatID in the field provided (incl. - characters).
3 protegear.io → TripShare → Handlers → + → Telegram; Create the handlers for message templates, entering the ChatID in the field provided (including - characters).
Please do not forget to save your changes (SAVE top right). You can now use the Telegram notification.