Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This object represents a BLE GATT service and is used to manage BLE clients in two-way , where the player acts as a peripheral and another device (phone, tablet, etc.) acts as the client/central. Unlike roBtManager, which allows for unidirectional, non-connectable communication (i.e. beaconing), the roBtClientManager object is used to facilitate two-way, connectable communication. It provides an event to an attached message port when a new client appearsconnects. It also manages the client state, provides client update events, and times out the client after a period of inactivity.

...

  • client_timeout: The amount of time (in seconds) that a client can be inactive before being disconnected.
  • service_uuid: A UUID that identifies the service
  • client_uuid: The client-identifier attribute. Once a client device connects to the player, it should write its unique client identifier value to this attribute.
  • user_variable_uuid: The user variables attribute. This attribute for updating user variablesis intended to be writable by both the player and the client, providing the primary means for exchanging state data. User variables can be written as a JSON string.
  • command_uuid: The attribute for commandscommand attribute. When a client device writes to this attribute, an event containing the command string is generated by the associated roBtClient instance.
  • device_info_uuid: The attribute for device information. This attribute is read-only for clients.
  • device_data_uuid: The attribute for device data. This attribute can be used to communicate available commands to clients. It is read-only for clients.
Note
titleNote

There is a limit 512 bytes on each attribute.


Stop() As Boolean

Stops BLE communication.

...