Improve chances of recovering stuck down bluetooth adapters (#96382)
This commit is contained in:
parent
899adfa74c
commit
c67a1a326f
5 changed files with 9 additions and 8 deletions
|
@ -16,8 +16,8 @@
|
|||
"requirements": [
|
||||
"bleak==0.20.2",
|
||||
"bleak-retry-connector==3.0.2",
|
||||
"bluetooth-adapters==0.15.3",
|
||||
"bluetooth-auto-recovery==1.2.0",
|
||||
"bluetooth-adapters==0.16.0",
|
||||
"bluetooth-auto-recovery==1.2.1",
|
||||
"bluetooth-data-tools==1.3.0",
|
||||
"dbus-fast==1.86.0"
|
||||
]
|
||||
|
|
|
@ -53,6 +53,7 @@ NEED_RESET_ERRORS = [
|
|||
"org.bluez.Error.Failed",
|
||||
"org.bluez.Error.InProgress",
|
||||
"org.bluez.Error.NotReady",
|
||||
"not found",
|
||||
]
|
||||
|
||||
# When the adapter is still initializing, the scanner will raise an exception
|
||||
|
|
|
@ -10,8 +10,8 @@ awesomeversion==22.9.0
|
|||
bcrypt==4.0.1
|
||||
bleak-retry-connector==3.0.2
|
||||
bleak==0.20.2
|
||||
bluetooth-adapters==0.15.3
|
||||
bluetooth-auto-recovery==1.2.0
|
||||
bluetooth-adapters==0.16.0
|
||||
bluetooth-auto-recovery==1.2.1
|
||||
bluetooth-data-tools==1.3.0
|
||||
certifi>=2021.5.30
|
||||
ciso8601==2.3.0
|
||||
|
|
|
@ -525,10 +525,10 @@ bluemaestro-ble==0.2.3
|
|||
# bluepy==1.3.0
|
||||
|
||||
# homeassistant.components.bluetooth
|
||||
bluetooth-adapters==0.15.3
|
||||
bluetooth-adapters==0.16.0
|
||||
|
||||
# homeassistant.components.bluetooth
|
||||
bluetooth-auto-recovery==1.2.0
|
||||
bluetooth-auto-recovery==1.2.1
|
||||
|
||||
# homeassistant.components.bluetooth
|
||||
# homeassistant.components.esphome
|
||||
|
|
|
@ -439,10 +439,10 @@ blinkpy==0.21.0
|
|||
bluemaestro-ble==0.2.3
|
||||
|
||||
# homeassistant.components.bluetooth
|
||||
bluetooth-adapters==0.15.3
|
||||
bluetooth-adapters==0.16.0
|
||||
|
||||
# homeassistant.components.bluetooth
|
||||
bluetooth-auto-recovery==1.2.0
|
||||
bluetooth-auto-recovery==1.2.1
|
||||
|
||||
# homeassistant.components.bluetooth
|
||||
# homeassistant.components.esphome
|
||||
|
|
Loading…
Add table
Reference in a new issue