Hi datnus, i’ve realized that, the enqueue API doesn’t change enough (API queue definition for POST starts at line 846 - chirpstack-rest-api/device.swagger.json at master · chirpstack/chirpstack-rest-api · GitHub).
If I enqueue a payload with MQTT and execute the GET method with curl to this chirpstack-rest-api: curl -X GET --header ‘Content-Type: application/json’ --header ‘Grpc-Metadata-Authorization: Bearer my_API_KEY’ --header ‘Accept: application/json’ ‘http://<IP_chirp_stack_rest_api>:8090/api/devices/xxxxxxxxxxxxxxxx/queue’ , it results something like this: {“id”:“aaaaaaa-aaaa-aaaaa-aaaaaaaa”,“devEui”:“xxxxxxxxxxxxxxxx”,“confirmed”:false,“fPort”:5,“data”:“MQ==”,“object”:null,“isPending”:false,“fCntDown”:0}. So, It works OK.
Now If I use the chirpstack-rest-api in order to enqueue executing this curl command: curl -X POST --header ‘Content-Type: application/json’ --header ‘Grpc-Metadata-Authorization: Bearer my_API_KEY’ --header ‘Accept: application/json’ -d ‘{“deviceQueueItem”:{“confirmed”:false,“fPort”:5,“data”:“EA==”}}’ ‘http://<IP_chirp_stack_rest_api>:8090/api/devices/xxxxxxxxxxxxxxxx/queue’ , it shows the ID and and entry is showed. If I execute the GET method with curl it returns the new entry with this behavior of fPort:0 and data:"" :
{“id”:“bbbbbbb-bbbb-bbbbb-bbbbbbbb”,“devEui”:“xxxxxxxxxxxxxxxx”,“confirmed”:false,“fPort”:0,“data”:"",“object”:null,“isPending”:false,“fCntDown”:0},
{“id”:“aaaaaaa-aaaa-aaaaa-aaaaaaaa”,“devEui”:“xxxxxxxxxxxxxxxx”,“confirmed”:false,“fPort”:5,“data”:“MQ==”,“object”:null,“isPending”:false,“fCntDown”:0}
Any ideas ?