Skip to main content

ChirpStack v4 – ABP

This page explains how to register HARDWARIO STICKER as a LoRaWAN end device in ChirpStack v4 using ABP (Activation by Personalization), including the recommended device-profile settings and how to add a payload decoder.

Useful HARDWARIO docs:

info

Before registering your STICKER, make sure ChirpStack v4 is installed and running.

Installation instructions:
https://docs.hardwario.com/apps/chirpstack/chirpstack-installation

Prerequisites​

  • A working LoRaWAN gateway connected to ChirpStack v4 and configured for your region / frequency plan.
  • A ChirpStack v4 tenant with the gateway visible and online.
  • Your STICKER powered and within gateway coverage.

1) Collect the required LoRaWAN identifiers & keys​

Use the HARDWARIO STICKER NFC Configurator to get the required identifiers and keys for your STICKER.

You will need:

  • DevEUI
  • DevAddr
  • NwkSKey (Network Session Key)
  • AppSKey (Application Session Key)

In ChirpStack v4:
Tenant → Device Profiles → Add Device Profile Chirpstack create device profile

Next, configure the following parameters:

  • Name: Sticker - ABP (or your chosen identifier for the device)
  • MAC Version: LoRaWAN 1.0.4
  • Region: EU866 (or US915 if you are outside the EU)
  • Expected uplink interval: X (according to your STICKER firmware configuration) Chirpstack profile general

Go to the Join (OTAA / ABP) tab and verify that Device supports OTAA is toggled off. Chirpstack profile ABP

As the final step, add a codec to the device profile. Switch to the Codec tab, select JavaScript functions in the Payload codec dropdown, and paste the codec linked below into the input field:

Save the device profile by clicking Submit.

Generating downlink commands

Downlink command encoding is part of the upcoming STICKER firmware v1.4.0 (not in v1.3.x).

This codec also encodes downlink commands (via its encodeDownlink function), so no extra setup is needed. To send a command to the device, for example to force a report, change a setting, or set an alarm rule, enqueue it on the device's Queue tab as a JSON object on fPort 85 and ChirpStack runs the codec to produce the byte payload. Use the Downlink Commands Generator to build a command and get its JSON and hex.

3) Create an Application in ChirpStack​

In ChirpStack, go to Applications → Add Application and fill in the fields:

  • Name: Sticker (or any name of your choice) Chirpstack add Application

Save by clicking Submit.

4) Register the STICKER end device​

In your application:
Application → End Devices → Add End Device

Fill:

  • Name (human-readable)
  • Device EUI (DevEUI)
  • Device Profile → select the STICKER profile you created

Chirpstack add end device

Save by clicking Submit.

Activate the device (ABP)​

After creating the device, open the Activation tab of the device.

Fill:

  • Device address (DevAddr)
  • Network session key (NwkSKey)
  • Application session key (AppSKey) Chirpstack add ABP keys

Then click (Re)activate device.

  • Go to Applications → (your application) → Events
  • Check Up events
  • You should see:
    • raw payload bytes
    • decoded JSON fields (if the codec is correct)