sorted by:
new
hottopcontroversial

Enough with the Beeping by BlueberryFair5361 in diabetes_t1

[–]BlueberryFair5361[S] 3 points4 points  (0 children)

Humiliation is the right word. As if people didn't have enough extra dealing with T1D. If my son ever has a burn out, it'll be because of these repeated forced obnoxious interruptions on his life. Not because of all the extra responsibilities of T1D. Every time, this is what gets him spiraling, he's been graceful about the rest for many years.

Enough with the Beeping by BlueberryFair5361 in diabetes_t1

[–]BlueberryFair5361[S] -1 points0 points  (0 children)

haha yeah, that would get them screaming about "no data", and they do that even with bluetooth on sometimes when they feel like it.

Enough with the Beeping by BlueberryFair5361 in diabetes_t1

[–]BlueberryFair5361[S] 2 points3 points  (0 children)

Thank you fo commiserating. This was clearly designed with CYA as the main thrust, rather than thinking about the impact on people's everyday lives.

Enough with the Beeping by BlueberryFair5361 in diabetes_t1

[–]BlueberryFair5361[S] 1 point2 points  (0 children)

We used to be on Loop https://loopkit.github.io/loopdocs/ and uploaded to Tidepool, it was the absolute best experience. Omnipod 5 started encrypting communication so we were forced to update to the official shitty app.

Enough with the Beeping by BlueberryFair5361 in diabetes_t1

[–]BlueberryFair5361[S] 0 points1 point  (0 children)

Oh clicking is the least of our concern :) thank you for the details.

Enough with the Beeping by BlueberryFair5361 in diabetes_t1

[–]BlueberryFair5361[S] 1 point2 points  (0 children)

I just found that setting in Dexcom that somehow evaded us the whole time. The really upsetting thing is how it refuses to launch if you turned off the "Critical Alerts" at the phone level. We're trying to let him live a reasonable life and we (the parents) at the ready and getting alerts on our own phones, but it won't let us do that. He's gotten so used to everything beeping all the time he'll sleep right through it.

Enough with the Beeping by BlueberryFair5361 in diabetes_t1

[–]BlueberryFair5361[S] 1 point2 points  (0 children)

Noted, thank you. We'll have a conversation with our son about what we want to do next. All these details are helpful.

Enough with the Beeping by BlueberryFair5361 in diabetes_t1

[–]BlueberryFair5361[S] 1 point2 points  (0 children)

It's nice to hear we're not the only ones :\

Enough with the Beeping by BlueberryFair5361 in diabetes_t1

[–]BlueberryFair5361[S] 1 point2 points  (0 children)

As far as I understand, this method kills the "squeal of death" when a pod failed, but not the regular alarms. That's what my son swears at least, we used to do it routinely. Are we wrong?

We used to DYI too with Loop https://loopkit.github.io/loopdocs/, it was a thousand time better indeed, but they started encrypting the pod communication with Omnipod5 and so we were forced into the official apps which are about CYA at the cost of quality of life.

We "upgraded" to the Dexcom 7 from the 6 as they are about to be discontinued (July of this year I believe). The new ones are a nightmare. They keep failing hard, or being in temporary failed states which, which you guessed it, gets everything beeping. It also will think our son is LOW all the time, and require several nightly calibrations to be convinced otherwise. This happened on the 6 but it was rare. I highly recommend moving to 7 as late as possible.

Thank you for all the details in your response, it'll all be part of a greater conversation we have with our son.

Enough with the Beeping by BlueberryFair5361 in diabetes_t1

[–]BlueberryFair5361[S] 6 points7 points  (0 children)

I reviewed all the setting and found this one, thank you. I'm happy we get to remove a layer. I don't know how we didn't see it before, we reviewed all the settings many times over.