fbpx
Skip links

How to think about Tip Over notifications

Table of Contents

Tip Over notifications may be triggered when a user falls, causing the walker to tip over as well. Folding the walker up for an outing or accidentally knocking it over can also cause Tip Over Notifications. These false positives are a concern and are often caused by user lifestyle. The notifications can be adjusted to alleviate some false positives; however, best practice is to verify all Tip Over notifications to ensure user safety and well-being.

It is also important to have someone receiving Tip Over notifications 24 hours a day, but it can be split up into two different recipient accounts. For example – a Tip Over notification can be received by one account from 8am to 5pm and another from 5pm to 8am.

Mitigating False Positives #

If the walker is folded up when it is in range of a Node, even if outside or in a garage, it can trigger a Tip Over notification. To alleviate these false positives, the Tip over time threshold can be set to a time frame that coincides with the user’s lifestyle (often 15 minutes). This allows time for the walker to be folded, put in the vehicle and driven away out of range of the Node. If the device is out of range of the Node then it will not trigger a Tip over notification. However, if there is a Tip Over and the device remains within range of a Node, the notification will not be sent until the walker is tipped over for at least 15 minutes.

Explore
Drag