Replace a queued downlink (and fPort)

Viewed 18
api chirpstack

I am discovering ChirpStack and LoRaWAN steps by steps and I am discovering downlinks "fPorts" which make me thinking about my previous post Replace a queued downlink which aims to request a flush-queue option to enqueue command when a end-device only supports one full-configuration downlink message kind, since queuing more than one message is useless in this case.

Of course flush-queue option is still sane and simple but now I understand that if end-device supports several fPorts for several message types, then an anti-duplicate spirit would better be "replace all latests enqueued downlinks sharing same fPort", if I am not wrong.

Just wanted to share it in case a "replace same fPort downlinks" is wanted alongside "flush queue before enqueing", opening a new thread since previous one is already discussed and implemented.

1 Answers

replace same fPort downlinks

It is very easy to add these small features, but these tend to pile up over time and make the project as a whole more complex to maintain. Therefore, I think staying just with the simple enqueue with the option to flush the queue before enqueue would be the most effective way which will probably serve the majority of the use-cases.

Orne Brocaar352
Related
Chirpstack 4 grpc with grpcurl
2 answers
Chirpstack v4 - API to send a Mac Command to endpoint?
1 answers
symbol "+": ERE53+//=. I am getting an error: "{"code":3, "message":"proto: (line 1:43): invalid value for bytes type: \"ERE53+//=\"", "details":[]} "
Received http2 header with status: 400, grpc_status:13
1 answers
Replace a queued downlink (and fPort)
1 answers
Replace a queued downlink
2 answers