org.bluez.AdvertisementMonitorManager(5)
| ORG.BLUEZ.ADVERTISEMENTMONITORMANAGER(5) | Linux System Administration | ORG.BLUEZ.ADVERTISEMENTMONITORMANAGER(5) |
NAME
org.bluez.AdvertisementMonitorManager - BlueZ D-Bus AdvertisementMonitorManager API documentation
INTERFACE
- Service
- org.bluez
- Interface
- org.bluez.AdvertisementMonitorManager1 [experimental]
- Object path
- /org/bluez/{hci0,hci1,...}
Methods
void RegisterMonitor(object application)
The application object path together with the D-Bus ystem bus connection ID define the identification of the application registering advertisement monitors.
Once a root path is registered by a client via this method, the client can freely expose/unexpose advertisement monitors without re-registering the root path again. After use, the client should call UnregisterMonitor() method to invalidate the advertisement monitors.
Possible errors:
- org.bluez.Error.InvalidArguments
- org.bluez.Error.AlreadyExists
- org.bluez.Error.Failed
void UnregisterMonitor(object application)
Upon unregistration, the advertisement monitor(s) should expect to receive Release() method as the signal that the advertisement monitor(s) has been deactivated.
Possible errors:
- org.bluez.Error.InvalidArguments
- org.bluez.Error.DoesNotExist
Properties
array{string} SupportedMonitorTypes [read-only]
Possible values:
- or_patterns
- Patterns with logic OR applied. With this type, property Patterns must exist and has at least one pattern.
array{string} SupportedFeatures [read-only]
Possible values:
- controller-patterns
- If the controller is capable of performing advertisement monitoring by patterns, bluetoothd(8) would offload the patterns to the controller to reduce power consumption.
| October 2023 | BlueZ |
