I’m on the new 64bit HassOS on my rpi3B. I was happy to see people saying in the release thread that Bluetooth tracking should work now. But it won’t work with me. I can put:
device_tracker:
platform: bluetooth_tracker
In my config but my known_devices stays the same untouched with a last modified date of last week. I was really looking forward to this! Has someone got it working? And if so, how?
Definately was working great (like really great!) on hass.io with the original resinOS implementation and the Bluetooth addon. Now with the new hassos and built in Bluetooth support, all of my location based automations are stuffed and it definately isn’t working!!! That makes me very sad.
Anyone have a fix worth noting? That is, short of rolling back to hass.io on resinOS.
Curious, what version of HassOS are people running that are having issues with Bluetooth? I’m running 1.7 and it’s broken (I upgraded it from the hass.io —> system menu. I can’t confirm if this was broken in the previous version I installed from the image (1.5 I think) so curious to hear from others.
How weird! I’m on HassOS 64 bits and bluetooth tracker is acting up on me too. How do I check what my version of HassOS is, and how do I confirm whether I’m actually running a 64bit version or just 32 bit?
I just joined HassOS and I too confirm having issues with Bluetooth. I’ve installed Hass.io supervisor 115 + HassOS 1.7 32bit right from the start (no x64 downgrade or anything) and Bluetooth isn’t working out of the box. I’ve even installed the “Bluetooth BCM43xx (ResinOS)” addon to see if it would solve it. I installs fine but will give errors upon launching. The logs show:
“bcm43xx_init
Failed to write reset command
Can’t initialize device: No error information”
I wonder if re-installing from a backup as some mentioned above could help?
BT tracking should work pretty much out of the box. Just make sure you have the device_tracker entry in your configuration.yaml file. As devices are discovered, they will populate known_devices.yaml file.
Thanks, trying to get the plant sensors to work and need to find their mac address. But the tooling (bluetoothctl) does indicate it has no controller. I added the device_tracker section now, lets see what that returns.
Since you are running in a docker container, you won’t get all of the same tools as you would in the base OS. Are your plant sensors std Bluetooth, or Bluetooth LE devices?
Somehow Hassio supervisor needs to expose the bluetooth device to the home assistant system. I cannot find any reference to an active bluetooth controller. The bluetoothctl responds by indicating there is no controller.
The plant sensors I have are LE sensors, however I also do not see any flic buttons or the nuimo controller. All bluetooth devices.
So I m wondering if the Pi 3B+ with Hassio has support for bluetooth?
I am running hassio .75.3 with hassos 1.9 on a pi3. I have bluetooth devices that I track, but these are not LE devices. There is a different tracker component for LE devices, but it has a warning about potential performance impacts.
I think there were a couple of projects looking at LE trackers, one of which is HappyBubbles. I can’t recall the other one, but they both use MQTT to send the state data over to HA.
Update: This one looks interesting if you have a consistent list of LE devices you want to track:==>