Skip to main content

Switch LoRaWAN Server by Rejoin

This page explains how to switch a LoRaWAN end node to another server by forcing it to rejoin the network.

Overview​

A LoRaWAN end node normally keeps the current join session after it has joined a network server. If you change the network server, device keys, or application settings, the device may need to rejoin before it can communicate with the new server.

When to Use This​

Use the rejoin method when:

  • The end node was moved from one LoRaWAN server to another.
  • The device keys or application settings were changed on the server.
  • The device remains joined to the old server session.
  • Uplinks are still visible on the gateway, but the new server does not process the device correctly.

Basic Procedure​

  1. Confirm that the new LoRaWAN server has the correct DevEUI, JoinEUI/AppEUI and AppKey.
  2. Confirm that the end node and gateway use the same frequency band and sub-band.
  3. Send a rejoin command or reset the device so it starts a new OTAA join process.
  4. Check the gateway traffic to confirm that Join Request packets are received.
  5. Check the server device page to confirm that Join Accept and new uplinks are processed.
  • If the device does not send Join Request packets, check the end node frequency band and battery/power status.
  • If the gateway receives Join Request packets but the server does not, check the gateway server address and packet forwarder settings.
  • If the server rejects the join, check the device keys on both the device and server.

See also LoRaWAN Communication Debug for a detailed join-process checklist.