When I call SimpleBLE::Adapter::bluetooth_enabled() for an early check, I have problems later with using my own instance of SimpleBluez::Bluez for a peripheral. bluetooth_enabled() initializes the internal BACKEND_LINUX() instance which doesn't seem accessible from outside, so I cannot reuse it for my peripheral. When I later create another instance of SimpleBluez::Bluez and initialize it, I see the following message in the log:

dbus[92076]: A handler is already registered for /
dbus[92076]: A handler is already registered for /org
dbus[92076]: A handler is already registered for /org/bluez
etc.

Which must be caused by the internal instance.

It might also cause a problem when client (with a SimpleBLE wrapper) and server (SimpleBluez only) functionality needs to be used within a single application. So ideally, it would be nice to have a SimpleBLE wrapper for a peripheral, but another (temporary?) solution might be to let the user reuse the internal backend instance.