Sparkfun IoT Node for LoRaWAN don't connect to Chirpstack

Wireless & IoT Digi XBee
1

Hi!, I have a Sparkfun IoT Node for LoRaWAN board with an XBee module and I am trying to get it to connect to the Chirpstack that I have running on a Linux docker instance through
a Kerlink Wirnet iFemtoCell Gateway.
The board has the data about Network Key, Application Key and the Application EUI, those same values except the Network Key are registered in the device
that you register in Chirpstack.

In the gateway I can see the Sparkfun board data and in Chirstack I can see the JoinRequest of the board, but the JoinAccept does not happen because
it gives the following error:

Details: 2025-05-26 07:02:52
time:“2025-05-26T05:02:52.312870545+00:00”
level: “ERROR”
code: “UPLINK_MIC”
description: “MIC of join-request is invalid, make sure keys are correct”
deduplication_id:“710e78af-2c8d-4742-8381-4ad8dcd3237a”

I saw sometime ago in the IoT for Solution Congress in Barcelona the board connected to the Digi gateway, can I only connect to the Digi gateway? I don’t think so.
I need some help to see what is happenning.

Data of the board:
SparkFun IoT Node LoRaWAN (c) 2023-2025 SparkFun Electronics
Version: 01.01.00 - build 00002c

Settings
1) Enabled - Enable or Disable the LoRaWAN Network connection : true
2) Application EUI - The LoRaWAN Application EUI : 4E11771276E0F41E
3) Application Key - The LoRaWAN Application Key : ********************************
4) Network Key - The LoRaWAN Network Key : ********************************
5) LoRaWAN Class - The LoRaWAN operating class : C
6) LoRaWAN Region - The LoRaWAN operating region : EU868

2

Did you try to test the board according to this hookup guide? Quick Start Guide - SparkFun IoT Node for LoRaWAN® Hookup Guide

3

Hello Dilshana,
I don’t have the gateway from Digi International, that’s the reason I’m trying to connect throw other Gateway. The board was a gifts during the Congress in Barcelona.

This is the diagram of I’m doing.

diagram
diagram800×200 45.7 KB

4

Eh, after rummaging a bit I think it might be one of a few things:

  1. Check that the LoRaWAN version on the board matches the one expected by ChirpStack
  • The SparkFun board reports version 01.01.00, which might imply LoRaWAN 1.0.1.
  • ChirpStack supports multiple LoRaWAN versions (1.0.1, 1.0.2, 1.0.3, 1.1).
  • In ChirpStack, go to your device profile and make sure it’s set to LoRaWAN 1.0.1 (not 1.1 unless you’re sure the device supports it).
  1. Confirm the keys are properly configured
  • LoRaWAN 1.0.x uses:
    • Application EUI (AppEUI)
    • Application Key (AppKey) — used to verify Join MIC
  • LoRaWAN 1.1 adds a JoinEUI and NwkKey, which the SF board mentions, but it may not be used depending on the LoRaWAN version.
  1. Check that AppEUI is in MSB format
  1. “…those same values except the Network Key are registered in the device that you register in Chirpstack.” – This may be the issue: If ChirpStack is expecting LoRaWAN 1.1 but your board is sending 1.0.1, then only the AppKey should be used — not a separate NwkKey. Double-check the device profile version and see :slight_smile: