We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If the connection is already established, a new call to read() will never finished in case the connection to the heat pump is lost inbetween.
read()
It seems to resume if the heat pump is available again.
Is this a bug or a feature?
The text was updated successfully, but these errors were encountered:
We could set _socket.setdefaulttimeout() to a sensible value, e.g., 5 seconds.
_socket.setdefaulttimeout()
What shall we do when the timeout occurs? Raise an error? Try to reconnect?
Sorry, something went wrong.
Normally I would close the socket and return the error status using the return parameter. The user then has to handle the error.
But that's almost like an "API change".
No branches or pull requests
If the connection is already established, a new call to
read()
will never finished in case the connection to the heat pump is lost inbetween.It seems to resume if the heat pump is available again.
Is this a bug or a feature?
The text was updated successfully, but these errors were encountered: