-
Notifications
You must be signed in to change notification settings - Fork 54
System Integrations
HAPP is designed to allow possible integrate with multiple systems. If you wish to sync data to/from a system not listed here please open a support ticket with details.
Any integration with HAPP must be set by the user, HAPP will never allow remote control from another system for safety reasons.
- CGM Readings - within xDrip / xDrip+ settings enable'Broadcast Locally'
- Active Basal, IOB and COB - this is then displayed on the xDrip Watch Face. Open 'xDrip Prefs' on the Android Wear watch and enable the setting 'Show External Staus'
- Only new CGM readings are passed to HAPP, historical readings are not synced
- The xDrip / xDrip+ app must be installed on the same phone with HAPP
Nightscout (via NSClient)
Nightscout integration is provided by NSClient, NSClient is another Android app installed on the same phone as HAPP and handles all the processes to read and write data to Nightscout. HAPP talks to NSClient not direct to Nightscout.
- Temp Basal adjustments
- Carb and Bolus Treatments
- Note: Enable the required settings in 'Settings' > 'Interactions' > 'Nightscout via NS Client'
- CGM Readings
- Note: To accept CGM readings from Nightscout HAPP setting 'CGM Source' must be set to 'Nightscout (NSClient)'
- Note: Getting CGM readings from Nightscout requires an active Internet connection. To use HAPP fully offline you must get your CGM readings direct from xDrip / xDrip+
- As of Nov 2016, Dev branch of Nightscout must be used to support NSClient
- Please be sure that NSClient can connect to your Nightscout instance before troubleshooting with HAPP
- There are plans to sync more profile data with Nightscout, changes are being made to HAPP to support the more flexible profile options from Nightscout (now complete) and sync code needs to be written (not started). There is currently no ETA for this.
- Support for NSClient
An Insulin Integration APP is an app installed on the same phone as HAPP that receives TBR, Extended Bolus and Bolus requests. An example app is a Pump Driver that will action the request on the pump, therefore producing a full Closed Loop System.
- HAPP is designed to be an Open Loop system to support any potential pump as the user is the interface between app and pump.
- HAPP follows the OpenAPS principal that the user must build a Closed Loop system themselves by connecting the required building blocks (or apps as in this case)
- This keeps the HAPP code base clean for capturing, sharing and processing data
- BY having separate apps safety checks are repeated and common shared code is limited to avoid a bug in one app affecting the other
- The Pump Drive apps job is to focus on Pump communication, this helps simplify the application
- TBR, Extended Bolus and Bolus
- Result of requests
From HAPP the following must be set in 'Settings' > 'Integrations' > 'Insulin Treatment Integration'
- Insulin Treatments App - the app you wish to Integrate with, this will list supported apps installed on the phone
- Send Temp Basal - allow Temp Basals and Extended Bolus to be sent
- Send Bolus - for safety reasons this must be enabled along with 'BOLUS_ALLOWED' UserPref in HAPPs Source Code and compiled by the user. It is recommended that Bolus are manually actioned.
As of Nov 2016 there are no Pump Drivers in use, the following have been created but are not ready for use...
- Pump Driver Example - Example Pump Driver app, please note this is currently out of date and best avoided
- RoundTrip2 - In the works Pump Driver that support OpenAPS compatible Medtronic pumps. This has the most recent integration code for HAPP communication.