Hi,
It depends on what you mean by âapplication serverâ and âdecrypting application dataâ. ChirpStack 4 is a network server, and you can send âraw payloadsâ to a third-party application server through integrations if you wish.
Yes, I can, but i cannot activate a module without entering the AppSKey if the activation is ABP, and that causes the decryption of the FRMPayload. Which means, I cannot send âraw payloadâ directly via integration.
âApplication Dataâ is âFRMPayloadâ, and âapplication serverâ is already defined in the LoRaWAN Backend Interface. In Chirpstack version 3, all servers were distributed but for chirpstack 4 they are all combined and I want to seperate the application server.
Iâm unable to retrieve the raw payload (frmPayload) that the ChirpStack Gateway Bridge sends to the MQTT broker, or that the MQTT broker sends to ChirpStack in version 4.
When the frmpayload is recieved by ChirpStack, it does decrypt the message to something like this:
When I set up an HTTP integration in application to my project, the payload I receive is something like the json in image, does not include the raw frmPayload. Instead, it only contains the decrypted data.
@Jerome73 , could you show me how to configure an integration so that the raw frmPayload (the payload before decryption) can be sent?
And if youâre unaware, the relevant MQTT gateway topic bconway is referring to would be your region prefix. i.e mosquitto_sub to âus915_1/#â instead of âapplication/#â to receive the messages directly from the gateway bridge. Although if you are looking for full end to end encryption you would have to do a lot more like setting up an external join server.
Thank you for your fast responses. Yes I am aware of subscribing MQTT broker to receive frmPayload, what I am trying to achieve is not to use appSKey (decrypt the message) but validate MIC and integrate with my project via HTTP