No module named bluetooth._bluetooth

[fencerJP]

IndyJoeA,

This plugin is amazing, and I really want to get it working. I'm using a Pi 3B, with a fresh install of CBPi on vanilla Noobs. At first I installed the plugin straight from the plugin list, but uninstalled and followed the readme once I actually read it. The hydrometer is on and registering on my phone.

Now, I get "Failed to load plugin TiltHydrometerPlugin/ No module named bluetooth._bluetooth" as a popup upon restarting, and I can't find Tilt in the thermometer list. Any idea what could cause this?

--
Edit: Just running through the install again, and noticed that python-bluez was never actually installed. Apt says "package python-bluez is not available, but is referred to by another package.... Package 'python-bluez' has no installation candidate"

I attempted the "pip install pybluez" listed in the pybluez readme, which also failed because my system apparently lacks bluetooth.h (output pastebin'd here)

[ewaldheinsen]

Try installing thee libraries. Then try again. I recently installed the plug in, and had the same issues.

sudo apt-get update
sudo apt-get install bluetooth
sudo apt-get install bluez
sudo apt-get install python-bluez

Hope it works.

[meisterbrew]

Hi ewaldheinsen

It worked perfect after updating these libraries.

Thanks!!!

[Palbitt]

It... didn't work for me. However, I have already done some pretty weird thing to try fixing the problem. (For example, I tried creating a new .py file called "bluetooth" that had the single line from pybluez.buetooth import *. It didn't work, [and was meant to fix another error] but that's another story.) I'm working with Debian Linux, on a chromebook (I know! The shame!), so maybe the problem involves Crostini's specific bluetooth system?

At this point, anything helps. Thank you!

Oh, and pip install pybluez didn't work in the first place.

P.S. Is there any way to install _bluetooth manually?

[ronytesler]

@Palbitt Did you solve it?

[jonnytest1]

lol in my case i was in the pybluez source folder , and simply moving out of it solved it - i guess theres probably a "bluetooth.py" in there that overwrites the module