-
Notifications
You must be signed in to change notification settings - Fork 72
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
Set up tconnectsync - login issues #80
Comments
Hey @bjornoleh -- I would try first ensuring they can log in to the t:connect website. I've seen some reports of this before and it typically occurs in users who have never used the online application and have only ever logged in via the mobile app. You might need to reset their password in the app (even if its to the same existing password, if tandem allows). If that still doesn't help, have them go to tconnect.tandemdiabetes.com and follow the "create account" instructions, which will use the desktop t:connect uploader application and should definitely set it up. Otherwise if they still can't log in to the website I'd contact tandem. |
I'm having the same issue. I'm trying to set tconnectsync up on a new laptop. It worked on the old one (which is at home so I can't easily compare settings or versions, but I suspect that the version of tconnectsync is not as recent). I can log into both the t:connect website and app just fine, and just confirmed the password. Any other suggestions? |
@clegoues any chance that your password has special characters in it? You might be specifying it as an environment variable or in the .env file improperly. I've added some additional logging to show when tconnectsync falls back on the default credentials (which won't work) |
Hi, we are trying to have another go at this again. Unfortunately the issue seems to be related to the fact that that t:connect is not available in this region (Scandinavia). Support pointed us to Diasend and Glooko as alternative portals available here. I don't suppose tconnectsync is able to interface these portals? |
Hi, I am helping someone with tconnectsync for the first time, and I am facing some issues.
When running
sudo docker run --env-file=.env jwoglom/tconnectsync --check-login
, it seems the .env file is read and it does seem to log into Nightscout, but apart from that it is complaining about credentials. Did I get the wrong credentials from those I am helping, or is there something I am missing? Is there any account activation they would have to do to make this work? I don't have any first hand experience with their t:connect app (iOS). I can get more details later, but this is what I have now.Setup details
--version
): 0.9.3I could not locate tconnectsync-check-output.log, but I don't se any sensitive info in the output, so am posting that here:
The text was updated successfully, but these errors were encountered: