-
Notifications
You must be signed in to change notification settings - Fork 25
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
Timeout not handled #129
Comments
released v2.0.0b8 with fix for it, please check and update thanks |
HI, unfortunately partially still there:
IS the only timeout line I get, all sensors are working fine. |
Can you pls try tobaccess that page directly? Thanks |
when trying to load the page, can you check if it take more than 3 seconds? thanks |
|
Thanks for answering the next question :) |
I can find it myself, no worries. The bad is that there is something holding the request in your integration as doing it manually it takes way less that 1s |
Agree, can you please increase the timeout set logs to debug and share the logs, i will be able to see what is that process Thanks |
Still
Let me enable debug now |
Cannot find any additional info in the log:
|
Seems to oscillate a lot:
|
Pls post a full debug log not parts of it, otherwise i cannot understand what happens in code Fact that total update time is more than 3 seconds doesn't indicate an issue, timeout is per request while in single update there are multiple http request that each of them can be timed out. I didn't experience any timeout that's the reason i'm asking for that information Thanks |
@chemelli74 is it still relevant? thanks |
I still see it from time to time, I think there is something blocking the refresh and this is the reason it's so slow. |
What machine are you running ha on? How many integrations do you have? I'm thinking maybe limitation of threads (as there are 5-6 endpoint to collect the data from) |
found out that ProductUsageDyn loading time can take up to 4.5 seconds at my network, printer from postman, thanks |
Only inside the integration, look at #129 |
4.5 seconds is for ProductUsageDyn measured in postman not HA same test as you conducted above for both resources: user@host:~# time wget -pq --no-cache --delete-after http://IP/DevMgmt/ProductUsageDyn.xml
real 0m4.577s
user 0m0.003s
sys 0m0.002s
user@host:~# time wget -pq --no-cache --delete-after http://IP/DevMgmt/ProductConfigDyn.xml
real 0m0.485s
user 0m0.002s
sys 0m0.002s if it would happen for different resources i would go with the assumption that something is blocking one of the threads that leads to the error, but since it's specific resource, maybe you can run the same test as load test, or just enable debug log level in logs, |
Side note: Can you please add a migration method when this happen ? Thank you in advance |
no, it was done at 2.0.1 but i also expirenced it when upgraded to 2.0.2 |
the method is to delete those entities, you can do it in the entity tab in device & services |
did you manage to check it with v2.0.2 or above? thanks |
The method is to use the migrate in config_flow ;-) |
Installed but need a bit of time to enable debug and check. |
With debug enabled I don't experience the timeout error anymore |
From time to time I see a timeout in my log:
I think this should be handled from the integration and not just tracing in the log.
The text was updated successfully, but these errors were encountered: