Verbose notification logging on bluezdbus client with characteristic notifications

[Matt-Hicks-Bose]

• bleak version: 0.7.1
• Python version: 3.7.3
• Operating System: Linux
• BlueZ version (bluetoothctl -v) in case of Linux: 5.50

Description

The bleak bluezdbus backend client emits a logging message at both the logging.DEBUG and logging.INFO level every time a characteristic notification is received. This behavior is different than the corebluetooth and dotnet backends which do not log on every notification. This is causing my application to emit several hundred logging messages per second at the logging.INFO level, rendering the logging extremely verbose and not very useful. I am currently changing the logging level of bleak.backends.bluezdbus.client to logging.WARNING, which unfortunately also suppresses some messages that I would like to keep.

I believe that the bluezdbus client should behave the same way as the other two backends and not emit a logging message on characteristic notification.

See BleakClientBlueZDBus._properties_changed_callback():
The logging.DEBUG message https://github.com/hbldh/bleak/blob/master/bleak/backends/bluezdbus/client.py#L777
The logging.INFO message https://github.com/hbldh/bleak/blob/master/bleak/backends/bluezdbus/client.py#L785

What I Did

Connect to a BLE device under Linux and enable notifications on a characteristic that changes frequently.

[hbldh]

I agree. I have not revisited the logging since I first used it for developing the package. Committed some changes now that will be present in upcoming 0.8.0 release.