WisDM User Manual
Overview
WisDM is a cloud-based LoRaWAN fleet management platform designed to simplify the deployment, monitoring, and maintenance of RAK gateways. It allows you to manage your IoT infrastructure remotely with features such as real-time gateway monitoring, remote troubleshooting, over-the-air (OTA) firmware updates, and role-based user management.
Built for the WisGate series, WisDM reduces operational costs and complexity by scaling device management from a single gateway to the entire network. It provides secure, scalable, and user-friendly management for LoRaWAN gateways.
Key Features
- Remote Gateway Configuration: Cloud-based configuration and management of gateways.
- Over-the-Air (OTA) Updates: Trigger gateway firmware updates remotely without manual flashing.
- Real-time LoRaWAN Network Monitoring: Track gateway status, GPS position, and performance metrics, with instant alerts for critical issues. (GPS tracking is available only on outdoor gateway models.)
- Remote Troubleshooting: Utilize tools like packet capture and secure SSH access for in-depth diagnostics.
- MultiWAN Configuration: Remotely configure Ethernet, Wi-Fi, and cellular interfaces with automatic failover.
- User Role Management: A multi-tier user and permission system for flexible access control across teams and organizations.
Hardware Requirements
To connect to WisDM, you need RAKwireless Gateways running WisGateOS version 1.2.2 or later (latest version recommended).
How to Build Your Network
This section helps you plan and organize your WisDM network structure before adding gateways and devices. Understanding the hierarchy and grouping strategy ensures efficient management, monitoring, and scalability across your deployment.
Understand the WisDM Components
WisDM organizes all assets under a clear management hierarchy:
| Term | Definition | Description / Notes |
|---|---|---|
| Organization | Your WisDM account | The top-level entity that group users, gateways, and activities. All assets and permissions belong to an Organization. |
| Location | A network or site grouping | An entity that holds the LoRaWAN configuration - Defines the LoRaWAN Network Server used and gateway configuration - all gateways added to the Location will use the same setting. Supports bulk management of gateways within the same location. |
| Gateway | Network access point for LoRaWAN devices | Provides connectivity for end devices.
|
| Application | Logical grouping of end devices (available only for Locations that use the built-in LoRaWAN Network Server) | Used to route data, integrate with external platforms, or organize devices by use case. |
| End Device | LoRaWAN node (sensor, meter, tracker, etc). | Sends uplink data through gateways and belongs to an Application within a Location. Represents the IoT data source within the WisDM ecosystem. |
Plan Your Network Strategy
Before designing your WisDM network, define a management strategy that ensures efficient gateway operation according to your business scenario.
Location-Based Management
This management strategy organizes gateways by physical location such as a campus, factory, or city zone. All gateways within the same location share a unified LoRaWAN® configuration, including the same region, network server, and LoRaWAN® configuration profile.
This unified setup enables bulk configuration, monitoring, and firmware upgrades to be carried out efficiently across all gateways within the same location.
When to Use:
This strategy is suitable for organizations that:
- Manage multiple sites or facilities within one organization.
- Require each site to maintain an independent LoRaWAN configuration.
- Prefer to manage and monitor gateways by geographic area.
Figure 1: Location-Based ManagementApplication-Based Management
This management strategy organizes gateways by application type instead of physical location, makign it ideal for enterprises that run multiple IoT applications within the same organization.
Each application subnet can operate with different LoRaWAN® profiles, network servers, or join servers, tailored to the specific data and connectivity requirements of each use case.
This flexible structure allows you to optimize performance, isolate interference, and maintain compliance across diverse IoT applications managed within one organization.
When to Use:
This strategy is suitable for organizations that:
- Operate multiple IoT applications or use cases under a single organization.
- Require each application type to utilize its own LoRaWAN settings or network server.
- Prefer to manage and monitor gateways by application logic rather than physical location.
Figure 1: Application-Based ManagementResources
- Visit the WisDM Support Center to access FAQs, getting started guides, and release notes.
- Need dedicated assistance? Contact RAKwireless Support.
FAQs
What is WisDM Remote Extension Install?
WisDM Remote Extension Install is a WisDM capability that lets teams remotely install, update, and manage supported WisGateOS 2 extensions on an eligible gateway from the WisDM console. Select a gateway, choose a supported extension, start the remote install, and monitor install status from one view.
How is an extension different from a firmware update?
An extension is a modular plugin that adds a specific capability to a WisGateOS 2 gateway after deployment. For example, cellular failover monitoring or scheduled reboots. Extensions do not replace the gateway's core firmware. They run alongside it.
A firmware update replaces or upgrades the gateway's core operating system (WisGateOS 2). Extensions and firmware are managed separately in WisDM.
| Extension | Firmware Update | |
|---|---|---|
| What it changes | Adds or updates a modular capability | Replaces or upgrades the core OS |
| Scope | One specific function (e.g., Wi-Fi Reboot) | Entire gateway operating system |
| Managed via | WisDM Remote Extension Install | WisDM firmware update workflow |
| Requires reboot? | No | Yes |
Which extensions are supported at launch?
Four extensions are supported for remote install at launch:
| Extension | What It Does |
|---|---|
| Cellular Failover Reboot | Monitors LTE, Ethernet, and WiFi links. If all links go offline, it automatically restarts the LTE module. If that does not restore connectivity, it reboots the gateway. |
| Wi-Fi Reboot | Monitors WiFi connectivity by running ping or HTTP tests at a set interval. If all tests fail, it reboots the WiFi module. If that does not restore connectivity, it reboots the gateway. |
| Operation and Maintenance | Provides scheduled gateway reboots at a defined interval (daily, weekly, custom) and includes cellular network monitoring with automatic cellular module restart. |
| RAK Open/Close Port | Manages gateway traffic rules: open or close specific ports and restrict access by source IP address. |
Which WisGateOS 2 firmware versions are compatible?
Remote Extension Install requires WisGateOS 2 firmware version 2.2.3.1 or later on eligible gateway models except RAK7437. A gateway running an earlier firmware version must be updated before the extension can be remotely installed.
How does the remote install work?
- Select the gateway. Choose which gateway will receive the extension. (Batch/group deployment is on the roadmap but not yet supported. Extensions are installed one gateway at a time.)
- Choose the extension. Pick a supported WisGateOS 2 extension from the catalog.
- Start the remote install. Confirm and begin the remote install. WisDM pushes the extension to the selected gateway over the air.
- Monitor install status. Track the installation status from the same WisDM view. WisDM shows which gateway have completed, are in progress, or have failed.
What happens during an extension install? What does progress visibility look like?
Installation and configuration happen as two stages:
Figure 1: Extension installation stagesStatus labels shown in WisDM:
| Status | Meaning |
|---|---|
| Installation pending | Request submitted; WisDM is waiting for the gateway to confirm. May take up to 180 seconds to reflect. |
| Installation in progress | Gateway is installing the extension; configuration fields and actions are temporarily unavailable. |
| Configuration pending | Installation complete; gateway is waiting to apply the initial configuration. |
| Configuration in progress | Gateway is applying configuration; fields and actions are temporarily unavailable. |
| Installed and configured | Extension successfully installed and configured. You can view, reconfigure, or deinstall it. |
| Installation failed | Extension could not be installed. Retry or cancel when available. |
| Configuration failed | Extension installed but initial configuration couldn't be applied. Update, retry, or deinstall when available. |
You can monitor the installation from the same WisDM view without switching screens.
What happens if an extension install fails on a gateway?
If installation or configuration fails, WisDM shows the gateway as Installation failed or Configuration failed in the Extensions view. From there, you can retry or cancel the action.
Can I roll back an extension after install?
Yes, an installed extension can be deinstalled remotely via WisDM:
- Go to Gateways, select the gateway, open the Extensions tab.
- In the Installed tab, find the extension and click Deinstall.
- Confirm in the dialog.
Once deinstalled, the extension is removed from the gateway and can be reinstalled from the Extension gallery. Status moves through:
Figure 1: Extension deinstallation status flowIs Remote Extension Install secure?
Only Organization Admins and Location Admins can manage extensions (install, configure, deinstall). Supervisors can only view extensions within their access scope.
Is Remote Extension Install available on all WisDM plans?
Remote Extension Install is available on all WisDM plans. There are no subscription or tier restrictions.
Can I install extensions on a single gateway, or only in groups?
Currently, extensions are installed on one gateway at a time. Batch installation across a gateway group is planned for a future release. The workflow is the same for each gateway. Choose the target, choose the extension, and then start the install.
Do extensions require configuration after install?
Yes. Each extension has its own configuration parameters, set during Install & Configure (and editable later via Reconfigure):
| Extension | Post-Install Configuration |
|---|---|
| Cellular Failover Reboot | Enable Service toggle, check interval (minutes), Auto Update toggle. |
| Wi-Fi Reboot | Enable Service toggle, ping addresses (IP/domain), HTTPing addresses (must be http/https and return status 200), check interval (minutes), Auto Update toggle. |
| Operation and Maintenance | Enable reboot toggle, reboot time, repeat period (None/Daily/Weekly/Monthly), repeat day or date, cellular network monitoring toggle, Auto Update toggle. |
| RAK Open/Close Port | Must be installed first, before rules can be added. Then: service name, protocol (TCP/UDP/TCP+UDP), allow-any-host toggle, up to 3 source IP addresses, destination port. |
Can I update an extension that is already installed?
Each extension has an Auto Update toggle. When enabled, WisDM automatically installs new compatible versions as they become available.
For configuration changes (not version updates), use Reconfigure: open the installed extension, modify parameters, and click Save. Updates may take up to 120 seconds to reflect on the gateway, moving through:
Figure 1: Configuration update status flow
