Skip to content

Uploading pump data erases data uploaded from other pump

In a two pump configuration, where a suspended 640G is serving as cgm data collector only, the uploaded syncs the suspended state to Nightscout, invalidating

  • site changes
  • basal rate
  • bolus
  • carb data

The alternating upload from loop and uploaded competes for the data, resulting in alternating displays of metadata and cgm-only, and data loss on the loop frontend to boot (which sometimes fails to handle such a situation where the data has been deleted on nightscout only - also an issue with using the careportal menu on the Nightscout site)


  • 1730 a Dexcom G5 sensor got started in addition to the running Enlite
  • 1930 Dexcom got calibrated
  • slight deviations in the tracks of both sensors leading to "loops". That's not a bug, the data source is linked to the data.

31958359-385C-462B-9226-4B8F768ABBF1 A69BE3B2-2173-43E0-9144-70D33054AC49 8B9B05EE-EF91-43AC-A697-F73E898265F2

Edited by theuser