You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I got reports from some FreeAPS users that they're having issues with Nightscout profiles. Checking their profile data, I noticed they have a huge amount of profile data in their system, where in some cases the profile has been synched in three times within one second, resulting in the profile collection bloating to be huge. I doubt the profile actually changes this often, so I wonder where the glitch is that causes this. One suspicious part of thee data was that the loopSettings section seems to have "scheduleOverride" section, which seems to be part of the runtime data and not part of the profile, where if the next scheduled basal change is sometimes entered into the profile data and sync is caused by a difference in the profile, this would trigger the profile sync to happen excessively.
The text was updated successfully, but these errors were encountered:
I had this problem too. Setup I use has Loop (FREEAPS), spike, blucon nightrider, libre1, nightscout.
Noticed this problem as spike stopped showing new treatments, but those were visible in NS chart. Then noticed that NS profiles were causing NS reports to not load.
The fix was to remove the profiles collection from the Mongo and let NS re create it by making profile change from loop settings.
Hi! I got reports from some FreeAPS users that they're having issues with Nightscout profiles. Checking their profile data, I noticed they have a huge amount of profile data in their system, where in some cases the profile has been synched in three times within one second, resulting in the profile collection bloating to be huge. I doubt the profile actually changes this often, so I wonder where the glitch is that causes this. One suspicious part of thee data was that the loopSettings section seems to have "scheduleOverride" section, which seems to be part of the runtime data and not part of the profile, where if the next scheduled basal change is sometimes entered into the profile data and sync is caused by a difference in the profile, this would trigger the profile sync to happen excessively.
The text was updated successfully, but these errors were encountered: