-
Notifications
You must be signed in to change notification settings - Fork 10
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
Issue identified : Something really wrong happened! #39
Comments
I started having the same issue an hour ago, something seems to have changed on the libreview side of things as their API is returning an HTTP/430 status, which is not officially defined. For me, this started happening at 11:04 today (CET). |
Yes, very same time |
I can confirm this happened to me as well at 11:04 CET today. |
I found another issue regarding the same status code from a couple of months ago: #31 In that it was suggested that it could be related to having to accept the terms of service on the libreview site/librelinkup app. Edit: Did not fix the issue. |
I tried already, signing in and out the LibreLinkUp on my mobile. Accepted the terms, reloaded the add-on, no changes |
Same problem. In these days the app LibrelinkUp warned to update compulsorily, otherwise it would stop working. They probably changed something in the API or simply the server for italy area |
Libreview, librelinkup and freestyle libre all seem to work as intended, so it seems to be the Libreview API that is causing these issues. I tried using different regions/api servers but all give the same result. |
Same here, same timestamp: This error originated from a custom integration. Logger: custom_components.librelink Error fetching librelink data: Something really wrong happened! |
They are now requiring a minimal version
id as a 64-char hexadecimal string along the JWT token.
Look at my Swift one-liners I PRed with JohanDegraeve/xdripswift@13e4a1e ;-) |
_> They are now requiring a minimal version
Thanks for the update. I managed to change 4.7 into 4.12.0 in that config file. Thanks. |
Have the issue as well… latest reported glucose measurement sensor value at at 11:03 CET |
Same issue here @gillesvs are you planing to fix issue ? |
Also the same issue, Czech region. However the region seems to be not important in this case. Please, prepare uodate to fix it. |
Same issue here in Denmark. |
Spain is not different |
Belgium has the same problem since 11:04 CET |
based on #39 (comment) but unfortunately i have no idea what to do with this sha256 function ;( |
@gui-dos "Account-Id": SOMETHING // and that SOMETHING has to be in sha256() |
The librelink/custom_components/librelink/api.py Lines 99 to 110 in 0b12fa9
If you follow yourself you can reuse the librelink/custom_components/librelink/api.py Line 168 in 0b12fa9
I just noticed tonight's Python implementation by robberwick/pylibrelinkup@06bce45 which makes use of
|
To ALL |
Also got the sam issue. Happy to see there might be a solution soon to this issues. First i was like ... there is alot of changes. Then I looked closer ... You changed alot, but I just read the comment from the author on you commit. Is is possible you can make a PR to just fix this issue so the packages can be updated via HACS? |
@syska its not my fork ;-)
Im afriad no, So the easiest way to fix issue is to remove this repo form HACS and add this one: |
It appears this new repo (https://github.com/kubasaw/librelink) was added to HACS a couple of hours ago, its using the same name and icon. There are some changes as to which entities it presents and the naming has changed compared to the old integration (_glucose_measurement -> _measurement) Also the newly added integration will install in the same location as the old one. so you should first delete and uninstall the old integration before installing the new one. Given the author of this repo's lack of response and the past issues with the PR on this repo it should probably be removed from hacs. |
Moved to that repo too, just finished reconfiguring sensors. Thank you! |
A HUGE thanks to @gillesvs ... It's not until things breaks you know how much you really need it. Now we just need to figure out where it should be hosted going forward. |
Also have "Something really wrong happened!", using from France, the librelinkup on mobile works |
@r-jean-pierre use this custom repo instead: |
I Can't read that language ... I have abosolutely no idea what is says. But I would open a terminal or editor and delete all the old "libre" files and try to install again. You should be able to select a "Patinet Id" with a radio button. ( Probably the email you want to follow ) |
Luckily, Google Translate can ;-) |
@zaffraz for me it looks like there is no patiend_id, Remember to download librelink on phone once, and accept terms. |
You were right. Now works. Thanks everyone for the supporto
|
Hey Guys. I have tried to install the new https://github.com/kubasaw/librelink Custom repositories in HACS. But I get the following error. I admit I am pretty new in HA, so it might be me doing somehintg worng, but everything else I have installed in HACS have worked well so far. Any help would be greatly appreciated :-) The only "Libre link" I can find in the HACS store, is the "old version" from gillesvs. |
@Rasmus-nylander it looks like you have already added this repo to hacs. Then add this repo: https://github.com/kubasaw/librelink |
@xamrex Thanks. I think I got confused that both versions seems to be by gillesvs when listed in HACS. But I took notice of the date and stars ratings, and spotted the difference. It all works again. Thanks a lot guys! |
** Which country are you from **
ITALY
Describe the bug
Since this morning, the add-on fails with error "Something really wrong happened!"
Log file
Logger: homeassistant.config_entries
Source: config_entries.py:640
First occurred: 11:55:48 (2 occurrences)
Last logged: 11:55:57
Error setting up entry MAIL for librelink
Traceback (most recent call last):
File "/config/custom_components/librelink/api.py", line 200, in api_wrapper
response.raise_for_status()
~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/aiohttp/client_reqrep.py", line 1157, in raise_for_status
raise ClientResponseError(
...<5 lines>...
)
aiohttp.client_exceptions.ClientResponseError: 430, message='', url='https://api-eu.libreview.io/llu/auth/login'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 640, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/librelink/init.py", line 48, in async_setup_entry
sessionToken = await myLibrelinkLogin.async_get_token()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/librelink/api.py", line 148, in async_get_token
reponseLogin = await api_wrapper(
^^^^^^^^^^^^^^^^^^
...<9 lines>...
)
^
File "/config/custom_components/librelink/api.py", line 209, in api_wrapper
raise LibreLinkApiCommunicationError(
"Error fetching information",
) from exception
custom_components.librelink.api.LibreLinkApiCommunicationError: Error fetching information
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: