miblepy fetches data from various (Xiaomi/Mijia/Mi) Bluetooth LE devices and push it to a MQTT broker. For every device supported, there are already libraries or anything else to fetch the data from - and they work perfectly. But as they are separated and often run as distinct (cron)jobs, which are not aware of each other, or even as daemons... the fight for the BLE interface starts...
miblepy solves this by acting as a "coordinator" to fetch the data in a controlled, sequential way.
Currently this is a private project tailored to my needs - but open for PRs
miblepy is available as pipโ package and Docker imageโ .
pip install miblepy
clone this repo & cd to it
git clone https://github.com/benleb/miblepy.git && cd miblepy
install via
poetry
poetry install
pip
pip install .
Copy mible.toml to ~/.mible.toml and adjust settings to your needs. ~/.mible.toml is the default location where mible expects your configuration. You can change this via --config.
Start a single round of fetching from your configured sensors in ~/.mible.toml
mible fetch
try mible --help to get more info.
To continously fetch data from your sensors check out the systemd timerโ and serviceโ . You can also use a classic cronjob or even an automation provided by your smart home system (home assistant for example)
The :latest tag is built from master, other tags can be found on Docker Hubโ
Mount your miblepy config to /miblepy/mible.toml
docker run --privileged --volume "mible.toml:/miblepy/mible.toml:ro" benleb/miblepy
Check the already available plugins to see some examples.
Content type
Image
Digest
Size
30.9 MB
Last updated
almost 6 years ago
docker pull benleb/miblepy