Hi,
I’m hoping someone has some experience they can share in getting a Mi Flora plant sensor working on an Intel NUC / Hass.io build. In particular, I’m having trouble running the hcitool
to discover the sensor’s bluetooth MAC address.
The closest I have got is running hcitool
inside the home assistant container:
nick@mars:~$ docker exec -ti homeassistant bash
bash-5.0# hcitool lescan
Could not open device: No such device
bash-5.0# hcitool dev
Devices:
Neither my Debian host nor the HA supervisor seem to have hcitool
or bluetoothctl
present.
The Mi Flora description is somewhat unclear about my situation. The guide notes that:
- On Hass.io: Miflora will work out of the box.
- On a generic Docker installation: Works out of the box with
--net=host
and properly configured Bluetooth on the host.
Now I’m not too sure which one I am: mine is a Hass.io build, but perhaps I fall into the “generic Docker installation” category. Because I used the Hass.io build script, I have no idea whether --net=host
has been configured. And I don’t know what “properly configured Bluetooth on the host” actually means.
I have successfully used bluetooth on my system before - at one stage I had the flicd add-on configured (which I have since disabled as I am no longer using flicd). As mentioned, my build is on an Intel NUC, upon which I have deployed Debian and built the Hass.io docker image per the guide.
So I am hoping someone has experience either running a Mi Flora sensor on an Intel NUC based Hass.io build and / or with configuring bluetooth / running hcitool
on a NUC / Hass.io build.
Many thanks in advance.