-
Notifications
You must be signed in to change notification settings - Fork 44
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
Error expecting ':' delimiter #436
Comments
which version of the integration are you running? I just upgraded, cleaned my logs and I have no errors. |
Nope, down in my post I said I was on 3.4.2 already. I always update automatically as soon as it's available. |
I had a couple of these this morning, not seen it before. I am on 3.4.2
|
Wierdly (or not), i had not seen this before. However, i upgraded to 2024.2 the other day and i had the same message this morning. Will be looking in to it. I presume something in 2024.2 has caused it - maybe another upgrade to aiohttp that doesn't like the Wiser response. |
I am still on 2024.1.6 |
@dpgh947 error doesn't seem the same I reported on this thread. The one your reported seems like the current ones I am seeing daily that I reported on this thread. Tbh, I haven't seen the ones reported in this issue anymore so far. |
@dpgh947 is the same in the sense it is a json format error just a different specific format error. Either way, same part of the code does not like the json returned from the hub. |
This should be resolved in v3.4.4. Please reopen if you have this issue again. |
I keep getting these, I wonder if it related to this issue? If I hadn't looked in the logs I wouldn't have known there's a problem, the integration seems to be working.
|
Sorry for opening so many issues lately. I'm just trying to clean up my error log that has been increasing for a long while, and tbh most have always been from this integration. Even if I haven't found actual issues when using it. :(
Reporting 2 types of errors here, although they seem very similar.
The text was updated successfully, but these errors were encountered: