P4a beta test - #4
Open
xloem wants to merge 265 commits into
Open
Conversation
This makes sure we start fresh each time we restart a scanner.
This handles the case where an InterfacesRemoved signal is received but the device hasn't been "seen" yet. Fixes: hbldh#407
This add a new BleakDBusError type for wrapping D-Bus errors. It also adds a utility function to check replies for errors. This will give better information when we encounter an error. Issue: hbldh#406
This fixes failed characteristic and descriptor writes when the data argument is not already a bytes object. The low-level D-Bus API requires strict typing. Fixes: hbldh#408
* document exceptions raised for connect and disconnect methods * include D-Bus object path in debug log messages * protect against reentrancy in _cleanup_all() method * rework disconnect method synchronization for ensuring everything was cleaned up properly
When GetManagedObjects returns without a org.bluez.Device1 interface at the requested object path, then the connect method would already fail before trying the org.bluez.Adapter1.ConnectDevice method. This moves the fallback code so that we handle this case. Also added interfaces_and_props local variable for improved type hints while touching this code.
* adv_service_data Co-authored-by: Jonathan <jonathan.Soto@polestar.eu>
and an example for kivy buildozer on android
Fix for pairing in .NET backend. Protection levels added to Windows backend. Added example with Philips Hue lamp. Updated version and changelog.
…' if not name. Updated BLEDevice.__str__ conditional to check not self.name instead of equality to 'Unknown'. Updated second return statement in BLEDevice.__str__ to use self.name or 'Unknown'. Updated changelog
Obviously misplaced code
Fix for the 'Unknown' name in scan results on Windows 10. Fixes hbldh#371
Implemented async callbacks for pythonnet, BlueZ txdbus and Core Bluetooth backends. New example: Async callbacks with a queue and external consumer
0f56dab made a breaking change by changing is_connected from an async method to a property. This wraps the return value of the property so that it won't break existing code, but will instead print a warning explaining the change.
use proper args and add stack trace level
Needed for Python 3.6. create_task() was introduced in Python 3.7
WIP: dbus-next
Use device.name instead of scraping the name from output of __str__().
several classes were missing overrides for abstract properties which causes a crash
These are things I had to do to get it to build and run
per dlech suggestion Co-authored-by: David Lechner <david@lechnology.com>
xloem
force-pushed
the
p4a-beta-test
branch
5 times, most recently
from
October 10, 2021 17:47
0228d7a to
af6c2b5
Compare
… PR recommendation Co-authored-by: David Lechner <david@lechnology.com>
This reverts commit 6c1e5e9.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request Guidelines for Bleak
Before you submit a pull request, check that it meets these guidelines:
CHANGELOG.rst, describing your changes as is specified by theguidelines in that document.
different problems and you are committing them in the same PR. In that case,
consider making several PRs instead.
AUTHORS.rstfile!