-
Notifications
You must be signed in to change notification settings - Fork 71.9k
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
Comments
Fixed in the mmconnect plugin; NS patch coming soon. |
Hi, Best Regards |
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
|
It works, I can see data on the webpage now. I will close this issue when the fix will be available on Dev with only fork action required. Thank you |
I can also confirm the working fix after the |
sorry doesnt work for me even after update (the line 90) :( dont you know what might be an issue? thank you. |
@Veronika0619 Try just updating your NS to 0.12.5; fix is included in that now. |
Unfortunately Im using Release 0.12.5 but still getting the same error "MiniMed Connect error: Error: Bad response from CareLink: {"statusCode":400" :(( |
Have you deployed the new release? |
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 :( |
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. |
all right I´m going to check out again |
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. |
Thanks a lot for your help!! its working .) I just didnt make a new connection in Heroku.. thanks again .) |
Excellent! |
@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 |
Describe the bug
On Friday Nightscout page stopped receiving data but Carelink page works itself.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Page works and data are displayed
Your setup information
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":"?
The text was updated successfully, but these errors were encountered: