Skip to content
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

Unable to determine reason for connection issues via error logs #86

Open
EuleMitKeule opened this issue Jan 13, 2024 · 0 comments
Open

Comments

@EuleMitKeule
Copy link
Contributor

To my understanding there are at least two different reasons for the various connection issues described in #75, #71 and #65.
One of them is a TimeoutError being raised when the notification / response by the thermostat takes too long after a request has been sent in bleakconnection._async_make_request_try and the other is raised when the BLEDevice or BluetoothScannerDevice is not returned by the Home Assistant bluetooth component in bleakconnection.async_get_connection.
While both of these exceptions might have the same underlying cause, I think it would be helpful for debugging to differentiate between both errors by logging different error messages for either case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant