Let me describe you my experiences with a custom Lora node (based on RN2483), a custom gateway (based on RAK833 concentrator) and the TTN server.
At the beginning of my project and for development purposes I kept the node always powered. I used OTAA as activation method and my node worked perfectly during 3-4 days until the TTN stopped accepting the data from the node. I learnt hat it was due to some kind of expiration of the OTAA session and that a OTAA join has to be issued every few days.Otherwise, the node, the gateway and the TTN server worked great.
Now a I would like to shut the power off my node between measures (including the RN2483). I read that a possible solution is to do an OTAA join and then after subsequent power-off sequeces use ABP joins and send the data. I did that and after some twiddling with the appkey, the devaddr and the upcnt registers of the RN2483, I managed to make it work.
The problem I’ve got with this configuration is that is only working for a few power-cycles. At one point the TTN server stops to show any new data from the node, but the node is still successfully joining with ABP and transmiting the data without errors in the RN2483. I think the problem has to do with the frame counter values in the node and in the server that for some reason are out of step but I have to checked that. Is that correct? Is there any possible solution to that problem?
Another issue I’m having is that in this situation (the node sending data and the TTN server ignoring it) I cannot reset the node for OTAA join because always denies it. The only way to recover from that is to kill and run the packet forwarder in the gateway. Is there any way to avoid that? Can I end an OTAA session from the server without having to reboot the gateway?
Thanks in advance