how do you know if it’s set up properly
Home assistant doesn’t set up any devices. They are setup by operating system. For os to be able to set up any device it should be supported by kernel.
If bluetooth adapter isn’t set up in operation system, it wan’t show up in home assistant. For debian linux you can check it with
hciconfig -a
or
bluetoothctl show
I run HA core on a pi. Not sure if that is Linux or how to do what you suggested.
well try to open terminal and type hciconfig. Maybe you should install some packages, like bluetooth, I don’t know. If you are using something than you should learn some basic things.
If you’re running HassOS it’s all set up for you. If you’re running any other system, the bluetooth documents covers all hardware that is known to work. Make sure you read over the entire page. Seeing that you’re running core you’d want to start here
HA Core on a PI is most likely Raspbian? You should really know what OS you’re running.
If there is a way, I do not know how to do it. Sorry.
Sorry, if the bluetooth info behind the link says a minimum kernel version down to the milli-grade (last digits) and that does not match, then - in my eyes - the thing is not “set up properly”.
Further the instructions beyond the “if the OS knows, then hassos knows” level is totally missing,
I have been scrutinizing the internet for for some time now, looking for any leads to how to get my BT GPS’es working (I really expect this to be possible on hassos!); and the only lead is gpsd
which requires a socket/serial port. So I cannot see it being possible to get working due to the lack of rfcomm in hassos (sudo apt install rfcomm on Ubuntu).
I have hci0 (Pi4 BT) and hci1 (BT-400) visible in Settings > Devices, but I cannot see any way to get further from there. Only e.g. IKEA LED-thingies I pass by has ever been seen here (as I had “add all discovered devices” set, as per default. NOTE: This is a hassos set up in a “RV”, a mobile home).
More:
I can get these BT-GPS:es flood the terminal with information, through a simplistic rfcomm -setup; on my Ubuntu machine; after bluetoothctl tells med the gps i paired and connected. (also listed in the output of bluetoothctl devices)
HassOS is running on a setup showing itself as “Alpine Linux 3.16”, this can be seen in
$ ssh root@ha
....
[core-ssh ~]$ uname -a
Linux core-ssh 5.15.61-v8 #1 SMP PREEMPT Fri Oct 21 00:45:05 UTC 2022 aarch64 Linux
[core-ssh ~]$ cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.16.1
PRETTY_NAME="Alpine Linux v3.16"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"
[core-ssh ~]$
Bluetooth only works for the integrations that HA supports. It does not support every Bluetooth device… maybe that’s the issue that many people have right now? They assume all BT devices will work, which is not the case.
Well, that might be part of the problem, yes.
But the fact that BT-requirements states a later kernel version than what is present is likely PART of the problem.
As it is stated with a “milli-level” (the third digit in version) requirement implies that there was an important change in that exact version.
HA states the requirements, that’s not really a WTH moment… 
I probably should - what is the easiest way to tell? I’m eager to learn.
Maybe we are having a miss communication here. I’m not sure how you could install HA Core and not know your OS. With that in mind, are you sure you’re running HA Core? Do you have Addons?
EDIT: I somehow missed a screenshot you posted 29 days ago. YOu’re not running HA core, you’re running HassOS.
It should just work with Bluetooth devices that HA can interface with. What device are you trying to connect?
Nevermind found this post here. So I’ll go through your devices:
Not supported.
This used to require a custom integration, this will not likely work anymore because it relies on the old bluetooth setup. I’d lean towards “Not Supported” anymore even witht he custom integration.
Phones are only supported when you enable the bluetooth tracker integration via yaml
So basically, you’re trying to connect devices that home assisant doesn’t support. FYI I simply googled your devices, bluetooth, and home assistant to see if they were supported via an integration. Your other option to look is to simply search for the device in HA via it’s brand. Nothing found → not supported.
Thanks. I appreciate the feedback.
I get the impression that HassOS running on a Pi is some kind of “beginner project”, not fully supported.
Most of the instructions provided in the forum/on the web misses (has no entries for) “Alpine Linux” (as shown by cat /etc/os-release in a ssh shell into HassOS).
Bugger; then why not just remove HassOS from the download section - as it appears to be a dead end.
It’s not though. What you’re asking for just doesn’t exist because it’s not built into home assistant. You can be the first to add that integration and then it would work. If you want to add custom things to HassOS you have to follow the custom integration requirements.
If you want to add something custom to the OS, you shouldn’t be using HassOS, you should switch to HA Container and manage your os and containers. You could try supervised but that takes a lot of linux knowledge to keep HA happy and you can’t run custom containers, but you can add stuff to the OS as long as it doesn’t interfere with HA’s requirements on the OS.
And there we got the statement that could have been brought out a lot earlier.
Summary: Any customization and “HassOS” is out of the question.
It’s customizable, but you’re going from the OS up, it needs to come from HA core/supervisor and go down 
Supervisor manages the OS.
Secondly, even if you added this to your OS, you’d still need a way to get the information into HA.
Thirdly, I have no idea why you’re upset with me. Remember, you’re here asking questions and I’m answering them. Yet it’s my fault for not providing the answer to a question you didn’t ask.