-
-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LibreLinkUp Update 4.7 #99
Comments
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. |
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. |
Yes of course, I forget it every time that happens. |
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. |
Thanks for responding @timoschlueter, if needed I am very much willing to help. |
Hello @timoschlueter, is there any progress? If needed I can also try to help, please let me know |
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. |
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. |
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? |
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
|
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? |
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") |
I updated just now (from Swedish AppStore), and so far no problems. I did not experience any lagging updates to NS earlier either. |
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. :) |
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? |
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. |
Looks like it. :( |
@timoschlueter Thanks for looking into this. This package has made my life a lot easier over recent months. |
I am in US and the lag is still here |
Same here. (US) |
[info]: Found 1 LibreLink Up connection. |
Update worked great, thank you so much for your efforts! My updates are still lagging by 20+ minutes, but that's a LibreLink problem. |
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. |
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 Also, hello from Dallas, TX. Be safe, friends. |
Hello! [info]: no authTicket.expires |
@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! |
Neither previous version of the app, nor the latest (2.4.0) works, unfortunately. |
@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 :) |
@timoschlueter The v2.4.0 docker container using docker-compose fails to start on my system with the following error:
The v2.3.0 container launches correctly. |
@jeremyhipp: which platform are you using? some sort oft raspberry pi maybe? |
@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. |
I'm getting the same on an Ubuntu 20.04 host. |
I am setting up a VPS with Ubuntu 20.04 on AWS Lightsail right now. Maybe I can reproduce the problem there. |
This might be related to this issue: nodejs/node#43064 |
it worked for me after the update node |
@maddox and @jeremyhipp: version 2.4.1 should fix your problems. |
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 |
@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 :) |
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! |
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. :) |
+1000 This app is the only way I've been able to get Loop working reliably without shutting down in the background (iPhone). It's a life saver. In a perfect world, we wouldn't have to have data go from the phone, to Abbot's servers, to Nightscout, and back to the phone just to get a few numbers from the Libre app to the Loop app, but... I'm grateful for any solution that works. |
This is really really great. Thank you so much for your work. Up to now i had no clue, how this works, but since ns10.be.de is still not uploading the data, i gave the local installation a try and it works. My windows pc has to run, so that this can be uploaded, but since i only need this temporary when Abbot decides again to annoy his customers or to make the process of running the follower still more intransparent and cumbersome, this works for me. Thanks again, Timo. This is brilliant 👍 |
This is in no way an advertisement, and it's certainly off topic, but with everyone expressing how important this data is...I thought it might be worth a mention. I built a simple tool that works like this project, that will read from Nightscout and publish it online to Amazon S3 in a way that Nightscout clients can read from it. https://github.com/maddox/nightscout-s3-proxy I did this because I self host Nightscout, and do not have any holes in my firewall for things to access it, I use a VPN instead. Using my project lets you point mobile clients at the endpoint on S3, so they can get the data, without having to access your home network. I use this specifically with Gluco Tracker to get my number on my watch face via a complication. So, I hope this might help someone else! |
Shoutout to Timo for hopping on zoom and fixing this for me. Thank you so much!!!!!! |
Hi, thank you for your great work timoschlueter! |
@moulicka: where did you host the app? On Heroku you can watch the "Logs" of the app from the console. If you have deployed the app via Docker, the patient-ids are logged to the console. Unfortunately, the Patient-ID is not easily visible from within an official webinterface. Thats why we log it to the console if you start the app without a patient-id set. |
aha, that's a simple solution, I'll try it. Thanks a lot for the advice. |
Hi I haven't got any data to my nightscout for about a month. When I look att deployment logs I get these errors which I didn't get before (previous to the update in june): > nightscout-librelink-up@1.9.0 start Anybody that has any idea what I need to do to get the readings from Libre working again? |
@kimsol1 That's due to an update that Abbott deployed about a month ago. Pull the latest of this repo and re-deploy it. The only real change is updating the version number for the LLU API calls. |
Thanks for the reply David! I read the thread before I posted and added LIBRE_LINK_UP_VERSION =4.7.0 to my variables. But stupid me forgot update the repo. And a big thanks to Timo for the work. Much appreciated! Now I just need to find an alternative to Railway... |
@kimsol1 |
hola comunidad, algun librelink up para escritorio o alguna alternativa para que mis registros lleguen directo a mi mac?? muchas gracias. |
hello, please accept my apologies in advance if this is an incredibly silly question, but... this evening I setup nightscout on azure as per the instructions here - https://nightscout.github.io/vendors/azure/new_user/# I have my librelink updating to librelinkup but have absolutely no idea how to use this to link librelinkup to nightscout, can anyone point me in the right direction? From the description here: "this image can be easily added to your existing docker-compose file" i guess that's what I need to do, I've tried google, but i don't understand the results I get back! (sorry!) Thank you in advance! |
hallo ... does anybody have a "howto" to install this on "https://ssh.cloud.google.com" ..... Nightscout is already running |
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?
The text was updated successfully, but these errors were encountered: