IO.Box Integration Configuration for WisNode Bridge

Integration Configuration enables Bridge IO devices to seamlessly integrate with mainstream LoRaWAN Network Servers and efficiently manage Device Profiles. It provides a streamlined workflow to onboard devices, generate payload codecs automatically, and synchronize configurations across multiple devices, significantly reducing deployment and maintenance effort.

Figure 1: Integration Dashboard for IO Box

Integration with LoRaWAN Servers

Integration with LoRaWAN Servers allows Bridge IO to connect devices to external LoRaWAN Network Servers (LNS). Through the IO.Box tool, you can effortlessly onboard devices to the server and automatically generate the necessary payload codec scripts to ensure proper parsing of uplink and downlink data.

Prerequisites

Before starting integration, ensure the following:

• Bridge IO is connected to a RAKwireless gateway and sensor data is being received.

• you have logged into the target LoRaWAN server (ChirpStack or TTN), registered your gateway, and created an Application before starting.

ChirpStack v4 Integration

Onboard to ChirpStack Server

This feature provides a one-click onboarding capability. It automatically registers the current Bridge IO device to a specified application on your ChirpStack server, populating essential device parameters like DevEUI and AppKey. Additionally, it automatically generates the required Encode/Decode Script. This eliminates manual device creation and reduces configuration errors.

Configuration Steps

1. In the Integration module, navigate to the ChirpStack v4 menu and click Onboard to ChirpStack Server.

2. Select an existing ChirpStack server and click the target Application.

   NOTE

   If no server is available, click Create New to add one. For detailed steps, refer to Create ChirpStack Server.

3. In the Register End Device to ChirpStack dialog, click Create. The device will then appear automatically under the selected ChirpStack application.

After completing the above configuration, you can view the decoded uplink data values in the device's Events tab.

Figure 1: ChirpStack Events tab

Figure 1: Parse Data

Copy Encode/Decode Script

This feature generates the JavaScript codec functions required by the ChirpStack server. This script defines how to decode the binary payload from the device into readable sensor values and encode downlink JSON commands back into a binary payload for the device.

NOTE

If the device has been registered using the Onboard to ChirpStack Server feature and the required Encode/Decode Script has been automatically generated, this step can be skipped.

Configuration Steps

1. In the Integration module, navigate to the ChirpStack v4 menu and click Copy Encode/Decode Script.

2. Paste the copied script into ChirpStack:

   • Go to the target device's Device Profile.

   • Under the Codec tab, set Payload codec to JavaScript functions.

   • Paste the script into the Codec functions editor and click Submit.

The Things Stack (TTN v3) Integration

Onboard to The Things Stack Server

This feature provides a one-click onboarding capability. It automatically registers the current Bridge IO device to a specified application on your The Things Stack server, populating essential device parameters like DevEUI and AppKey. Additionally, it automatically generates the required Encode/Decode Script. This eliminates manual device creation and reduces configuration errors.

Configuration Steps

1. In the Integration module, navigate to the The Things Stack menu and click Onboard to The Things Stack Server.

2. Select an existing TTN server and click the target Application.

   NOTE

   If no server is available, click Create New to add one. For detailed steps, refer to Create TheThingsStack Server.

3. On the Add New The Things Stack Server page, click OK. The device will then appear automatically under the TTN application.

After completing the configuration, decoded uplink data values can be viewed in the device's Overview tab under Latest decoded payload.

Figure 1: TTN Device Overview

Copy Uplink Decode/Downlink Encode Script

This feature generates the JavaScript scripts required for both the TTN server's Uplink payload formatter (to decode device-sent data) and Downlink payload formatter (to encode server commands into a device-readable format).

NOTE

If the device has been registered using the Onboard to The Things Stack Server feature and the required Encode/Decode Script has been automatically generated, this step can be skipped.

Configuration Steps

1. In the Integration module, navigate to The Things Stack menu and click Copy Uplink Decode Script or Copy Downlink Encode Script.

2. Paste the copied script(s) into The Things Stack:

   • Select the target device and navigate to Payload formatters.

   • Set Formatter type to Custom JavaScript formatter.

   • For Uplink, paste the uplink decode script. For Downlink, paste the downlink encode script. click Save changes.

Profiles

The Profiles feature allows you to save the complete configuration of a Bridge IO device (including LoRaWAN parameters, RS485 polling tasks, AI/AO calibration values, and more) as a named template. This is useful for:

• Configuration Rollback: Quickly revert a device to a known working state if configurations are mistakenly changed.

• Rapid Network Joining: Enable immediate network access for devices not yet registered on a LoRaWAN Network Server (LNS).

• Bulk Deployment: Efficiently deploy a verified configuration to multiple devices of the same model, ensuring consistency and saving configuration time.

IMPORTANT

• When performing bulk deployment, the Bridge IO device models must be identical, and their interface types and connected sensor types must also match.

• If a device has already been registered with a LoRaWAN server, applying a Profile is generally not required. However, if a device is not yet registered, you must apply the corresponding Profile to enable it to join the network.