Problem adding input from Xiaomi Miji Hygro/Thermometer

Hi,
When i try to add the input, i am notified about unsatisfied dependencies. Installing them, the script runs on an error saying it can’t build wheel for bluepy.
Bookworm on a Pi 4, Mycodo 8.15.13, Python 3.11.2

Any help is appreciated, i don`t want to go back to i2c sensors.

Regards Holger

The whole mess:

[2024-04-14 12:20:40]
[2024-04-14 12:20:40] ********************************************************************************
[2024-04-14 12:20:40] Usage of dash-separated ‘description-file’ will not be supported in future
[2024-04-14 12:20:40] versions. Please use the underscore name ‘description_file’ instead.
[2024-04-14 12:20:40]
[2024-04-14 12:20:40] By 2024-Sep-26, you need to update your project and remove deprecated calls
[2024-04-14 12:20:40] or your builds will no longer be supported.
[2024-04-14 12:20:40]
[2024-04-14 12:20:40] See Configuring setuptools using setup.cfg files - setuptools 69.5.1.post20240413 documentation for details.
[2024-04-14 12:20:40] ********************************************************************************
[2024-04-14 12:20:40]
[2024-04-14 12:20:40] !!
[2024-04-14 12:20:40] opt = self.warn_dash_deprecation(opt, section)
[2024-04-14 12:20:40] running bdist_wheel
[2024-04-14 12:20:40] running build
[2024-04-14 12:20:40] running build_py
[2024-04-14 12:20:40] Working dir is /tmp/pip-install-jbdyzih9/bluepy_947fbeb59eb44ac783fba155bed3bbf2
[2024-04-14 12:20:40] execute make -C ./bluepy clean
[2024-04-14 12:20:40] execute make -C bluepy -j1
[2024-04-14 12:20:40] Failed to compile bluepy-helper. Exiting install.
[2024-04-14 12:20:40] Command was ‘make -C bluepy -j1’ in /tmp/pip-install-jbdyzih9/bluepy_947fbeb59eb44ac783fba155bed3bbf2
[2024-04-14 12:20:40] Return code was 2
[2024-04-14 12:20:40] Output was:
[2024-04-14 12:20:40] b"make: Entering directory ‘/tmp/pip-install-jbdyzih9/bluepy_947fbeb59eb44ac783fba155bed3bbf2/bluepy’\ntar xzf bluez-src.tgz\ntouch ./bluez-5.47/lib/bluetooth.c ./bluez-5.47/lib/hci.c ./bluez-5.47/lib/sdp.c ./bluez-5.47/lib/uuid.c ./bluez-5.47/attrib/att.c ./bluez-5.47/attrib/gatt.c ./bluez-5.47/attrib/gattrib.c ./bluez-5.47/attrib/utils.c ./bluez-5.47/btio/btio.c ./bluez-5.47/src/log.c ./bluez-5.47/src/shared/mgmt.c ./bluez-5.47/src/shared/crypto.c ./bluez-5.47/src/shared/att.c ./bluez-5.47/src/shared/queue.c ./bluez-5.47/src/shared/util.c ./bluez-5.47/src/shared/io-glib.c ./bluez-5.47/src/shared/timeout-glib.c\nPackage glib-2.0 was not found in the pkg-config search path.\nPerhaps you should add the directory containing glib-2.0.pc'\nto the PKG_CONFIG_PATH environment variable\nPackage 'glib-2.0', required by 'virtual:world', not found\nPackage glib-2.0 was not found in the pkg-config search path.\nPerhaps you should add the directory containing glib-2.0.pc’\nto the PKG_CONFIG_PATH environment variable\nPackage ‘glib-2.0’, required by ‘virtual:world’, not found\ncc -L. -g -Wall -Os -DHAVE_CONFIG_H -I./bluez-5.47/attrib -I./bluez-5.47 -I./bluez-5.47/lib -I./bluez-5.47/src -I./bluez-5.47/gdbus -I./bluez-5.47/btio -I./bluez-5.47/sys -o bluepy-helper bluepy-helper.c ./bluez-5.47/lib/bluetooth.c ./bluez-5.47/lib/hci.c ./bluez-5.47/lib/sdp.c ./bluez-5.47/lib/uuid.c ./bluez-5.47/attrib/att.c ./bluez-5.47/attrib/gatt.c ./bluez-5.47/attrib/gattrib.c ./bluez-5.47/attrib/utils.c ./bluez-5.47/btio/btio.c ./bluez-5.47/src/log.c ./bluez-5.47/src/shared/mgmt.c ./bluez-5.47/src/shared/crypto.c ./bluez-5.47/src/shared/att.c ./bluez-5.47/src/shared/queue.c ./bluez-5.47/src/shared/util.c ./bluez-5.47/src/shared/io-glib.c ./bluez-5.47/src/shared/timeout-glib.c \nbluepy-helper.c:33:10: fatal error: glib.h: No such file or directory\n 33 | #include \n | ^~\ncompilation terminated.\n./bluez-5.47/attrib/att.c:33:10: fatal error: glib.h: No such file or directory\n 33 | #include \n | ^~\ncompilation terminated.\n./bluez-5.47/attrib/gatt.c:32:10: fatal error: glib.h: No such file or directory\n 32 | #include \n | ^~\ncompilation terminated.\n./bluez-5.47/attrib/gattrib.c:34:10: fatal error: glib.h: No such file or directory\n 34 | #include \n | ^~\ncompilation terminated.\n./bluez-5.47/attrib/utils.c:30:10: fatal error: glib.h: No such file or directory\n 30 | #include \n | ^~\ncompilation terminated.\n./bluez-5.47/btio/btio.c:37:10: fatal error: glib.h: No such file or directory\n 37 | #include \n | ^~\ncompilation terminated.\n./bluez-5.47/src/log.c:38:10: fatal error: glib.h: No such file or directory\n 38 | #include \n | ^~\ncompilation terminated.\n./bluez-5.47/src/shared/io-glib.c:30:10: fatal error: glib.h: No such file or directory\n 30 | #include \n | ^~\ncompilation terminated.\n./bluez-5.47/src/shared/timeout-glib.c:22:10: fatal error: glib.h: No such file or directory\n 22 | #include \n | ^~~~~~~~\ncompilation terminated.\nmake: *** [Makefile:30: bluepy-helper] Error 1\nmake: Leaving directory ‘/tmp/pip-install-jbdyzih9/bluepy_947fbeb59eb44ac783fba155bed3bbf2/bluepy’\n"
[2024-04-14 12:20:40] [end of output]
[2024-04-14 12:20:40]
[2024-04-14 12:20:40] note: This error originates from a subprocess, and is likely not a problem with pip.
[2024-04-14 12:20:40] ERROR: Failed building wheel for bluepy
[2024-04-14 12:20:40] Failed to build bluepy
[2024-04-14 12:20:40] ERROR: Could not build wheels for bluepy, which is required to install pyproject.toml-based projects

[2024-04-14 12:20:41] End install of bluepy

[2024-04-14 12:20:41]
[2024-04-14 12:20:41] #### Setting permissions

[2024-04-14 12:20:41] #### Dependencies installed. Restarting frontend and backend…

[2024-04-14 12:20:57] #### Dependency install complete.

libglib2.0-dev seems to be missing somehow. I manually installed it, now the wheel builds.

And the show goes on. Now i added an Input, selected debugging, enabled ATC-Mode (The hygrometer runs the ATC firmware), and i still get no data.
Live Measurements shows nothing, Asynchronous Data shows nothing, and the log is full of
DEBUG - mycodo.inputs.xiaomi_mijia_lywsd03mmc_d948d663 - Received BLE packet
About 100 Entries per second.

I flashed the Mijia back to a super old stock firmware, now it runs at least for the last hour. Lets see tomorrow.