xdripswift/xdrip/Core Data
Johan Degraeve f631d54bd8 DexcomG7 companion mode
Identifies the Dexcom G7 without the need for filling in the device name. Requires that the official Dexcom App always runs in parallel.
2024-02-25 12:15:25 +01:00
..
Extensions further changes for calibration 2021-12-21 22:03:57 +01:00
accessors initial commit - bg readings swiftui view 2023-07-30 20:53:15 +02:00
classes DexcomG7 companion mode 2024-02-25 12:15:25 +01:00
xdrip.xcdatamodeld DexcomG7 companion mode 2024-02-25 12:15:25 +01:00
README.md temp commit, a few alerts, default values, and no snoozing yet 2019-04-23 17:24:05 +02:00

README.md

alerts

There's different kinds of alerts : high, low, very high, very low, iPhone muted. For each kind of alert, one can define per minute of the day, which alerttype should be applied. Example between 00:00 and 08:00 high alert should have specific sound, between 08:00 and 23:59, high alert should not have sound but only vibrate. In this example there would be two alerttypes, one defined with sound, the other with vibrate only There would also be two alertentries with alertkind high, one with start 0, another with start 480 (480 minutes = 08:00). The first ets alerttype that gives sound, the other the one that vibrates

The alerttypes can be reused for other kinds of alerts.

alerttype Each alertentry must have an alerttype.

  • name, name of the alert type as shown to user, chosen by user
  • enabled, enabled or not enabled, if not enabled, then the alerts that use this alert type will simply never go off
  • vibrate, vibrate yes or no
  • snooze, snooze via notification yes or no, should it be possible to snooze the alert via the home screen
  • snoozeperiod, If snooze = yes, then the value defines how long the alert will be snoozed if the user snoozes from the home screen
  • soundname?, name of the sound as stored in the assets - if not present then default ios sound to use
  • overridemute, yes or no, should mute be overriden or not

alertentry Each alert has a list of alertentries.

  • start, start time in minutes from 0 to 24*60 (first needs be 0) - as of when is the alert applicable, till the next entry
  • value, the value
  • alerttype, applicable alerttype for the period
  • alert, the alert to which the entry belongs
  • alertkind, the kind of alert for which it is used : high, very low, very high, ... there's a predefined list, in the code this is an enum named AlertKind