1. Creating a Bluetooth Data Source

• Log in to the Kuika platform.
• Open your mobile project from the Apps screen.
• Go to the Datasources module.

• Click the + button to add a new data source.
• Select Bluetooth as the Datasource Type.

• Fill in the required fields:
  
  • Device Name: The name of the device that will be displayed (required)
  • Device ID: Device-specific ID (optional)
  • Device Address: Bluetooth address (optional)
• Click the CREATE button.

2. Creating a Bluetooth Method

1. Click on the data source you created.
2. Press the ADD NEW METHOD button at the top right.
3. Fill in the following fields:
   
   • Name: E.g. checkSavedDevice
   • Characteristic ID and Service ID
   • Characteristic Type: Read, Write, Notify, Indicate
4. Click the SAVE button.

3. Adding the Saved Device Available Action

1. Click on the method you created.
2. From the Properties panel on the right:
   
   • +ADD ACTION → Custom → userguide123 → SavedDeviceAvailable_bluetooth
3. Add the action and then complete the configuration with SAVE.

In a health monitoring application, the user has previously registered their blood pressure device with the application. When the application is reopened or the device search screen is loaded, the system checks whether the registered device is within range. If the device is within range, the connection is established automatically, so the user does not have to perform any additional actions.

1. When the app is opened or the device search screen is loaded:

• OnPageInit can be set as the trigger. Alternatively, a Button element can be added and triggered with OnClick.

2. Action Sequence:

• Custom → Kuika → SavedDeviceAvailable_bluetooth

(Checks if the registered device is nearby.)

• Conditional Action: If Then Else
  
  • If the device is within range:
    
    • Custom → Kuika → Connect_bluetooth
    • Notify
      
      • title: “Notification”
      • message: “Device connection is being initiated.”
      • type: “info”
  • Otherwise:
    
    • Notify
      
      • title: “Notification”
      • message: “The registered device is not nearby.”
      • type: “warning”

With this flow, the user can quickly take measurements without having to connect the device. The user experience is simplified and the need for manual operations is minimized.

• Conditional Redirection: If the device is in range, you can automatically redirect to the data collection or data transmission screen.
• Dynamic Notifications: If the device is nearby, a notification can be sent to the user; if not, a scan can be initiated.
• Critical Process Pre-Check: Before performing medical measurements or device checks, the device must be checked to ensure it is available.
• Retry with Timer: If the device cannot be found during the initial check, the check can be repeated at specified intervals.

Technical Risks and Precautions

• False Positive Results: Bluetooth scanning may not find the device; therefore, a retry mechanism is recommended.
• Permission Issues: The application cannot perform this check without Bluetooth access or location permissions.
• Device Name Conflicts: If there are multiple devices with the same name, there is a risk of connecting to the wrong device; pairing with the Device ID is required.
• Platform Limitations: This action is only available on mobile devices and does not work on web applications.

Saved Device Available is an action that saves users from having to perform manual actions and significantly simplifies the experience, especially in applications that require connections to devices running in the background. Thanks to the automatic connectivity feature, users find the device ready to use when they open the application. This creates a unique use case for Bluetooth-based applications.