No configure button displayed for an Asus USB-BT500

[Nardol]

The problem

I have an Asus USB-BT500 I plugged on my Odroid N2+ running Armbian Bullseye which has been successfully integrated to Home Assistant.
I wish to try passive scan and have enabled experimental features by ading --experimental in the systemd unit file but I have no configuration button displayed in my integrations.

What version of Home Assistant Core has the issue?

2022.9.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Bluetooth

Link to integration documentation on our website

https://www.home-assistant.io/integrations/bluetooth

Diagnostics information

config_entry-bluetooth-f0ed455421680aa75a029d9936b51118.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

busctl introspect org.bluez /org/bluez/hci0 shows org.bluez.Adapter1 in the list
systemctl status bluetooth.service displays the switch --experimental in the main process.
In the case it could be helpful to know, I also have an ESPHome Bluetooth proxy
Related to this topic.

[probot-home-assistant]

bluetooth documentation
bluetooth source
_{^{(message by IssueLinks)}}

[probot-home-assistant]

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (bluetooth) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[bdraco]

From the diagnostics it doesn't look like the adapter supports org.bluez.AdvertisementMonitorManager1

      "/org/bluez/hci0": {
        "org.freedesktop.DBus.Introspectable": {},
        "org.bluez.Adapter1": {
          "Address": "F0:2F:74:64:64:39",
          "AddressType": "public",
          "Name": "homeassistant",
          "Alias": "homeassistant",
          "Class": 4194304,
          "Powered": true,
          "Discoverable": false,
          "DiscoverableTimeout": 180,
          "Pairable": false,
          "PairableTimeout": 0,
          "Discovering": true,
          "UUIDs": [
            "00001801-0000-1000-8000-00805f9b34fb",
            "00001800-0000-1000-8000-00805f9b34fb",
            "0000112d-0000-1000-8000-00805f9b34fb",
            "00001200-0000-1000-8000-00805f9b34fb",
            "0000110c-0000-1000-8000-00805f9b34fb",
            "0000110e-0000-1000-8000-00805f9b34fb",
            "0000180a-0000-1000-8000-00805f9b34fb"
          ],
          "Modalias": "usb:v1D6Bp0246d0537",
          "Roles": [
            "central",
            "peripheral"
          ]
        },
        "org.freedesktop.DBus.Properties": {},
        "org.bluez.GattManager1": {},
        "org.bluez.LEAdvertisingManager1": {
          "ActiveInstances": 0,
          "SupportedInstances": 4,
          "SupportedIncludes": [
            "tx-power",
            "appearance",
            "local-name"
          ],
          "SupportedSecondaryChannels": [
            "1M",
            "2M",
            "Coded"
          ]
        },
        "org.bluez.Media1": {},
        "org.bluez.NetworkServer1": {},
        "org.bluez.SimAccess1": {
          "Connected": false
        }
      },

[Nardol]

Should I buy another Bluetooth dongle to test?
After that maybe it could be useful to document this dongle doe not manage passive scan...

[bdraco]

Sorry for the lack of clarity, that dongle should work. It's the bluez setup that likely needs to be adjusted. I'll see if I can find the setup instructions

[bdraco]

Here are the instructions for settings up BlueZ to work with passive mode

hbldh/bleak#884

[Nardol]

OK, so it looks like Bluetooth integration documentation need to be updated for passive scanning because instructions are exactly the same I used to enable experimental features.

The integration documentation specifies:

Passive Scanning on Linux can be enabled in the options flow per adapter if the host system runs BlueZ 4.63 or later with experimental features enabled.

When the instruction from Bleak PR specifies:

System requirements are BlueZ >= 5.56 and Linux kernel >= 5.10.

$ uname -r
5.10.123-meson64
$ dpkg -l bluez
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom            Version      Architecture Description
+++-==============-============-============-=================================
ii  bluez          5.55-3.1     arm64        Bluetooth tools and daemons
$ bluetoothctl --version
bluetoothctl: 5.55

According to Home Assistant documentation I meat the requirements but not according to Bleak 🙁 which could finally explain everything 😉 Debian has not the right version to enable passive scan for Home Assistant core install and unfortunately there is no backport for Bluez 5.56.

[bdraco]

Looks like there is a typo in the docs. It should have read 5.63 instead of 4.63. Technically it will work with the version bleak mentions but others reported problems with any version before 5.63

[Nardol]

Thanks.
So I've just asked for a Bluez 5.65 backports to the maintainers of the Debian package.
If they don't accept I simply won't use passive scan 🙂 and I'm going to make a PR for the little typo in the doc except if it is already done or if you want to do it.
EDIT: already done before my comment.