GluKaMon is now released. If you are happy with the 1.0 release there is no need to upgrade, but there are a few enhancements, fixes to some rarely occurring bugs, and some legal stuff to make sure that GluKaMon is fully compliant with privacy regulations in all major jurisdictions (GluKaMon takes your privacy seriously, release 1.1 just provides makes that more explicit)

To download and install GluKaMon 1.1, just:

• Go into the extensions menu on your Karoo and delete the current copy of GluKaMon
• Download the latest version from the Setup page
• Install as normal (instructions are on the Setup page)

You will have to re-enter your CGM credentials and any other settings

Enhancements

Find your xDrip / Juggluco server without typing its address 

• Setting up the local xDrip / Juggluco connection over Wi-Fi used to mean finding your phone’s hotspot IP address yourself and typing it in — and if you got it wrong, the only sign was a generic “cannot reach server” when you pressed Authenticate. There is now a Find server button under the URL field (Wi-Fi transport only). Tap it and GluKaMon looks for xDrip / Juggluco on the network your Karoo is joined to, then fills in the address.
• It only fills in an address that actually answered, so if it finds something, it works. You can still type an address by hand, and nothing is saved until you press Authenticate and Save as usual.
• What it looks for. Find server looks for your phone — the device your Karoo is routing through — which is exactly right when you are on the phone’s own hotspot. If your Karoo and phone are instead both joined to a home or office Wi-Fi router, the phone is just another device on that network and Find server cannot pick it out; type its IP address in by hand and GluKaMon works out the rest, including the port. It deliberately does not scan every address on your network, which would be slow, drain the Karoo’s battery, and look like a port scan to anyone watching.
• One caveat worth knowing: many recent phones deliberately stop hotspot clients from reaching the phone itself. If yours does, nothing GluKaMon tries can get through — not Find server, and not an address you type either. The way around it is to install xDrip or Juggluco on the Karoo and pick the Loopback transport instead. See Troubleshooting in the README.

When a local server rejects your secret, it now says so. 

• Setting up xDrip used to fail with a bare “authentication failed (HTTP 403)”, which looks the same whether the secret is wrong, the address is wrong, or the wrong app is answering. GluKaMon now passes along what the server actually said — for example “server said: secret_api wrong” — so you know to go fix the API Secret rather than hunt for a network problem.
• Your secret itself is never shown.

FreeStyle Libre: the patient’s name is now optional. 

• If your LibreLinkUp account follows only one person, you can leave First name and Last name blank and GluKaMon will pick that person automatically. This matters if your name uses characters your Karoo’s keyboard cannot type — previously there was no way to finish setup at all.
• Fill the names in only if your account follows more than one person; if you do type a name it still has to match, so a typo is rejected rather than quietly ignored.
• Nothing changes for riders who already entered their name — and as a bonus, GluKaMon now remembers which person it resolved, so a name change in LibreLinkUp no longer stops your data. Both fields are now labelled optional, with a note above them explaining when you can skip them.

Bug Fixes

• The trend arrow no longer overlaps the timer in a tile’s heading. On the combined Value, Change & Trend tiles the arrow could, on rare occasions, be drawn touching the “⏲Xm” data-age indicator in the top-right corner, clearing itself a few seconds later. The arrow now always keeps clear of the heading, at every tile size.
• A local xDrip / Juggluco server with no recent readings no longer looks broken.
  When your local server had nothing to report for the window GluKaMon asked about, it answered in a way GluKaMon mistook for a corrupted response — so your tiles showed ? (“can’t reach your CGM”) and polling kept retrying as if something were wrong. It now correctly reads that as “reachable, just no readings yet” and shows —, exactly like every other source during a sensor warm-up.
• “Cannot reach server” no longer names the wrong port. The message could report the port GluKaMon had already given up on rather than the one it actually tried last, sending you to check something that was never going to answer. It now names the address it really used.

Legal Notices

• [!] You will need to re-accept the disclaimer once. GluKaMon now asks for your explicit permission to process your glucose data, so the text on the CGM Account Settings screen has changed and your previous acceptance no longer counts. Open Settings → CGM Account Settings, read the disclaimer and the new data-handling note beneath it, tick the consent box and press Authenticate and Save. Until you do, GluKaMon will not poll and your tiles will stay empty — you will see the usual
  “credentials missing” message at the start of a ride as a reminder.
• [!] If you record glucose into your FIT files, you need to confirm that too. Display & Log settings now explains where those files can end up — FIT files containing your glucose may be uploaded to Hammerhead/SRAM and passed on to any activity service you have connected to your Hammerhead account, each of which handles the data under its own privacy policy — and asks you to consent explicitly before
  GluKaMon writes glucose into them. Recording is paused until you answer, even if you had it switched on before, because consent to the old, shorter wording is not consent to this. Open Settings → Display & Log Settings, read the note, and choose Yes. Choosing No is recorded too, and stops future recording — but neither answer can remove glucose from FIT files you have already created or uploaded.
• A plain-language note about what happens to your data. Above the consent box there is now a short paragraph explaining that GluKaMon connects from your Karoo straight to whichever CGM service you chose, that your CGM password never leaves this device and is encrypted with AES-256-GCM, that your credentials travel only to that service over HTTPS — the one exception being a local xDrip or Juggluco server on your own network, where the connection may be unencrypted but never leaves your LAN — and that neither your credentials nor your readings are ever sent to, or visible to, the developer of GluKaMon. The full privacy policy is at glukamon.com/privacy/. You can withdraw your consent at any time by deleting GluKaMon; there is no separate disconnect button, because without your CGM account the app has nothing to show.