nightscout/android-uploader

Old-school standalone Nightscout uploader

Lennart Goedhart

@pazaan

I’m not sure about monitoring only for 5/7 series pumps.

th122

@th122

@meenanader there currently is a discussion on the mm-connect at the gutter channel nightscout/public. If you ask there, I'm hopeful that someone with recent experience with that configuration would answer.

(autocorrect is messing up again: Gitter Channel)

idowolf

@idowolf

Hi, question - I'm currently getting my BGs from 640G & Guardian 2 Link. My transmitter is old and I have an option of getting another of the same model, or a Guardian Connect that sends data to the phone. Is there a way to get BGs to Nightscout from the Guardian Connect? Will 600 series uploader work with the Bluetooth data transmitted to the phone from this transmitter?

Lennart Goedhart

@pazaan

There’s no way that I currently know of to get Guardian Connect data to Nightscout

And 600-series uploader doesn’t work with BLE direct to the Guardian

idowolf

@idowolf

Just found this tutorial, it's not operational anymore? http://nightscout.pl/medtronic/guardian-connect/

Also is 600 series uploader not supporting that because the data on the bluetooth transmission is encrypted or something?

Lennart Goedhart

@pazaan

Oh cool. So that’s getting data from CareLink Cloud

Not form the Uploader, so definitely give that a try. I’ve not tried it myself, but it’s worth giving it a go :)

And yes, BLE is encrypted. Also, I don’t have a Guardian Connect to test with ;)

So I never added support for GC to 600-series Uploader

idowolf

@idowolf

I'm considering getting the GC and try to help with development for that, but hopefully I can verify with someone that I can send data from CareLink Cloud as a failsafe first :sweat_smile:

Lennart Goedhart

@pazaan

Hopefully someone else on this channel has some experience then, because I haven’t come across it myself.

Thomas katzner

@Archchancellor66

Hello everybody,

Somehow the reading of the ConturNext Link 2.4 and the Minimed640G doesn't work yet:-(
I read the links from Mike:

https://github.com/pazaan/600SeriesAndroidUploader/wiki
http://www.nightscout.info/wiki/welcome/nightscout-and-medtronic-640g
https://androidaps.readthedocs.io/en/latest/CROWDIN/de/Configuration/BG-Source.html?highlight=640g#fur-minimed-640g-630g-nutzer

Then I installed these APK files:
xDrip-plus-20190518-14a03a7.apk
nightwatch204_2.apk
600-series-ns-uploader.apk

and opened a nightscout instance on "https://ns.10be.de/".

The measuring instrument is read out. In the "600-series-ns- software I have specified the server URL of NightScout (with port) and "Send to xDrip+"!

In xDDrip+ I have under "Cloud-Upload - MongoDB (even if it is not recommended for NightScout) the xDrip+ URL of NightScout is given).

In NightScout I have specified the given URL.

Problem from me:

I either missed something / am not good enough / the error is somewhere else:

In the 600 Series Uploader and xDrip the BZ values are displayed (WHY not the KH values etc - although pretty much all the hooks are set)?

Nothing arrives in NightScout.

I'm getting desperate. Probably the point I overlooked is too obvious? I would be grateful if you could help me!

I hope that was detailed enough?

With kind regards
Thomas aka Archchancellor

Thomas katzner

@Archchancellor66

It is fixed!!

Thomas katzner

@Archchancellor66

Hello again,
the Data are now read out from the pump. What strikes me:
At 600 Seriwes Uploader and NightWatch, only the blood sugar values are displayed.
At xDrip+ the blood glucose values are indicated and the carbohydrates and notes

What do I have to set where so that blood glucose, carbohydrates, insulin and notes are set for all three programs?

In Nightscout I see everything

I would be very happy to receive an answer.

THANKS
THomas

Lennart Goedhart

@pazaan

The 600SeriesUploader only shows CGM in the app. It doesn’t display any other treatments - it just uploads them to Nightscout

Thomas katzner

@Archchancellor66

That is OK. And Nightwatch or xDrip+?

Lennart Goedhart

@pazaan

Don’t know about those apps

I thought xDrip should, though I don’t know if the treatment events get sent to its

er0780

@er0780

Hey guys,

we are using the great 600SeriesUploader and a Pebble HR 2 which shows us the data uploaded by the Uploader. The Pebble watch ist connected the uploading mobile phone by bluetooth.

Unfortunately one of our 2 Pebbles is broken now. I tried to buy a new or used one but these are as expensive as "normal" Android Smartwatches.

Is it possible to connect the uploading mobil phone with a Android smartwatch without using Nightscout or xDrip?

The urchin watchface (whatever it means) is for us more usable as the watchfaces used by xDrip.

Kind regards.

akumpu

@akumpu

Hi
Yesterday I finally managed to get all the needed devices + cables to try out Medtronic uploader.
and to my surprise it started working immediately without any adjustments or fiddling with the parameters.
But then about after 10-15min it suddenly stop to read anything.
It seems that my CNL 2.4 went to sleep/power save mode and vanished from USB bus.
Any workarounds available to fix it?

Thank you advance.
br.ari

Steve Sixty-Four

@steve8x8

@akumpu Error 86, I suppose? This is a known problem with the CNL - not yet fully fixed. The device (apparently) needs to be power-cycled to get out of a state where queries and responses are no longer in sync, but there's a suspicion that an error message (sent by the CNL) gets in the way of normal data exchange. More debugging needs to be done, but there's a python-based non-android approach now available (see github.com/ondrej1024/ddguard) which may be used for this. Another approach would be power-cycling the device while attached to the USB bus - Yepkit provides such a beast if there's no way to control USB power on the host itself.

akumpu

@akumpu

I don't know about the error code, didn't check it yet. I would like to use android version because it can mobile and it is not so clumsy as rasberry version.
I noticed that there exists UsbPower class in the code. So can it handle the issue if the mobile is rooted?

Steve Sixty-Four

@steve8x8

@akumpu I didn't notice this piece of code before, but with the setup I handed over to a friend the error shows up but there's no su request. Yes, the device is rooted, and the first attempt to run "su" should trigger a choice box but I haven't seen any at all. Checking the code, I cannot find any reference to PowerOn() and PowerOff() - and "git log USBPower.java" reveals that the code hasn't been worked on for 3 years. You may ask the developer by opening a ticket...

akumpu

@akumpu

yes you're right about it.. That class is not used anywhere. CNL gave E86, like you suggested. Even if UsbPower class in use, I can't utilize it. Because the used mobile is brand new Honor 7s. And if I want to root it, I need to purchase an unlockcode with 50 euros or something..

Steve Sixty-Four

@steve8x8

There's a suspicion (and with the Python code now available, someone may actually debug this) that the CNL reported "something" (a status message?) in response to a query first, but then wanted to actually deliver - while confronted with a new query. First one would have to find out how this "extra message" looks like, and whether just reading again would provide the expected response. This, I suppose, is easier done in Python than tweaking a Java app. Unfortunately, I don't have access to a CNL (and even if I had, it would be rather useless without the pump - which I'd have to steal from its owner). See pazaan/600SeriesAndroidUploader#261 for a discussion.

akumpu

@akumpu

Yes I agree, python is much more easy to debug .. But unfortunately the issue is not easy to reproduce with python "driver" . I have run several hundred read rounds without problems. But with Java it occurs within ten or fifteen minutes. Perhaps I should move this discussion overthere to "pazaan..."

akumpu

@akumpu

FYI. I wrote similar story to github location

akumpu

@akumpu

FYI. I managed to sort it out, hopefully. This my issue is Huawei related thing. It has a process called "ash" which takes care of power consumption issues etc. It puts Medtronic uploader to hibernation in middle of packet transmission, which then causes E86. Below is a snippet from logcat output where you can see it:
12-10 23:53:39.686 10862 11253 D ContourNextLinkMessage: READ: [22ms/9250ms]
12-10 23:53:39.689 10862 11253 D ContourNextLinkMessage: RESPONSE: MULTIPACKET_SEGMENT_TRANSMISSION (FF01)
12-10 23:53:39.689 10862 11253 D ContourNextLinkMessage: Got a Multipacket Segment: 8 of 192, count: 8 [packetSize=94 94/26]
12-10 23:53:39.711 1422 1743 I ash : ignore front app :info.nightscout.android screen off:146109ms
12-10 23:53:39.711 1422 1743 I ash : info.nightscout.android is front app
12-10 23:53:39.711 1422 1743 I ash : ignore front app :info.nightscout.android screen off:146109ms
12-10 23:53:39.713 1422 1743 I ash : info.nightscout.android { doze duration=6050 UptimeDuration=6050 } transition to: hibernation reason:
12-10 23:53:39.713 1422 1743 I ash : perform hibernation actions: info.nightscout.android
12-10 23:53:39.714 1001 1476 D PMS : checkProximityLockIncallingAcquired: package=com.huawei.powe

So I changed all the power saving options from automatic to manual ones, and now it works much much better.. Still no E86 visible :)

akumpu

@akumpu

Okay.. it didn't work out.. It still does it..

12-11 00:31:13.704 6200 6924 D ContourNextLinkMessage: READ: [1886ms/25000ms]
12-11 00:31:13.705 6059 6059 I ADB_SERVICES: +read_data=37767 local_socket_list_len=5
12-11 00:31:13.710 1504 1737 I ash : ignore front app :info.nightscout.android screen off:94674ms
12-11 00:31:13.710 1504 1737 I ash : info.nightscout.android is front app
12-11 00:31:13.711 1504 1737 I ash : ignore front app :info.nightscout.android screen off:94674ms
12-11 00:31:13.712 1504 1737 I ash : info.nightscout.android { doze duration=6056 UptimeDuration=6056 } transition to: hibernation reason:
12-11 00:31:13.712 1504 1737 I ash : perform hibernation actions: info.nightscout.android
12-11 00:31:13.713 969 2452 D PMS : checkProximityLockIncallingAcquired: package=com.huawei.powergenie flags=1
12-11 00:31:13.714 1504 1737 I ash : treat as im in oversea for never opt : info.nightscout.android

Steve Sixty-Four

@steve8x8

The device I've seen E86 with is a 7 year old Kitkat (yes, Android 4.4) tablet, no power savings at all (and it's connected to the charger all the time). The Huawei thing must be a red herring.

Jothi Kothandapani

@jothi1971

Hi Could anyone please tell be the command and parameters bytes to send a EMOTE BOLUS command via CNL 2.4 to medtronics 630G pump I only found command code as 0x0100. But not aware of payload paramters and format

Lennart Goedhart

@pazaan

It’s not possible to do via the CNL. There’s a firmware block that prevents it from being sent over the air.

cameronrenwick

@cameronrenwick

hey looking at a new phone. It's a sonim xp8 (a rugged phone). I'm wondering if anyone is using one with xdrip aps and NS?

LuminaryXion

@LuminaryXion

hi. I know this is an old app. But we in Japan need it for uploading our G4 dexcom to nightscout. Where can I find the apk download? I can't find it in any of the old usuals. Thank you!

for example- does anyone have experience with this host? is this a safe source?
https://m.apkpure.com/nightscout-uploader/com.nightscout.android

Lennart Goedhart

@pazaan

Can you not get it from the Play Store?

Ah, not there any more.

LuminaryXion

@LuminaryXion

good news. the APK is in the files on this page. :D
https://github.com/nightscout/android-uploader/releases/tag/v0.1.13

Kemal1118

@Kemal1118

Hello everybody,

When sharing the values via the function send to Nightscout, I completely inserted the Nightscout Url and the API key, which I have specified at Herokuapp.
However, I get the following error message:
The upload to Nightscout was not successful (device status) Unauthorized.
I use Medtronic 640g and Enlite Sensor with Contour next
Can you help with this?

Thanks in advance

Jason Curry

@mccgm

Finally giving up on my Edison and switching to Pi Hat. I'm following instructions and everything seems to be going fine, but as the install finishes up, there are several "not found" or 404 errors for dependencies or something.
'code'
Need to get 723 kB/58.2 MB of archives.
After this operation, 161 MB of additional disk space will be used.
Err:1 http://raspbian.raspberrypi.org/raspbian buster/main armhf libcurl3-gnutls armhf 7.64.0-4+deb10u1
404 Not Found [IP: 93.93.128.193 80]
Err:2 http://raspbian.raspberrypi.org/raspbian buster/main armhf libjs-jquery al l 3.3.1~dfsg-3
404 Not Found [IP: 93.93.128.193 80]
Err:3 http://raspbian.raspberrypi.org/raspbian buster/main armhf libjs-underscor e all 1.9.1~dfsg-1
404 Not Found [IP: 93.93.128.193 80]
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/c/curl/lib curl3-gnutls_7.64.0-4+deb10u1_armhf.deb 404 Not Found [IP: 93.93.128.193 80]
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/j/jquery/l ibjs-jquery_3.3.1~dfsg-3_all.deb 404 Not Found [IP: 93.93.128.193 80]
E: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/u/undersco re/libjs-underscore_1.9.1~dfsg-1_all.deb 404 Not Found [IP: 93.93.128.193 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-mis sing?
Couldn't install packages

Lennart Goedhart

@pazaan

Which repo is this for?

Jason Curry

@mccgm

Is there a set of instructions that enables me to go step by step and not use the bootstrap script?

Steve Sixty-Four

@steve8x8

@mccgm I know that the answer will be late for you but others facing something similar may be interested...

404s when doing "apt upgrade" or "apt install" point at an outdated package list - which can be updated using "apt update" (or "apt-get update" if you're more used to the old style). During the life cycle of a Debian or Raspbian distribution, security and other isses get fixed by replacing older package version with newer ones (which come with the same package nanem but an updated file name, of course). The suggestion in the last line indeed is what you should try first ;) Watch out for issues when running the "update" - they may in turn indicate that e.g. the Raspbian version is too old and no longer supported, etc. (although this should not be the case for "buster" you're using).

Where communities thrive

People

Repo info

Activity