This looks awesome. Current features?

[ChrissHF]

Hi,
this looks awesome, great work on the design.
How far are you in terms of implementing all the features and menus of the original app?

The features I'm looking for are the ability to clone the values to the WearOS app, LibreLink and NFC readings of the Novopen

Is it possible to switch between jugglucoNG und juggluco with an already started sensor?

I'd really like to try this and help with testing (Libre 3 Plus)

[gui-dos]

@ctqwa: I am a final user of the Libre 3, too, and I have noticed that sending the NFC command 0xA0 (ACTIVATE) instead of 0xA8 (SWITCH_RECEIVER) doesn't break the pairing with the official app and that the current BLE PIN is returned instead of obtaining a new one: https://github.com/ctqwa/JugglucoNG/blob/35cd7c0cb60f9f5aefc78ce661a437858eff498f/Common/src/libre3/java/tk/glucodata/libre3/NFC.java#L52-L54

Unfortunately I am not getting any feedback from Android's xDrip+ team about my second PR NightscoutFoundation/xDrip#4421 which employs this trick.

Could you please add the option to select which NFC command (A0 or A8) to use when scanning the Libre 3?

In my iOS project https://github.com/gui-dos/DiaBLE, I've always enjoyed displaying the complete debug logs openly to the user, and I truly appreciate that you are adopting the same approach!

[gui-dos]

Thanks @ctqwa for your prompt feedback!

Time for me to try to relearn seriously Jetpack Compose now that Android, too, is a supported platform by Swift officially...

Juggluco is displaying in its logs just the numerical constants and I had to work hard to make sense of its cryptic code and obtain from the decrypted IPAs/APKs the struct members and enums' definitions in clear which are shared between iOS and Android (this is i.e. my code to parse the activation repsonse: https://github.com/gui-dos/DiaBLE/blob/cfc3a94827a07ff3035b39e35ea04f00d8f34c16/DiaBLE/Libre3.swift#L897-L937).

[gui-dos]

When using the custom NFC command A0 instead of A8 you can reconnect to the same sensor from the Libre 3 app running on another phone (even switching iOS <-> Android) without the need to sign-out, re-login to your LibreView account and scanning again the sensor.

After a couple of failed connections, the official app in fact redoes again the pairing process and renegotiate new ephemeral keys: it is very important that the initial activation is made by using the vendor app.

@ctqwa: Could you please add the chance to input manually the "Receiver ID"? It is a long hash computed from a user's LibreView Account UUID string

https://github.com/ctqwa/JugglucoNG/blob/35cd7c0cb60f9f5aefc78ce661a437858eff498f/Common/src/main/cpp/settings/javasettings.cpp#L924-L932

and doesn't vary so you need to get it only once from the libreview.io servers for the rest of your patient life ;-)

(see https://www.juggluco.nl/Jugglucohelp/getaccountidhelp.html)

[ctqqa]

Sure — test it out (a bit ugly, but I'll redo this mess properly at some point).
I wonder, though, esp. looking at your work, why we even need an Abbott server login there at all? Granted I haven't used Libre in ages, no clue how they work these days.

[gui-dos]

If you activate a Libre 3 without being logged in LibreView and not appending the receiverId hash to the activation command, you cannot reuse that sensor on another app instance (you can notice in fact that they are defining NOT_YOURS error constants).

Paradoxically, however, you can notice that, after re-logging on another phone and rescanning the sensor, the historical data are restored directly from the sensor memory, not from the libreview.io servers.

As you can see in the attached screenshots, after activating with A0 the sensor in JugglucoNG, the official app on iPhone cannot reconnect to it but you have to wait just a couple of minutes for the repairing process to be made, without having to sign out, re-login and re-scan the sensor B-)