How to integrate with Blecon BLE

This guide explains how to integrate Blecon , a Bluetooth / BLE network service, with the TagoIO IoT Platform.

By the end of this tutorial, your Blecon-connected Bluetooth devices (BLE devices) will send events to TagoIO, and TagoIO will be able to respond with downlink messages for BLE-based device.request operations.

Prerequisites

Before you begin, make sure you have:

  • Access to the Blecon Console with permission to manage Networks and Devices.
  • A TagoIO account with permission to create devices and authorizations.
  • The Blecon Device ID (URN or UUID) of the BLE/Bluetooth device you plan to connect to TagoIO.

Step 1: Create the Authorization in TagoIO

  1. In TagoIO, open Devices and click Authorizations.
  2. Create a new authorization, give it a friendly name such as Blecon-Integration, and save it.
  3. Copy the generated authorization token. You will paste it in the Blecon integration form.

Step 2: Add the Integration in Blecon

  1. Log into the Blecon Console.
  2. Navigate to Networks > Integrations and choose Add new Integration.
  3. Find TagoIO under Platform Service Integrations and select it.
  4. Fill the form:
    • Integration Name: Any name that helps identify this connection.
    • Namespace: The namespace the middleware should use for request events (for example tago).
    • TagoIO Region: Region where your TagoIO account is hosted.
    • TagoIO Authorization Token: Paste the token copied in Step 1.
  5. Save the integration to enable event delivery to your TagoIO Profile.

Blecon now forwards the following event families to the middleware: network.device_spotted, device.message.*, and device.request.* (expects a JSON response containing a payload). Other event types are acknowledged with HTTP 200 and intentionally ignored.


Step 3: Collect the Blecon Device ID

  1. Still in the Blecon Console, open Network > Devices.
  2. Locate the device that will send events.
  3. Copy its Device ID. Blecon may expose it as a URN (e.g., urn:uuid:...) or a UUID string.


Step 4: Create the Device in TagoIO

  1. In TagoIO, create a new device using the Blecon Network option.
  2. Choose the “Custom Blecon” if your specific device doesn’t appear on the list.
  3. Provide a device name, choose the appropriate data retention policy, and set the Blecon Device ID collected in Step 3.
  4. Complete the wizard and save the device.

TagoIO doesn’t support yet automatic registration/deregistration of Devices from Blecon. You’re required to create the Device manually at TagoIO.

When the device is saved, TagoIO will be able to resolve the events sent from Blecon using the authorization you configured in Step 1.


Step 5: Validate the Integration

  • TagoIO Device Live Inspector: Monitor the device you just created to confirm that spotted events, messages, and requests are arriving. For device.request events, ensure the middleware responds with the payload stored in the device parameters.
  • Downlink Messages: Downlink is supported with Blecon Network Server, and will be delivered through Blecon device.requestwebhook messages.

Once events appear in the Live Inspector, you can continue building dashboards and payload parsers in TagoIO while Blecon handles the device communications layer.

1 Like

Blecon user here - very pleased to see the native support in Tago as Blecon is a great platform.

One comment I would make on your Step 5 details: As of this writing, the native Tago-Blecon integration referenced above does not support downlinks (confirmed via Blecon developers).

It is technically viable (we have done it), but it requires the development of unique 3rd party middleware and associated Tago analysis scripts to accommodate Blecon’s downlink messaging requirements.

1 Like

Hello Steven,

Thanks for the detailed feedback. You are correct, it looks that native downlink support isn’t available in the current integration, though it is great to hear you found a workaround using Analysis.

We are actively working with the Blecon team to bring native downlink support to TagoIO soon. We will update this thread as soon as that functionality is live so you can simplify your middleware setup.

Thanks for helping us improve the documentation!

2 Likes