Name: Gluc Data Field
Author: exoji2e

Gluc is a data field that displays glucose values from Freestyle Libre sensors using the LibreLinkUp follow functionality.

Getting started:
Download the LibreLinkUp app and create an account. Link the account to your regular LibreLink account, so you can view your own glucose data in the LibreLinkUp app.
Enter the account email and password for the LibreLinkUp account in the settings for the data field.

Select your region in the settings.

The following regions exists. Help fill out what countries are in each region by writing a review or sending a message to the developer:

- AE: ???
- AP: ???
- AU: Australia?
- CA: Canada?
- DE: Germany?
- EU: Sweden + ???
- EU2: UK
- FR: France?
- JP: Japan?
- US: US?

If your watch show Error E10, it means you account is in another region than what is selected in the settings.

+++++
PLEASE READ THIS ADVISORY
Never make a medical decision based on a reading that you see on this app e.g. your watch. Always perform a fingerstick blood glucose check first.
+++++

Limitations:

- Only uses mmol/L (and no support for displaying in mg/dL yet)
- Sometimes you need to open up the LibreLinkUp app and accept new ULAs.
- Data field is created and provided open source with no affiliation with Abbott.
- Only updates every 5 minutes.
- I have no control over the server the data field is talking to, so it might stop working when the API changes but I try to fix it as soon as I am able.

LibreLinkUp app store: https://apps.apple.com/us/app/librelinkup/id1234323923?ls=1
LibreLinkUp play store: https://play.google.com/store/apps/details?id=org.nativescript.LibreLinkUp

Error codes displayed when failing to fetch data:

- E1: Couldn't login with credentials provided.
- E2: Received malformatted data when trying to login.
- E3: Password incorrect according to server
- E4: Need to accept new ULA in LibreLinkUp app
- E5: Received non-ok unknown status after login
- E6: Internal error with saved auth token
- E7: Didn't receive glucose data from server, usually because clock had no contact with phone.
- E8: Received malformatted data from server when fetching glucose data.
- E9: Saved auth token is not valid, will delete and login again during next fetch.
- E10: Server response indicated wrong region was selected.
- E11: Unable to unpack account-id from token
