BLE protocols are standardized; however, custom profiles can be defined. If an app attempts to retrieve device information based on a custom profile that doesn't match the service characteristics of our transparent module, it won't discover the service. This mismatch can lead to disconnections or communication issues.

Our commands do not include carriage return and line feed characters by default. Some serial port assistants might add these characters automatically, so you need to remove them to properly process the commands.

Broadcasting upon power-up in the module requires pulling the SLP pin low. Sometimes it occurs and sometimes it doesn't because leaving the SLP pin floating can result in unpredictable pin states. This situation can lead to the observed behavior.

In our pass-through module, command mode is defined as when the module is not connected and the serial port is open. During this time, all serial data sent is considered as commands. When connected, all data sent is considered as pass-through data.

Any broadcasting device can be a beacon. Initially, iBeacon was defined by Apple as a set of broadcast data packet formats embedded in the Apple system for recognition and triggering purposes. However, this functionality no longer exists.

The Service UUID is the UUID for GATT (Generic Attribute Profile) connection communication, whereas the UUID, as defined by us, refers to the UUID in the iBeacon protocol.s-through mode.

Not supported.

Not supported, the chip does not support the mesh protocol.