Does a node ever need to rejoin after OTAA?

[arjanvanb (Arjan)]

@catuin

can this be detected via the downlink response given by the backend

…or the lack of such response.

When rolling out a lot of nodes we will (also) use the lack of some specific response (like receiving an ACK or downlink at least, say, every 48 hours), to start a join again. We want this to allow for switching networks:

How can an operational node be triggered to join a different network?

I know “commonly used” is vague, but: do commonly used LoRaWAN modules/libraries (such as used in the TTN UNO) make it easy to change networks? For Over-the-Air Activation (OTAA) the LoRaWAN R1.0 specifications only define: An end-device has to go through a new join procedure every time it has lost the session context information. I guess an application could use a node’s downlink receive window to tell it to commence a new join procedure, or a node could do that when it’s not getting any r…