LoRaWAN Gateway Hub¶
Dual-Channel LoRaWAN-Compatible Gateway with External Antenna
Product status: Production-ready beta
Overview¶
The Cubicore Gateway Hub is a dual-channel, Wi-Fi-connected LoRaWAN-compatible gateway designed for desktop installations, shelves, classrooms, laboratories, IoT projects, and small-scale deployments.
The Gateway Hub uses the same internal gateway platform and firmware as the Cubicore Gateway Pocket. Its main differences are its larger enclosure and external LoRa antenna connection.
The Gateway Hub includes an external 915 MHz blade antenna connected through an RP-SMA connector. This provides more flexibility for antenna positioning than the Gateway Pocket, which uses an integrated internal LoRa antenna.
The Gateway Hub is preconfigured to work with The Things Network (TTN) by default using the recommended Philippine AS923 Group 3 settings. After both internal gateway channels are provisioned to Wi-Fi, the gateway is ready to forward LoRaWAN packets.
A TTN account is still required
Gateway claiming is optional, but you still need a The Things Network account to create applications, register LoRaWAN end devices, configure your deployment, and view incoming application data.
For complete setup instructions, see Getting Started: Cubicore Gateway Series.
For the optional gateway claiming process, see Set Up and Claim Your Cubicore Gateway.
Key features¶
- Dual-channel LoRaWAN-compatible gateway
- Same internal platform as the Cubicore Gateway Pocket
- Pre-installed and preconfigured firmware
- Wi-Fi network connectivity
- Wi-Fi provisioning via Bluetooth Low Energy (BLE)
- Support for the ESP BLE Provisioning app
- External LoRa antenna connection
- RP-SMA antenna connector
- Included 915 MHz blade antenna
- Uplink and downlink support
- Recommended Philippine AS923 Group 3 configuration
- Two USB Type-C ports
- One externally accessible USB Type-C port
- One internally hidden USB Type-C port for advanced users
- Gray PETG enclosure
- Rubber feet for stable desktop or shelf placement
- Optional TTN gateway claiming
- Suitable for prototyping, education, testing, and small-scale deployments
Create or use a TTN account¶
The Things Network, commonly called TTN, is a LoRaWAN network server used to manage gateways, applications, and end devices.
You need a TTN account to:
- Create a LoRaWAN application
- Register and configure end devices
- View incoming application data
- Check gateway status and activity
- Manage gateway access if you claim the Gateway Hub
If you do not have a TTN account, create one through The Things Network.
Gateway claiming is optional
The Gateway Hub is already configured to work with TTN by default. You do not need to claim the gateway before using it. However, you still need a TTN account for your LoRaWAN applications and end devices.
Recommended Philippine configuration¶
The Gateway Hub is shipped with the recommended configuration for Philippine deployments.
| Setting | Recommended value |
|---|---|
| Frequency plan | Asia 920–923 MHz (AS923 Group 3) |
| LoRaWAN specification | LoRaWAN 1.0.4 |
| Regional Parameters | RP002 Regional Parameters 1.0.2 |
| Frequency 1 | 916.600 MHz |
| Frequency 2 | 916.800 MHz |
| Data rate | DR2 |
| Spreading factor | SF10 |
| Bandwidth | 125 kHz |
| ADR | Disabled |
| Dwell time | Disabled |
| Default network server | The Things Network |
| TTN server address | au1.cloud.thethings.network |
| Packet-forwarder port | 1700 |
| SNTP server | ntp.pagasa.dost.gov.ph |
The gateway is intended to work out of the box with LoRaWAN end devices configured for these recommended settings.
Use compatible regional settings
The gateway and end devices must use compatible regional parameters, frequencies, data rate, bandwidth, ADR, and dwell-time settings. A device configured for another region or channel plan may fail to join or communicate reliably.
The recommended device configuration is intended for Philippine AS923 Group 3 deployments. Other frequency plans, frequencies, spreading factors, bandwidths, or LoRaWAN settings may require additional configuration and regulatory review.
Network connectivity¶
Wi-Fi¶
Wi-Fi provides the Gateway Hub's connection to the LoRaWAN network server or cloud platform.
The gateway uses Wi-Fi for normal network communication and packet forwarding. It requires a Wi-Fi network with internet access.
Wi-Fi provisioning via BLE¶
Initial Wi-Fi setup is performed through Bluetooth Low Energy (BLE) using the ESP BLE Provisioning app.
The app uses BLE to send the Wi-Fi credentials to each internal gateway channel. BLE is used during setup only; it is not the gateway's LoRaWAN backhaul.
BLE is used only for Wi-Fi setup
The ESP BLE Provisioning app uses Bluetooth Low Energy to configure the gateway's Wi-Fi connection. After provisioning, the Gateway Hub uses Wi-Fi to connect to the network server.
Both internal channels must be provisioned to the same Wi-Fi network.
Provision both gateway channels
The Gateway Hub contains two internal one-channel gateway devices. Both channels must be provisioned to Wi-Fi for the complete dual-channel gateway to operate correctly.
For the complete Wi-Fi setup procedure, see Getting Started: Cubicore Gateway Series.
Bluetooth¶
Bluetooth Low Energy is used for initial Wi-Fi provisioning and maintenance setup.
Bluetooth is not the LoRaWAN backhaul and is not used to forward LoRaWAN packets to TTN.
External LoRa antenna¶
Unlike the Gateway Pocket, the Gateway Hub uses an external LoRa antenna connected through an RP-SMA connector.
An included 915 MHz blade antenna is supplied with the gateway.
The RP-SMA connector where the external antenna attaches.
Antenna orientation¶
The antenna is hinged and can be folded for storage or positioning.
The recommended antenna orientation depends on the installation environment, the location of the gateway, the orientation of the end devices, and the required antenna polarization.
The included blade antenna is designed for vertical polarization when positioned upright. In some deployments, the antenna orientation may need to be adjusted to match the intended radio-coverage pattern and end-device orientation.
There is no single antenna orientation that is correct for every installation.
Antenna folded down for storage or compact placement.
Antenna upright for recommended vertical polarization.
Connect the antenna before operation
Connect a suitable LoRa antenna before operating the gateway. Do not operate the LoRa radio without an antenna connected.
Handle the RP-SMA connector carefully
Attach the antenna by hand and avoid overtightening the RP-SMA connector. Do not force the connector or bend the hinged antenna beyond its intended movement.
Antenna placement
For best results, place the Gateway Hub on a stable desktop or shelf with the antenna clear of large metal objects and other obstructions.
The included antenna is intended for the gateway's supported 915 MHz operating range. Do not replace it with an antenna intended for an incompatible frequency range.
For additional antenna information, see the 915 MHz blade antenna datasheet.
Optional TTN gateway claiming¶
The Gateway Hub is preconfigured to work with TTN by default. Claiming is optional and is not required for normal operation.
You may claim the gateway if you want your own TTN account to manage it.
Claiming adds your TTN User ID as an administrator collaborator for the gateway. Cubicore remains an administrator by default so that support can continue when needed.
After claiming, you may remove Cubicore's administrator access or delete and configure the gateway independently according to your own deployment requirements.
To claim the Gateway Hub, see Set Up and Claim Your Cubicore Gateway.
One claim code is used for both channels
The Gateway Hub contains two internal one-channel gateway devices and therefore has two Gateway EUIs. One claim code is associated with both Gateway EUIs. You do not need to submit two separate claims.
Claiming does not interrupt operation
Claiming is an account-access and administration step. It does not update the firmware, change the Wi-Fi settings, modify the LoRaWAN frequency settings, or interrupt packet forwarding.
The gateway does not need to be powered on while the claim is being submitted or processed. Claims normally complete within approximately 1-2 minutes.
Application data and network metadata¶
The Gateway Hub forwards LoRaWAN packets but does not decrypt or inspect the application payload.
LoRaWAN application data is protected by encryption between the end device and the application server. The customer's application and end-device configuration determine how application data is handled and displayed.
Cubicore may still have access to limited technical metadata needed to operate and support the gateway, such as:
- Gateway status
- Connection status
- Packet timing
- Radio statistics
- Device identifiers
- Frequency and data-rate information
- Uplink and downlink activity
Application data and network metadata
Your sensor or application payload is protected by LoRaWAN encryption. However, technical metadata such as gateway status, timestamps, radio statistics, and device identifiers may still be visible to the network infrastructure operator.
LoRaWAN operation¶
The Gateway Hub provides two LoRaWAN channels using the external LoRa antenna.
It supports:
- Uplink reception
- Downlink transmission
- Two-channel LoRaWAN operation
- Wi-Fi packet forwarding to the configured network server
The recommended operating configuration is the Philippine AS923 Group 3 configuration listed above.
Connected end devices should use:
- AS923 Group 3
- 916.6 MHz and 916.8 MHz
- SF10
- 125 kHz bandwidth
- ADR disabled
- Dwell time disabled
Hardware specifications¶
| Feature | Specification |
|---|---|
| Product | Cubicore Gateway Hub |
| Product status | Production-ready beta |
| LoRaWAN compatibility | LoRaWAN-compatible |
| Internal platform | Two internal one-channel gateway devices |
| Radio channels | Dual-channel |
| Regional configuration | AS923 Group 3, Philippines |
| LoRa antenna | External 915 MHz blade antenna |
| Antenna connector | RP-SMA |
| Wi-Fi antenna | Internal |
| Bluetooth antenna | Internal |
| Network connectivity | Wi-Fi |
| Provisioning | Wi-Fi provisioning via BLE using the ESP BLE Provisioning app |
| Enclosure material | PETG |
| Enclosure color | Gray |
| Placement | Desktop or shelf |
| Feet | Rubber feet |
| Mounting holes | None |
| USB ports | 2 × USB Type-C |
Included antenna specifications¶
The included blade antenna is intended for the gateway's 915 MHz operating range.
| Antenna specification | Value |
|---|---|
| Frequency range | 902-928 MHz |
| Peak gain | 2.3 dBi |
| Connector | RP-SMA |
| Polarization | Vertical |
| Feed impedance | 50 Ω |
| Antenna type | Blade antenna |
Physical dimensions¶
Gateway body¶
| Dimension | Measurement |
|---|---|
| Length | 145 mm |
| Width | 70 mm |
| Height | 30.5 mm |
Overall body dimensions:
145 × 70 × 30.5 mm (L × W × H)
The Gateway Hub does not have mounting holes. It is designed for desktop or shelf placement and includes rubber feet for stability.
Antenna-installed dimension¶
The antenna is hinged and may be folded upward.
When the antenna is folded upward, the approximate end-to-end product dimension becomes:
Approximately 213 mm
Antenna-installed dimension
The approximate 213 mm measurement refers to the end-to-end product dimension when the hinged antenna is folded upward. It is not the total vertical height from the bottom of the gateway to the top of the antenna.
Allow additional space around the gateway and antenna for:
- Wi-Fi and LoRa radio performance
- Antenna movement
- Cable access
- Ventilation
- Maintenance and setup
USB Type-C ports¶
The Gateway Hub has two USB Type-C ports:
- One externally visible USB Type-C port
- One USB Type-C port hidden inside the enclosure
The visible port is intended for normal power and user access.
The hidden port is intended for advanced users and service or debug access. It is rarely needed for normal operation.
The rear of the Gateway Hub showing the externally accessible USB Type-C port.
Disconnect power before accessing the hidden port
Disconnect the Gateway Hub from power before opening the enclosure or accessing the hidden USB Type-C port.
Future product iterations or other Gateway Hub models may provide a more accessible version of the second port. The current default Gateway Hub design has the second port hidden internally.
If the port mapping is confirmed for the current hardware, use the following descriptions:
- Visible USB-C port: Power and Channel 1 setup/debug access
- Hidden internal USB-C port: Power and Channel 2 setup/debug access
Either USB-C port may be used to power the gateway.
Do not use two separate power supplies
Do not connect both USB Type-C ports to separate power supplies at the same time.
Power requirements¶
The Gateway Hub is powered through USB Type-C.
| Requirement | Value |
|---|---|
| Input voltage | 5 V DC |
| Connector | USB Type-C |
| Recommended power supply | 5 V / 2 A |
| USB-C Power Delivery | Not required |
| Power button | None |
| Shutdown procedure | Disconnect the USB-C power source |
The gateway may be powered through either USB Type-C port.
There is no separate power button. To turn off the gateway, disconnect the USB-C power source.
Estimated power consumption¶
The following values are preliminary engineering estimates. Actual power consumption may vary depending on Wi-Fi traffic, LoRa transmission activity, firmware behavior, and power-supply efficiency.
| Operating condition | Estimated consumption |
|---|---|
| Idle or light operation | 0.6-1.0 W |
| Typical Wi-Fi and LoRa operation | 1.0-1.8 W |
| Short-duration peak | Up to approximately 3.5 W |
Estimated values
These values are estimates and have not been presented as laboratory measurements.
Power LED¶
The Gateway Hub has a simple power LED.
- On: The gateway is receiving power.
- Off: The gateway is not receiving power.
The power LED does not indicate:
- Wi-Fi connection status
- LoRaWAN activity
- Uplink reception
- Downlink transmission
- TTN connectivity
- End-device application data
Power LED behavior
The power LED only indicates that the gateway is receiving power. It does not confirm that the gateway is connected to Wi-Fi or forwarding packets to TTN.
Firmware and provisioning¶
The Gateway Hub is shipped with:
- Pre-installed firmware
- Preconfigured LoRaWAN settings
- Default Philippine AS923 Group 3 configuration
- Wi-Fi provisioning support through BLE
Initial Wi-Fi setup is performed using the ESP BLE Provisioning app.
Both internal gateway channels must be provisioned to the same Wi-Fi network for normal dual-channel operation.
For full instructions, see Getting Started: Cubicore Gateway Series.
Internal controls and enclosure access¶
The Gateway Hub contains:
- RESET and BOOT buttons for each internal channel
- A screw-secured top button cover
- Two screws securing the top button cover
These controls are normally only needed when changing the Wi-Fi network or performing advanced setup and service procedures.
Disconnect power before opening the enclosure
Disconnect the Gateway Hub from power before removing the two screws or opening the top button cover. Do not work inside the enclosure while it is powered.
For instructions on changing Wi-Fi networks and triggering pairing mode, see Getting Started: Cubicore Gateway Series.
Recommended placement¶
The Gateway Hub is intended for desktop or shelf placement.
Recommended placement practices:
- Place the gateway on a stable, level surface.
- Use the built-in rubber feet.
- Keep the antenna clear of large metal objects.
- Avoid placing the gateway inside a metal cabinet.
- Leave enough space for the antenna and USB-C cable.
- Position the antenna according to the required polarization and deployment layout.
- Keep the gateway in a location with reliable Wi-Fi coverage.
- Keep the gateway and antenna dry and protected from unsuitable environmental conditions.
The Gateway Hub does not have mounting holes.
Do not describe the Gateway Hub as outdoor-rated or weatherproof unless separate product documentation confirms this.
Supported applications¶
The Cubicore Gateway Hub is suitable for:
- IoT prototyping
- Educational projects
- LoRaWAN development and testing
- Desktop IoT demonstrations
- Environmental monitoring prototypes
- Smart agriculture prototypes
- Asset and equipment monitoring prototypes
- Building and facility monitoring prototypes
- Laboratory and classroom deployments
- Small-scale LoRaWAN deployments
- Projects requiring an external LoRa antenna
The product is intended for indoor desktop or shelf installations unless additional deployment documentation specifies otherwise.
Package contents¶
The standard Gateway Hub package includes:
- Cubicore Gateway Hub
- 915 MHz blade antenna
- USB Type-C cable
- Power adapter
- Quick-start guide
The supplied antenna connects to the Gateway Hub through the RP-SMA connector.
Related guides¶
- Getting Started: Cubicore Gateway Series
- Set Up and Claim Your Cubicore Gateway
- The Things Network
- 915 MHz blade antenna datasheet
For support, email support@cubicore.io.
When contacting support, include:
- Gateway serial number
- TTN User ID, if applicable
- Description of the issue
- Screenshot of the error with sensitive information hidden
Do not send your TTN password or publicly share your gateway claim code.