Conversation
|
Thanks for working on the 503 errors. I get one occurrence of these errors at HA boot time. I know this is a nit-picking, but now instead of one "Invalid response" error I now have the one 503 Service Unavailable after retry, the API may be overloaded" error in my log. Which just trades one logged error for another, although the second is more descriptive. Is it possible to change the current overloaded API error to just informational unless a certain retry limit is reached? It currently logs an error on even a single occurrence. It seems to me that 503 means "I'm busy, come back later", so it really shouldn't be an error. Sorry if I sound too picky. Just trying to reduce messages in my logs. to those that I need to fix. Again, thanks for your work on this. |
|
@Yang3535 Thanks for letting me know the simple immediate retry did not help. @Yang3535 If I send you some python scripts for testing, are you able to run them (just on a normal windows PC using python3)? |
|
@starkillerOG I'd be happy to run the scripts |
|
@Yang3535 could you test the following python code, (fill in the password, username and IP of the router): This schould generate the 503 error since the same calls are beeing made as with HomeAssistant startup. If it does, could you experiment a bit with the line 'sleep(10)' and see how much seconds we need to wait untill the 503 error disapears? |
|
@starkillerOG, I got the scripts working (thanks) and it seems that the 503 error still occurs with sleep(1), but disappears with sleep(2). There are always exceptions when the script executes. No sure if it's a problem. Output for sleep(2) is below. |
|
@Yang3535 thanks for the testing. You could prevent those errors by using: |
|
@Yang3535 since a sleep 2 appears to work I will build in a sleep of 3 seconds to be on the safe side. |
|
That would be great. Thanks for your work on this!
On Apr 30, 2022, 4:19 AM, at 4:19 AM, starkillerOG ***@***.***> wrote:
***@***.*** since a sleep 2 appears to work I will build in a sleep of 3
…seconds to be on the safe side.
--
Reply to this email directly or view it on GitHub:
#112 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
|
@Yang3535 did you already test HomeAssistant 2022.05? |
|
@starkillerOG Yes, the log entries are gone. Thank you! |
No description provided.