[3.0-beta1] Omnipod Dash feature request - Automatically acknowledge alerts + add notes for pod alerts

[kristinsmotz]

Testing 3.0-beta1 with Omnipod Dash after successfully using 2.8.2 with Omnipod Eros since November 2020. Just noticed for Omnipod Dash we no longer have the option in settings to automatically acknowledge pod alerts (Like reservoir low, pod expired after 72 hrs etc). This means pod keeps beeping regularly until we go in the Dash tab and press Acknowledge alert(s).

I would appreciate if this is eventually added for Dash as well since it creates more frequent interruptions in class etc when we have these persistent loud regular beeps until we manually acknowledge whatever the pod is telling us.

If I remember correctly these pod alerts were also added as notes before automatically acknowledging them to the pod, but that may have been a dream scenario. In a parent/child setup like we have with AAPS and NSClient where the parent is the one monitoring pod reservoir, alerts, pod change schedules etc, having a note in the log/graph area (either a Notification like from automation or a Note like AndroidAPS started) is much more useful than repeating pod beep alerts when I am not in the same room as my daughter, since a note will also be visible in NSClient. Attached screenshot of settings for Eros in AAPS v 2.8.2: Screenshot of settings for Dash in 3.0-beta1: Graph area with Notes/Notification:

Thank you all for doing really great work in creating and maintaining this app/system, it is very appreciated!

[avereha]

I will not have time to implement the background scanner, but here is what I remember.

When a pod has an active alert or alarm, it advertises a new service UUID. One way to detect that the pod has an active alert would be to periodically scan for that service uuid, and when it is found to run a getPodStatus to receive the active alert.

[kristinsmotz]

@avereha update: I have now been using eros again for a few pods, then dash for a few pods, then eros again. What happens in eros is IF the "auto ack" flag is activated, the alert from the pod is acknowledged and silenced next time the pod and phone are connected. the phone/AAPS does not "listen"/background scan, but if you refresh in pod tab (or for some other reason the phone and pod connects, like setting a temp basal, bolusing/ending bolus), it will receive the alert and ack it without pressing anything. With dash it does not ack the alert at this point, it must be done manually.

So I'd like to revise my feature request to "receive alert, add notification, ack alert" at next "ordinary" connection.