Guide · LoRaWAN provisioning
AU915 and The Things Network: the settings that stop your node joining.
You've registered the device on The Things Network, powered it up, and the console shows nothing. No join request, no activity, no errors. The node sits there flashing its LED as if everything is fine. Nearly every dead-on-arrival LoRaWAN node we've had on the bench came down to one of a short list of settings, and most of them trace back to how Australia's frequency plan works. This page is the checklist we run before assuming a device is faulty.
Last reviewed: 18 July 2026 · by Alien IT Solutions
Why Australian nodes fail more than most
Australia uses the AU915 frequency plan: 72 uplink channels spread across 915–928 MHz. No gateway listens to all 72. The Things Network expects devices on sub-band 2 (channels 8–15, often labelled FSB2), and a typical 8-channel gateway hears only that slice.
Most LoRa devices ship with a default that doesn't match. Some default to US915, some to AU915 sub-band 1, some to a mode that hops across all 72 channels. A node on the wrong sub-band transmits its join request into spectrum nobody is monitoring. Nothing is broken, so nothing reports an error. The device transmits into the void, forever, and the console stays blank.
That's the shape of almost every join failure: the node and the gateway are each working, on settings that never intersect.
The join-failure checklist
Run these in order. Stop at the first one that's wrong.
1. Antenna actually attached
Check this first because it's the one that damages hardware. Transmitting without an antenna can destroy the radio's output stage, and a node with no antenna may still join at bench range, then fail in the field. Screw the antenna on before first power-up, every time, and check the connector actually seated: some SMA/RP-SMA mismatches feel tight while making no contact.
2. Region set to AU915
Not US915, not EU868, not "auto". US915 overlaps the same band and looks plausible in a config menu, but the channel plan differs and joins will fail or misbehave. Set the region explicitly in the device firmware or its serial config.
3. Sub-band set to FSB2
The setting that catches almost everyone. Depending on vendor it's called sub-band 2, FSB2, channel mask 8–15, or CHE=2 on some serial-configured devices. Set it to match your gateway and TTN's AU915 plan. If the vendor tool only offers a channel mask, enable channels 8–15 and disable the rest.
4. Keys entered in the right byte order
OTAA needs the DevEUI, JoinEUI (AppEUI) and AppKey to match exactly between the device and the TTN console. Two traps.
Byte order. Some vendor tools want the EUIs MSB-first, others LSB-first. The TTN console can display either: use the byte-order toggle and match it to what the vendor tool expects. A reversed DevEUI produces a join request TTN silently ignores.
Transcription. Generate the AppKey in the console and copy-paste it. Hand-typed 32-character hex strings fail often enough that we no longer type them.
If the console shows join requests arriving but no accept, keys are your problem. If it shows nothing at all, go back to region and sub-band.
5. Distance for the first join
Don't attempt the first join with the node sitting on top of the gateway. A transmitter half a metre from a receiver designed to hear -120 dBm signals overloads the front end, and joins fail in a way that looks identical to a range problem. Move the node to another room, or at least several metres and a wall away. The sweet spot for bench joins is roughly 5–20 metres. Only after a clean join at that distance should you take it to the far paddock.
6. Serial config at the right baud rate
Many nodes are configured over a USB serial connection, and the terminal has to match the device's UART speed. The trap from our bench: the vendor documentation and half the forum posts said one thing, and the device actually wanted 115200 baud, not 256000. At the wrong rate you get garbage characters or dead silence, which is easy to misread as a broken device or cable. If the serial console prints rubbish, cycle through 115200 first, then 9600, before blaming hardware.
Once it joins: skip the custom decoder
Uplinks arrive at TTN as raw bytes, and normally you'd write a JavaScript payload decoder to turn them into readings. If your device supports CayenneLPP payload format, use it. CayenneLPP is a self-describing encoding: temperature, humidity, digital inputs and GPS all have standard type codes, and TTN decodes it natively. Select the Cayenne payload formatter in the device settings on the console and named, typed values appear with no decoder written at all. For a farm sensor reporting a handful of readings, it removes an entire category of bugs.
The five-minute reset
When a node has been fiddled with past the point of knowing its state: factory-reset it over serial, set region AU915, set sub-band FSB2, re-enter the keys by paste, confirm the antenna, and join from the next room. That sequence has recovered every "dead" node we've bench-tested that wasn't genuinely hardware-faulty.
Once it joins and the readings flow, the next thing to watch is the link itself: a node can report perfectly and still be unreachable for configuration. That failure mode has its own page: your uplinks arrive but your downlinks don't.
The short version
Australian LoRaWAN nodes fail to join TTN mostly because of one setting: the AU915 sub-band. TTN expects FSB2 (channels 8–15) and most devices ship on something else, transmitting where no gateway listens. Work the checklist in order: antenna on, region AU915, sub-band FSB2, keys pasted in the right byte order, first join from a few metres away, serial console at 115200. Then use CayenneLPP so you never write a payload decoder.
General guidance from bench experience: check your device's own manual for its exact configuration commands.
Who works this out for you
Long Range WiFi is a service of Alien IT Solutions, 18 years of networks and wireless in places without a power point in sight. LoRa nodes and gateways get configured on the bench before they go up the hill; for the wider picture, start with the long-range wireless guide.
Got a node that won't join?
Tell us what the device is and what the console shows. We'll run the checklist, get it joined, and hand it back configured for the paddock it's going to.
Get a quote