Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chirpstack-rest-api enqueue problem? #8

Open
fernandobarreto opened this issue Jan 16, 2023 · 0 comments
Open

Chirpstack-rest-api enqueue problem? #8

fernandobarreto opened this issue Jan 16, 2023 · 0 comments

Comments

@fernandobarreto
Copy link

I've opened a chirpstack forum topic "Chirpstack-rest-api problem?" (https://forum.chirpstack.io/t/chirpstack-rest-api-problem/15724/3) and after some time and many tests I think it should be a bug. In summary:

  • If I enqueue a payload with the 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’ , an entry is created and presented in the que device tab on the chirpstack web interface. However the added entry always present fPort:0 and data:"". And if I also change the "confirmed":true in the DeviceQueueItem from curl command, it still shows the confirmed field as false.

If I enqueue with the python example, which uses GRPC, it works OK.

Any ideas ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant