Console guide
The console is a web app the gateway serves itself, over HTTPS, from its ethernet port, LAN ports, USB cable or setup AP. There is no LuCI. The terminal UI has the same pages for serial, SSH, HDMI and USB.
A page appears only on a board built with its feature: a router has no LoRaWAN page, and a RAK unit has no LAN page. The feature list per board is on each hardware page.
Signing in
Section titled “Signing in”| Gateway state | Sign in with |
|---|---|
| Unadopted | the local password (initial password first, then yours) |
| Adopted, online | your cloud account |
| Adopted, offline | offline recovery: a challenge the cloud signs, read off a phone |
Why it works this way is in Authentication and SSH.
Overview
Section titled “Overview”The gateway at a glance: uplink in use, LoRaWAN and radio state, resources, firmware version, OpenWrt and kernel.
Connectivity
Section titled “Connectivity”| Page | What you do there | Feature |
|---|---|---|
| Backhaul > Ethernet | DHCP or a static address on each wired uplink, and its VLAN | every board |
| Backhaul > Cellular | APN, on or off, signal and the modem’s state | cellular |
| Backhaul > WiFi | scan and join a network, see why it is not online, sign in to a captive portal | wifi |
| Network > Ports | each port an uplink, a LAN port or unused; tagged VLANs. Undone unless confirmed. | every board |
| Network > LAN | clients, reservations, per-device policy and cellular rule, exposed ports | lan |
| Network > Uplinks | uplink order, health tracking and failover | failover |
| Network > DNS | upstream servers, local names, rebind protection, dynamic DNS | dns |
| Network > Speed Test | a test out of each uplink, never cellular | speedtest |
| Access | the setup access point and its passphrase, the management tunnel | every board |
Details: Networking, Setup access.
Radios
Section titled “Radios”| Page | What you do there | Feature |
|---|---|---|
| LoRaWAN > Forwarders | each concentrator slot: detected part, gateway ID, packets, the LNS broker it publishes to | lorawan |
| LoRaWAN > Settings | region plan, bus and reset line on kit boards, uplink delivery over cellular | lorawan |
| WiFi | each radio, what runs on it, the path from the internet to its clients; channels, access points, the uplink’s radio, a repeater. Undone unless confirmed. | wifi |
| Bluetooth | the adapter and what it forwards | bluetooth (the pulzr-ble add-on) |
| GNSS | receiver, live fix and recorded position | gnss |
On fixed hardware (RAK units) the radio settings are read-only: the hardware cannot change. Details: Concentrators and GNSS, Bluetooth, WiFi radios and repeaters.
Gateway
Section titled “Gateway”| Page | What you do there |
|---|---|
| Panel | each light on the board and what it shows now, the blink codes, the reset button |
| Logs | the system log, filtered and followed live |
| System > Resources | CPU, memory, temperature, storage, processes |
| System > Maintenance | firmware upgrade, the local password, add-ons, reboot |
Upgrading from the console: Firmware updates and signing.
Developing the console
Section titled “Developing the console”The console is React, built to static files by build.sh and served by uhttpd over a ucode API.
cd consolenpm installnpm run typecheckPULZR_GATEWAY=https://<gateway-ip> npm run dev # against a real gatewayIts text follows the rules in CLAUDE.md: no subtitles, no explanatory paragraphs on screen, no emoji, write for a technician.