Enhanced personal research version of the xDrip android app
if anybody could help: i am wondering what kind of value Xdrip is sending to the watch? When i try to add a complication expression in watchmaker it ask me if i want a ''value complication'' a ''text complication'' or a ''title'' complication and the only one working is the ''Title Complication value. What is the difference and why only the ''title complication'' is working?
So I was asking few days ago about HM-10 module for xBridge... I got this fake one, but I couldn't get it to work... It seems that pins on module are not at the same place: Original has following pins: BRK - RXD - TXD - GND - VCC - STATE, and mine has EN - VCC - GND - TXD - RXD - STATE. I followed what is on mine, and at the moment I can't communciate with my device. HM is just blinking and I can't communicate with it... If I install xdrip fimrware it doesn't work either... So if the module doesn't work there is nothing more than I can do with it? If I would put lines in same order as on original one, it would probably destroy the module?
G6 - Last time, when I had to replace the sensor I unticked "Restart Sensor" and even "Preemptive Restarts", stopped the sensor from the menu, then made sure status changed to "Stopped", but after the few minutes that took me to put the new one and to click the transmitter to it I found that xDrip had started it again by itself and asked for double-calibration instead of calibration code. Is that an expected behavior? Is there a way to keep sensor stopped without auto-restarting?
Any idea how to remove the second identical status line on the Xdrip+ interfacfe above the graph (left of the large blood sugar number) that shows the calibration plugin calculation? IE "(xDrip original) s:1.13 i:-24.8 => 91 mg/dl. It is showing the idential line right below the first.
Not sure how I can post my screenshot in Gitter.
Anyone know what Sensor failed 4 means in system status? Running G6 with latest nightly.
help! suddenly i have missed/no readings on my oneplus 6 with android 8.1.0, security update 1.july 2018 and oxygenOS 5.1.11 and xdrip+ version f20d8da-2018.05.30. the phone is new, and i set it up 2 days ago. everything was working fine for appr. 24h, then this night i started having gaps. opening the app brought back the readings, but after appr. 15 min the readings stopped again. i reset verything, unpaired the transmitter, closed xdrip, but nothing helped. the transmitter is shown connected in bluetooth settings. i also set xdrip to not use any battery optimizations. localisation services are at the best settings.
@stackenblochen Switch the update channel to Alpha in the settings and install the newest version
@jamorham thanks for the quick reply, downloaded the latest alpha and testing it
@jamorham thank you so much for your help. the latest alpha works fine so far.
9th Sept nightly is out. I would be very grateful if everyone can test this version for goodness as this is hoped to be the next release candidate. Especially on this version please check that the graphical trend arrow (Accessed via long press of xDrip logo on home screen) still works correctly.
@miguelleon94 well it means the sensor is marked as failed by the transmitter. You can try restarting it but it may go to failed state again.
@teleriddler I'm thinking there is something unusual with your plugin settings, which glucose plugin are you using?
XDrip Original. I had Oopalgorithm installed but removed it and unchecked the 3rd party settings. Do you think it may be left over?
@teleriddler you need to disable the use of plugins if you're only using xDrip original. If its Libre of course I would choose to use Datricsae but that is personal preference.
@jamorham that did it, thanks. I will check out Datricsae as I am using libre.
@jamorham thx, this release looks good. the wear sync works again!
Anyone else getting large differentials with the latest batch of FreeStyle Libre sensors? The official Libre app is consistently 50 mg/dl below blood calibration values. Glad I have xDrip+ (thank you @jamorham) and can at least calibrate the correct slope. FYI datricsae is working great even with auto calibration turned on.
FYI I am in Munich, Germany and can post EU lot numbers if anyone is curious.
hi all, i want to use xdrip+ to get dexcom g6 readings on my smartphone (Moto G6), but I'm a bit unsure of how to use the app. for starters I want to use it in parallel with a dexcom receiver. that should work, right? after putting in the sensor id, should I click "start sensor"? I mean actually the sensor is already running and transmitting to the receiver.
@teleriddler ... a moving constant in my case. I reached an offset of 90 and am 5 days left to go. At which point does Abbott accept sensors as failures?
@rollerdecom wow.... That is a large difference. Agreed in regards to Abbott. I have 13 days to go, hopefully the next one is improved. You would think they would want to know.
@teleriddler ... my current one started with 20 and moves forward since. I started calibrating daily since last sensor. After 2 days perfect BG, 105 +/- 15 on aaps ... I got suspicious, tested and received 328... on 3 different meters and stripes manufacturer +/- 5
Glucose meters can not be activated, does anyone have the same problem?
I use the last nightly (Nightly build 8th Sep 2018), the same problems on my Android 8.1 smartphone
@jonas-frey Best to make sure using a very recent build, switch update channel to Alpha in xDrip+ Update Settings, then long press the xDrip logo on the home screen and enable source wizard and select G6 and it should guide you through the process. Yes you can use with an already started sensor.
Is that like Nichtscout 2.0? More accessible, easy to maintain, setup and understandable? Looks great
Struggling quite a bit with latest nightly version, and the one before as well, as readings are not constant and reliable as before. Main issue is related with impossible calibration process when required for starting up the sensor again. It reads the sensor data, but not "quality data" or something like that, so it's not allowing to calibrate and only switching to non-OB1 Collector I can make the system work again.
@jamorham Were there some code changes regarding blucon? I'm getting a lot of missed readings with the latst two nightlies.
@nsghub not that I can think of regarding blucon
any tips on this internal server error?
restart the NS server
Have done everything I can think of. Is there possibly a setting in xdrip that switches it to the internal server vs going to the base url?
@ELUTE Could be full disk.
Internal Server Error just means that the request was received and was valid and there was an unrecoverable error (exception) while processing it. Generally an http status 500 is returned.
Yes. I had guessed mlab full. They said they wiped their mlab but turns out they had two db's and had not wiped the correct one. Resolved now. Thanks!
@jamorham I have a proof-of-concept Tidepool uploader working that takes the xDrip+ export file (SiDiary format) and uploads the data to Tidepool. It is using their new, and yet unreleased API. There's one messy workaround for uploading carbs. I can start to work on integrating it into xDrip+, but I think we will need to wait for the new API to be finished before we could finish the xDrip+ work.
@alexkeremid Same thing happened to us today when putting on a new sensor. We hit stop sensor, and confirmed. We put on the new sensor, and when we looked at his phone again, it was asking for a calibration.
Evening all. My daughter managed to crack the screen in her pebble classic today, completely knackered. I am looking at ebay for replacements but thought it would be worth asking what others use and find hardy enough for children to wear.
@ptinson Sony smartwatch 3 is discussed as being suitable and reliable for xdrip.