GluKaMon is not affiliated with, endorsed by, sponsored by, or supported by Abbot, Dexcom Inc., Medtronic, Hammerhead, SRAM LLC, Nightscout, or Gluroo

Limitations

GluKaMon is a Companion App Only: GluKaMon acts as a secondary display, for the convenience of seeing your glucose values on your bike computer, for passive monitoring purposes only. All treatment decisions should be based on data confirmed on the app provided with your Continuous Glucose Monitor

Update Rate: Most continuous glucose monitors update every 5 minutes, so even though 1 minute data fields are available, those data fields will only update every 5 minutes. If you configure 1 minute data fields and GluKaMon detects that data is only available every 5 minutes, the “1m” indicator in the top left of the data field will be in italics (i.e. “1m“) to indicate that it is not actually receiving data every minute

1 Minute Update Reliability: The Freestyle Libre 3 CGM updates approximately once a minute, which is why 1 minute data fields are available. However, these updates can have frequent gaps and can be irregular (e.g. GluKaMon has observed gaps between readings ranging from 40 seconds up to 2 minutes). These gaps will be most visible on the 1 minute Dots data field (which displays 5 readings for the last 5 minutes)

Libre Regions: Which regional servers your Freestyle Libre 3 account is set up in is not always predictable or obvious. If you choose “automatic” for region, GluKaMon uses it’s best efforts to determine which server your account is on based on where you are in the world and what language you have specified on your Karoo (e.g. if your timezone is set to Central Europe and your language is German it will first attempt the German servers.) If that fails, GluKaMon will attempt other servers. It may take a few seconds to try all servers

Initial Libre Readings: When GluKaMon starts up it makes an initial request to the CGM servers to get data over the prior 3 hours. For Libre servers, even if Libre has 1 minute values, it returns historical readings at 5 or 15 minute intervals, so the historical graphs will only show those 5 or 15 minute readings. The most recent 15 minutes will often be empty. Once GluKaMon has started it requests data every minute or every 5 minutes from Libre, depending on the settings, so while the historical part of a graph or the dots tile will show gaps, from that point on the results should be more consistent

Language Support: Wherever CGM providers provide messages (e.g. if you enter an incorrect username/email or password/token) GluKaMon shows the messages received from the CGM provider. So while all of GluKaMon’s own messages are in the language specified on your Karoo, messages from the CGM providers are in the language chosen by the CGM provider (usually English)

Usernames/Passwords: GluKaMon doesn’t enforce any rules on username/email or password, but the CGM providers do. For example, most xDrip implementations require a password to be >=12 characters, while Juggluco doesn’t require a password at all

Karoo Ride Profiles: GluKaMon runs and displays messages (if configured) even if you are riding with a profile that has no GluKaMon data fields configured on it, or a page with no GluKaMon fields. i.e. GluKaMon assumes that you would want to received glucose messages (if configured) even if you aren’t looking at a screen with your glucose data displayed. The Karoo only displays messages when you are in a ride.

  • If your Karoo is running but not in a ride, and GluKaMon determines that a message should be displayed or audio played, it will queue that message until you are actually in a ride. If those messages are still applicable, it will display the messages once a ride has begun. (If a message is no longer applicable, e.g. if your glucose has gone from target to high but then returned to target all while you are not in a ride, no message will be displayed.)
  • If your Karoo is running and you are in a ride, and GluKaMon determines that a message should be displayed or audio played, GluKaMon will deliver the message to the Karoo. However, if you are in a ride but the ride app is not on screen (e.g. you have switched to another app or to settings), the message will not be displayed. This is a limitation of the Karoo

Juggluco Security: Juggluco offers “self-signed certificates” as a security option. GluKaMon doesn’t support this

Bluetooth: Currently GluKaMon does not support connection from your Karoo to xDrip or Juggluco on your phone via Bluetooth, because of stability issues with bluetooth pairing on the Karoo. You can use WiFi instead, and we are continuing to investigate the option of connecting with Bluetooth

If you find GluKaMon useful, please support me with a contribution. GluKaMon is free, contributions are optional and always appreciated