Single Channel Packet Forwarders (SCPF) are obsolete and not supported

Single channel packet forwarders are obsolete and are not supported

Single Channel in this article refers to both Single Channel and Dual Channel devices (and any variations thereof).

Single Channel Packet Forwarders are not LoRaWAN compliant gateways.

They negatively impact proper operation of gateways and end devices (nodes) in their area which means they negatively impact The Things Network and its users, but they also impact other LoRaWAN operators. Not only now, but also in the future when new nodes and new gateways are added in the area.

Single Channel Packet Forwarders are often called Single Channel Gateways which is incorrect, confusing and misleading. They shall not be called gateways.

Be aware that some vendors will try to sell Single Channel Packet Forwarders as a gateway which they are not. These cannot be used as gateway for The Things Network.

NOT supported also means that Single Channel Packet Forwarders may no longer work after the community network will be migrated to V3.

Only LoRaWAN compliant gateways are supported by The Things Network.


Years ago in the early days of The Things Network, LoRaWAN gateways were very expensive and out of reach for many. In those days a Single Channel Packet Forwarder was an affordable alternative to start experimenting with the technology and The Things Network.

During recent years much cheaper and much more affordable gateways have become available. The Things Indoor Gateway costs around €85 (VAT included) and there are many options for both DIY and commercial gateways in the price range from €120 to €200. There is even an outdoor gateway for around €160.

In the last years many gateways have been deployed worldwide and network coverage has become available in many areas on the globe. The effect and importance of the negative impact of Single Channel Packet Forwarders on successful operation of the network and its users has substantially increased with the growth of the network.

Therefore Single Channel Packet Forwarders are now deprecated, their use is condemned by The Things Network and they are no longer supported on The Things Network Forum.

Connecting Dragino LG01 Gateway
Single-channel operation of LoRaMAC with Dragino LG01-N
Can LMIC 1.6 be set up to use a single channel and SF?
Can I avoid data being shown in other gateways' Traffic in TTN Console?
The LIBRARY basement part 11
Single channel gateway on RPi on Private network
Big ESP32 + SX127x topic part 3
Problem connecting ESP32
Data in Gateway but not on Application console
No data transfer to sensor node in V3
Customized Frequency for Single Channel Packet Forwarder
Beginner: Raspberry PI SX162 SX1302 Gateway
Problem with sending join accept on dragino lora hat gateway single_chan_pkt_fwd to my node
LMIC delay of 12 minutes (720 seconds)?
About the [obsolete] SCPF-related category
Fail to send webhook to ThingSpeak problem?
How can I register a deleted SCPF?
Unable to join ttn. Gateway receive the message
How can I register a deleted SCPF?
Heltec WIFI Lora v2
Imposible to get Data from LSE01
Rspi and RN2483 gateway a single channel
Join request to TTN with atmega and sx1276
Failure to receive packets from my devices on thethingsnetwork application
Connecting an an end divice
Problem getting my first node working
Gateway is flooded with packets Augsburg
My Dragino LoraWay LG02 is not connected
Unknown Traffic on my Gateway
How to use FiPy nano-gateway connection to send sensor data to TTN
My new Gateway does not pass data to the Application
OTAA join failed for SF10
LG01-P Dragino with Heltec Esp32
How to store data if connection drop with dragino LG01?
The future of single-channel gateways
Host cluster failed to handle message: no device matches uplink
RPI with dragino HAT Gateway Status Connected but not able to see the data stream in traffic view