Open oddst opened 11 months ago
bewest
commented
11 months ago Does this occur with openaps? Can you inspect your devicestatus API endpoints to see if iAPS is uploading this data consistently? When openaps pump mode is used as a plugin in Nightscout this information is read exclusively from devicestatus records.
oddst
commented
11 months ago This occur with iAPS. I believe only with iAPS…! AAPS probably does not have this problem, but that might be due to using Websockets and with 3.2 also APIv3….?
I have no idea about about OpenAPS…
iAPS might have problems with its Nightscout implementation overall. Too much is based on what takes place during a looping cycle, and Jon Björn is looking at ways to get “Upload CGM Readings” out of that cycle. I have asked if it somehow would be possible to do calculations even when the pump is busy giving insulin. An OmniPod will typically use 15-20 minutes giving a 30U bolus… He is looking at this.
There has also been some suggestions from Bjørn Ole that iAPS might not get to send all it should send, due to the time allocated during each processing cycle…
Several of the developers are currently looking into the Nightscout integration issues for iAPS right now…!
I believe that the time is good to look into this now, as several Loop users are migrating to iAPS due to wanting more aggressiveness than the development group behind Loop wants…
The Remote Functionality involving Nightscout also needs to be looked at. The Remote Profile/Override functionality in iAPS does not even exist so far. The Bolus/Pump/Looping functionality is also working when it cares to…!
I do believe that it is imperative that Nightscout works well with iAPS going forward. It should since so much of it is the same as AAPS/OpenAPS. But all CGM/Pump code is from Loop…
I can try to look closer at the Devicestatus API endpoints…!
If you need support for Nightscout, PLEASE DO NOT FILE A TICKET HERE For support, please post a question to the "CGM in The Cloud" group in Facebook (https://www.facebook.com/groups/cgminthecloud) or visit the WeAreNotWaiting Discord at https://discord.gg/zg7CvCQ
Describe the bug When receiving new BG value through Dexcom Share/Connect or Bridge, the OpenAPS pill and the OpenAPS prediction curves disappear for a few minutes. Currently the OpenAPS pill is displayed around 60-80% of the time, but the OpenAPS prediction curves is displayed around 50% of the time. Scrolling the Nightscout graph back and forth again, will usually make the OpenAPS pill appear again - but unfortunately containing random older data (not the current data). To Reproduce Steps to reproduce the behavior:
Expected behavior I expect the OpenAPS information pill to be displayed all the time, but if it does not contain fresh data - it should say so. But often the OpenAPS pill disappears from the page, when it does not disappear then a mouseover says either "iAPS o Waiting" or "iAPS x Not enacted". This bevavior could be improved and made more logical for users.
The OpenAPS prediction curves do disappear around half of the time. They should be present but they should show what BG time they are based on...!
Screenshots
How it should have been looking all of the time... ;)
How it looks with prediction curves not displayed, even though they are displayed at other times and have been selected in the Nigthscout local config:
Local configuration:
Examples of OpenAPS pill status, when it is shown:
Your setup information
Additional context AAPS users claim that they do not have the same problems, so parts of this might be due to iAPS uploading problems. But I still do not think that the OpenAPS pill and the OpenAPS prediction curves should disappear if updates are missing...!