Struct rustable::gatt::server::AppWorker

pub struct AppWorker { /* fields omitted */ }

[−] Expand description

An active GATT application that is registered with the Bluez daemon.

This worker will continue to work even if this handle to it is dropped.

Implementations

impl AppWorker

pub async fn unregister(self) -> Result<Application, Error>[−]

Deregister the application with Bluez, shutdown the workers, and return the original Application.

pub async fn update_characteristic(
    &self,
    service: UUID,
    character: UUID,
    val: ValOrFn,
    notify: bool
) -> Result<(), Error>[−]

Update the value of the given characteristic with val.

pub async fn update_descriptor(
    &self,
    service: UUID,
    character: UUID,
    descriptor: UUID,
    val: ValOrFn
) -> Result<(), Error>[−]

Update the value of the given descriptor with val.

pub fn notify_char(
    &self,
    service: UUID,
    character: UUID,
    val: Option<AttValue>
) -> impl Future<Output = Result<(), Error>> + Unpin + '_[−]

Trigger a notification for the Bluetooth service.

pub async fn get_char(&self, serv: UUID, cha: UUID) -> Result<AttValue, Error>[−]

Get the current value of the characteristic.

If the value of the characteristic is a ValOrFn::Function the callback will be called. If this is the case, note that this could affect what remote devices see if the callback changes based on number/timing of reads.

pub async fn get_serv_handle(&self, serv: UUID) -> Result<NonZeroU16, Error>[−]

Get the ATT handle for the given service.

pub async fn get_char_handle(
    &self,
    serv: UUID,
    cha: UUID
) -> Result<NonZeroU16, Error>[−]

Get the ATT handle for the given characteristic.

pub async fn char_notifying(&self, serv: UUID, cha: UUID) -> Result<bool, Error>[−]

Check if the characteristic is notifying.

This just indicates that Bluez has called org.bluez.GattCharacteristic1.AcquireNotify and has not hungup the socket, or org.bluez.GattCharacteristic1.StartNotify was called and has not been stopped. This does not guarantee that the device(s) that requested notifications are still connected or listening.

pub async fn char_notify_acquired(
    &self,
    serv: UUID,
    cha: UUID
) -> Result<bool, Error>[−]

Check if the characteristic is notifying through a file descriptor.

This indicates that Bluez has acquired a file descriptor with org.bluez.GattCharacteristic1.AcquireNotify and it hasn’t been closed yet. This does not guarantee that the device(s) that requested notifications are still connected or listening.

Notes

• When remote devices acquire notifications, Bluez will almost always call org.bluez.GattCharacteristic1.AcquireNotify to services them.

pub async fn char_notify_signaling(
    &self,
    serv: UUID,
    cha: UUID
) -> Result<bool, Error>[−]

Check if the characteristic is notifying via DBus signals.

This indicates that Bluez has started a notification session by with org.bluez.GattCharacteristic1.StartNotify.

Notes

• Bluez will almost never uses org.bluez.GattCharacteristic1.StartNotify, but it can be useful for debugging.

pub async fn get_desc(
    &self,
    serv: UUID,
    cha: UUID,
    desc: UUID
) -> Result<AttValue, Error>[−]

Get the current value of the given descriptor.

If the value of the descriptor is a ValOrFn::Function the callback will be called. If this is the case, note that this could affect what remote devices see if the callback changes based on number/timing of reads.

pub async fn get_desc_handle(
    &self,
    serv: UUID,
    cha: UUID,
    desc: UUID
) -> Result<NonZeroU16, Error>[−]

Get the ATT handle for the given descriptor.