Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

jamorham/xDrip-plus

Enhanced personal research version of the xDrip android app

People

Repo info

Activity

Andy Rozman

@andyrozman

@sethgagnon what is the solution?

sethgagnon

@sethgagnon

in xdrip+ i had to go to less common settings > extra status line > check the box for external status

then in AAPS, i had to go to Config Builder > check the box next to xDrip Statusline (watch)

and on the gear icon there

you select show detailed IOB and show BGI

i could then see the same details for IOB/COB in AAPS and in xdrip

although not sure how frequently xrip updates with the info from AAPS, as its already out of sync

looks like it could become out of sync for a min or 2 and then it catches up, so works pretty well

nsghub

@nsghub

is it possible to use AAPS without the need to enter the eaten carbs? I know that the website says it's not ;) But then I don't understand the purpose of a closed loop system.

sethgagnon

@sethgagnon

I believe this is possible, as I think I have seen dana going the unannounced meal route. might want to post in AAPS channel to ask?

swissalpine

@swissalpine

AFAIK Dana enters Carbs and let openaps control the insulin doses.

Eric

@ecc1

@nsghub it's technically a "hybrid closed-loop" system -- the hybrid part is the human input for meals etc.

n0rbertg

@n0rbertg

@nsghub with Fiasp (or another rapid insulin) a few ppl does it successfully

@swissalpine Dana said some time ago that she hasn't entered any carb in about a year :)

Thomas

@thkr_twitter

Would be interesting what her usual diet is... with a big breakfast (many carbs) I‘ve doubt that this works today... but I didn’t tried fiasp in the Pump now - only manual as a boost parallel to the pump (before looping).

Julius de Bruijn

@pimeys

Tried with fiasp but you need to eat either a small amount or very slow carbs

n0rbertg

@n0rbertg

you can ask her on a channel where she's on

nsghub

@nsghub

I tend to eat between 40 and 120 carbs per meal. I guess that at a low carb input it works best. But on the other hand, one has to carry another device.

Milos Kozak

@MilosKozak

@jamorham in G5 native mode xDrip is broadcasting G5 Native but to NS is writing "device":"xDrip-DexcomG5". can this be resolved?

JamOrHam

@jamorham

@MilosKozak maybe, but isn't the setting Append source info to device name in the xDrip Upload settings what should be enabled for this extra detail?

Milos Kozak

@MilosKozak

that's it. Thanks!

updated AAPS wiki to do this

JamOrHam

@jamorham

@MilosKozak I can make xDrip automatically set the setting if it is always needed in the presence of AAPS, we do this for other broadcast settings etc.

Milos Kozak

@MilosKozak

ok, great

old-square-eyes

@old-square-eyes

xDrip keeps crashing on my SW3. Have updated to latest nightly, still happens. Reset Wear DB and resynced Wear apps and turned off Wear collection.

Still happens

Any idea how to debug?

n0rbertg

@n0rbertg

what's in the log?

Zach Gohr

@zgohr

Troubles patching a zenwatch2 502Q. “ERROR: could not patch BT with demigod mode” but no other hints

ronaldhacker

@ronaldhacker

Not to sound dumb, but what is AAPS?

Eric

@ecc1

Android APS

(openaps ported to Android)

old-square-eyes

@old-square-eyes

Have to enable Wear logs. Will report back.

Zach Gohr

@zgohr

@jamorham any ideas on getting my Zenwatch2 502Q patched? Everything goes fine until actual patching, then I just see the generic “could not patch BT” error message.

JamOrHam

@jamorham

@zgohr does your watch build number match the one described in the care package PDF ?

Zach Gohr

@zgohr

it does not. looks nothing like it

/facepalm

JamOrHam

@jamorham

@zgohr either it needs up or downgrading so it matches

Zach Gohr

@zgohr

How would one go about doing that?

Royce Simpson

@roycesimpson

Hello all. I just fired up the "native algorithm" options on xdrip+ and g5... I enabled that for a sensor that I've had for a few days and just "stopped/started" the sensor and went through the 2 hour warm up... that was last night. Now, when I calibrate, it doesn't seem to do anything. For example, xdrip is showing I'm at 80 but when I enter a calibration of 100, the number and graph stay at 80. That doesn't seem right.

Should I expect different behavior in xdrip now that I'm using the "native algorithm" options? Does it take a few readings to adjust?

Royce Simpson

@roycesimpson

Do do see that a reading has come in after that calibration and it's jumped to 87... about half way between my prior-to-calibration reading and the actual calibration.

teleriddler

@teleriddler

calibrations in general usually wait about 15 minutes, I believe to make sure there is not a spiking value so sit can compare over 3 values to normalize the trend a bit. This is what I have observed but others may be able to give more specific information.

Julius de Bruijn

@pimeys

yeah, first it puts the calibration in queue, next time you get a value from the sensor, it sends the calibration to the transmitter

then the next time you get a value from the transmitter, it gives back a value calibrated with the new measurement

actually now when I don't use AAPS, I like the xdrip algorithm way better

Royce Simpson

@roycesimpson

@pimeys @teleriddler Thanks, makes sense. Yeah, I think I like the xdrip algorithm better too but I'll give this a few days. I also like having that grey "filtered plot" on the graph which doesn't show up anymore with this native algorithm.

Julius de Bruijn

@pimeys

yeah, native algorithm makes sense if you do closed loop with android apis

and use oref1 smb

Royce Simpson

@roycesimpson

Curious, do I need to enable these native settings to use the G6 transmitter/sensor? I got those on order and will be replacing the g5 soon.