You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would suggest changing the alertMissedReading stepValue from 5 to 1.
With 5 minute increments, the alert can be triggered at the same moment a new reading appears. It would be better to allow triggering at times such as 6, 11, 16, 21 minutes instead of 5, 10, 15 or 20 minutes. This will reduce false alerts, and give the user four minutes until next reading is inbound to figure out if it is relevant to consider moving the receiving phone closer to the person who is wearing the sensor (typically a kid who left the phone in another room).
I would suggest changing the alertMissedReading stepValue from 5 to 1.
With 5 minute increments, the alert can be triggered at the same moment a new reading appears. It would be better to allow triggering at times such as 6, 11, 16, 21 minutes instead of 5, 10, 15 or 20 minutes. This will reduce false alerts, and give the user four minutes until next reading is inbound to figure out if it is relevant to consider moving the receiving phone closer to the person who is wearing the sensor (typically a kid who left the phone in another room).
Possibly other stepValue = 5 could be changed similarly. Either by setting it to 1, or forcing n+1 as the criterion.
The text was updated successfully, but these errors were encountered: