fix: handle device going in and out of range frequently #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
services can vanish between connections if the device is
on the edge of bluetooth range. In this case we need
to avoid using the cache. This isnt a problem in the
native bleak implementation but its not merged yet.
This workaround is wrapped with a broad exception
catch so it assumes services cannot be cached if
anything fails in case bleak changes something
under the hood since its making some assumptions
about the implemenation that will not be safe in
future versions