# How to handle an automatic re-join process?

**URL:** <https://www.thethingsnetwork.org/forum/t/how-to-handle-an-automatic-re-join-process/34183>\
**Category:** Hardware\
**Created:** [February 8, 2020, 10:49am UTC](https://www.thethingsnetwork.org/forum/t/how-to-handle-an-automatic-re-join-process/34183 "2020-02-08T10:49:23Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [February 10, 2020, 1:51pm UTC](https://www.thethingsnetwork.org/forum/t/how-to-handle-an-automatic-re-join-process/34183/11 "2020-02-10T13:51:57Z")

</div>

> [@ledi007](#):
>
> In this case i want to check the status byte from RN2483 every hour. Bit number 4 shows the Join status (‘0’ – network not joined, ‘1’ – network joined).

For future readers: that’s unlikely to ever change from “joined” to “not joined”, like [has been discussed elsewhere](https://www.thethingsnetwork.org/forum/t/rn2483-how-to-handle-if-connection-to-ttn-is-lost/30956/19).

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/how-to-handle-an-automatic-re-join-process/34183)._