error when connecting via Bluetooth with status = 255

[AlexOchkin]

Hi, I encountered an error when connecting via Bluetooth to Libre2(RU) on the 9th day, status 255, what does this status mean? Data is received via NFC. version Juggluco-9.0.19-arm64.apk
error when connecting via Bluetooth with status = 255

[j-kaltes]

I myself never experience a status=255 connection error. Others reported that that connection error resolved itself after some time. The only thing having to do with 255 (=0xFF) I can find is,

#define  GATT_OUT_OF_RANGE                   0xFF /* Attribute value out of range */

gatt_api.h

But I don’t know if that has to do with a connection error.

[AlexOchkin]

Thank you for the information. A day later the sensor began transmitting readings. Now the connection is stable. Good luck.

[dassystem]

I actually have that error quite often on Libre3 (roughly 1 out of 3 sensors). In those cases I switch to the official libre app and check what that is saying: "signal loss" / "status 57" in the protocol. Sometimes the connection comes back up after 1 to 4 hours, but sometimes it doesn't. For my next sensors I turned off "Turbo" and "Android" modes in Juggluco, because I reread through the descriptions and think this is now right choice for me. I hope that it might help.

What's really weird about this situation is, that it's so unpredictable. I always have my phone with me in my pocket, have it next to me while sleeping or showering. Sometimes sensors last the full 14 days, sometimes they drop out with "signal loss" (status=255). Sometimes after 1 day, sometimes 3, sometimes 10 days. Until now it seems to be random for me.

Edit: new sensor settings did not help. Got status=255 after 24h of wearing the sensor.