Devices are no longer removed from .discovered_devices on the bluez scanner when InterfacesRemoved is fired
#942
Labels
Comments
dlech
added
bug
bdraco
added a commit
to bdraco/home-assistant
that referenced
this issue
Aug 23, 2022
- We now check the time of each service info in the history since bleak currently has a change that prevents them from disappearing See hbldh/bleak#942
23 tasks
|
It would actually be better to get a callback when a device is removed so we know to mark it unavailable right away. Then we won't be relying on the implementation details of discovered_devices |
dlech
added a commit
that referenced
this issue
Aug 29, 2022
…d_devices This fixes a regression introduced in v0.15 where device removed from BlueZ while scanning were no longer removed from this list of discovered devices. This caused the `discovered_devices` property to return devices that could no longer be connected to by BlueZ since they were removed. Fixes #942.
dlech
added a commit
that referenced
this issue
Aug 30, 2022
…d_devices This fixes a regression introduced in v0.15 where device removed from BlueZ while scanning were no longer removed from this list of discovered devices. This caused the `discovered_devices` property to return devices that could no longer be connected to by BlueZ since they were removed. Fixes #942.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In 0.14.3, the devices would get removed from
self._devicesso whenBleakScannerBlueZDBus.discovered_deviceswas enumerated we knew they were now gone.Since the switch to the global bluez manager in 0.15, they now stay in
BleakScannerBlueZDBus.discovered_devicesforever since the scanner never gets a removal callback.The text was updated successfully, but these errors were encountered: