• Please Remember: Members are only permitted to share their own experiences. Members are not qualified to give medical advice. Additionally, everyone manages their health differently. Please be respectful of other people's opinions about their own diabetes management.
  • We seem to be having technical difficulties with new user accounts. If you are trying to register please check your Spam or Junk folder for your confirmation email. If you still haven't received a confirmation email, please reach out to our support inbox: support.forum@diabetes.org.uk

Libre

rebrascora said:
The reader does get alarms though whereas, if the blue tooth connectivity with the phone is an issue, you won't get alarms on the phone even though you can still scan to get readings via NFC
Click to expand...
Only if the issue is at the phone/app.
"Bluetooth connectivity with the phone" has two parts - the transmitter on the sensor and the receiver on the phone (which the application accesses). It is not a simple case of the "Bluetooth connectivity issues with the phone" being a phone issue.
It is possible for the Bluetooth transmitter on the sensor to have a problem. If that is the case, you will not get alarms on reader or app but you can scan for readings on either (depending which you used to start the sensor, of course).

I am not suggesting this problem is the sensor or the phone or the app - without having access to either, we cannot categorically say. As an engineer, I know from experience, it is rarely worth speculating; only investigating.
And I am not suggesting one is better than the other - like so much diabetes related, we are all different with different preferences. I am just highlighting the impact of an Bluetooth error on a sensor.
 
You must log in or register to reply here.
Back
Top