-
Notifications
You must be signed in to change notification settings - Fork 20
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 with name resolver #58
Comments
This is unfortunately completely out of my hands. That's something you have to take with your ISP. |
Maybe I was not clear enough in the first message. Of course the ISP DNS resolution is out of the extensions hands, but I expect that when the connection comes back then the extension resumes working. In this case, on the other hand, the connection came back 3 days ago, but the extension did not work. I assume it is because the exceptions in the logs are not handled correctly, and so the pyworxcloud extension stops working |
As it says - max retries exceeded. When that happens, no more retries will be tried until you restart your Home Assistant |
Well, that's the point... I think that an automatic system shall not need to be restarted in case something happens, but it shall be able to automatically recover. So in this case I think that after some time it shall try again, otherwise it becomes locked in this state forever |
You could have a point in that. I'll reopen the issue and do some investigation into if it's possible to somehow reset/reload/retry after a given time. |
I'll close this, as everything is up for a rewrite as a result of recently gaining access to the full Positec repository with the correct documentation of the API and description of how to use the API the correct way. |
Hello
Due to issues with the ISP, sometimes the name of servers cannot be resolved.
This however permanently blocks the extension, since from that moment the extension (I assume) doesn't try again to contact the server.
Here is the log entry with that problem.
pyworxcloud - log.txt
The issue happened on 1st July, and until now (3 days) it has not recovered. No additional log entries are present in the log list in Home Assistant, so I assume the script crashed.
I expect the extension to continue retrying and, when the DNS come back online, resume proper operations
The text was updated successfully, but these errors were encountered: