I have installed the source in Platform IO; changed the device EUI, the OTAA keys and the region to EU868 (on the lmh_init call).
It compile OK and uploads to the device OK.
IT attempts to join Chirpstack and this request reaches there:
Sorry for reformatting your post, but it was difficult to read.
On Chirpstack, do you have created an application and do you have added the device?
This tutorial is not for WisBlock, but it shows the principle steps (on Chirpstack) you have to do to register the device in an LoRaWAN server application.
Hi,
thanks for replying
Yes, the device is already set up from previous tests I was doing.
I have just tried it again, but rather than looking at the LORAWAN packets I looked at the device data and discovered this (6 times):
[
{
“type”: “error”,
“payload”: {
“applicationID”: “2”,
“applicationName”: “app”,
“deviceName”: “Tracker-2”,
“devEUI”: “rB8J//4EYV4=”,
“type”: “OTAA”,
“error”: “join-server returned error: response error, code: MICFailed, description: invalid mic”,
“fCnt”: 0,
“tags”: {}
}
}
Apparently I have an invalid mic??? I have no idea what it means by this.
The original posters problem was that the DevEUI, AppEUI and/or AppKey was different on the device and in the device on the LoRaWAN server application.
The keys and EUI’s must be identical on both the device and the server, on both the node and the server these values are MSB.
What exactly is your problem, what LoRaWAN region are you using, what gateway, what LoRaWAN server?
If you have logs from the device, from the gateway and from the LoRaWAN server, that would be very helpful.
I’m using Chirpstack server with risinghf gateway. I use eu868 as my region and when i register the device in the application, the live data send was error and the lorawan frame only join request.