LGW915SH Quick Start Guide

1. Product Overview

1.1 What Is This Product?

The LGW915SH is a mini indoor IoT gateway built on LoRaWAN® low-power wide-area network (LPWAN) technology. Supporting global LoRaWAN frequency bands, it connects up to 100 LoRaWAN end nodes and quickly establishes a LoRaWAN low-power private network for small industrial environments, with a coverage range of up to 500 m.

With built-in LoRa and Wi-Fi antennas in a compact housing, the gateway connects to the wide area network via Wi-Fi or Ethernet and forwards node data to the cloud, enabling remote IoT data monitoring. It is designed for small industrial environments such as workshops, warehouses, and small plants.

The gateway uploads data to the cloud via Wi-Fi or wired Ethernet. It is compatible with mainstream LoRaWAN network servers (such as ChirpStack and The Things Stack), and also provides a built-in network server (NS) with on-gateway terminal management, so you can deploy your own IoT applications quickly and flexibly. In this guide, the gateway is used with the AdoModel LoRaWAN NS cloud platform (http://adomodelcloud.com:4560/).

Key features at a glance:

• Global LoRaWAN bands, up to 100 nodes — 8-channel full-duplex SX1302 transceiver, connects up to 100 LoRaWAN end nodes.
• Built-in antennas — LoRa and Wi-Fi antennas integrated; nothing to install.
• Private LoRaWAN network in minutes — coverage up to 500 m, ideal for small industrial sites.
• Built-in NS with terminal management — add OTAA/ABP end devices directly on the gateway.
• Flexible backhaul — Wi-Fi (2.4 GHz only) or wired Ethernet.
• Open ecosystem — works with mainstream LoRaWAN network servers, the built-in NS, or third-party IoT platforms.

1.2 Where the Gateway Fits in Your System

The gateway is one link in a complete data chain. Figure 1 shows a typical AdoModel IoT deployment and the role of each component.

How data flows through the system

• Uplink: field sensors report their readings over an RS485 cable to a LoRaWAN-DTU, which packages the data into LoRaWAN frames and transmits them over the air. The gateway receives these radio signals and forwards them — via Wi-Fi or wired Ethernet — to the cloud, where the AdoModel LoRaWAN NS platform decodes them into application data.
• Downlink: commands sent from the platform travel the reverse path. The gateway transmits them over the air to the DTU, which outputs them through its RS485 port to the sensor or controller.

The role of each component

1.3 What This Guide Helps You Accomplish

This guide walks you through everything needed to get a single gateway from the box to a working connection with the AdoModel LoRaWAN NS platform. Follow the chapters in order; by the end you will have:

• unpacked and verified the shipment (Chapter 2);
• familiarized yourself with the interfaces and indicators (Chapter 3);
• powered the gateway and connected it to the Internet via Ethernet or Wi-Fi (Chapters 4–5);
• opened the gateway web console and verified its platform connection settings (Chapters 6–7);
• seen the gateway appear online on the AdoModel LoRaWAN NS platform (Chapter 8);
• learned what the platform can do for you once the gateway is online (Chapter 9).

If anything does not work as described, turn to Chapter 10 (Troubleshooting).

Connecting end-node devices (e.g., a LoRaWAN-DTU with sensors) to the network is covered in a companion document, the LoRaWAN-DTU Quick Start Guide.

The gateway itself never interprets your sensor data — it simply relays LoRaWAN frames. All intelligence (decoding, device management, integrations) lives in the NS platform. This separation is what allows one gateway to serve thousands of heterogeneous devices.

2. Packing List

Unpack the box and verify the shipment contains the following items:

• LoRaWAN Type III Mini Indoor Gateway ×1
• Power Adapter ×1
• Type-C Data Cable ×1
• Factory Reset Pin ×1
• Certificate of Conformity
• Quick Installation Manual

3. Interfaces and Indicators

The interfaces are arranged on the rear of the device. Figure 2 shows the layout; the tables below list each interface and indicator.

Interface definitions

Status indicators (LED)

After power-on, a solid red indicator with the green indicator off or blinking means the gateway is ready for first-time configuration through the gateway hotspot (Section 6.1). The green indicator turns solid once the network connection is established.

4. Installation and Power

No special tools are required. The gateway needs no antenna installation.

4.1 Powering the Gateway

1. Plug the included power adapter into the DC jack on the rear of the gateway and into a wall outlet.

4.2 Connecting the Network (choose the backhaul)

Choose a backhaul for the network connection:

1. For Ethernet backhaul: connect a network cable from your router or switch to the RJ45 port. A solid green light on the port indicates a successful connection (Figure 3).
2. For Wi-Fi backhaul: no cable needed — configure the Wi-Fi connection on the gateway web console (Chapter 6 → Network → WiFi).

4.3 Reset (if needed)

1. Use the supplied factory reset pin to press and hold the reset pinhole for 5 seconds. The device is restored to factory settings and all configurations are cleared.

5. Power On & Network Backhaul

The gateway supports three backhaul options:

5.1 Post Power-On Checks

• The power adapter is connected and the device is powered.
• The Ethernet cable is firmly seated (if used); the Ethernet port LED is solid green.
• The green status indicator is solid once the gateway has obtained an IP address and the network connection is up.

Once powered and connected to the Internet, the gateway automatically starts sending data to the NS platform. In a good network environment the gateway comes online within 1–3 minutes of power-on (up to ~5 minutes). You will verify this on the platform in Chapter 8, after checking the web console settings in Chapters 6–7.

6. Accessing the Gateway Web Console

The gateway is managed through a built-in web console. The mini indoor gateway differs from the other AdoModel models: its console is reached primarily through the gateway’s own Wi-Fi hotspot. There are three ways to reach it:

• Option 1 — Gateway Wi-Fi hotspot: connect your computer to the gateway’s built-in hotspot and open the console at 192.168.4.1. Works out of the box, no network infrastructure needed.
• Option 2 — Ethernet via your LAN: connect the gateway to your router or switch and look up its IP address with the supplied LoraGW_IPScan tool.
• Option 3 — Remote access via the CMP platform: if the gateway is already online, open its web console remotely through the AdoModel IoT Management Platform (CMP) without going on site.

6.1 Option 1: Gateway Wi-Fi Hotspot

For first-time setup, the gateway broadcasts a Wi-Fi hotspot with default settings:

1. On your computer, find the gateway’s Wi-Fi hotspot and connect to it with the password above.
2. Open a browser (Chrome recommended) and enter http://192.168.4.1.
3. Log in with the default credentials: root / admin.

6.2 Option 2: Ethernet via Your LAN

1. Connect the gateway’s Ethernet port to your router or switch (Section 4.2).
2. Make sure the network has DHCP enabled — the gateway obtains its IP address automatically.
3. On a computer connected to the same LAN, use the supplied LoraGW_IPScan tool to find the gateway’s IP address. The tool can be downloaded from www.adomodeltech.com or obtained from your account manager.
4. Enter the IP address in a browser to access the web console.

6.3 Option 3: Remote Access via the CMP Platform

1. Log in to the AdoModel IoT Management Platform (CMP): http://adomodelcloud.com/ (account provided by your account manager).
2. Click “Device Management” to expand the menu, then click “Group”.
3. Enter the gateway ID (IMEI) in the search box and click “Search”.
4. Click “View” on the found device.
5. Under the operation column, click “Remote Configuration” (Figure 5).
6. Confirm the device status is “Online”, then click “Enable Remote Connection”. Wait until a dialog confirms success and shows the “Open Configuration Page” and “Close Remote Connection” buttons.
7. Click “Open Configuration Page” — the gateway web console login page opens.

7. Connecting to the AdoModel Platform

7.1 Verifying the NS Settings

The gateway is factory-configured for the North American band (US915) and for the AdoModel LoRaWAN NS platform. In most cases you do not need to change anything — just verify that the settings match the table below.

1. Open the gateway web console (Chapter 6).
2. Go to “Gateway Configuration” → “NS Network Server Settings”.
3. Verify the following values:

7.2 Using the Built-in NS

The gateway also provides a built-in network server: set the server address to 127.0.0.1 with uplink port 1780 and downlink port 1782, and you can add OTAA/ABP end devices directly on the gateway (Terminal Management). This is useful for standalone deployments without a cloud platform. See the LGW-SH Gateway Web Configuration Guide for details.

7.3 Using a Different Network Server

If you operate your own LoRaWAN network server (e.g., ChirpStack or The Things Stack), enter its address and ports on the same page. Frequency-plan customization is beyond the scope of this guide — see the LGW-SH Gateway Web Configuration Guide.

8. Verifying the Gateway Is Online

8.1 Log In to the NS Platform

1. Open http://adomodelcloud.com:4560/ in your browser.
2. Log in with the account provided by your account manager.

8.2 Check the Gateway Status

1. Click the “Gateway” tab on the left side.
2. Enter the gateway MAC ID in the “Search” box and locate your gateway (Figure 6). If it does not exist, click the “CREATE” button in the upper left corner to create it.
3. Check the status dot:
   • Green dot — the gateway is online and connected to the platform. You are done with this guide’s setup path; continue to Chapter 9 to learn what the platform offers.
   • Red dot — the gateway is offline. After power-on (or a new registration), the gateway typically comes online within 1–3 minutes in a good network environment, and within about 5 minutes at most. If it is still offline after 5 minutes, see Chapter 10.

8.3 Alternative Check via CMP

You can also confirm that the gateway has Internet access from the CMP platform (http://adomodelcloud.com/): search the gateway IMEI as described in Section 6.3; an “Online” status means the backhaul link works. If the gateway is online in CMP but offline on the NS platform, re-check the NS settings of Chapter 7.

9. What the Platform Can Do for You

Once your gateway is online, the AdoModel LoRaWAN NS platform is your window into the network. Highlights:

• Applications & device management — organize end-node devices into applications; register devices, manage activation keys (OTAA), and monitor device status.
• Live Data — view decoded application data from your devices in real time.
• Live LoRaWAN Frames — inspect raw LoRaWAN protocol frames (e.g., JoinRequest / JoinAccept) for network debugging.
• Downlink control — send commands to devices from the platform (e.g., through the downlink tool).
• Integration — retrieve your data via standard RESTful APIs and MQTT subscriptions for custom application development.

A quick end-to-end walkthrough — registering the gateway and a LoRaWAN-DTU node, and testing uplink/downlink data — is provided in the companion LoRaWAN-DTU Quick Start Guide. The complete platform documentation is available separately (AdoModel NS Platform User Guide).

10. Troubleshooting

For further assistance, contact your agent or sales representative, or visit www.adomodeltech.com.

Appendix A: Specifications

Key specifications of the gateway (from the LGW-L-III Product Specification; refer to the full specification sheet for details):

Appendix B: Default Parameters

Regulatory Compliance

Related Documents

• LoRaWAN-DTU Quick Start Guide — end-to-end system setup: gateway + DTU node + platform, uplink/downlink testing.
• LGW-SH Gateway Web Configuration Guide — complete reference for the gateway web console (advanced network, LoRaWAN, and system settings).
• AdoModel LoRaWAN NS Platform User Guide — complete reference for the NS platform.