LibreLinkUp Update 4.7

[Jonaskjellsson]

Hi LibreLinkUp will be updated to version LibreLinkUp 4.7.

All older versions will stop working on 6/21 Will Nightscout LibreLink Up work after 6/22?

[prospo]

I share the same worry as @Jonaskjellsson, based on the email we got it seems that the API will change and that after June 21st we might be blocked.

[pettermork]

Seems mine broke last night, I get a No AuthTicket recieved error.

[prospo]

Seems mine broke last night, I get a No AuthTicket recieved error.

I think you need to accept the new agreement, go to your phone, logout of LibreLinkUp and log back in. You should get the new agreement, then accept it. Afterwards, getting a token should work again.

[pettermork]

Yes of course, I forget it every time that happens.

[timoschlueter]

Hi everyone! Since I don't have access to the update in advance or any other documentation we might run into a the situation that this app needs to be updated when the new LLU version is released.

I will do my best to keep the downtime as short as possible. Unfortunately we need to actually look at the updated API in order to see how much we need to change.

Nevertheless I am confident that we will be able to keep using this app. Just prepare for a day or two without data.

[prospo]

Thanks for responding @timoschlueter, if needed I am very much willing to help.

[yaronkhazai]

Hello @timoschlueter, is there any progress? If needed I can also try to help, please let me know

[alinadrian2391]

I am getting the glucose data with ~20 min delay on LinkUpApp, anybody else?

[PhilaBurger]

I am getting the glucose data with ~20 min delay on LinkUpApp, anybody else?

I'm seeing the same behavior, in the LLU app 4.6. The Apple App Store hasn't made 4.7 available to me, yet, so I can't tell whether or not it will fix this behavior.

[PhilaBurger]

Did anyone else get errors, after unpacking the LLU uploader 2.3.0, about not finding the @tsconfig/node18/tsconfig.json?

I dug and found that the entire node_modules subdirectory appeared to be missing after unpacking v2.3.0.tar.gz.

I copied the entire node_modules subdir from the v.2.2.0 installation path and now it runs, but as others have noted, I'm receiving the No AuthTicket received error.

I know that timoschleuter is already looking to fix the auth issue...my only reason for this message is to ask him to look at the tar.gz package and correct the missing node_modules issue.

Thanks.

[timoschlueter]

I have not received the updated version yet. Unfortunately I won't be able to fix things without the update on my phone. Does anyone have the new version installed already? If so: Which region are you from and do you use an Android or iOS device?

[david-lively]

I'm also seeing ~20-30 minute delays (US, iPhone). The LibreLinkUp app on my phone also isn't working, just says "An error occurred please try again later." Yay, Abbot. NSLU is saying "LibreLink Up - No AuthTicket received. Please check your credentials." But, the actual error page that's returned is saying

What happened?\n

The web server reported a gateway time-out error.

\n

[timoschlueter]

Seems like 4.7.0 has just been released to the App Store. I downloaded the app a few minutes ago and so far nightscout-librelink-up seems to still be working just fine.

Can somebody else confirm this?

[david-lively]

I had to uninstall the app and re-install it - it didn't just show up as an available update. It's now showing 4.7.0. NLU appears to be working, but the readings are still lagging ~20-30 minutes on Nightscout (as they are in the LibreLinkUp app, so that's not an issue with NLU.)

(Where "NLU" means "Nightscout-Librelink-up")

[pettermork]

I updated just now (from Swedish AppStore), and so far no problems. I did not experience any lagging updates to NS earlier either.

[timoschlueter]

I just finished analysing the traffic between LLU version 4.7.0 and Abbotts infrastructure. The APIs seem to still be compatible with nightscout-librelink-up. Only minor changes have been added in version 2.4.0 just to be safe. You can see the details in PR #101.

Version 2.4.0 should be available to download on GitHub and Docker Hub within the next hour. :)

[timoschlueter]

I have not yet experienced any lags on the update (neither on 4.7.0, nor the previous version). I am using the DE region since i am located in germany. Can we find a common region that is having issues?

[david-lively]

The nature of the errors coming from their API and from the LibreLinkUp app have changed throughout the day. I suspect they're still rolling out and, in true IT professional fashion, doing it badly. Given that their own app isn't working with their servers in the US at the moment, I doubt there's anything that can be done on this end.

[timoschlueter]

Looks like it. :( Lets hope they get things in order soon.

[david-lively]

@timoschlueter Thanks for looking into this. This package has made my life a lot easier over recent months.

[alinadrian2391]

I have not yet experienced any lags on the update (neither on 4.7.0, nor the previous version). I am using the DE region since i am located in germany. Can we find a common region that is having issues?

I am in US and the lag is still here

[david-lively]

Same here. (US)

[alinadrian2391]

[info]: Found 1 LibreLink Up connection. [info]: -> The following connection will be used: Alin ... (Patient-ID: 40d3f021-6354-...) /usr/src/app/src/index.ts:297 const measurementDate = getUtcDateFromString(glucoseMeasurement.FactoryTimestamp); ^ TypeError: Cannot read properties of null (reading 'FactoryTimestamp') at createFormattedMeasurements (/usr/src/app/src/index.ts:297:69) at uploadToNightScout (/usr/src/app/src/index.ts:332:50) at main (/usr/src/app/src/index.ts:154:11) at processTicksAndRejections (node:internal/process/task_queues:95:5)

[stncttr908]

Update worked great, thank you so much for your efforts! My updates are still lagging by 20+ minutes, but that's a LibreLink problem.

[rmcferran]

Currently seeing the same error as reported above by alinadrian2391. Could it be related to the delayed reporting we're seeing from the LLU app? I'm definitely seeing the same sort of 20-30 min delay others are reporting, as well.

[david-lively]

As of 10:55 CST, LibreLinkUp is working again, as is Nightscout-LibreLink-Up, NightScout and, thus, Loop. I'm in DFW (US), so not sure if it'll take longer for the changes to roll out to other US zones. Also, make sure you're using the latest main that @timoschlueter pushed earlier today to update to the 4.7.0 API version header.

Also, hello from Dallas, TX. Be safe, friends.

[Ederborg]

Hello! Im getting this error after the update in Sweden. Am I doing anything wrong?

[info]: no authTicket.expires [info]: renew token [info]: Logged in to LibreLink Up

error: getting libreLinkUpConnection: Cannot read properties of undefined (reading 'data')

[timoschlueter]

@Ederborg I released version 2.4.0 yesterday. This version should fix your problem. Although I don't receive any data here in Germany right now. But that might still be a problem with Abbotts infrastructure.

Just try the new version 2.4.0 and your error should be gone :)

[Ederborg]

@Ederborg I released version 2.4.0 yesterday. This version should fix your problem. Although I don't receive any data here in Germany right now. But that might still be a problem with Abbotts infrastructure.

Just try the new version 2.4.0 and your error should be gone :)

Thank you! It has been working fine for so long I haven't done anything to it :) Including updating anything!

[prospo]

@Ederborg I released version 2.4.0 yesterday. This version should fix your problem. Although I don't receive any data here in Germany right now. But that might still be a problem with Abbotts infrastructure.

Just try the new version 2.4.0 and your error should be gone :)

I am in Germany as well, 2.4.0 works for me and I am receiving data again. I had to update due to receiving {"minimumVersion":"4.7.0"} after my LibreLinkUp app on my phone was updated.

Thanks for your time and effort!

[timoschlueter]

For me there is no data at all since last night. I have no idea what happened but even the LLU app does not show anything anymore. I guess I have to wait till Abbott has things sorted out.

But I am very glad to hear the my update yesterday works for you all! :)

[yaronkhazai]

Hi

following the thread here i just changed this line const LIBRE_LINK_UP_VERSION = "4.7.0"; and everything is working perfectly i am using the DE endpoint

thanks

[Havanna22]

2.4.0 doesn't work for me, unfortunately. Still no data. Will there be a build with that const corrected for english version? I am not used to making my own builds, not possible for me to learn right now.

[timoschlueter]

@yaronkhazai thats what I changed with v2.4.0. Maybe you can just update to the latest version. It should work as well :)

[timoschlueter]

@Havanna22 you can always go back to a previous release of this app. All versions are available for download on here under the "Releases" tab as well as the global Docker Hub container registry. I won't delete older version exactly for those backwards compatibility reasons.

[buzlachok]

Thank you. Updated applications and agreement. Code too. But at startup it says: Unexpected token ?

npx ts-node --transpile-only src/index.ts Unexpected token ? npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! nightscout-librelink-up@2.4.0 start: npx ts-node --transpile-only src/index.ts npm ERR! exit status 1

What does this mean?

[Havanna22]

Neither previous version of the app, nor the latest (2.4.0) works, unfortunately. So there's something more wrong. Or to be clear: I have tried the latest available version of XDrip+ and it doesn't give values. I can't see which version it is, if it's 2.4.0, but it is a build from 15th of June. But you are talking about Nightscout versions perhaps? Sorry if I am confusing things...

[timoschlueter]

@Havanna22 when was the last time it worked for you? Maybe we can find out.

As of 10 minutes ago I am receiving values in LLU again and in nightscout-librelink-up as well :)

[jeremyhipp]

@timoschlueter The v2.4.0 docker container using docker-compose fails to start on my system with the following error:

Starting nightscout-libre-link
Attaching to nightscout-libre-link
nightscout-libre-link    | node[1]: ../src/node_platform.cc:68:std::unique_ptr<long unsigned int> node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start(): Assertion `(0) == (uv_thread_create(t.get(), start_thread, this))' failed.
nightscout-libre-link    |  1: 0xb7a940 node::Abort() [node]
nightscout-libre-link    |  2: 0xb7a9be  [node]
nightscout-libre-link    |  3: 0xbe98be  [node]
nightscout-libre-link    |  4: 0xbe99a1 node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
nightscout-libre-link    |  5: 0xb38f5b node::InitializeOncePerProcess(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, node::ProcessFlags::Flags) [node]
nightscout-libre-link    |  6: 0xb395ab node::Start(int, char**) [node]
nightscout-libre-link    |  7: 0x7f2e0bcb418a  [/lib/x86_64-linux-gnu/libc.so.6]
nightscout-libre-link    |  8: 0x7f2e0bcb4245 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
nightscout-libre-link    |  9: 0xabbdee _start [node]
nightscout-libre-link exited with code 139

The v2.3.0 container launches correctly.

[timoschlueter]

@jeremyhipp: which platform are you using? some sort oft raspberry pi maybe?

[jeremyhipp]

@timoschlueter I'm running on a VPS with Ubuntu 16.04, 4 cores (<10% load), 8GB RAM (~5.5 GB free). It could very well be the old Ubuntu version, I was just surprised it stopped since v2.3.0 ran fine.

[maddox]

The v2.4.0 docker container using docker-compose fails to start on my system with the following error

I'm getting the same on an Ubuntu 20.04 host.

[timoschlueter]

I am setting up a VPS with Ubuntu 20.04 on AWS Lightsail right now. Maybe I can reproduce the problem there.

[timoschlueter]

This might be related to this issue: https://github.com/nodejs/node/issues/43064 I will look into it.

[buzlachok]

it worked for me after the update node

[timoschlueter]

@maddox and @jeremyhipp: version 2.4.1 should fix your problems. The new version will be available in about 30 minutes on Docker Hub.

[cabbage2400]

Hello, my nightscout hasn't been receiving values from LLU for 19 hours, and after reading these comments I am unsure what exactly to do to get this up and running again. My LLU account is working normally now. I am not familiar enough with this website/functionality to follow how to make whatever updates are recommended to resolve this issue. If anybody is able to provide me with some specific instructions or would be willing to hop on a quick zoom call and walk me through, I would so greatly appreciate it! I use nightscout to feed my loop app so am struggling big time without being able to get my CGM readings into nightscout. Thanks in advance for anybody willing to engage with me on this

[timoschlueter]

@maddox / @jeremyhipp: the update is available. can you verify that it works for you?

@cabbage2400: I set up a zoom meeting you should be able to join. I will be here for about an hour :) https://us05web.zoom.us/j/89858968770?pwd=Z3pyNFFhQkp0MjBKQUh0U0RYelRFUT09

[maddox]

Looks good now! Thanks so much. Incredible support for something you're doing in your off time. We all really appreciate it. It's amazing how important this project has become for me so I can get my numbers on my watch face, which has become a big deal for me.

Thanks!

[timoschlueter]

Thank you so much @maddox, I really appreciate the kind words and the sponsorship! I will do my best to keep this app going since it made life so much easier for myself as well. :)