Closed mboterma670G closed 4 years ago
Try this guide: https://wolke.rueth.info/index.php/s/NjjgCF9rdbiWNbX#pdfviewer
Hi, issue is not connecting Heroku to Atlas, that part is working fine. I can see that the app is populated with data from Atlas. Also tested the API response from the Atlas instance through SOAPUI. Also that part is working. However for some reason the uploader can't connect to Heroku to upload data. I followed the instructions from Mongo. [https://docs.mlab.com/how-to-migrate-sandbox-heroku-addons-to-atlas/]
The Uploader uses the Nightscout API, which is not dependent on whatever version/provider of MongoDB you have backing Nightscout. Are you able to view your data on Nightscout since the transition, and use the API Secret to manually log treatments to Nightscout? If you can, then we'd need more specific instructions on how to reproduce (I personally am running Nightscout on my own VPS connected to Atlas).
There are reports on the FB page of successful transition for 600 Series uploader users.
Another guide that may help: https://docs.google.com/document/d/1gV7dFeipTI3Fas246N10iAxQC8gETV5PIVfL31AYu_c/edit#heading=h.2xm1e0u2gzdc
Hi Pazaan, i will verify and update you. Need to reconnect the site back to Atlas. Also trying to get Nightscout up and running on VPS, but get stucked on the MONGODB_CONNECTION part. Even thought it is the env, it is being read, but still errosrs
Hi Pogman, seems this one is more specific then the version from Atlas.
Thanks for your fast reply
Update,
Set the MongoDB connection string again and all works like a charm. No clue why it is working now as I made a copy of the connection string yesterday and it failed. Did the same again today and now it's working. Also the site is being updated by the uploader. Great progress!!!!
Next project, get Nightscout running on Ubuntu 18.04 + plesk.
Thanks to both
Not sure why it happened. entering the URL again solved the issue.
HI! I know the issue is closed, but now I have exactly the same problem after migrating to Atlas. My cell phone uploader cannot send any data the the DB. I can though upload svg values manually (and see them on the my NS site) using the script by: https://github.com/cjo20/ns-api-uploader
I am not sure what really happened with the uploader. Any help is certainly appreciated. Thanks!
The migration to Atlas is transparent to the uploader as the NS server handles the database.
Can you post a screenshot of the uploader log screen?
Thanks Pogman for the quick reply.
I tried yesterday to upload the image, but I do not know why I was not able. Here it is:
I am really puzzled, as the uploader seems to not have any problems.
Thanks for the help!
Best,
Daniel
On 03 Sep 2020, at 22:12, Pogman notifications@github.com wrote:
The migration to Atlas is transparent to the uploader as the NS server handles the database.
Can you post a screenshot of the uploader log screen?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pazaan/600SeriesAndroidUploader/issues/278#issuecomment-686767223, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEO7HPV5K5KQNGUHYVFVX63SEABEFANCNFSM4O4UOW5A.
As MongoDB pulls the plug on the mlab plugin (10-Nov), I've migrated the code to cloud.mongodb.com (atlas). However it seems that the loader doesn't work anymore. Generating the message; Uploading to nightscout was unsuccessful. (device status) Internal Server Error.
Your Environment
Brief Explanation of Issue
occured when moving from heroku mlab plugin to cloud.mongodb.com. as per instruction on "https://docs.mlab.com/how-to-migrate-sandbox-heroku-addons-to-atlas/"
Uploader Error Code
Uploading to nightscout was unsuccessful. (device status) Internal Server Error.
Steps to Reproduce (for bugs)
Severity Score
5 -> Use nightscout to monitor BG while driving my car (mirrored to iWatch), as you get fines driving a car when holding the medtronic 670G in your hands, to check your BG's. And driving without a clear understanding of your BG's is not smart.