ruthbia said: @meginer when the sensor I wait for 60 min and free passthen I reinstall Diabox on top, I give scan and step on the sensor.He recognizes it and does not disconnect again. It works for me like that.I have a Samsung A52s 5g
Ok, he did not do it exactly so but only scanned with free once the time passed, and then reinstated Diabox.I will do so the prox time to see Q al.Thank you.
No signature configured, update it from user's profile.
@Solman in the Borra Cache and data application, it is made from mobile settings, the application is restarted. Before doing it, do a data back-up and then import them.
No signature configured, update it from user's profile.
Solman said: What version of the Diabox app worked for me? I have already updated freeLink usigue diabox without reading by BloutoBh I appreciate help
I use the February 2022 version. It is the one that goes best.
Within a couple of hours I have a sensor change.Fear gives me.The first two days are absolute madness: continuous disconnections, reading failures, ect ...
Tonight I may not stick an eye.
From the third or fourth day it stabilizes and does not usually give problems until the end of its useful life.
No signature configured, update it from user's profile.
I have a sensor change, in half an hour or less it works for me.What I do is the following: Quito Diabox of the background, scan the free, I wait for the warm -up time, before scanning with free I have allowed access to mobile devices in LibreLink. Cdo is already spending the time, scanning with free and then with Diabox and I already removed the access permit to close devices for free.It does not usually work at the first, it is clooded in Diabox, what I do then is to install the same version of Diabox on top and I scanning again with Diabox, if not to the second, to the third it usually connects me, it is rare that I latemore than an hour.It also depends on the mobile, now I have a Samsung and it does not take me just and almost never disconnected, before I had a Xiaomi and I was doing well but it was more disconnected and it took longer to hook with Diabox.
No signature configured, update it from user's profile.
It gives me erratic measures the first 18 hours, then well. I put it 12 hours before activating it, when it expires according to Abbott but Diabox continues to work with him exhausted. Active with the reader, then I pass the freeLink app (which has no alarms because they are annulled when activating the sensor with reader) and clean diabox data from mobile settings (so as not to lose the historic I do a back-up). At 60 min he entered Diabox, links the sensor, I identify and charge the back-up, and Vòila, up to 14.7 days.
If you use Diabox, FreeLink's alarms do not make sense.
ruthbia said: I give me erratic measures the first 18 hours, then well. I put it 12 hours before activating it, when it expires according to Abbott but Diabox continues to work with him exhausted. Active with the reader, then I pass the freeLink app (which has no alarms because they are annulled when activating the sensor with reader) and clean diabox data from mobile settings (so as not to lose the historic I do a back-up). At 60 min he entered Diabox, links the sensor, I identify and charge the back-up, and Vòila, up to 14.7 days.
If you use Diabox, FreeLink's alarms do not make sense.
I don't know why but the diabox signal loss alarm does not go a while ago.
Hipo-Hiper alarms do work.
I have no idea of the reason, since it is happening with the last 2 or 3 sensors.
25mar2000 said: good, someone who works the diabox to measure the values by bluetooth every five minutes can explain the steps to do so? I understand that it can be done without bubble using the Bluetooth of the device itself but I can not work so that I have come to the conclusion that I am doing something wrong. I have removed the battery savings for application and I think you have all the permits you need but still the value is not updated unless I look at it with the NFC, someone knows that I am doing wrong or if you have to configure somethingIn the app itself to read it. Thank you very much in advance
Now read every minute for Bluetooth.Look to see if you have the latest version first.
For the rest once everything is configured (read every minute, capillary manual calibration or not, upper and lower limits, alarms, etc) you have nothing to scan (sometimes on several occasions for link) and you piece to read by Bluetooth eachMinute
Hello.In Diabox where is "Reading every minute" configured?
25mar2000 said: 25mar2000 said: good, someone who works the diabox to measure theBluetooth values every five minutes can explain the steps to do it? I understand that it can be done without bubble using the Bluetooth of the device itself but I can not work so that I have come to the conclusion that I am doing something wrong. I have removed the battery savings for application and I think you have all the permits you need but still the value is not updated unless I look at it with the NFC, someone knows that I am doing wrong or if you have to configure somethingIn the app itself to read it. Thank you very much in advance
Now read every minute for Bluetooth.Look to see if you have the latest version first.
For the rest once everything is configured (read every minute, capillary manual calibration or not, upper and lower limits, alarms, etc) you have nothing to scan (sometimes on several occasions for link) and you piece to read by Bluetooth eachMinute
Hello.In Diabox where "Read every minute" is configured?