WisGateOS 2 Extensions User Manual

Overview

WisGateOS 2 introduces an extension framework that allows gateways to expand their functionality by installing additional software modules. Extensions can be added, removed, or updated based on operational needs, providing greater flexibility and customization for different deployment scenarios.

Starting from WisGateOS 2 2.2.x, the extension installation process is further improved for better security and user experience:

• All extensions are verified with a digital signature to ensure authenticity and compatibility.
• The Extension Gallery enables direct access to verified extensions, simplifying installation and management workflows.
• An Internet connection is required during installation to complete the signature verification.

To check your gateway firmware version, navigate to Dashboard > Overview in the Web UI.

• For gateways running WisGateOS 2 2.0.x or 2.1.x, follow the installation procedure outlined in the WisGateOS 2 2.0.x/2.1.x section.
• For gateways running WisGateOS 2 2.2.x or later, proceed to the updated steps in the WisGateOS 2 2.2.x or Later section.

Supported Extensions

Extensions	Descriptions	Remarks
Breathing Light	By using the breathing light extension, you can personalize the LED light’s working modes, frequency, and color.	-
Custom Logo	The Custom Logo extension allows you to upload your logo in the Web UI. This extension is universal and applicable to all gateways that support WisGateOS 2.	-
Country Settings	Listen Before Talk (LBT) ensures the gateway checks the availability of the channel before transmitting. This is crucial in LoRaWAN, a multi-channel protocol and uses ISM band, to prevent collision from simultaneous transmission. LBT regulations vary by country, and WisGateOS 2 provides a country table easy configuration of the country code.	-
Open/Close Port	This extension enables you to add or delete packet traffic management rules on the gateway, allowing designated subnet host IPs to communicate with the gateway through specified ports.	-
Solar Battery	The Solar Battery extension displays the operational status information of the solar battery used by the gateway. This includes information on the performance of the solar battery, battery health status, cycle period, battery capacity, charging and discharging modes, and more.	Compatible with any WisGateOS 2 gateway equipped with solar power systems.
WireGuard	WireGuard is a simple and fast VPN, designed to be more efficient and leaner than the IPsec protocol, and to outperform the well-known RAKwireless OpenVPN. Support for WireGuard has been implemented on RAKwireless gateways.	-
OpenVPN Client	OpenVPN is a VPN solution that creates a secure network through a server accessible via a public IP address. This server allows the gateway and various client devices, such as PCs and smartphones, to connect. It can utilize backhaul options like Ethernet, Wi-Fi, or LTE. For LTE connections, ensure the gateway has a static public IP address.	-
Operation and Maintenance	This is an operation and maintenance tool that features scheduled device reboot and monitoring of the 4G network status. If the 4G network connection is lost, it automatically restarts the cellular module to recover the connection.	This extension is only compatible with WisGateOS 2 2.2.2 and later.
Field Test Data Processor	This application is designed to provide backend computing services for Field Tester. It communicates with the LoRaWAN network server via MQTT subscribe/publish, supporting both the built-in LNS in the RAK gateway and third-party LNS. This extension allows you to view and download measurement data from the Field Tester.	This extension is only compatible with WisGateOS 2 2.2.2 and later.
Failover Reboot	The Failover Reboot tool periodically checks the status of all enabled network links (LTE / Ethernet / Wi-Fi) of the gateway. Once it detects that all network links are offline, it will try to restore network connectivity by rebooting LTE module or gateway with failover.	This extension is only compatible with WisGateOS 2 2.2.2 and later.

WisGateOS 2 2.0.x/2.1.x

Before installing the extension, you need to obtain the extension file in .ipk format. Gateways running WisGateOS 2 2.0.x/2.1.x support the extensions shown in the table below.

Extension Names	Extension Files
Breathing Light	Download
Custom Logo	Download
Country Settings	Download
Open/Close Port	Download
Solar Battery	Download
WireGuard	Download
OpenVPN Client	Download

How to Add an Extension (v2.0.x/v2.1.x)

1. To install an extension, access the gateway by referring to the Access the WisGateOS 2 Web UI user manual.

Figure 1: WisGateOS 2 login page

2. Once logged in successfully, navigate to the Extensions tab ().

NOTE

• You can click on the WisGate logo () to expand the menu on the left and see the full names of the tabs.
• By default, no extensions are installed.

Figure 1: Extensions tab

3. Proceed with the installation by clicking on the Add new extension button or the install one now link. This will open the Add new extension window.

Figure 1: Add new extension

4. In the window, either drag and drop the extension file into the Drop your Extension file here area, or click the choose file link in the form to browse and select the extension file manually.

NOTE

The extension files are in .ipk format, specifically created for the WisGateOS 2 and WisGate Edge hardware platform. A general .ipk file for OpenWrt cannot be installed.

Figure 1: Choose an Extension

5. Once the extension file is selected, click Add extension to begin the installation. The process may take a few moments to complete.

Figure 1: Add an Extension

6. When the installation is complete, the WisGateOS will automatically reboot, and you will need to log in again.
7. After logging in, navigate back to the Extensions tab. The newly installed extension should now be listed and visible in the interface.

Figure 1: Installed Extension

8. To install additional extensions, use the Add new extension button or manage existing ones by clicking the Launch button next to the desired extension.

How to Remove an Extension (v2.0.x/v2.1.x)

1. Navigate to the Extensions tab and click on the Remove button of the extension you want to uninstall.

Figure 1: Remove the installed Extension

2. A pop-up window will appear to verify if you want delete the extension. Click Remove and wait for the process to finish.

Figure 1: Confirm the Extension removal

At this point, the uninstalled extension will no longer appear on the Extensions page.

Figure 1: Successful Extension removal

How to Use the Extensions (v2.0.x/v2.1.x)

Breathing Light

The breathing light LED is located on the top cover of the WisGate Edge Lite 2 gateways, which helps to easily determine the gateway’s status visually. The breathing light extension allows you to enable or disable the breathing light on the gateway’s top cover. The default state of the LED is as in its Normal state—a slowly blinking blue light.

NOTE

The Breathing Light extension is available only for the WisGate Edge Lite 2 version 2 gateways.

Working Mode

By using the Breathing Light extension, the working mode, frequency, and color of the LED light are now customizable. This extension has two working modes: All and Warning Only.

• Choosing the All mode can:

  • Change the Normal light color, that is the light you see when the gateway is working properly.
  • Set the blinking frequency from slow, fast, and steady.
  • Configure the color of the Warning light.
    NOTE

    The colors for the Normal and the Warning Light should not be the same.

• If you choose Warning only mode:

  • The LED light will only work in case of abnormal activities like Internet connection loss.
  • Light's color can be modified, but not its frequency.

Install the Breathing Light Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.0.x/2.1.x.

Configure the Breathing Light Extension

1. To access the Breathing Light extension, click Launch.

Figure 1: Launch the Breathing Light Extension

2. In the Configuration page, configure the mode, color, and blinking frequency of the LED.

Figure 1: Configuration Page

• Interface

  • Enable Breathing Light: Enables or disables the breathing light extension.
  • Mode: Sets the mode of the extension.
    • All: The Normal light is enabled.
    • Warning only: Disables the Normal light settings and only Warning light will glow.

• Normal light: The settings for the normal light.

  • Color: The color of the light (red, green, blue).
  • Frequency: Blink frequency of the led (slow, fast, steady).
  NOTE

  The Normal light settings are disabled if Warning only mode is selected.

• Warning Light: The color of the warning light.

3. Once done with the configuration, click Save changes.

You can check the status of the LED on the gateway itself.

Custom Logo

The Custom Logo extension allows you to upload your logo in the Web UI. This extension is universal and applicable to all gateways that support WisGateOS 2. It was developed with both small or bigger enterprises in mind, allowing them to have their logo recognized and used in their daily operations.

info

Having the capability to rebrand your Web UI is essential for companies that need to effectively promote and visualize their brand or product. This necessity is met by RAKWireless’ white label feature, which allows clients to customize the user interface to reflect their branding elements seamlessly.

Size and Format Requirements

The uploaded logo image must be in .svg format and cannot exceed 300 kb. You can preview the Web UI page before finally switching RAKWireless’ logo with your brand logo.

Install the Custom Logo Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.0.x/2.1.x.

Configure the Custom Logo Extension

1. To access the Custom Logo extension, click Launch.

Figure 1: Launch the Custom Logo Extension

2. In the Configuration page, you can set a custom logo on the login page and on the sidebar menu.

Figure 1: Configuration Page

• Interface: Enables/disables custom logo extension.
• Large logo: This logo will be used on the login page and the expanded sidebar menu. Upload a logo by dragging and dropping it, or by clicking Choose File to browse manually.
• Small logo: This logo will be used for mobile view and the collapsed sidebar menu. Upload the logo by dragging and dropping it, or by clicking Choose File to browse manually.
• Preview:After selecting the images, click Preview to see how the logo appears on the login page and sidebars in both desktop and mobile views.

Figure 1: Logo Preview for Desktop Users

Figure 1: Logo Preview for Mobile Users

3. To apply the selected logos, click Save changes. The page will reload and apply the logos.

Country Settings

LBT (Listen Before Talk) means that, before transmitting, the gateway checks the availability of the channel. This is necessary because LoRaWAN is a multi-channel protocol and uses ISM Band. Anyone can use the band—a collision occurs if two or more end devices send signals simultaneously.

The gateway checks for empty channels and uses one of them to send downlink data. If a channel is occupied, the gateway performs a random back off. In case all of the channels are occupied, the gateway waits for a free channel and tries to send the downlink data again.

LBT is usually governed by regulations per country. In WisGateOS 2 2.x, there is a country table which includes proper configurations for all countries so you can set the country code in WisGateOS 2 2.x.

NOTE

AS923 end-devices operating in Japan shall perform Listen Before Talk (LBT), based on ARIB STD-T108 regulations. The ARIB STD-T108 regulation is available for free and should be consulted as needed.

You can switch the frequency plan in the following regions:

• AS923, KR920
• EU868, RU864, IN865
• CN470

The frequency plan will be limited to a particular region. Tx power will be limited to under the maximum.

• Downlink Tx Power
• Beacon Tx Power

Install the Country Settings Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.0.x/2.1.x.

Configure the Country Settings Extension

1. To access the Country Settings extension, click Launch.

Figure 1: Launch the Country Settings/LBT Extension

2. In the Configuration page, click the Select your Country button to set your country.

Figure 1: Country selection

Figure 1: Find your country in the list

3. In the new window, find your country and select it. Tick the checkbox below to confirm that you have chosen the country where the gateway is located. Then click Confirm to set the LBT for your country.

Figure 1: Confirm your country

4. Enable the LBT by clicking on the Enable Listen Before Talk switch.

Figure 1: Enable LBT

5. Click Save changes to apply the configuration. Your gateway now has LBT enabled.

Open/Close Port

This extension allows you to add or delete packet traffic management rules on the gateway, allowing any (or specific) host IP from a designated subnet to communicate with the gateway through specified ports.

Install the Open/Close Port Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.0.x/2.1.x.

Configure the Open/Close Port Extension

1. To access the Open/Close Port extension, click Launch.

Figure 1: Launch the Open/Close Port Extension

After clicking Launch, the Traffic rules page will be displayed, showing the default rules of the Open/Close port extension with the following parameters:

• Service name: A readable name for the service
• Protocol: The protocol used
• Family: The protocol version used for the traffic
• From: External source
• To: Internal source

Figure 1: Traffic rules list

For example, the Allow-http service indicates that any host in WAN can communicate with the gateway through port 80 using the TCP protocol type.

2. To add a new rule, click the Add new rule and configure the following information:

• Service name: Provide a readable name for the rule.
• Protocol: Select the protocol used for the rule.
  • TCP
  • UDP
  • TCP + UDP
• Sources:
  • Allow any host: Allows any host to access the rule.
  • Source IP address: Specify up to three host IPs.
• Destination port: The destination port for routing.

Figure 1: Add a new rule

3. To save the changes, click Add new rule. The newly created rule will then appear in the Traffic rules interface.

Solar Battery

The Solar Battery extension is used to display the operational status information of the solar battery used by the gateway. This includes information on the performance of the solar battery, battery health status, cycle period, battery capacity, charging and discharging modes, and more.

This extension is compatible with the following gateways:

• RAK7240V2
• RAK7267
• RAK7289
• RAK7289V2
• RAK7285

You can learn the status of the solar battery in real-time through the UI interface.

Install the Solar Battery Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.0.x/2.1.x.

Configure the Solar Battery Extension

1. To access the Solar Battery extension, click Launch.

Figure 1: Launch the Solar Battery Extension

After clicking Launch, the Details page will be displayed, showing information about the Solar Battery:

• Solar battery performance: Shows the real-time performance of the battery.

  • Temperature: The temperature of the battery. Used to prevent overheating or freezing.
  • Voltage: The voltage level of the battery.
  • State of charge: The current battery level.
  • Current: Indicates whether the battery is charging or discharging.

• About solar battery: Contains additional information about the battery.

  • State of Health: Represents the battery’s overall condition.
  • Cycle times: The number of charge/recharge cycles.
  • Remaining Capacity: The current available capacity of the battery.
  • Full-charge capacity: The maximum capacity when the battery is fully charged.
  • Battery working mode: Indicates whether the battery is charging or discharging.

• Solar battery active events: Notifies users about battery-related issues.

  • FAULT: The system detects a potentially damaged battery and recommends immediate replacement.
  • PROTECT: The system detects a serious issue and shuts down the battery as a protective measure. Once conditions are safe, the battery resumes operation automatically.

2. Enable the switch to activate Monitor solar battery.

Figure 1: Details page

WireGuard

WireGuard is a simple but fast VPN. It aims to be faster, simpler, and leaner than the IPsec protocol. It intends to be more performant than the well-known RAKwireless - OpenVPN. Before, it was not possible to use the WireGuard protocol on the RAKwireless gateways, but that is not the case now.

The new WisGateOS 2 now offers Extension features, where you can install and set up the WireGuard extension. In this tutorial, you will learn how to set the WireGuard client on the gateway.

This guide assumes that you have some knowledge in setting up a WireGuard server and have a WireGuard server set up.

Install the WireGuard Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.0.x/2.1.x.

Configure the WireGuard Extension

1. To access the WireGuard extension, click Launch.

Figure 1: Launch the WireGuard Extension

2. In the Configuration page, enable the Enable WireGuard switch and configure the following information:

• Interface: Settings for the WireGuard client.

  • Address with netmask: The address used by the WireGuard client. It must be in the same range (e.g., 10.0.8.0 to 10.0.8.255) defined by the server.
  • Generate key pair: Automatically generates the key pair.
  • Public key: The public key of the WireGuard client.
  • Private key: The private key of the WireGuard client.
    NOTE

    Do not share your private key with anyone.

• Server: Settings for the WireGuard server.

  • Endpoint host: The IP address of the machine or cloud service where the WireGuard server is hosted.
  • Endpoint port: The port used for WireGuard traffic.
  • Persistent keepalive (ms): The interval at which keepalive packets are sent to maintain the connection.
  • Public key: The public key of the WireGuard server.
  • Enable preshared key: Enables the preshared key field. This key is used as part of the Noise protocol during encrypted connection setup between the two peers.
    Figure 1: Enable preshared key

• Route All Traffic: allows traffic from all IPs

  • Allowed IPs: you can set current IPs that will have the right to connect to the gateway via the WireGuard IP. Only available when Route All Traffic is disabled.

Figure 1: Configuration page

3. To save the changes, click Save changes.

NOTE

Remember to add the WireGuard Client credentials to the WireGuard server configuration.

4. After the connection is established, check the status of the WireGuard in the Status tab.

Figure 1: WireGuard status

OpenVPN Client

OpenVPN (Open Virtual Private Network) is a type of VPN in which a server is deployed to allow both the Gateway and multiple client devices, such as PCs, phones, and other endpoints, to connect via a public IP address. This setup can be implemented using any backhaul connectivity supported by the gateway, including Ethernet, Wi-Fi, or LTE. When using LTE as the backhaul, make sure that the gateway has a static public IP address.

By connecting to the OpenVPN server from a remote client, the gateway can be securely managed from anywhere, at any time. As mentioned above, an OpenVPN server is required. Detailed instructions for deploying a server in the AWS cloud can be found in the How to Configure WisGate Edge v2 Gateways Remote Management - OpenVPN guide.

Install the OpenVPN Client Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.0.x/2.1.x.

Configure the OpenVPN Client Extension

Make sure you have local network access to your gateway and connect to it to access the Web UI.

1. To access the OpenVPN Client extension, click Launch.

Figure 1: Launch the OpenVPN Client Extension

2. Add an OpenVPN tunnel by clicking Add tunnel button or add one now link.

Figure 1: Add OpenVPN tunnel

3. Click choose file link and browse for the .ovpn file or drag and drop the .ovpn file you have created following the How to Configure WisGate Edge v2 Gateways Remote Management - OpenVPN guide.

Figure 1: Add .ovpn file to the gateway

4. Once the file is added, click Add tunnel to add the OpenVPN tunnel.

Figure 1: Add OpenVPN tunnel

When the tunnel is added successfully, a confirmation message will appear at the bottom of the window.

Figure 1: Successfully added tunnel

5. Click Configure button of the VPN tunnel. On the next window, click the Enable Connection switch to enable the OpenVPN tunnel and click Save changes.

Figure 1: Start the OpenVPN tunnel

NOTE

• Once the configurations are set, you may see the OpenVPN status by checking on the Logs tab.

Figure 1: OpenVPN tunnel status

• You may also see the assigned IP in the OpenVPN overview page.

Figure 1: OpenVPN assigned IP

WisGateOS 2 2.2.x or Later

If your gateway firmware is WisGateOS 2 2.2.x or later. Installing extensions becomes easier, you can select and install extensions from the Extension gallery.

How to Add an Extension (v2.2.x or Later)

1. To install an extension, start with accessing the gateway by checking the Access the WisGateOS 2 Web UI user manual.

Figure 1: Login page

2. Once logged in successfully, navigate to the Extensions tab ( ).

NOTE

• You can click the WisGate logo ( ) to expand the menu on the left and see the full names of the tabs.
• By default, no extensions are installed.

Figure 1: Extensions tab

3. Proceed with the installation by clicking on the Extension gallery tab. All extensions that support WisGateOS 2 2.2.x or later will be displayed in the gallery.

Figure 1: Extension gallery

4. Select the desired extension, such as RAK OpenVPN Client, and click the Install button. The process may take a few moments to complete.

NOTE

• If the icon appears on the Extension tab, it means that the gateway hardware does not support the installation of this extension.
• If the icon 🟢 appears on the Extension tab, it means that the gateway hardware support the installation of this extension. You can choose to install this extension.
• If the Auto Update is enabled during installation, the gateway will automatically update the extension when the latest version is available.

Figure 1: Installing extension

5. Once installed, go to the Installed tab where the newly installed extension should now be visible.

Figure 1: Installed extension

How to Remove an Extension (v2.2.x or Later)

1. Navigate to the Extensions > Installed and click on the Remove button of the extension you want to uninstall.

Figure 1: Installed Extension

2. A pop-up window will appear to verify if you want delete the extension. Click Remove and wait for the process to finish.

Figure 1: Removing an Extension

Figure 1: Removing extension

At this point, the uninstalled extension will no longer appear on the Extensions page.

Figure 1: Extension is removed

How to Update an Extension (v2.2.x or Later)

In order to use the latest features of the extension, it is strongly recommend to update the extension to its latest version.

1. To update an extension, navigate to the Extensions > Installed.

Figure 1: Installed extensions page

2. If the latest version of the extension is available, the Update button will be highlighted, indicating that you can choose to update the extension. For example, the RAK Open/Close port extension. Click Update. The process may take a few moments to complete.

Figure 1: Updating extension

After the update is complete, the extension will show as up to date, with no further updates available.

Figure 1: Updated extension

To facilitate timely updates, the RAK gateway provides an automatic update feature. It allows you to check the Auto Update button on the extension tab. Once Auto Update is enabled, the gateway will automatically update the extension when the latest version is available.

Figure 1: Auto Update

How to Use the Extensions (v2.2.x or Later)

RAK Breathing Light

The breathing light LED is located on the top cover of the WisGate Edge Lite 2 gateways and helps to easily determine the gateway’s status visually. The breathing light extension allows you to enable or disable the breathing light on the gateway’s top cover. The default state of the LED is as in its Normal state—a slowly blinking blue light.

NOTE

The Breathing Light extension is available only for the WisGate Edge Lite 2 version 2 gateways.

Working Mode

By using the Breathing Light extension, the working mode, frequency, and color of the LED light are now customizable. This extension has two working modes: All and Warning Only.

• Choosing the All mode can:

  • Change the Normal light color, that is the light you see when the gateway is working properly.
  • Set the blinking frequency from slow, fast, and steady.
  • Configure the color of the Warning light.
    NOTE

    The colors for the Normal and the Warning Light should not be the same.

• If you choose Warning only mode:

  • The LED light will only work in case of abnormal activities like Internet connection loss.
  • Light's color can be modified, but not its frequency.

Install the RAK Breathing Light Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.2.x or Later.

Configure the RAK Breathing Light Extension

1. To access the RAK Breathing Light extension, click Launch.

Figure 1: Launch the RAK Breathing Light Extension

2. In the Configuration page, configure the mode, color, and blinking frequency of the LED.

Figure 1: Configuration Page

• Interface

  • Enable Breathing Light: Enables or disables the breathing light extension.
  • Mode: Sets the mode of the extension.
    • All: The Normal light is enabled.
    • Warning only: Disables the Normal light settings and only Warning light will glow.

• Normal light: The settings for the normal light.

  • Color: The color of the light (red, green, blue).
  • Frequency: Blink frequency of the led (slow, fast, steady).
  NOTE

  The Normal light settings are disabled if Warning only mode is selected.

• Warning Light: The color of the warning light.

3. Once done with the configuration, click Save changes.

You can check the status of the LED on the gateway itself.

RAK Custom Logo

The Custom Logo extension allows you to upload your logo in the Web UI. This extension is universal and applicable to all gateways that support WisGateOS 2. It was developed with both small or bigger enterprises in mind, allowing them to have their logo recognized and used in their daily operations.

info

Having the capability to rebrand your Web UI is essential for companies that need to effectively promote and visualize their brand or product. This necessity is met by RAKWireless’ white label feature, which allows clients to customize the user interface to reflect their branding elements seamlessly.

Size and Format Requirements

The uploaded logo image must be in .svg format and cannot exceed 300 kb. You can preview the Web UI page before finally switching RAKWireless’ logo with your brand logo.

Install the RAK Custom Logo Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.2.x or Later.

Configure the RAK Custom Logo Extension

1. To access the RAK Custom Logo extension, click Launch.

Figure 1: Launch the RAK Custom Logo Extension

2. In the Configuration page, you can set a custom logo on the login page and on the sidebar menu.

Figure 1: Configuration Page

• Interface: Enables or disables the custom logo extension.
• Large logo: This logo will be used on the login page and the expanded sidebar menu. Upload a logo by dragging and dropping it, or by clicking Choose File to browse manually.
• Small logo: This logo will be used for mobile view and the collapsed sidebar menu. Upload the logo by dragging and dropping it, or by clicking Choose File to browse manually.
• Preview: After selecting the images, click Preview to see how the logo appears on the login page and sidebars in both desktop and mobile views.

Figure 1: Logo Preview for Desktop Users

Figure 1: Logo Preview for Mobile Users

3. To apply the selected logos, click Save changes. The page will reload and apply the logos.

RAK Country Settings

LBT (Listen Before Talk) means that, before transmitting, the gateway checks the availability of the channel. This is necessary because LoRaWAN is a multi-channel protocol and uses ISM Band. Anyone can use the band—a collision occurs if two or more end devices send signals simultaneously.

The gateway checks for empty channels and uses one of them to send downlink data. If a channel is occupied, the gateway performs a random back off. In case all of the channels are occupied, the gateway waits for a free channel and tries to send the downlink data again.

LBT is usually governed by regulations per country. In WisGateOS 2 2.x, there is a country table which includes proper configurations for all countries so you can set the country code in WisGateOS 2 2.x.

NOTE

AS923 end-devices operating in Japan shall perform Listen Before Talk (LBT), based on ARIB STD-T108 regulations. The ARIB STD-T108 regulation is available for free and should be consulted as needed.

You can switch the frequency plan in the following regions:

• AS923, KR920
• EU868, RU864, IN865
• CN470

The frequency plan will be limited to a particular region. Tx power will be limited to under the maximum.

• Downlink Tx Power
• Beacon Tx Power

Install the RAK Country Settings Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.2.x or Later.

Configure the RAK Country Settings Extension

1. To access the RAK Country Settings extension, click Launch.

Figure 1: Launch the RAK Country Settings/LBT Extension

2. In the Configuration page, click the Select your Country button to set your country.

Figure 1: Country selection

Figure 1: Find your country in the list

3. In the new window, find your country and select it. Tick the checkbox below to confirm that you have chosen the country where the gateway is located. Then click Confirm to set the LBT for your country.

Figure 1: Confirm your country

4. Enable the LBT by clicking on the Enable Listen Before Talk switch.

Figure 1: Enable LBT

5. Click Save changes to apply the configuration. Your gateway now has LBT enabled.

RAK Open/Close Port

This extension allows you to add or delete packet traffic management rules on the gateway, allowing any (or specific) host IP from a designated subnet to communicate with the gateway through specified ports.

Install the RAK Open/Close Port Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.2.x or Later.

Configure the RAK Open/Close Port Extension

1. To access the RAK Open/Close Port extension, click Launch.

Figure 1: Launch the RAK Open/Close Port Extension

After clicking Launch, the Traffic rules page will be displayed, showing the default rules of the Open/Close port extension with the following parameters:

• Service name: A readable name for the service.
• Protocol: The protocol used.
• Family: The protocol version used for the traffic.
• From: External source.
• To: Internal source.

Figure 1: Traffic rules page

For example, the Allow-http service indicates that any host in WAN can communicate with the gateway through port 80 using the TCP protocol type.

2. To add a new rule, click the Add new rule and configure the following information:

• Service name: give a readable name for the rule
• Protocol: choose the protocol used for the rule:
  • TCP
  • UDP
  • TCP + UDP
• Sources
  • Allow any host: allows any host to have access to the rule
  • Source IP address: you can set up three host IPs
• Destination Port: the destination port of the routing

Figure 1: Adding new rule

3. To save the changes, click Add new rule. The newly created rule will then appear in the Traffic rules interface.

RAK Solar Battery

The RAK Solar Battery extension is used to display the operational status information of the solar battery used by the gateway. This includes information on the performance of the solar battery, battery health status, cycle period, battery capacity, charging and discharging modes, and more.

This extension is compatible with the following gateways:

• RAK7240V2
• RAK7267
• RAK7289
• RAK7289V2
• RAK7285

You can learn the status of the solar battery in real-time through the UI interface.

Install the RAK Solar Battery Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.2.x or Later.

Configure the RAK Solar Battery Extension

1. To access the RAK Solar Battery extension, click Launch.

Figure 1: Launch the RAK Solar Battery Extension

After clicking Launch, the Details page will be displayed, showing information about the Solar Battery:

• Solar battery performance: Shows the real-time performance of the battery.

  • Temperature: The temperature of the battery. Used to prevent overheating or freezing.
  • Voltage: The voltage level of the battery.
  • State of charge: The current battery level.
  • Current: Indicates whether the battery is charging or discharging.

• About solar battery: Contains additional information about the battery.

  • State of Health: Represents the battery’s overall condition.
  • Cycle times: The number of charge/recharge cycles.
  • Remaining Capacity: The current available capacity of the battery.
  • Full-charge capacity: The maximum capacity when the battery is fully charged.
  • Battery working mode: Indicates whether the battery is charging or discharging.

• Solar battery active events: Notifies users about battery-related issues.

  • FAULT: The system detects a potentially damaged battery and recommends immediate replacement.
  • PROTECT: The system detects a serious issue and shuts down the battery as a protective measure. Once conditions are safe, the battery resumes operation automatically.

2. Enable the switch to activate Monitor solar battery.

Figure 1: Details page

RAK WireGuard

WireGuard is a simple but fast VPN. It aims to be faster, simpler, and leaner than the IPsec protocol. It intends to be more performant than the well-known RAKwireless - OpenVPN. Before, it was not possible to use the WireGuard protocol on the RAKwireless gateways, but that is not the case now.

The new WisGateOS 2 now offers Extension features, where you can install and set up the WireGuard extension. In this tutorial, you will learn how to set the WireGuard client on the gateway.

This guide assumes that you have some knowledge in setting up a WireGuard server and have a WireGuard server set up.

Install the RAK WireGuard Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.2.x or Later.

Configure the RAK WireGuard Extension

1. To access the RAK WireGuard extension, click Launch.

Figure 1: Launch the RAK WireGuard Extension

2. In the Configuration page, enable the Enable WireGuard switch and configure the following information:

• Interface: Settings for the WireGuard client.

  • Address with netmask: The IP address the WireGuard client will use. It must be in the same range (e.g., 10.0.8.0 to 10.0.8.255) defined by the server.
  • Generate key pair: Automatically generates the key pair.
  • Public Key: The public key of the WireGuard client.
  • Private Key: The private key of the WireGuard client.
    NOTE

    Do not share your private key with anyone.

  • DNS: The DNS server used by the client.

• Server: Settings for the WireGuard server.

  • Endpoint Host: The IP address of the machine or cloud instance where the WireGuard server is hosted.
  • Endpoint Port: The port used for WireGuard traffic.
  • Persistent Keepalive (ms): The interval for sending keepalive packets to maintain the connection.
  • Public Key: The public key of the WireGuard server.
  • Enable Preshared Key: Enables the preshared key field. The preshared key is part of the Noise protocol used to establish an encrypted connection between peers.
    Figure 1: Enable preshared key

• Route All Traffic: Allows traffic from all IPs.

  • Allowed IPs: Specifies the IPs that are allowed to connect to the gateway via the WireGuard IP. This option is only available when Route All Traffic is disabled.

Figure 1: Configuration page

3. To save the changes, click Save changes.

NOTE

Remember to add the WireGuard Client credentials to the WireGuard server configuration.

4. After the connection is established, check the status of the WireGuard in the Status tab.

Figure 1: WireGuard status

RAK OpenVPN Client

OpenVPN (Open Virtual Private Network) is a type of VPN in which a server is deployed to allow both the Gateway and multiple client devices, such as PCs, phones, and other endpoints, to connect via a public IP address. This setup can be implemented using any backhaul connectivity supported by the gateway, including Ethernet, Wi-Fi, or LTE. When using LTE as the backhaul, make sure that the gateway has a static public IP address.

By connecting to the OpenVPN server from a remote client, the gateway can be securely managed from anywhere, at any time. As mentioned above, an OpenVPN server is required. Detailed instructions for deploying a server in the AWS cloud can be found in the How to Configure WisGate Edge v2 Gateways Remote Management - OpenVPN guide.

Install the RAK OpenVPN Client Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.2.x or Later.

Configure the RAK OpenVPN Client Extension

Make sure you have local network access to your gateway and connect to it to access the Web UI.

1. To access the RAK OpenVPN Client extension, click Launch.

Figure 1: Launch the RAK OpenVPN Client Extension

2. Add an OpenVPN tunnel by clicking Add tunnel button or add one now link.

Figure 1: Add OpenVPN tunnel

3. Click choose file link and browse for the .ovpn file or drag and drop the .ovpn file you have created in the WisGate Edge V2 Gateways Remote Management - OpenVPN guide.

Figure 1: Add .ovpn file to the gateway

4. Once the file is added, click Add tunnel to add the OpenVPN tunnel.

Figure 1: Add OpenVPN tunnel

When the tunnel is added successfully, a confirmation message will appear at the bottom of the window.

Figure 1: Successfully added tunnel

5. Click Configure button of the VPN tunnel. On the next window, click the Enable Connection switch to enable the OpenVPN tunnel and click Save changes.

Figure 1: Start the OpenVPN tunnel

NOTE

• Once the configurations are set, you may see the OpenVPN status by checking on the Logs tab.

Figure 1: OpenVPN tunnel status

• You may also see the assigned IP in the OpenVPN overview page.

Figure 1: OpenVPN assigned IP

Operation and Maintenance

The Operation and Maintenance extension is operation and maintenance tool that features scheduled device reboot and monitoring of the 4G network status. If the 4G network connection is lost, it automatically restarts the cellular module to recover the connection.

NOTE

This extension is only compatible with WisGateOS 2 2.2.2 and later.

Install the Operation and Maintenance Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.2.x or Later.

Configure the Operation and Maintenance Extension

1. To access the Operation and Maintenance extension, click Launch.

Figure 1: Launch the Operation and Maintenance Extension

2. On the Configuration page, configure cellular network monitoring and set a reboot schedule.

Figure 1: Configuration page

• Cellular Network Monitoring: When enabled, the gateway will monitor the cellular connection status every 2 minutes. If the 4G network connection is lost, it will automatically restart the cellular module to restore the connection.
• Schedule Reboot: When enabled, the gateway will reboot periodically based on the configured schedule.
• Gateway Current Time: The system time must be synced for scheduled tasks to function properly. To change the current time, go to User Preferences and set the time.
• Reboot Time: The time when the gateway will reboot.
• Repeat Time: The reboot cycle interval.

3. To save the changes, click Save changes.

Field Test Data Processor

The Field Test Data Processor Extension is an optional application designed to enable local signal processing and data analysis for the Field Tester Plus. Installed on a RAK WisGateOS 2 gateway, it subscribes to uplink data from the connected LoRaWAN Network Server (LNS) using the MQTT protocol.

This extension supports both:

• The built-in LNS on RAK gateways.
• Third-party LNS platforms such as ChirpStack v3 / v4, TTN, TTI, and AWS IoT Core.

Once installed and connected, it provides the following capabilities:

• Local computation of RSSI, SNR, and packet loss.
• Storage and export of structured test data (e.g., CSV reports).
• Heatmap visualization of signal strength and gateway coverage.
• Support for offline or GPS-denied testing using manual location tags.

This extension allows you to analyze signal quality without relying on external cloud services, making it ideal for both indoor and field deployments.

NOTE

This extension is only compatible with WisGateOS 2 2.2.2 and later.

Field Test Data Processor Extension – Parameter Definitions

Name	Description
Device EUI	The unique identifier of the Field Tester Plus device currently being analyzed.
RSSI Chart	Received Signal Strength Indicator. Shows the signal strength of uplink packets received by the gateway. Measured in dBm. Closer to 0 = stronger signal.
SNR Chart	Signal-to-Noise Ratio. Indicates how much stronger the signal is compared to background noise. Higher values represent better communication quality.
DateRate	The LoRaWAN Data Rate (DR) used for the uplink. Lower DR values offer longer range but lower data throughput.
Region	Frequency band used by the Field Tester Plus (e.g., EU868, US915). Must match the configuration of the connected gateway.
Loss Rate	Uplink packet loss rate, calculated based on gaps in frame counters. Ideally should be 0%.
Last Time	Timestamp of the last successfully processed uplink. Useful for checking if the device is still active.
Label	A user-defined location tag for the current test point (e.g., 3F-Elevator). This label will appear in exported CSV reports.
No. of Gateway	Number of gateways that received the latest uplink.
Gateway EUI	The unique identifier of the gateway that received the latest uplink (typically the nearest or strongest gateway).
Distance	Estimated distance (in meters) between the device and the gateway. Requires GPS on the device.

Install the Field Test Data Processor Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.2.x or Later.

Configure the Field Test Data Processor Extension

The following steps describe how to configure the extension to communicate with the supported LoRaWAN network servers via MQTT.

Built-in Network Server

Before configuring the Field Test Data Processor extension, ensure that the gateway is set to Built-in Network Server mode, and the Field Tester Plus device has been successfully added to the server and is communicating properly.

For setup instructions, see the Pre-Test Network Setup section of the Field Tester Plus User Guide.

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Set parameters

• LoRa Network Server: Select the LoRaWAN Network Server where the Field Tester device is registered. In this example, select Built-in Server.
• MQTT Integration:

  • MQTT Broker Address: Set to localhost for the built-in server.

  • Port: Use the default port 1883.

  • Enable User Authentication: Leave as default (no authentication required).

  • Enable TLS Setting: Leave as default.

  • Uplink Topic: Use the following format:

    application/{appName}/device/{devEui}/rx

  • Downlink Topic: Use the following format:

    application/{appName}/device/{devEui}/tx

3. To save the changes, click Save changes.

4. Click the Device Overview tab to access the Field Tester’s heatmap and network performance data.

Figure 1: Device Overview

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. Optional: Click Export to generate a CSV report containing the Field Tester’s collected data.

   NOTE

   Only data points that have been labeled on the device (e.g., marking a specific test location) will be included in the exported report.

Chirpstack v3

Before configuring the Field Test Data Processor extension, ensure that:

• The gateway is correctly configured and connected to the same ChirpStack v3 instance.
• The Field Tester Plus device has been successfully registered on your ChirpStack v3 Network Server.
• The device has joined the LoRaWAN network and is actively sending uplinks.

For detailed instructions, refer to the Pre-Test Network Setup section in the Field Tester Plus User Guide.

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Set parameters

• LoRa Network Server: Select the LoRaWAN server where the Field Tester device is registered. In this case, choose ChirpStack v3.
• MQTT Integration:

  • MQTT Broker Address: Enter the IP address or domain of your ChirpStack MQTT broker.

  • Port: Use the default MQTT port 1883.

  • Enable User Authentication: Leave as default (no authentication required).

  • Enable TLS Setting: Leave as default.

  • Uplink Topic: Uplink topic template:

    application/{applicationId}/device/{devEui}/event/up

  • Downlink Topic: Downlink topic template:

    application/{applicationId}/device/{devEui}/command/down

3. To save the changes, click Save changes.
4. Click the Device Overview tab to access the Field Tester’s heatmap and network performance data.

Figure 1: Device Overview

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. Optional: Click Export to generate a CSV report containing the Field Tester’s collected data.

   NOTE

   Only data points that have been labeled on the device (e.g., marking a specific test location) will be included in the exported report.

Chirpstack v4

Before configuring the Field Test Data Processor extension, ensure that:

• The gateway is correctly configured and connected to the same ChirpStack v4 instance.
• The Field Tester Plus device has been successfully registered on your ChirpStack v4 Network Server.
• The device has joined the LoRaWAN network and is actively sending uplinks.

For detailed instructions, refer to the Pre-Test Network Setup section in the Field Tester Plus User Guide.

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Set parameters

• LoRa Network Server: Select the LoRaWAN server where the Field Tester device is registered. In this case, choose ChirpStack v4.
• MQTT Integration:

  • MQTT Broker Address: Enter the IP address or domain of your ChirpStack MQTT broker.

  • Port: Use the default MQTT port 1883.

  • Enable User Authentication: Leave as default (no authentication required).

  • Enable TLS Setting: Leave as default.

  • Uplink Topic: Uplink topic template:

    application/{applicationId}/device/{devEui}/event/up

  • Downlink Topic: Downlink topic template:

    application/{applicationId}/device/{devEui}/command/down

3. To save the changes, click Save changes.
4. Click the Device Overview tab to access the Field Tester’s heatmap and network performance data.

Figure 1: Device Overview

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. Optional: Click Export to generate a CSV report containing the Field Tester’s collected data.

   NOTE

   Only data points that have been labeled on the device (e.g., marking a specific test location) will be included in the exported report.

The Things Network

Before configuring the Field Test Data Processor extension, make sure that the following conditions are met:

• The gateway is online and properly connected to TTNv3.
• The Field Tester Plus device has been successfully registered on your TTNv3 (The Things Network v3) server.
• The device has joined the LoRaWAN network and is actively transmitting uplink messages.

For detailed setup steps, refer to the Pre-Test Network Setup section in the Field Tester Plus User Guide.

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Set parameters

On TTN, you can view your application's MQTT credentials under: Applications > your application > Other integrations > MQTT.

Figure 1: MQTT integration credentials

• LoRa Network Server: Select the LoRaWAN server where your Field Tester device is registered. In this case, choose The Things Network.
• MQTT Integration:

  • MQTT Broker Address: The public address for the MQTT broker is eu1.cloud.thethings.network.

  • Port: Use the default MQTT port: 1883

  • Enable User Authentication: This option must be enabled.

    • Username: Copy the Username from the MQTT Connection credentials section in the TTN console.
    • Password: Use the API key generated by clicking Generate new API key in the TTN console.

  • Enable TLS Setting: Leave this at its default value.

  • Uplink Topic: Uplink topic template:

    application/{applicationId}/device/{devEui}/event/up

  • Downlink Topic: Downlink topic template:

    application/{applicationId}/device/{devEui}/command/up

3. To save the changes, click Save changes.
4. Click the Device Overview tab to access the Field Tester’s heatmap and network performance data.

Figure 1: Device Overview

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. Optional: Click Export to generate a CSV report containing the Field Tester’s collected data.

   NOTE

   Only data points that have been labeled on the device (e.g., marking a specific test location) will be included in the exported report.

AWS IoT

Before configuring the Field Test Data Processor extension, make sure the following conditions are met:

• All required destination and rule configurations have been completed on the AWS IoT side.
• The gateway has been successfully registered in AWS IoT Core for LoRaWAN and is online.
• The Field Tester Plus device has been properly registered in AWS IoT Core for LoRaWAN.
• The device has successfully joined the LoRaWAN network and is sending uplink messages.

For detailed setup instructions, refer to the Pre-Test Network Setup – AWS IoT Core for LoRaWAN section in the Field Tester Plus User Guide.

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Configure the MQTT broker parameters

• LoRa NetWork Server: Select the LoRaWAN network server where your Field Tester device is registered. In this example, select AWS IoT.

• MQTT Broker Address:

  To obtain the MQTT broker address, navigate to: AWS IoT > Connect > Domain configurations, then click on iot:Data-ATS in the Domain configurations list and copy the Domain name.

  Figure 1: Configure the MQTT broker address

• Port: Set to 8883, the default port for secure MQTT communication over TLS.

• Enable User Authentication: Leave this setting as default.

• Enable TLS Setting: Enable TLS setting to ensure the security of MQTT message transmissions. Therefore, you need to create certificates in AWS IoT.
  a. AWS IoT policies allow you to control access to the AWS IoT Core data plane operations. To create an AWS IoT policy. Go to AWS IoT > Security > Policies, click Create policy.

  Figure 1: Go to create an AWS IoT policy

  b. Configure policy parameters and click Create.

  Figure 1: Configure parameters

  c. Create certificates to authenticate the connection between the device and the Field Test Data Processor extension. Go to AWS IoT > Security > Certificates, click Create certificate.

  Figure 1: Go to create certificates

  d. Configure certificate parameters and click Create.

  Figure 1: Configure parameters

  e. Download the certificate and key files. Click Continue.

  Figure 1: Download the certificate and key files

  f. In the Certificates list, click the Certificate ID created in the previous step to enter the certificate details page.

  Figure 1: Certificate details

  g. Click Attach policies to add the created AWS IoT policy for the certificates.

  Figure 1: Attach policies

  h. Add the certificates to the Field Test Data Processor extension.

  Figure 1: Add certificates

• Uplink Topic: To receive the uplink data from AWS IoT, you need to create a destination that will process the uplink data to this uplink topic.

  The uplink topic used here should match the one configured in your AWS IoT destination (e.g., RecvFieldTesterUplink) — typically created during device registration.

• Downlink Topic: To send downlink messages to a Field Tester device, you need to create a Lambda function.
  a. To create a Lambda function. Go to the AWS Lambda console and click Create function.
  b. Configure the function name and runtime.

  Figure 1: Create Lambda function

  c. Copy the following Python code into the Code source and click Deploy.

  import json
  import boto3
  import base64
  import codecs
  import binascii
  
  client = boto3.client("iotwireless")
  
  def lambda_handler(event, context):
  
      print(event)
  
      device_id = event["deviceID"]
      data = event["data"]
      fPort = event["fPort"]
      client.send_data_to_wireless_device(TransmitMode=0,
                                        Id=device_id,
                                        WirelessMetadata={
                                            "LoRaWAN": {"FPort": fPort}},
                                        PayloadData=data)
    return {
        'statusCode': 200,
        'body': json.dumps('Hello from Lambda!')
    }
  Figure 1: Add Python code

  d. Create a message routing rule in AWS IoT to subscribe the downlink topic and call this Lambda Function to process the downlink message. Go to AWS IoT > Message routing > Rules and click Create rule.
  e. Follow the steps in the following figure to create the message routing rule. Then click Create.

  Figure 1: Specify rule properties
  Figure 1: Configure SQL statement
  Figure 1: Attach rule actions
  Figure 1: Review and create

  f. Configure the downlink topic.

  Figure 1: Downlink topic

3. To save the changes, click Save changes.
4. Click the Device Overview tab to access the Field Tester’s heatmap and network performance data.

Figure 1: Device Overview

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. Optional: Click Export to generate a CSV report containing the Field Tester’s collected data.

   NOTE

   Only data points that have been labeled on the device (e.g., marking a specific test location) will be included in the exported report.

The Things Industries

Before configuring the Field Test Data Processor extension, ensure the following prerequisites are met:

• The gateway is properly registered in TTI and is online.
• The Field Tester Plus device has been successfully registered with The Things Industries (TTI) network server.
• The device has joined the LoRaWAN network and is actively transmitting uplink data.

For step-by-step setup instructions, refer to the Pre-Test Network Setup – TTI section in the Field Tester Plus User Guide.

1. To access the Field Test Data Processor extension, click Launch.

Figure 1: Launch the Field Test Data Processor extension

2. Click the Configuration tab to set the following parameters.

Figure 1: Set parameters

On TTI, you can view your application's MQTT credentials under: Applications > your application > Other integrations > MQTT.

Figure 1: MQTT integration

• LoRa Network Server: Select the LoRaWAN network server where your Field Tester device is registered. In this example, select The Things Industries.
• MQTT Integration:

  • MQTT Broker Address: Use the TTI public MQTT broker address: eu1.cloud.thethings.industries

  • Port: The default MQTT port is 1883.

  • Enable User Authentication: This option must be enabled.

    • Username: Copy the Username from the MQTT Connection credentials section in the TTN console.
    • Password: Use the API key generated by clicking Generate new API key in the TTN console.

  • Enable TLS Setting: Leave this at its default value.

  • Uplink Topic: Uplink topic template:

    application/{applicationId}/device/{devEui}/event/up

  • Downlink Topic: Downlink topic template:

    application/{applicationId}/device/{devEui}/command/down

3. To save the changes, click Save changes.
4. Click the Device Overview tab to access the Field Tester’s heatmap and network performance data.

Figure 1: Device Overview

5. Click Show Data to view a detailed breakdown of all data points collected by the Field Tester. For complete definitions of all parameters shown in this table, refer to the Field Test Data Processor Extension – Parameter Definitions section.

Figure 1: Detailed data

6. Optional: Click Export to generate a CSV report containing the Field Tester’s collected data.

   NOTE

   Only data points that have been labeled on the device (e.g., marking a specific test location) will be included in the exported report.

Failover Reboot

The Failover Reboot tool periodically checks the status of all enabled network links (LTE / Ethernet / Wi-Fi) of the gateway. Once it detects that all network links are offline, it will try to restore network connectivity by rebooting LTE module or gateway with failover.

The following is the logic diagram of the Failover Reboot extension.

Figure 1: Logic diagram

NOTE

• This extension is only compatible with WisGateOS 2 2.2 and later.
• The gateway can be rebooted up to five times.

Install the Failover Reboot Extension

To install the extension, follow the steps in How to Add an Extension on WisGateOS 2 2.2.x or Later.

Configure the Failover Reboot Extension

1. To access the Failover Reboot extension, click Launch.

Figure 1: Extensions tab

2. In the configuration page, enable the Failover Reboot service and set the Check Interval.

Figure 1: Configuration page

• Enable Service: the Failover Reboot service
• Check Interval: time interval for checking the network status, in minutes

3. To save the changes, click Save changes.