org.bluez...erManager(5)

🎀 NAME 🎀

org.bluez.BatteryProviderManager — BlueZ D-Bus BatteryProviderManager API documentation, bestie. This is the org.bluez.BatteryProviderManager(5) page, and it's literally here to explain the BlueZ D-Bus BatteryProviderManager API. 💅

💖 DESCRIPTION 💖

okay so a battery provider starts by registering itself as a battery provider with the RegisterBatteryProvider() method, passing an object path as the provider ID. Then it can start exposing org.bluez.BatteryProvider(5) objects having the path starting with the given provider ID. It can also remove objects at any time. The objects and their properties exposed by battery providers will be reflected on the org.bluez.Battery(5) interface.

bluetoothd(8) will stop monitoring these exposed and removed objects after UnregisterBatteryProvider is called for that provider ID. That's the whole flow, no cap.

✨ INTERFACE ✨

Here's the vibe check for the D-Bus side, bestie:

• Service: org.bluez 🌸
• Interface: org.bluez.BatteryProviderManager1 🦋
• Object path: /org/bluez/{hci0,hci1,...} 🎀

🧚 METHODS 🧚

🌟 void RegisterBatteryProvider(object provider)

Registers a battery provider. A registered battery provider can then expose objects with the org.bluez.BatteryProvider(5) interface. Slay.

💫 void UnregisterBatteryProvider(object provider)

Unregisters a battery provider previously registered with RegisterBatteryProvider(). After unregistration, the org.bluez.BatteryProvider(5) objects provided by this client are ignored by bluetoothd(8). Important vibe: they're ignored, fr fr.

---

mwah 💋 — this page comes from BlueZ, dated October 2023. Catch you in the group chat, bestie 🫶✨