What exactly is the problem. From the screenshot it seems like the node has successfully connected via OTAA. What exactly do you want to do?
Which manual are you referring to?
The problem is that the node never gets activated. It goes into a loop of JoinRequest/JoinAccept pair of messages and never finishes properly. The device shows “This device has not (yet) been activated.” in its Activation tab on the web interface. Actually, if you notice on the serial communication, an “OK” is issued in response to “at+join=otaa”, but it should also send “at+recv=3,0,0” (3 = STATUS_JOINED_SUCCESS), which I believe confirms joining.
Instead, after 8 minutes of trying I receive: “at+recv=6,0,0” (6 = STATUS_RX2_TIMEOUT) instead (this is not shown in the screenshot I posted earlier). Dureing those 8 mins, no AT commands can be send to the node (it isn’t responding, as it is waiting for the resulting at+recv message).
Hmm, are you sure you have the MSB, LSB, formating of the keys right. Loraserver is different than TTN. I just flashed anode to make sure and it had no issues. True I got no response on join but I was able to send packets without problems. Could you double check the keys.
I just swapped the app_key’s endianess and sent it via set_config and now loraserver generates a processing uplink frame error: “join-request to join-server error: response error, code: MICFailed, description: invalid mic”. If I send it as I had it the server accepts it.
Which firmware did you f;ash your node with? Are you able to get it “activated” ?
I see now that I receive an “at+recv=3,0,0” after roughly 4-5 minutes, but the device is still not activated on the web ui of the lora server.
Same as yours, but I use TTN. I have had this issue with other nodes from other manufacturers before too.
Just to make sure, do you receive repetitive join requests or 1 join request and 1 join ack and you are still not connected?
I receive many JoinRequests and JoinAccept messages for the entire duration until an at+recv=X,0,0 response shows up in the serial console. I actually moved the devices around and switched off some equipment in proximity and the node managed to activate once.
Yet, when I retry to at+join=otaa again it still takes several minutes for the OTAA negotiation and it can be unsuccessful. Is that like a normal timeframe and behavior?
The gateway and node are around 50 meters apart within a building. Should I expect faster and more robust comms, or is this typical?
Is it ok to use it like this?
The node is equivalently used at its default config (its included antenna has a sticker writing 868 Mhz) as in the product picture.
I am testing inside a building and sure there are walls and doors, but building materials are normal concrete/bricks; it should work at a range of 30-50 meters right?
It should indeed work through the walls, even outside a couple of hundred meters outside of the building at least. I Believe the issue is not in the hardware as you get the join accept, right ?
Have you tried ABP, or TTN, just so we know if the issue is only in the case of LoRa Server OTTA?
Yes, you said earlier that you did connect successfully. Can you connect the information sent by the server at the moment of your successful connection?
I managed to find something in the logs (at 22:41). That is the only instance where a successful negotiation has been established, but I don’t quite remember what I was doing at that moment.
What about logs for the unsuccessful ones.
By the way have you verified all of the LoRa Server Setings, The gateway and device profiles. LoRaWAN 1.0.2, Class A, etc.
Can you post your configuration parameters for both the LoRa Server and Node in detail?
Thank you.
If you have modified the configuration as shown in the figure, and you can see from the logo that you have successfully connected, then do you try to send data through the node?
I have done minor modifications on the default configs of loraserver 3, but I just reverted all configs to defaults. Still the same problem, join request/accept loop.
Can someone at least confirm the firmware and Wisnode versions that are known to work? As I already wrote Wisnode is v1.2 and its loaded firmware: v2.0.3.4.
Should I try to load another firmware?
Is there some sort of delay I should add to the loraserver to make it work?
Is there any documentation at all on what a successful negotiation looks like? A sample log of the kit working properly?