New to RAK WisBlock, using basic starter kit with quick start guide sample app.
I’m trying to better understand the join process. As part of this I am “purposely” causing a join failure.
If I define 5 join retries via
#define JOINREQ_NBTRIALS 5
Then as expected I do see the 5 tries. At that point the runtime gives up trying, which it should, but how is the device app level to know it needs to restart the join process.
The app level is waiting for a joined handler callback, which will not come, the runtime level is not going to keep trying as it’s exhausted the retry count.
The app level could interrogate lmh_join_status_get() to find out the “current” join status, but it has no way to tell if the runtime has exhausted the retry count or just taking a long time.
Other than using an arbitrary time limit, giving up on the join, and re-initializing everything, is that a way I’m not seeing for the app level to “know” the join has failed??
Any sort of best practice?
I’m sure it’s more of a question for the LoRaWAN library implementation than for the WisBlock per-say.