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?
1 Like
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.
1 Like
… and I would like to go as far as to say, better drop the whole Bluetooth hype if you run Bluetooth on a raspberry, it will not work.
Note: HassOS on pi.
+1 on that.
I have the very same experience.
Any BT adapter turns up, but it is not possible to get BT devices visible in any form.
1 Like
My man, you’re trying to get an unsupported device to work. Do you expect your car bluetooth to connect to a BT speaker? Or is it designed to only connect to phones? Same principle here. If it doesn’t have the functionality to connect to your bluetooth device, then it wont.
1 Like
It took me a while, but with help of the forum, and people here, I was very able to get Bluetooth running on a raspi 4.
But as said by others here there is a limit in the support of devices, many do not work, stronger even, my Bluetooth tracker now sees a zillion devices around the house, but there is no way to interact with them like speakers and such,
I added a new Bluetooth dongle & it immediately was picked up by HA. Once configured it I grabbed my meat prob (Chugod) > this seems to interface with the Inkbird integration.
SOOOO Excited…
Smoked meat & smart home technology…what a time to be alive!
What no one has mentioned or replied is that we (as at least me) using HassOS image and that means RPI4 config file is to be updated by HA.
I’m getting error
Retrying setup: hci0 (49:02:91:02:89:88): Failed to start Bluetooth: [org.bluez.Error.InProgress]
Now if its config.txt file issue then what and how to fix it, its still HA WTH issue as its not a standalone installation. No one has been explaining how to fix this ?
Resolved the issue by updating the config.txt file in RPi 4 by doing this
#enable_uart=1
dtoverlay=miniuart-bt
No errors 
2 Likes
I appear to be missing something big because I have HA installed just a few days ago by imaging a card with the image from this link: https://github.com/home-assistant/operating-system/releases/download/9.4/haos_rpi4-64-9.4.img.xz and not only can I not find a file called “config.txt” anywhere but I appear to have no /boot judging from hunting around the filesystem with the Terminal add-on. I understand this is a Docker container so who knows what restrictions it has on what it can see, but I can’t find that file anywhere else in the UI either.
Consequently, I can’t figure out how to start troubleshooting my BT/Z-Wave conflict problem (which I guess is what I’m having). When I correctly configured my Z-Wave dongle, the Pi 4’s built-in Bluetooth stopped working. I gather the problem is that the Z-Wave device appropriated /dev/ttyAMA0 for itself, but then the Bluetooth device was not given another device path. I have the same recurring/reloading error message in my Devices list complaining about hci0 as the above users. There is no /dev/hci0 in my system.
Your diagnosis is correct, and to access the root you need to access it using Putty with Private Key to fix this in config.txt file.
Should be able to find some you tube video of root access to Pi with Private Key
Noob here, so I’d appreciate any help!
Been trying to connect a miflora device to rpi4 bluetooth, but hci0 doesn’t recognise everything, even at a dead close distance from the device.
I’ve included the le tracker script mentioned above, but still nothing…
So I quit and go for an external bluetooth adapter or am I missing something?
Thank you so much in advance!
Have you installed the Xiaomi BLE integration?
I have three of them with no problems, but I have to have a BLE proxy (ESP32) in each room I use them, otherwise the distance is very limited.
1 Like
That was the key element missing!
Thank you so much!