mddub / minimed-connect-to-nightscout Goto Github PK

How complicated is it to get this information out of carelink into nightscout?
I've had a brief look at the code and as far as I can see it looks like a different url is needed to query for the information - after that it shouldn't be too complicated to get it packaged up should it?

hello, i'm install your minimed-connect-to-nightscout on my raspberry ubuntu os.
this app run but my request return no result ..

where i found debug log

Tue Feb 18 2020 10:35:49 GMT+0000 (Coordinated Universal Time) Logging in to CareLink
Tue Feb 18 2020 10:35:49 GMT+0000 (Coordinated Universal Time) POST https://carelink.minimed.eu/patient/j_security_check
Tue Feb 18 2020 10:35:50 GMT+0000 (Coordinated Universal Time) GET https://carelink.minimed.eu/patient/main/login.do
Tue Feb 18 2020 10:35:50 GMT+0000 (Coordinated Universal Time) GET https://carelink.minimed.eu/patient/connect/ConnectViewerServlet?cpSerialNumber=NONE&msgType=last24hours&requestTime=1582022150780
Tue Feb 18 2020 10:35:51 GMT+0000 (Coordinated Universal Time) Stale CareLink data: 26367035.85 minutes old
Tue Feb 18 2020 10:35:51 GMT+0000 (Coordinated Universal Time) No new items for https://XXXX.herokuapp.com/api/v1/entries.json
Tue Feb 18 2020 10:35:51 GMT+0000 (Coordinated Universal Time) No new items for https://XXXX.herokuapp.com/api/v1/devicestatus.json

I can't get this to work with node.js. Where do i need to set the username/password? i supposed in the run.js files var config section by replacing CARELINK_USERNAME, that doesn't seem to work because i always get this error:

Error: Missing CareLink username at Object.<anonymous> (/xxx/xxx/minimed-connect-to-nightscout/run.js:32:9) at Module._compile (module.js:409:26) at Object.Module._extensions..js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Function.Module.runMain (module.js:441:10) at startup (node.js:140:18) at node.js:1043:3

@mddub Can you update your dependencies and publish this package?

Updating the dependencies will remove the warning:
[email protected]: Use uuid module instead like reported here:
nightscout/cgm-remote-monitor#3535

Publishing this package makes it possible to install Nightscout without git, and also makes Nightscout a bit more secure, because packages uses checksums and a dependency like "git://github.com/mddub/minimed-connect-to-nightscout.git#v1.1.0", does not use a checksum. Therefore it's vulnerable if people somehow are able to hack your github.

The european Version of Minimed Connect is released now.

The device is called Guardian Conenct and there is a Minimed Connect tab in Carelink. It works similar to the US Minimed Conenct but it does not work with nightscout because the URLs are different i suppose.

Would be great if there is a way to get it working with carelink.minimed.eu

Can you please fix this. I try to integrate minimed-connect-to-nightscout into Nightscout and get:

$ npm audit
npm WARN audit Both npm-shrinkwrap.json and package-lock.json exist, using npm-shrinkwrap.json.
=== npm audit security report ===

# Run  npm update lodash --depth 2  to resolve 1 vulnerability

  High            Prototype Pollution

  Package         lodash

  Dependency of   minimed-connect-to-nightscout

  Path            minimed-connect-to-nightscout > lodash

  More info       https://nodesecurity.io/advisories/1065

Can you upgrade lodash and confirm it works with minimed-connect-to-nightscout and then release a 1.3.1?

Nightscout users who are using mmconnect in NS are now reporting the site crashes every couple days due to running out of memory. The issues seems to be isolated to this module; help checking where the leak is would be great.

Hi!

There was a major upgrade in EU CareLink services (28.06.2020) and since then MMConnect module is not working anymore in EU.

Login changed
https://carelink.minimed.eu/patient/j_security_check?j_username=&j_password= throws HTTP 400
EU CareLink seems to using now the following service for logins:
https://mdtlogin.medtronic.com/mmcl/auth/oauth/v2/authorize/login

Dataservice changed
https://carelink.minimed.eu/patient/connect/ConnectViewerServlet?cpSerialNumber=NONE&msgType=last24hours&requestTime= throws HTTP 404
EU CareLink connect webapplication seems to be using the following service to fetch SGV values:
https://carelink.minimed.eu/patient/connect/data?cpSerialNumber=NONE&msgType=last24hours&requestTime=

The returned SGV data seems to be the very same JSON as earlier
lastSensorTSAsString
bgunits
lastSensorTS
...
lastSGTrend
lastSG{}
lastAlarm{}
activeInsulin{}
sgs[]
limits[]
markers[]

Could you please change the MMConnect module to support the new EU CareLink Connect services?

Thank you!

Since about 9:15 PST on 5/9/2016, I am getting the following error within Nightscout when the MMCONNECT_VERBOSE=true environment variable is enabled. Before this everything was working as expected for the last 2 weeks.:

Mon May 09 2016 22:33:31 GMT-0700 (PDT) Logging in to CareLink
Mon May 09 2016 22:33:31 GMT-0700 (PDT) POST https://carelink.minimed.com/patient/j_security_check
MiniMed Connect error: Error: unable to verify the first certificate

I am not certain what is wrong, and this may be a red herring but in the authentication POST in carelink.js it doesn't look like the j_character_encoding key=UTF-8 is being sent. When attempting to mimick the login using POSTMAN, I was unable to authenticate without this value in the payload.

is it possible to use this uploader for nightscout with the european portal?
i noticed the URL of Carelink website is hardcoded and cannot be set to https://carelink.minimed.eu.

I replaced the URL in carelink.js to carelink.minimed.eu, but I get errors in Nightscout.
timestamp1 Logging in to Carleink
timestamp2 POST https://carelink.minimed.eu/patient/j_security_check
...
MiniMed Connect error: Error: read ECONNRESET

Can I help you to make this uploader also work for European Carelink users?