The current implementation assumes that carbs corresponding to a meal bolus are always available within the diasend API up to one minute prior or after the corresponding bolus. However, some samples indicate that this may well be 2 minutes, and potentially even more. This may also contribute to the situation described in #18.
The current implementation assumes that carbs corresponding to a meal bolus are always available within the diasend API up to one minute prior or after the corresponding bolus. However, some samples indicate that this may well be 2 minutes, and potentially even more. This may also contribute to the situation described in #18.
https://github.com/burnedikt/diasend-nightscout-bridge/blob/184691c00b6f4e81dad511006b25d6fbf93d8a3c/adapter.ts#L59