From 28cb94bc89624e152e4efdf7f7fdbf2de5602b2b Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Fri, 9 Aug 2019 12:59:00 +1000 Subject: [PATCH] base: fix failing registration of new devices Regression introduced in e1a3675439116c00a5bd5e14b5b539b0193db59e Where a device has no config entry, the e1a367 change would return early. This is fine for devices previously seen and still lingering in the config but for completely new devices, we'll never get past that KeyError. Return to the old behaviour: where we don't have a stored UUID we continue with the None UUID. Fixes #148 Signed-off-by: Peter Hutterer --- tuhi/base.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tuhi/base.py b/tuhi/base.py index c83fda6..1b36470 100644 --- a/tuhi/base.py +++ b/tuhi/base.py @@ -370,7 +370,7 @@ class Tuhi(GObject.Object): config = self.config.devices[bluez_device.address] uuid = config['uuid'] except KeyError: - return + uuid = None # if we got here from a currently live BlueZ device, # ManufacturerData is reliable. Else, consider the device not in