The Things Stack Documentation

The Things Stack is a robust, yet flexible LoRaWAN® Network Server that caters to the needs of demanding LoRaWAN deployments, from covering the essentials to advanced security configurations and device life cycle management.

Getting Started

Get started with The Things Stack. If you’re new to The Things Stack and/or LoRaWAN, this is the place to start.

End Devices

Learn how to configure and manage LoRaWAN End Devices in The Things Stack.


Learn to connect and manage various LoRaWAN Gateways on The Things Stack.


Learn how to work with End Device data on The Things Stack and how to integrate with external systems.

The Things Stack

Learn about the different flavours of The Things Stack and how to install/access them.


Curated list of advanced topics for The Things Stack. Leverage the full customization capabilities of The Things Stack.


  • Experimental channel steering API, which allows steering end devices from the wide (250kHz or 500kHz) channels towards the narrow (125kHz) channels.
    • This API is mainly relevant for end devices operating in the US915 and AU915 regions, as they may join via a wide channel, but users may want to steer them towards the narrow channels.
    • The new settings can be found under
    • steers the end devices towards the LoRa modulated narrow channels.
    • does not steer the end devices - end devices are left to operate in their currently active channels, wide or narrow.
    • The default behavior is to avoid steering the end devices, but this is subject to change in future versions. Consider explicitly specifying a certain behavior (lora-narrow or disabled) if you depend on not steering the end devices.


  • Network Operations Center end device uplinks performance retention rate to 30 days.
    • This requires a database schema migration (ttn-lw-stack noc-db migrate) because of added table records.
  • Uplink and downlink message frequencies are now validated and zero values are dropped.
    • Such traffic would have always been dropped by the Network Server, but it is now dropped in the Gateway Server.
    • Simulated uplink traffic now requires a frequency value as well.


  • Multiple ADR algorithm bugs:
    • An off-by-one error which caused the ADR algorithm to not take into consideration the signal qualities of the uplink which confirmed a parameter change. In effect, this fix improves the quality of the link budget estimation.
    • A flip-flop condition which caused the algorithm to swap back and forth between a higher and a lower transmission power index every 20 uplinks. In effect, this fix will cause the algorithm to change the transmission power index less often.
    • A condition mistake which caused the algorithm to avoid increasing the transmission power if it would not completely fix the missing link budget. In effect, this will cause the algorithm to increase the transmission power in situations in which the link budget deteriorates rapidly.
  • In fixed channel plans such as US915 and AU915, the the associated wide (500kHz) channel is now enabled by default.

See what's new in V3.25.2