AAPS 3.3.x and Libre 2/3 identifier sent from Xdrip

[miklosz]

With the release of AAPS 3.3.x SMB always could be enabled for Libre 2 & 3 (which was earlier discriminated)

Hovewer, it's not working, AAPS reports "activce BG source doesn't support advanced filtering.'

According to Milos, the cause is the wrong identifier for Libre sensor send by Xdrip
nightscout/AndroidAPS#3589

In mentioned issues - LIBRE_1_OTHER, in my case (xdrip+ 2124091707) it's LIBRE_1_LIMMITER, while the physical sensor is Libre 2 EU and hardware data source set to "Libre Bluetooth" as per instructions: https://xdrip.readthedocs.io/en/latest/install/libre2/

Sorry, no idea what's the correct and expected value, I am just a user :)

Originally posted by @miklosz in #3840

[InvaderStef]

The same problem exists when data is coming from Juggluco and xdrip+ Hardware Data Source is set to Libre (patched App).
I'm using freestyle 3 with Juggluco

[olorinmaia]

I've checked in AAPS sourcecode and double checked with Milos.

AAPS expects Libre2 or Libre3 in com.eveningoutpost.dexdrip.Extras.SourceInfo to be able to properly identify Libre 2 or 3 for full SMB support in AAPS 3.3

[FbnLny]

When checking my AAPS logs, it appears xDrip+ sends the identfier "Libre2 Native", instead of just "Libre2"
(I am using Libre 3 with patched Libre broadcast from juggluco)

[ga-zelle]

I just sent an email to the author of Juggluco so he can implement that adaptation of the label as well in case readings go directly to AAPS. It may even be required for xDrip to recognize it.

[miklosz]

I just sent an email to the author of Juggluco so he can implement that adaptation of the label as well in case readings go directly to AAPS. It may even be required for xDrip to recognize it.

Great, thanks for the contribution!

[olorinmaia]

FYI; "Libre2 Native" also added, for eventually backwards compability as well. This means it will work for those sending that from 3.3.0.1 if you don't cherry pick commit

nightscout/AndroidAPS#3697