I’m migrating my Hassio from Rpi3 to Intel NUC using vid image v. 0.29 in a Ubuntu 64bit vm
After succesully installation and restored last snapshot …bluetooth do not works…
Error setting up platform bluetooth_tracker
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/device_tracker/init.py”, line 183, in async_setup_platform
disc_info)
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/device_tracker/bluetooth_tracker.py”, line 81, in setup_scanner
for dev in discover_devices():
File “/usr/local/lib/python3.6/site-packages/homeassistant/components/device_tracker/bluetooth_tracker.py”, line 59, in discover_devices
lookup_class=False, device_id=device_id)
File “/usr/local/lib/python3.6/site-packages/bluetooth/bluez.py”, line 26, in discover_devices
device_id = _bt.hci_get_route()
OSError: [Errno 97] Address family not supported by protoco
I’m also having the same issue. I was previously running hassio on docker on an Ubuntu VM and my bluetooth device tracker was working. Since I moved to running HassOs 2.10 vmdk on proxmox I can’t get bluetooth working. I get the same log message as @vpomax
Do you mean you installed Docker in Ubuntu and then hassio in a Docker container?
I’m sorry but I’m new to all these VM technologies especially Linux based. My only experience in VMS is a small bit of Windows tinkering.
I installed proxmox on my intel nuc. Proxmox is a virtual machine and linux container platform which uses debian as it’s base. So from there I set up a Ubuntu Virtual Machine and then installed docker on the Ubuntu VM. After installing docker I followed the instructions here which explain the steps necessary to get hassio up and running with docker. Depending on your needs you can just install Ubuntu or another flavor of linux on your machine instead of setting up a virtualization environment. If windows is your host OS you could probably just set up a linux virtual machine with something like virtual box and follow the instructions that I linked to earlier in this post. One caveat that you may find is that you will only be able to use your bluetooth adapter on either your windows host or the virtual machine you assign it to, not both. In other words 2 machines won’t be able to share the same bluetooth adapter
That’s interesting, thanks.
I just today installed hassio in Proxmox on a NUC (I’d outgrown the Pi).
Proxmox, Ubuntu, Docker, Hassio sounds like a lot of layers. Are there any down sides to doing it that way? What are the benefits over simply Proxmox, Hassio?
EDIT: Did you use the template for Ubuntu that you can download from inside Proxmox?
There is definitely a hit on performance when using a virtualization environment. I don’t think it’s too much of one and it shouldn’t be an issue if you have a decent machine as a host. The only reason I use proxmox is so that I can spin up linux containers and virtual machines at will. You could get the hassio vmdk image running on proxmox but as myself and others in this thread have reported, bluetooth isn’t working with the vmdk image. So that’s why you need to install a linux virtual machine (not a container) on proxmox to run docker which is where hassio will be running. So no, you don’t want to download the container template from proxmox because docker won’t work in a container without disabling apparmor which isn’t advisable. So instead you want to download an ubuntu live install iso to install as a virtual machine to proxmox
EDIT: Hassio is a set of docker containers, so you can’t run hassio without docker. So in other words you can’t run hassio on proxmox without installing a virtual machine that has docker running on it.
EDIT2: I guess you could install docker on the the proxmox-debian host. I have heard of some people doing that. Maybe that’s what you meant by just running proxmox with hassio. Personally I like to keep my virtualization host as pristine as possible. But that is an option that I had forgot about…
Now I’ve migrated my Hassio from Raspberry to intel NUC.
I installed Hassio in a Proxmox VM with Debian and Docker… but Debian is unable to works the internal NUC bluetooth.
Someone has solved this problem?
I need to use bluetooth_tracker for presence detection.
if that’s ok.