-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NS downloads register as current #346
Comments
@LiroyvH Hello |
@NSFriend my base URL to nightscout? I run nightscout on a server in my private LAN, it's inaccessible to the outside world. |
@LiroyvH Ok |
@LiroyvH Please wipe the app from your device and reinstall from latest commit adae8bf |
This problem appears to have been resolved by commit [adae8bf]. Thank you! |
Actually. It would appear it doesn't download any data anymore at all :P I've added treatments and carb intake in to nightscout, and the app doesn't seem to be downloading them (keeps saying 0U insulin and 0g carbs). The connection to nightscout is fine and I can see in Xcode that it is actually downloading it from nightscout. It just doesn't process it. |
@LiroyvH Have you added treatments and carb in to nightscout from our app? If not could you please provide response from GET Probably we should leave treatments and readings fetching only for follower mode? How do you think? |
Hi,
When enabling "Download data" in the NS settings, xDrip appears to really start download everything; weeks and weeks worth of data before I switched it off again.
Its probably unnecessary to download that much data to begin with; for its purpose the last 24hrs would probably already be good enough, but the bigger problem is: this registers as current data, as if it's new data at the current timestamp. So by the time I switched it off, it registered and claims there's over 10KG of carbs on board, hehe.
-edit-
This also seems to cause all kinds of alarms to be triggered based on historic readings, such as the missed readings alarms. Needs sanitisation
The text was updated successfully, but these errors were encountered: