WTH Why is the raspberry Pi 4 bluetooth integration not seeing any bluetooth devices

Month of "What the heck?!"
82

First of all I did remove the word “Discovery” from my configuration.yaml. I did put it there for some told me it would help, but I knew a great number of HA updates ago for it was automatically done from there, it was meant to be removed so took it out again.
Then I made a line in the configuration.yaml like this one:

device_tracker: !include devices.yaml

And made a file devices.yaml in that file I placed the code seen above!

- platform: bluetooth_tracker
- platform: bluetooth_le_tracker
  track_new_devices: true
  track_battery: true
  interval_seconds: 90
83

Only thing is I do not know what to do with the found Bluetooth devices, till now they have no use for they appear in a file named “known_devices.yaml” but how to use them in code or automations no idea!

84

I’m still getting

“Retrying setup: hci0 (E4:5F:01:AB:68:02): Failed to start Bluetooth: [org.bluez.Error.NotReady] Resource Not Ready”

I’m at a loss of what to do. If the Raspberry Pi 4 has built in Bluetooth and it’s getting interference, should I disable it & go for a dongle or perhaps ESPHome proxies? Would I need both?

Any help would be appreciated.

85

Remember, just because it discovered all these things - HAss has no ideas what to do with them at this point. example - if the BT/BLE was for iBeacon, it would be acted upon, my guess. If not iBeacon, it just sits there, lingering sadly, waiting for something to take ownership of it.

At least that is my understanding.

On top of that, I vaguely read somewhere in the docs that the known_devices.yaml is deprecated or going away (?). Still, it is a good indicator that BT/BLE is functioning at low level.

86

Where do you find what has been discovered though?

87

file named “known_devices.yaml” and in states when you search for tracker you see them all, and the list builts through time wow

88

I don’t see that file.

89

To further expand on this, the file know_devices.yaml gets automatically generated in the same directory where you have the configuration.yaml file.

In HA OS, this would be /config if using Studio Code Server from the main left-side menu, or ssh into the HA OS.

90

The information so far has not been correct. Yes, you can get known_devices if you’re using an integration that generates known_devices. Otherwise, devices that are discovered show up in the integration page. Keep in mind, that only devices that have integrations will show up in the integration page. I.e. if you have some obscure bluetooth device made by company XYZ, it won’t show up because home assistant doesn’t have an XYZ integration.

For example, I have 4 xiaomi bluetooth BLE temperature sensors. They were the only things that were discovered when I enabled bluetooth. I also discovered some grill temperature sensor that my neighbor owns. That’s it. Nothing else. If you add the bluetooth_le_tracker integration, you’ll get a whole bunch of BLE device_tracker entities. Those will show up in known devices.

Lastly, this should go without saying, these will only appear if you have these devices within range of your bluetooth proxy or home assistant server.

91

I am still perplexed. If I try to add an integration it says no know devices (example inkbird and govee bluetooth).

92

put the inkbird device right next to your HA or bluetooth proxy.

It has to be one of these devices.
image

Then integrate it.

If it doesn’t show up, something else is wrong, most likely your bluetooth on HA or the proxy.

93

Thanks for helping. I keep getting this.

Screenshot_20221031-152747_Home Assistant
Screenshot_20221031-152747_Home Assistant1079×860 104 KB

94

What installation of HA are you running?

95

have JBL bluetooth speaker and the list get swamped with entries :slight_smile: make it three and you do not know what you see.

96

Screenshot_20221031-163820_Home Assistant
Screenshot_20221031-163820_Home Assistant1080×679 79.4 KB

On a raspberry pi 4

97

If you have further advice I’d certainly appreciate it.

98

So, I’m not alone after all.

ha-beginner, fighting with BT on the Pi4 with 4GB RAM
Now this is the Pi “ha-OS” so it seems nothing is user-changeable beyond the usual config/yaml stuff.

lists a set of requirements, one of which is
Linux kernel 5.15.62 or later… and

$ ssh root@ha
$ uname -a
Linux core-ssh 5.15.61-v8 #1 SMP PREEMPT Fri Oct 21 00:45:05 UTC 2022 aarch64 Linux

… tells the recently downloaded OS has kernel 5.15.61-v8.

Can I find an update schedule shown somewhere?

  • D-Bus access for ha? How to determine if true in “OS”?

  • D-Bus == dbus-broker? true or not?

  • Bluetooth adapter is apparently visible to ha, even so the USB-dongle version; they appear in ha Settings > Devices …

  • Home Assistant OS version 9.0 or later; yes.

  • and… bluez >=5.43 is also a “yes”

[core-ssh ~]$ apk list bluez
bluez-5.65-r0 aarch64 {bluez} (GPL-2.0-or-later) [installed]

Now who can answer these questions?

99

All of this will be set properly if you’re running hassos. Your issue is most likely related to signal on the pi itself, as highlighted by many people in this thread already. Secondly, only some devices will show up if they have an integration. Random bluetooth devices that do not have an integration will not show up.

100

Is it possible somehow to trace bluetooth device by rssi signal strength?

I have smart watch with bluetooth that doesn’t have integration. I integrated it with passive ble monitor integration. It shows up but it’s reports cycle between not at home and at home when I’m at home but I don’t know why.

101

Respectfully - how do you know if it’s set up properly. Again I’m fairly new & far from a programmer. Just trying to learn. If Bluetooth has “failed to start” it’s not likely to pick up anything ever.