8000 Login Issue · Issue #18 · gagebenne/pydexcom · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Login Issue #18

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 s 8000 ervice and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
eracknaphobia opened this issue Dec 13, 2021 · 13 comments
Closed

Login Issue #18

eracknaphobia opened this issue Dec 13, 2021 · 13 comments

Comments

@eracknaphobia
Copy link
eracknaphobia commented Dec 13, 2021

I'm trying to debug a login issue I'm experiencing.

It seems that my account passes the DEXCOM_AUTHENTICATE_ENDPOINT which tells me my username and pwd are correct

image

However, I receive the DEFAULT_SESSION_ID for the DEXCOM_LOGIN_ENDPOINT.
image

Any Ideas? Seems like dexcom may have recently made some changes on their end. Should I just wait for the dust to settle and try later?

@eracknaphobia
Copy link
Author

Here's the actual error message I get when running it in python

Session ID default
Traceback (most recent call last):
  File "C:\Users\redacted\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\pydexcom\__init__.py", line 163, in create_session
    self._validate_session_id()
  File "C:\Users\redacted\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\pydexcom\__init__.py", line 125, in _validate_session_id
    raise SessionError(SESSION_ERROR_SESSION_ID_DEFAULT)
pydexcom.errors.SessionError: Session ID default

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\redacted\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\pydexcom\__init__.py", line 66, in __init__
    self.create_session()
  File "C:\Users\redacted\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\pydexcom\__init__.py", line 165, in create_session
    raise AccountError(ACCOUNT_ERROR_UNKNOWN)
pydexcom.errors.AccountError: Account error

@gagebenne
Copy link
Owner

Are you a US user, or outside of the US?

@eracknaphobia
Copy link
Author

US user

@gagebenne
Copy link
Owner

Yeah, this issue closely aligns with #17. One last question -- are you using an email address for your username? I am able to replicate your exact error, but only when I send an incorrect password. Could you ensure your password is alphanumeric?

Either way, this should fail more gracefully than it is with the endpoint changes. Thank you.

@eracknaphobia
Copy link
Author
eracknaphobia commented Dec 13, 2021

I'm using email address for the username and the password is alphanumeric.

I do get the DEFAULT_SESSION_ID if i purposely send the incorrect password in the DEXCOM_AUTHENTICATE_ENDPOINT, but with the DEXCOM_LOGIN_ENDPOINT I get it no matter what.

Thanks for the quick response!

EDIT: Sorry, I had my calls switched around. I always fail the Login endpoint, but I do get a unique session id for the authenticate endpoint. I've updated my comments.

@gagebenne
Copy link
Owner
gagebenne commented Dec 13, 2021

When you go to your Dexcom G6 application, what do you see under Settings > Account > Username? Is it an email?

Lot's of changes in the endpoints in the past few days, sorry to pester you for information... Just trying to learn all I can about how exactly the endpoint responses have changed for different users with different situations.

@eracknaphobia
Copy link
Author

No problem at all. In the app the username is the email address.

@gagebenne
Copy link
Owner

Fixed. Please use pydexcom==0.2.2! Let me know if you have any more issues!

@eracknaphobia
Copy link
Author

image

Still getting the all 0's UID with the new call.

@gagebenne
Copy link
Owner
gagebenne commented Dec 17, 2021 via email

@eracknaphobia
Copy link
Author

image
I manually updated the files and it worked! Thanks for fixing this so quickly @gagebenne!

As far as Home Assistant is concerned will these changes be pulled in automatically or will we need to wait for a version bump?

@gagebenne
Copy link
Owner
gagebenne commented Dec 17, 2021

Nice! Glad to hear. I think it'll have to wait for a version bump unfortunately, here's the pull request. You could probably just go in and edit the same files in the pull request in your own setup, and it should work.

@eracknaphobia
Copy link
Author

Ok, sounds good. Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0