nightscoutfoundation / xdrip Goto Github PK

This starting happening the other day. I am using a Nexus 6P with android 7.1.1. Whenever I add a BG through the add treatment dialog, I get the "got zero slope calibration" error. Any ideas what could be causing this,

Sorry I'm kinda new (G5 & Xdrip user for only 3months now) Is this where we can ask for support & features?

My insurance only covers Verio meters; I try adding the onetouch verio flex; I can get it paired (with the phone & xdrip+). I can have it sync with its own app; but I get timeout errors when trying to sync with xdrip+
Timed out on : get new glucose records

I'm using latest nightly builds; currently xdrip ver: 381226d-2017-05.12

I'm using a Motoroloa G5plus phone, running droid 7.0

Soon some work will be done to add a few additional Tasker features.

This issue is an opportunity to suggest useful events/commands which could be included.

Feel free to suggest anything, but please also explain briefly a usage scenario where the event/command would be used and how you would find it useful.

Easier and more generically useful to everyone events/commands are the most likely to be implemented first.

It would be helpful to be able to have the Extra Status Line display the current day's Treatment Insulin Total.
Thanks

It would be great to silence/snooze the alarms with the press of either the volume buttons or the power button. It would be the same as when silencing an incoming phone call.

Case: I was caught in church this morning with my xDrip+ alarm going off and in a panic trying to turn it off. Luckily, I remembered the snooze button on my Pebble, but the ability to silence/snooze from the volume or power buttons would be great!

Hi,

I'm curious can I use a rooted Sony Smartwatch 3 as an NFC reader with xDrip+ as you can with LibreAlarm? I'm planning to buy one only if it's possible to attach one to a Freestyle Libre NFC chip so it could read the glucose values constantly and send them to the Android phone using Bluetooth. I'm currently using this software with Libre using the phone NFC functionality, but a nightly alarm for hypos would be more than a nice feature.

i can not connect anymore to the equipment...
errormessage on the phone: xdrip collection service running-------- bg reading unavailable....
howto change it? or restet it to default settings?????
thanks 4 help
wf

Can you please add the feature that an alarm will be snoozed if an treatment is active that will bring you back above/below threshold?

See example line here, the result is cast to int but can be null. There are a few places this occurs. What should we do with those to fail through cleanly when for whatever reason there could be invalid data?

Can we use Integer instead and test for null. What is the correct way to exit the onTouch listener when this might happen?

Hi,

Android Wear 2.0 is coming very soon for many smart watch owners and it has one pretty cool API to use with xDrip+: the Watch Face Complications[0]. I already branched and started working on it, thinking that it would be quite easy: the class just needs to extend the ComplicationProviderService and implement an asynchronious method onComplicationUpdate, allowing the user to display xDrip data on any Android watchface, basically removing the need for separate watchfaces only for xDrip.

I realized the current watchfaces take the value updates as callbacks from the xDrip running on the mobile phone, but here the watchface itself should trigger the updates and the new provider should reply with the values the watchface wants to display. This made me think for a while... I either need:

• A class that gets the updates from the phone, caches them and reports to the watchface. Sounds kind of wrong to me, because I don't have control over the instances and if I cache the updates, I need to keep them in a global variable; no good.
• A class that when the watchface asks for data, the class asks the latest value(s) from the xDrip running on the phone and reports them back. This eats a bit more battery but makes the code design nicer.

Both of the options mean the values are a bit older than the ones on the phone or the watch is using more battery if it asks for new data too often.

I'd like to hear some ideas how to move forward and if any of these two options is the way to go, some hints how on earth the value update works between the watch and the phone. The prize is basically to create infinite amount of different possibilities how the watch looks like while still having the most important information visible.

Regards,
Julius

[0] https://developer.android.com/wear/preview/features/complications.html

When the xdrip+ daydream feature kicks in, the screen turns black and the graph, current BG values show up on the screen.... all good there. However, at the top of the screen the status bar remains, will all the status bar items... clock, notification icons, etc... and, the status bar is a bright blue color.

I'm concerned about screen burn-in with this and would rather there be nothing on the screen except for the floating graph and bg value.

since 2 days seems I have no Bluetooth connection ....the green led is on and blinks all 5 minutes ..

maybe here is someone who can give me directions, howto search for the error in my equipment?
running xdrip plus..Bluetooth wixel .....is there a reset to the initial settings??
everything was fine running till yesterday ago..
thanks for reading
wf

It shows the "direct value" and not the value that is based on some noise calculation.

Is it possible to add an option to snooze or disable the calibration reminders just during night? So you would not have to enable and disable it every day again...

I sometimes put xDrip into vibrate only or Ascending volume, and neither vibrate when the phone is on silent mode. Putting the profile in Low, Medium, or High, works properly and the phone makes the sound even in silent mode, however, they do not vibrate.

The SlopeParameters constant "DEFAUL_HIGH_SLOPE_LOW" should be "DEFAULT_HIGH_SLOPE_LOW"
in Calibration.java

I know that might be pedantic, but the missing 'T' annoys me.
Fix it, or don't.
Just thought you should know.

It would be useful for me, and possibly others, to be able to see a plot of the raw unfiltered (or filtered) data plotted on the Home Screen. The benefit would be the ability to see trends in BG values even when normal plotted data changes due to calibration algorithms, rewriting history, or other reasons. Ideally it should be easy to turn this extra plot off and on - possibly via an icon on the Home Screen. The plot could also be adjusted with an offset to keep it on screen in a useful manner, and/or a scale factor, but otherwise should not be affected by changes in calibration, plugins, or other affects.

Currently there is a status line dedicated to "x minutes ago" for the length of time since last reading. Would be convenient and time saving for the user if when the time is "4 minutes ago" to read " in x seconds". For example, lets say there are 20 seconds left until the next reading, instead of showing "4 minutes ago" show "in 20 seconds" ... "in 19 seconds" ... "in 18 seconds". That way the user knows exactly when to come back and check and not simply be in the ballpark of "4 minutes ago".

Often when in a different app, xDrip will open over the current app. I have yet to discover what is causing this and I'm wondering if it's a bug related to android 7.1.1. <-- I am using the Nexus 6P. Is anyone else having the same issues?

Starting with Android 7.0, Google added the ability to change your display size (basically adjust the DPI). When you change the display size from from Default to Large, Larger, and Largest, the app scales properly. However, when you change the display size from Default to Small, the app (and more specifically the Status Line text) does not scale properly at all; the size of the Status Line text appears to at least double.

While only mildly annoying with the just the default Status Line or even one Status Line items, the improper scaling makes the ability to add multiple extra Status Line items impossible.

I've included screenshots of what the behavior looks like below. The top photo is with "Display Size = Default" and the bottom is with "Display Size = Small".

Hi there,
I tried vehicle mode and it works fine. I wonder, if there is a possibility to make a setting to enable "read values out loud" automatically in vehicle mode without enabeling it manually?! It would be a helpful feature don´t you think..?

I have been using xdrip+ for several months, but due to an upcoming endo appointment I started looking at the best way to generate reports and Nightscout seemed to be the seamless way. I'm a software dev, so the complicated setup didn't bother me.

I went through all the setup to get nightscout up and running, and my xdrip app is uploading current blood sugar readings as expected. However, it's been about 18ish hours since I got it running and as of yet it hasn't uploaded any of my several months worth of back data.

I've been told in the xdrip+ facebook group that it should be uploading the back data, so since it's not I'm filing this issue. Thanks!

xdrip+ is adding two entries to careportal, one listed as xdrip (what I chose to list xdrip+ app as) and one listed as blank. One is of the type of entry it is (e.g. meal bolus) and one is just a note.

First time I've recorded an issue so please let me know what further info you need.

Can you a the ability to change the prediction values by time. For instance in the morning I need more bolus and correction Insulin.

Hello,

can anyone explain the mathematical process of the calibration algorithm to me?

when i connect the wixel to write the usb-serial.wxl..it works...and flashes with the file..next when I open the terminal NinjaTerm or Putty to write "AT" or "AT+SBLUP" , i get no response or echo ...what is wrong???
thanks for help ( used the right port, right speed 9600 right stop bits and so on)
'but something is wrong...????
wefi

I recently updated my circuit to suit the xBridge2 firmware with battery charge indicator resistors. Initially it appeared to be working fine, but after my first charge/discharge cycle I'm getting weird results.

Overnight off a low amp (computer) USB port it wouldn't go above around 40% charge. This morning it depleted quickly to 20%. I just now plugged it into a 1A phone charger and it immediately jumped to 79%. It quickly charged to 100% after that, but when I disconnected it dropped almost immediately to 84%.

What troubleshooting steps can I take? Any ideas on what might be wrong?

I'm using the recommended resistors from the pdf (10k and 27k, 1/2 Watt metal film). But I'm not using the Adafruit charger. I'm using a Chinese alternative, battery in parallel with the Wixel, and a 1A Li-Po if it helps.

The nightly Builds after 17.12 have a broken Watchface.
On the SmartWatch, the xDrip-Watchface is only Black and show nothing :-(

Since changing to xDrip+ about a month ago, I have found the packaged 'Color Trend Watchface' goes into a mode where the following problems occur :-

• the watch doesn’t process/vibrate for any alerts coming from xDrip+ (via Notification Center).
• pressing any righthand side button causes the watchface to load again, pressing button again causes the watchface to crash.
• ‘timeago’ is missing from the watchface, not sure if this is a cause or consequence.

I can see it is in this mode when the ‘timeago’ is missing, all other controls are still updating as usual (bg,trendline, delta,etc.)
Watchface goes into this mode about once or twice a day, usually overnight, I can’t identify what’s causing it to go into this mode. Atm, I’m not using the watchface overnight as I rely on the pebble vibrations for my BG alerts. Alerts work when I swap to a non xDrip watchface, even after it goes into this mode.
Once in this mode, it can be difficult to get it running normally again, I often have to reboot phone and reinstall watchface from xDrip+ settings.
Hardware/software:-

• Samsung S5 with android 5.0
• Pebble time steel running v4.3
• xDrip+ latest beta with G4 via xBridge wixel
• I use ‘Notification Center’ to provide an extended vibration pattern for xDrip alerts.
  Any help resolving this would be appreciated.

Hi All,
I forked @jamorham 's xDrip+ and added a new all-in-one 'Add Treatment' view with features:
I've modified it as I was finding the current add treatment entry slow to navigate.

1. Material Design Time picker (defaulting to now & restricted to < currentTime+1hr)
2. Native android keyboard with editView's and imeOptions for quickly cycling through the fields and submitting from the keyboard
3. Native inputType's for simpler input validation
4. DialogFragment View to retain visibility of the graph in the background
5. For xDrip+ I've added quick suggestion buttons for carbs and insulin, for a quick entry similar to MySugr app (see video). Notice the suggestion disappears on editing any field, as to avoid confusion/outdated suggestions. [I would love to make this dynamic based on what's being entered into the carbs field, but I have no experience with the calculations. If anyone can help there, I'd love to hear.]
6. Toolbar 'ifRoom' add treatment button (My big fingers have constantly been hitting the wrong button in the current version)

Quick demo here: https://www.youtube.com/watch?v=MKpDlzaXHOU&feature=youtu.be
I'm interested to hear people's thoughts or if a PR would suit?

I have my phone set as the sync master and my tablet set as a sync follower. Last night sync stopped. I just looked at it now and saw that on the tablet "Disable all sync features" was checked. I thought that was strange because I hadn't touched the tablet since before sync was discontinued last night.

I waited for sync to resume, but it did not. Rebooted with no success. Then I looked at my phone and was astonished to see that "Disable all sync features" was checked there too! Reboot and sync has resumed.

This leads me to believe that there may have been a problem with the latest nightly apk. I updated both the tablet and phone last night before the sync behavior was disabled. Has this problem been previously reported?

Hi! I've just got yesterday a Dexcom G5 and I am currently testing the xDrip+ application, which is really awesome. I've started a new sensor with an iPhone running the Dexcom official app, then I've stopped the sesnor on the Dexcom app and started a new session (wearing same sensor) using the xDrip+ app on a Samsung Galaxy tablet. The xDrip application required about 20 minutes to connect to the G5 transmitter and to start to get data. Next I've stopped and restarted the sensor, for debugging purposes, from the xDrip+ app, but this time it started again the warmup process of 2 hours. Is it possible to skip the two-hours warmup phase after a stop/restart in case the sensor has not been replaced?

Clicking on the Wiki tab seems to reload the code page. Is the wiki page disabled? Is there another wiki? If so, should the wiki tab redirect to that?

Hi,

The battery status got stuck at 2% on the Sony Z3C we use as an uploader. Tried deleting documents, restarting Azure, reboot of phone and all had no effect. Rolled back to the previous release we were using and issue resolved immediately.

I cannot enable the "use bluetooth meter" option in Xdrip+ - the off/on button seems to be stuck in the off position despite pairing my meter with the app using the scan for bluetooth meter option.

How does this integration work or is it still in development?

Love the app and appreciate the help.

Please extend the new "extra line status" options for total carbs and total insulin to include another (and last) option for the ratio of those two. carbs/insulin. For example if the total carbs for last 24 hrs is currently 100 and total insulin is currently 15 then this new option would show 6.67.

There are 3 casses where users can enjoy from multicast packets:
This is not intended instead of other ways, but as a way to make data more reliable and fast when one is at home.

1. In the case of all house coverage. Currently there are two ways that xDrip can connect to the receivers. The first is through the cloud (parakeet or mongo) or through configuring static ip addresses.
   From my experience, many users have a problem with static ip addresses (configuring routers and so on).
   So the suggestion is to have the wixel receivers send the data as multicast as well.

2. Remote snoozing: This messages usually reach all tablets at home, but it might take a few minutes for the messages to arrive. In the case of an alarm, this is sometimes too long.

3. sending normal bg data. As before, the messages arive through the cloud, but it would be nicer to have the bg reach faster.

xDrip should listen to a predefined udp port and receive these messages.

Format for 1 should be:
const number^ version^ Dex ID ^ unfilt ^ filt ^ G4bat ^ sigstrength ^ txcount ^ xDripBat ^ time from packet captering
0x16324234 1 10858926 120488 111488 216 -49 105 3021 0

Format for 2,3 are the same as they today, (with their existing encription).

Does this sound reasonable?

My tablet is set up as an xDrip+ Sync Follower. When I enter a treatment proposal on my phone, which is set up as the master, but do not confirm it as accepted treatment, the treatment proposal shows as accepted treatment on the tablet (xDrip+ Sync Follower).

For instance if I propose an insulin treatment of 7u, then abandon it, then 9u and abandon it, then propose an insulin treatment of 10u and accept that, the data on the phone correctly shows an insulin treatment of 10u but the data on the tablet incorrectly shows insulin treatment of 10u+9u+7u. Note the graphs and the extra status line.

Thanks.

It would be really great if you could add a setting to configure how many time in past we see the BG curve.
Same way as NS doest it for example with a 3, 6, 12 and 24 hours views.

Would it be possible?

I've been playing around trying to better understand the predicted BG system. From what I can tell the model isn't quite complete or accurate.

I've attached a photoshopped overlay of what the system thought would happen versus what did. Treating a low with 20g of pure dextrose dissolved in water. This is quite different from eating 20g of chocolate. Although, next time I'd be happy to treat a low with chocolate for the sake of science...

I think the system needs to know how much fat, protein, and fiber is in the food as well. Even the type of carb is probably relevant given how dextrose, sucrose, and fructose to name a few are metabolized. There are probably other factors too that I don't know about or understand.

From a UI standpoint, nobody is going to want to enter all the components each time so I think a good implementation would be to store the food item in a database (that could also be network distributed). This way, picking the food item, you can get an accurate model of how it will be absorbed. With this, the system can even provide suggested pre-bolus times to overlay peak insulin action and peak absorption.

For some unknown reason, my Moto Z Force no longer recognizes the bluetooth transmitter. It has been two days now. Transmitter just stopped working. I've tried two different (new) transmitters thinking that one was bad. No luck.
Transmitter appears to be connecting to the Dexcom receiver, so I may be forced to suffer with another device again, but I would rather not.
I see now that that the Beta is over and I have since downloaded the latest Nightscout apk. Same result. What can I do?

I'm noticing that if I add a treatment in xdrip+ and then undo it, that entry is does not get removed from nightscout site. This can be problematic as many times I will enter treatments into xdrip+ to do "what if" scenarios. What if I eat this much carbs, what if I take x bolus, etc... I'll many time do this several times until I get the numbers I want and keep that as my final input. If I do this and go into my nightscout site, I'll see all the "what if" treatments that got "undone" in xdrip+ and I have to manually remove those from the nightscout treatments.

I am using version 1704032023 (which I believe is the latest one?) on a samsung galaxy S6, with a sony smartwatch 3, xbridge (v2), and a dexcom G4.

Since the update, the xbridge battery status appears to be getting confused with the watch battery level when using the wear based collection service (which I use the majority of the time as I seem to get more reliability in that).

This is a particular pain for me at the moment as I am havaing issues with my xbridge battery not lasting as long as it used to, so it would be really helpful to be getting correct battery information.

What seems to happen is that when the watch is doing the collecting, it displays both the watch and xbridge battery as the same level even when I know they are not the same (for example if I've just charged the watch and not the bridge, it will show "W:100% Bridge:100%" on the watch screen and on the phone app xBridge Battery: 100%.

This was not seen in the previous version.

Thanks

Paul

The Calibration Check-Ins are not working. When I click on the button, it says that the calibrations are checked-in but in the log there is appearing the message "No useable driver found".

can the program be changed, so it can be installed on older android versions? ( 4.1.2.)
that would be nice... I get an parsing errormessage when I try to install...
wf

The default minimum slope for the calibration algorithm is problematic. I originally noticed a problem calibrating some sensors last year. Adrian helped me resolve my issues, and created a new "DexParametersAdrian" class, which could be enabled when engineering mode is enabled. This method allowed me to continue using at least 6 of my sensors that would otherwise be useless, and still occasionally I need a slope lower than the default minimum (1.08). Since that time I have helped 5 or 6 other people enable this special mode to get their calibration slopes to fit the data. I am reasonably certain that for every person that discovers this issue, there must be many more that are not aware of it and may be throwing out perfectly good sensors.

I suggest the default minimums be changed for everyone -- copying the class DexParametersAdrian to DexParamters may be the proper solution. Except I would consider opening the ranges between lows and highs a little to allow for more flexibility - I had at least two sensors where I had to lower even the Adrian defaults to get them to calibrate properly. Maybe the DexParametersAdrian class could be kept, but extended even further for special situations.

I am submitting this issue in the hopes of helping more people without having them enable the potentially dangerous "engineering mode".

EDIT: This is in the dexdrip/Models/Calibration.java source file