-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Cant sign-in #38
Comments
Fix van @sedy89 hierboven lost het login probleem alhier op. |
New version with a fix is released. |
I would like to notice you that you hard coded last time new host "mdtlogin-ocl.medtronic.com" , after last Carelink maintenance, but it's true only for EU server. US server host is still "mdtlogin.medtronic.com" so it's better to change the code for more flexible. Probably you can use : |
Yes, you are right. I just saw it on the xdrip PRs. Thanks for the hint! |
2023_6 version for me is working again.. :-) |
After updating through HACS today I'm now getting: 2023-06-29 12:00:27.474 ERROR (MainThread) [custom_components.carelink] Unexpected error fetching carelink data: 'auth_tmp_token' File "/usr/local/lib/python3.11/site-packages/httpx/_models.py", line 1148, in getitem I noticed line 185 in api.py is using version 2023.6.6 |
I wasn't sure how exactly it should read so I just removed the "-ocl" and it works again. |
Login url fix release ready with version 2023.6.7 |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
I was having issues with my account and had to reset my password in CareLink itself. This was done succesfully and now can sign-in through the Browser, but after deleting, upgrading CareLink with HACS i'm not able to setup the CareLink integration anymore. I have enabled Debug logging and see the following:
This might have to do with the switch of the Auth server as suggested in the latest release (3 hours ago)?
Home Assistant 2023.6.3
CareLink: 2023.6.5
The text was updated successfully, but these errors were encountered: