Issues a request to read the value of the characteristic and returns the value if the operation was successful.

Possible options:

Possible Errors:

Issues a request to write the value of the characteristic.

Possible options:

Possible Errors:

Acquire file descriptor and MTU for writing. Only sockets are supported. Usage of WriteValue will be locked causing it to return NotPermitted error.

For server the MTU returned shall be equal or smaller than the negotiated MTU.

For client it only works with characteristic that has WriteAcquired property which relies on write-without-response Flag.

To release the lock the client shall close the file descriptor, a HUP is generated in case the device is disconnected.

Note: the MTU can only be negotiated once and is symmetric therefore this method may be delayed in order to have the exchange MTU completed, because of that the file descriptor is closed during reconnections as the MTU has to be renegotiated.

Possible options:

Possible Errors:

Acquire file descriptor and MTU for notify. Only sockets are support.

Usage of StartNotify will be locked causing it to return org.bluez.Error.NotPermitted.

For server the MTU returned shall be equal or smaller than the negotiated MTU.

Only works with characteristic that has NotifyAcquired property which relies on "notify" Flag and no other client have called StartNotify().

Notification are enabled during this procedure so StartNotify() shall not be called, any notification will be dispatched via file descriptor therefore the Value property is not affected during the time where notify has been acquired.

To release the lock the client shall close the file descriptor, a HUP is generated in case the device is disconnected.

Note: the MTU can only be negotiated once and is symmetric therefore this method may be delayed in order to have the exchange MTU completed, because of that the file descriptor is closed during reconnections as the MTU has to be renegotiated.

Possible options:

Possible Errors:

Starts a notification session from this characteristic if it supports value notifications or indications.

Possible Errors:

Stops or cancel session previously created by StartNotify().

Note that notifications from a characteristic are shared between sessions thus calling StopNotify will release a single session.

Possible Errors:

Confirms value was received.

Possible Errors:

org.bluez.Error.Failed

128-bit characteristic UUID.

Object path of the GATT service the characteristic belongs to.

The cached value of the characteristic. This property gets updated only after a successful read request and when a notification or indication is received, upon which a PropertiesChanged signal will be emitted.

True, if this characteristic has been acquired by any client using AcquireWrite.

For client properties is ommited in case 'write-without-response' flag is not set.

For server the presence of this property indicates that AcquireWrite is supported.

True, if this characteristic has been acquired by any client using AcquireNotify.

For client this properties is ommited in case 'notify' flag is not set.

For server the presence of this property indicates that AcquireNotify is supported.

True, if notifications or indications on this characteristic are currently enabled.

Defines how the characteristic value can be used. See Core spec "Table 3.5: Characteristic Properties bit field", and "Table 3.8: Characteristic Extended Properties bit field".

The "x-notify" and "x-indicate" flags restrict access to notifications and indications by imposing write restrictions on a characteristic's client characteristic configuration descriptor.

Possible values:

Characteristic handle.

Characteristic handle. When available in the server it would attempt to use to allocate into the database which may fail, to auto allocate the value 0x0000 shall be used which will cause the allocated handle to be set once registered.

Characteristic MTU, this is valid both for ReadValue() and WriteValue() but either method can use long procedures when supported.