jwoglom / tconnectsync

Syncs insulin pump data from Tandem t:connect to Nightscout for the t:slim X2

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Unable to Setup

MrJordanRoth opened this issue · comments

Describe the problem
I'm following the directions to use a Docker install but when I run docker -run --env-file=.env tconnectsync --check-login I'm getting various issues. The t:connect API errors are related to HTTP 200 which says to check my username and password which I have done in the app and the website tconnect.tandemdiabetes.com. I do not see where the log file is actually written to the system as I cannot find tconnect-check-output.log anywhere to really troubleshoot this further. I've also noticed when looking at the output the NS_URL is only sending https:/url-to-nightscout and not https:// so I'm not sure if there is a code issue somewhere.

To Reproduce
Steps to reproduce the behavior:

  1. Run the command docker -run --env-file=.env tconnectsync --check-login

Expected behavior
Expected to work or provide a more detailed error log file.

Setup details

  • Operating system: Ubuntu 22
  • tconnectsync version (from --version): 0.9.3
  • On what platform are you using the t:connect mobile app? (Android or iOS) Andriod
  • What version are you using of the t:connect mobile app? 2.3

Terminal output
If applicable, add the full output from your terminal from running tconnectsync. Copy the output into a text editor like Textedit or Notepad first and find-and-replace sensitive strings, like your Nightscout URL and pump serial number, if they appear.

Check Login output
If applicable, please run --check-login and upload the tconnectsync-check-output.log file as an attachment on the issue. This file should have sensitive details like your Nightscout URL and pump serial number automatically removed, but double-check before uploading.

Unable to find the file.

This log will contain pump and CGM related information such as delivery events and blood sugars. If you would prefer to keep the contents private, send an email to tconnectsyncwogloms.net with the log output so @jwoglom can investigate.

Additional context
Add any other context about the problem here.

Discard, I found it in the README.

I've added some improved logging around login failures. Confusingly, tconnect returns a HTTP 200 status code when your password is incorrect, so showing the status code in the error message is a bit confusing. Hope you were able to get it working!