Problem with downlink in v4 rest-api contexte

ChirpStack Network Server
1

When I send to chirpstack rest api downlink enqueue wth data

data : “EUe/ASAK” (B64(1147BF01200A))

I see in the Chirpstack queue e1e6ff00 as a value

I also try to use hex string instead of B64 … basically the value is looking the same and not the right one.

Any idea ?

2

Apparently this is related to the presence of object field in the payload:

{
    "queueItem" : {
        "confirmed" : false,
        "data" : "EUe/ASAK",
        "fPort" : 2,
        "object" : {}
    }
}

gives a wrong value

{
    "queueItem" : {
        "confirmed" : false,
        "data" : "EUe/ASAK",
        "fPort" : 2,
    }
}

gives a correct value.
It’s not easy to remove a field from a structure in language like Java, so it would be interesting to consider empty or null value for object field as absence of it.

3

Are you using the Java SDK files from the ChirpStack repo to generate the JSON?

4

N, i rereacted the models

5

But then there shouldn’t be an issue to just leave the object field out? You can just remove it from your Java struct and encode it to JSON without the object field being present.

6

Yes, I’ve managed it, it’s not a blocking issue but it’s more a strange behavior, eventually it should return an error of the best would be to get the data field when object is empty.