Managing diabetes around the clock is a demanding task, and the OpenAPS (Open Artificial Pancreas System) offers a powerful tool to automate insulin delivery. But the system is only as useful as your ability to stay informed and act on changes. The built-in alert system is your early warning network, but out-of-the-box settings often don't align with the unique rhythms of your life. By customizing your OpenAPS alerts, you can transform noise into actionable, life-enhancing signals. This guide will walk you through building a personalized alert system that supports your daily activities, sleep patterns, and health goals, reducing burnout while keeping you safe.

Understanding OpenAPS Alerts: Beyond the Default Settings

OpenAPS operates on a closed-loop system, but it requires human oversight for safety and optimization. Alerts are the primary way the system communicates with you. Default alerts are designed for safety, but they're often too frequent or not tailored to individual needs. Understanding the types of alerts and how they interact with your rig is the first step.

Types of OpenAPS Alerts

OpenAPS generates several categories of alerts, each serving a distinct purpose. These are typically configured in the openaps.ini file or through a tool like Nightscout. The main types include:

  • Low Blood Glucose Alerts (BG Lows): Triggered when predicted or current glucose falls below a threshold. These are critical for preventing hypoglycemia.
  • High Blood Glucose Alerts (BG Highs): Triggered when predicted or current glucose exceeds a threshold. These help you proactively manage hyperglycemia.
  • Device and Sensor Alerts: Notifications for battery low, pump occlusion, sensor expiration, or communication failure between devices.
  • System Notification Alerts: Alerts for changes in loop status (e.g., temp basals, suspend events) or configuration updates.
  • Nightscout Enacted Alerts: If you use Nightscout, you can set remote alerts based on the same data, often with more granular control via text message or push.

How Alerts Reach You

Your OpenAPS rig (typically a small computer like an Edison with an Explorer Board, or an Android phone running AndroidAPS) can send alerts through multiple channels:

  • Local notifications: The rig itself can beep, vibrate, or flash LED lights.
  • Smartphone push notifications: Via Nightscout or dedicated apps like xDrip+ or LoopFollow.
  • Text messages (SMS): You can configure Nightscout to send SMS alerts.
  • Wearable device integration: Connect your alerts to smartwatches or fitness bands for discreet notifications.

Each channel has pros and cons. For example, local sounds are reliable but can be missed if you're not near the rig. Push notifications are convenient but may be delayed by phone settings. A robust system uses multiple layers – for instance, a loud local alarm for critical lows plus a smartphone notification for all other alerts.

Step 1: Assess Your Lifestyle Needs

Before touching any configuration file, take a hard look at what matters most. Everyone’s diabetes management is different. Ask yourself:

  • What times of day are you most at risk for lows or highs? (e.g., night, post-meal, during exercise)
  • How do you typically react to alarms? Do you sleep deeply or wake easily?
  • Are you often in meetings, driving, or in public places where intrusive alarms are problematic?
  • Do you have caretakers or family members who need to be alerted?
  • What's your tolerance for alert fatigue? Too many false alarms can cause you to ignore real ones.

Document your answers. They will guide every decision from threshold values to notification method. For example, a heavy sleeper will need a very loud, continuous local alarm for lows, while someone with a high desk job might prefer a vibration pattern on a smartwatch.

Step 2: Modify Your Alert Configuration

OpenAPS configuration is done via text files on the rig or through the Nightscout web interface if you use that as a front-end. The core file is openaps.ini, but you'll likely work with pump.ini or a dedicated alerts file depending on your setup. Here’s a structured approach:

Base Configuration via openaps.ini

Locate your openaps.ini file. It contains sections for each device and loop module. The alert settings are often under a section like [pulse] or [oref0]. You'll see parameters such as:

  • ALERT_LEVEL: how much in advance or how many data points before triggering.
  • LOW_ALARM_MIN_BG and HIGH_ALARM_MIN_BG: thresholds.
  • ALARM_SOUND or ALARM_VOLUME: some rigs allow file-based sounds.

Make a backup before editing. Use nano or a text editor via SSH. Change values slowly and test after each adjustment.

Nightscout Alert Configuration (If Used)

If you use Nightscout, you have a graphical interface to set alerts. Navigate to the “Settings” gear icon, then “Alert Settings.” Here you can define:

  • BG High/Low thresholds (absolute or percentage of target).
  • Time-based alerts (e.g., only from 10 PM to 8 AM).
  • Reminder intervals: how often the alert repeats if not acknowledged.
  • Notification methods: push, SMS, email. SMS requires additional setup with Twilio or similar.

Nightscout allows you to create multiple profiles (e.g., “work week” and “weekend”) so you can switch without re-entering numbers.

AndroidAPS Users

If you run OpenAPS on Android via AndroidAPS, alerts are managed in the app's settings under “Local Alarms” or “Notifications.” You can set distinct actions for each alert type: beep, vibration, or overlay notification.

Step 3: Set Personalized Alert Thresholds

Thresholds are the most critical part of customization. Rather than using generic numbers, base yours on your personal data and targets.

Low Glucose Thresholds

The OpenAPS default low alert might be at 70 mg/dL (3.9 mmol/L), but you may want to trigger earlier if you have hypoglycemia unawareness or a history of rapid drops. Many users set a “warning” low at 80-85 mg/dL and a “critical” low at 60-65 mg/dL. This gives you time to treat before you reach dangerous levels.

Consider also the rate of change (arrow direction). If your CGM shows a steady drop with a “double down” arrow, you might lower the threshold for alert urgency, and have the alarm trigger at a higher BG. Some configurations allow rules like “if BG is below 80 and dropping faster than 2 mg/dL/min, sound an immediate alarm.” That's advanced but possible with custom scripts.

High Glucose Thresholds

High thresholds should reflect your post-meal targets and how quickly you correct. A typical high alert might be 180 mg/dL (10 mmol/L), but if you aim for tighter control, you could set it at 150 mg/dL. However, beware of alert fatigue if you increase sensitivity too much. Also consider time-of-day: you may tolerate higher BG during exercise but want a stricter limit after meals.

Time-Based Profiles

Nightscout and AndroidAPS support time schedules. For example:

  • Daytime (7 AM – 10 PM): Low warning at 85 mg/dL, high at 180. Notifications as vibration on phone.
  • Nighttime (10 PM – 7 AM): Low warning at 90 mg/dL, high at 200. Notification as loud local alarm + text to partner. This accounts for sleep inertia and increased risk of nocturnal lows.

You can also set different thresholds on weekends vs. weekdays, or when you're sick.

Using Predictions

OpenAPS can alert based on predicted glucose (e.g., using the forecast from your loop algorithm). This is more proactive. For example, you can set a “predicted low” alert when the system expects BG to drop below 80 in the next 30 minutes, even if current BG is normal. This gives you time to eat a snack. Look for parameters like predicted_min_advance or forecast_hours in your configuration.

Step 4: Choose Notification Methods

Match the urgency of the alert with the appropriate channel. Use a multi-layered approach to avoid missed alarms.

Local Alarms on the Rig

The rig typically has a speaker and/or a buzzer. You can set different sounds for different alert types. Some users have rigs that play distinct MP3 files per alert. For example:

  • Low: a continuous, high-pitched beep that repeats every 30 seconds.
  • High: a single tone every 5 minutes.
  • Device error: a pattern like three short beeps.

If you have a rig with an LED (like the Explorer board), you can set LED color or blinking pattern. Red flashing for lows, yellow for high, green for normal.

Smartphone Push Notifications

Use xDrip+ or Nightscout to relay alerts to your phone. Ensure your phone's notification settings are appropriate – set alerts as “critical” for low BG so they bypass silent mode. On iOS, you can set specific alert tones for the Nightscout app.

Wearable Device Notifications

Many people attach a vibration motor to the rig or use a smartwatch. A smartwatch with cellular or constant Bluetooth connection can show alerts even if your phone is across the room. Configure the watch to use strong vibrations for low alerts.

Text Messages (SMS)

For extreme low alerts or when you're sleeping, SMS to a trusted contact or caregiver can be a lifesaver. Set up Twilio or a similar service with Nightscout to send SMS for critical lows. Use a unique SMS tone on the recipient's phone.

Smart Home Integration

Advanced users can connect OpenAPS alerts to smart home hubs like Home Assistant or IFTTT. For example, if a critical low alert fires, have your smart lights flash red and your smart speaker announce “Low blood sugar, please check.” This is especially helpful for people with hearing impairments or those who are deep sleepers.

Step 5: Test Your Alerts Thoroughly

Never trust a config change without real-world testing. Simulate scenarios and confirm each layer works.

Dry Runs with Simulated Data

Use a tool like oref0-simulator (if available) or manually trigger alerts by altering the data source. For example, you can push a fake BG value into your Nightscout site to see if the alert fires. Test each alert type: low, high, predicted low, sensor failure, battery low.

In-Vivo Testing

When you're in a safe environment (e.g., at home with someone else), intentionally let your BG drift into a low or high range (if it's safe to do so) to verify the alert. Or, if you can't control your BG precisely, use a calibration trick – but be careful not to interfere with actual treatment. Better: test with a CGM data pause to trigger a sensor error alert.

Check Alarm Fatigue

If you get too many false positives, adjust thresholds or time-based settings. Remember: the goal is to be alerted when you need action, not to be nagged.

Tips for Effective Customization

Beyond core configuration, these practices will keep your alert system useful long-term:

  • Balance sensitivity with specificity. Use rate-of-change filters to avoid alerts from noise. For instance, ignore a single low CGM reading if the next one is above threshold.
  • Personalize sounds and vibrations. Use different tones for different alert types so you can react without looking at the screen.
  • Review and revise settings regularly. Life changes – new job, new diet, pregnancy, aging. Adjust thresholds every few months or when your A1c trends shift.
  • Integrate with other devices. Explore APIs. Some users have their rig send MQTT messages to trigger home automation.
  • Enable snooze or temporary silence. Many setups allow you to snooze non-critical alerts for 15–60 minutes, which is great during a meeting or a nap.
  • Share with your care team. Inform your endocrinologist about your custom thresholds. They may have insights based on your clinical history.

Advanced Configuration: Conditional Alerts and Scripts

For power users, OpenAPS allows custom scripts that evaluate multiple conditions. You can write a small Python or bash script that checks not only BG but also insulin on board (IOB), carbs on board (COB), and recent activity. For example:

  • If BG is below 100 and IOB > 3 units and COB is 0, trigger an immediate low alarm with high priority.
  • If BG is above 200 and IOB is minimal and no carbs have been entered in the last 2 hours, send a suggest-to-bolus notification.

These scripts can be run as cron jobs or integrated into the oref0 loop. This is beyond default alerts, but it can dramatically reduce unnecessary alarms while increasing relevant ones.

Example: Nighttime Hypoglycemia Prevention

One common custom script: if between midnight and 6 AM, and predicted BG is below 80 mg/dL, and the rig has already suspended insulin delivery, then send a text to a caregiver AND increase the alarm volume to maximum. This provides an extra safety net during deep sleep.

To implement, you'd modify oref0-alert or use a separate script that polls your Nightscout API and triggers alerts via curl to Pushover or Twilio.

Troubleshooting Common Alert Issues

Even with careful setup, problems arise. Here are solutions to common issues:

  • No sound from rig: Check audio output device settings. Use amixer to ensure volume isn't muted. Test with a simple beep command.
  • Phone not receiving push notifications: Verify Nightscout URL and API secret. On iOS, ensure notifications are enabled for the Nightscout app in phone settings. On Android, check battery optimization exceptions.
  • Alerts too frequently: Increase threshold buffer (e.g., add 10-20% to high threshold). Apply a cooldown period (e.g., don't repeat for 5 minutes). Use rate-of-change gating.
  • Alerts missed at night: Set local alarm to maximum volume. Use a dedicated vibrating pad under the pillow. Have a secondary SMS alert to a family member.
  • Conflicting alert sources: If both rig and Nightscout alert for the same event, you may get duplicate notifications. Deactivate one source for non-critical alerts.

Conclusion

Your OpenAPS alert system is not a set-and-forget feature. The most effective systems are those that adapt to your changing life. By assessing your personal risks, configuring thresholds to your specific targets, layering notification channels, and periodically reviewing performance, you create a safety net that works for you, not against you. Remember, the goal is to reduce the mental burden of diabetes, not add to it. Start with small tweaks, test thoroughly, and refine. With time, your customizable alert system will become an integral, unobtrusive partner in your day-to-day management.

For further reading, check out the official OpenAPS documentation, the Nightscout setup guides, and the OpenAPS Alerts Wiki. If you use AndroidAPS, the AndroidAPS notifications page is also invaluable.