Skip to content
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

Guardian Connect, Heroku: Error 400 with Carelink #5032

Closed
norbicz opened this issue Sep 28, 2019 · 16 comments
Closed

Guardian Connect, Heroku: Error 400 with Carelink #5032

norbicz opened this issue Sep 28, 2019 · 16 comments

Comments

@norbicz
Copy link

norbicz commented Sep 28, 2019

Describe the bug
On Friday Nightscout page stopped receiving data but Carelink page works itself.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy Dev branch to Heroku and setup app with provided instructions for Guardian Connect CGM

Expected behavior
Page works and data are displayed

Your setup information

  • Nightscout Dev branch
  • Guardian Connect, Heroku app
  • All browsers and devices

Additional context

Error is like this:

2019-09-28T14:44:53.340236+00:00 app[web.1]: MiniMed Connect error: Error: Bad response from CareLink: {"statusCode":400,"body":"","headers":{"cache-control":"No-Cache","pragma":"No-Cache"","server":"BigIP","connection":"Keep-Alive","content-length":"246"},"request":{"uri":{"protocol":"https:","slashes":true,"auth":null,"host":"carelink.minimed.eu","port":null,"hostname":"carelink.minimed.eu","hash":null,"search":"?

@unsoluble
Copy link
Contributor

Fixed in the mmconnect plugin; NS patch coming soon.

@norbicz
Copy link
Author

norbicz commented Sep 29, 2019

Hi,
Thank you for fast reaction :)
Could you let me know when I can update webpage?

Best Regards

@unsoluble
Copy link
Contributor

This should be fixed now with a redeploy of your existing codebase. If it isn't fixed by that, you can PR your own fork with a change to line 90 in package.json — set it to:

"minimed-connect-to-nightscout": "https://github.com/szymjaw/minimed-connect-to-nightscout.git#dev-v.1.3.2",

@norbicz
Copy link
Author

norbicz commented Sep 30, 2019

It works, I can see data on the webpage now.
I have edited package.json in my fork because Dev branch still has old package.json.

I will close this issue when the fix will be available on Dev with only fork action required.

Thank you

@pleinolijf
Copy link

I can also confirm the working fix after the package.json edit. Many thanks @unsoluble !

@Veronika0619
Copy link

sorry doesnt work for me even after update (the line 90) :( dont you know what might be an issue? thank you.

@unsoluble
Copy link
Contributor

@Veronika0619 Try just updating your NS to 0.12.5; fix is included in that now.

@Veronika0619
Copy link

Unfortunately Im using Release 0.12.5 but still getting the same error "MiniMed Connect error: Error: Bad response from CareLink: {"statusCode":400" :((

@unsoluble
Copy link
Contributor

Have you deployed the new release?

@Veronika0619
Copy link

well I´m not sure wheter I´m doing everything all right, but I just deleted cgm-remote-monitor repository and than forked it with the newest version..e.g. when I select http://nightscout.github.io/pages/update-fork/ there is a message no update abailable :(

@unsoluble
Copy link
Contributor

Well that's a pretty nuclear option, but okay. :)

Still need to be clear whether or not you've actually deployed that fresh code to a Heroku app.

@Veronika0619
Copy link

all right I´m going to check out again

@unsoluble
Copy link
Contributor

If you actually deleted your fork and then created a new one, you'll need to make a new connection to the new fork in your Deploy section in Heroku.

If you end up deploying a brand new app, you'll need to make sure to delete the previous app, so that you don't accidentally blow through your free dyno hours each month.

@Veronika0619
Copy link

Thanks a lot for your help!! its working .) I just didnt make a new connection in Heroku.. thanks again .)

@unsoluble
Copy link
Contributor

Excellent!

@PieterGit
Copy link
Contributor

@norbicz @Veronika0619 Closing this issue. It appears you solved your deployment issue. This issue is resolved in Nightscout 0.12.5 release with PR #5060 (upgrade from minimed-connect-to-nightscout to ^1.3.2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants