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

The gateway is connected to the LNS, the required application is configured on the LNS, and the gateway and device use the same frequency band.

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.

You can onboard to the ChirpStack Server using the following method.

Create a New ChirpStack Server

1. Navigate to the ChirpStack v4 menu and click Onboard to ChirpStack Server to create a device profile. Click OK.

2. Click Create New to create a ChirpStack Server and configure the following parameters.

   Figure 1: ChirpStack Device1

   • Name: The name of the ChirpStack server.

   • Server Address: The ChirpStack server address. The default port is 9480.

   • Auth Method: Password or API Key. Here we use API key.

   • API Key: ChirpStack server API key. You can create one by following the steps below.

     1. To create a personal API key, go to Network Server > API keys in the left-hand sidebar and click Add API key.

     2. Enter a Name for your key and then press Submit.

     3. You will see the newly created API Key. Copy the key and save it in a safe place, press Back. You will not be able to see this key again in the future, and if you lose it, you can create a new one by following this same procedure.

        Figure 1: ChirpStack Device2

   • Tenant: ChirpStack.

3. Click Create to save the configuration.

4. Select the ChirpStack server you just created, click on the target Application.

   Figure 1: ChirpStack Device3

5. In the Register End Device to ChirpStack dialog, click Create.

   Figure 1: ChirpStack Device4

Select an Existing ChirpStack Server

1. Navigate to the ChirpStack v4 menu and click Onboard to ChirpStack Server to create a device profile. Click OK.

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

   Figure 1: ChirpStack Device5

3. In the Register End Device to ChirpStack dialog, click Create.

Figure 1: ChirpStack Device6

After the device is created successfully, you can view the added device in the ChirpStack.

Figure 1: ChirpStack Device7

Onboard Details (Optional)

After onboarding to a ChirpStack server, you can use Onboard Details to review the server configuration applied during onboarding. It also allows you to register the device directly to an application on the selected server.

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.

You can onboard to The Things Stack Server using the following method.

Create a New The Things Stack Server

1. Navigate to the The Things Stack menu and click Onboard to The Things Stack Server to create a device profile. Click OK.

2. Click Create New to create a TheThingsStack Server and configure the following parameters.

   Figure 1: TTN Device1

   • Name: The name of TheThingsStack Server.

   • Server Address: The ThingsStack Server address. In this case, it is eu1.cloud.thethings.network. The default port is 1884.

   • User ID: Your User ID, which can be obtained from Profile settings > Edit profile.

   • API Key: Your personal API key. You can create one by following the steps below.

     1. To create a personal API key, go to Home > User settings > API keys in the left-hand sidebar and click +Add API key.

     2. Enter a Name for your key, set the Expiry date, select rights that you want to grant and then press Create API Key.

        Figure 1: TTN Device2

     3. You will see a screen that shows your newly created API Key. You now can copy it in your clipboard by pressing the copy button. After saving the key in a safe place, press I have copied the key. You will not be able to see this key again in the future, and if you lose it, you can create a new one by following this same procedure.

        Figure 1: TTN Device3

3. Click Create to save the configuration.

4. Select The Things Stack server you just created, click on the target Application.

   Figure 1: TTN Device4

5. In the Add New The Things Stack Server dialog, Click OK.

   Figure 1: TTN Device5

Select an Existing The Things Stack Server

1. Navigate to the The Things Stack menu and click Onboard to The Things Stack Server to create a device profile. Click OK.

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

   Figure 1: TTN Device6

3. In the Add New The Things Stack Server dialog, Click OK.

Figure 1: TTN Device7

After the device is created successfully, you can view the added device in the TTN.

Figure 1: TTN Device8

Onboard Details (Optional)

After onboarding to a TTN server, you can use Onboard Details to review the server configuration applied during onboarding. It also allows you to register the device directly to an application on the selected server.

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 a Bridge IO device configuration (such as RS485 polling tasks, AI/AO calibration values, and interface settings) as a named template. It is mainly used for fast deployment across multiple devices.

• 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.