600SeriesAndroidUploader
600SeriesAndroidUploader copied to clipboard
pazaan
Basal profile switch is sometimes not recognised
Placeholder issue. I still need to determine how to reliably reproduce. This has happened to me twice, and has been reported once in the FB group by someone else.
Sometimes a basal profile switch is not recognised, so the incorrect basal value shows in the basal pill (not in Auto Mode). The current solution is to switch to different basal profile, hit "Get Data Now", then switch back to your preferred basal profile and hit "Get Data Now" again.
In v0.6.1 there are a few potential things that could cause this.
If the pump - uploader time deference is over a certain amount it may miss the most recent history item due to a bug in how the RTC range is calculated for it's pull request. It should eventually get the history though it may have been delayed. Fixed for 0.7.0
The history request trigger code may not have been able to infer a change took place, possibly due to incomplete polls mixed with a change that fell on/around the 15 minute stale boundary. A history request is always done when poll status message data is considered stale.
If you see this happen again, check the user log for the 'basal pattern changed' history trigger and make a note of the time difference. Also don't do your workaround and just wait and see if it eventually gets the pattern change from the next history pull.
Another note as I just read the FB posts:
The user had a 670G and was recently in Auto Mode and noted a basal rate of '0.0' when they expected their non-AM basal to show. This is NOT A BUG as the AM update rate is only a near realtime update and will only reflect pump changes at the user selected rate. They may see a considerable delay (default is 90 minutes) for a basal switch to happen after a Auto Mode exit.
The status message we get poll to poll does not contain any info to infer a change and for AM users these changes will only get processed for NS on a schedule. This can be as often as 15 minutes and set via the 'advanced system settings' menu.
No, the other user I mentioned has a 640G. I also had the issue myself when I was in manual mode. There is another historical message that tells us about Auto Mode changeover. I really just left this issue as a placeholder to investigate. I’ll close it if I can’t repro.
Ok - they had mentioned a rate of "0.0" which is odd for the 640 but not for the 670. Anyhow deleted the FB comment I made rather then confuse the issue.
Keep it open in case there is something else going on.
Hi, I can replicate the problem with lates uploader version released few days ago. I think the problem is in number of the profiles used in the pump. Basal profiles changes like it should using basal profiles 1-3, but if 4th profile is created, I wont report the values like it should. Can anyone else replicate?
I can't reproduce this and any pattern change on the pump produces the corresponding switch in nightscout. If you change a pattern insulin settings or add a new one a "update pump profile" needs to be manually done in the uploader. Switches will be automatic.
As of version 0.7.3 pump patterns will be read from the pump once every 24 hours and automatically updated in nightscout. This will help if the manual entry is forgotten. It also gets around an issue in nightscout that can have it not see a current profile after several days when there is no switch in its current dataset window.