Is there a reason, why the gRPC method “StreamEventLogs” and “StreamFrameLogs” shouldn’t be used for application integration?
My application needs the gRPC integration anyway, because I need to create/delete devices and I want to send downlinks to the device and check with the “StreamEventLogs” method if the downlink was acknowledged.
Any information on this is appreciated!
1 Like
These API endpoints are there for debugging.
I want to send downlinks to the device and check with the “StreamEventLogs” method if the downlink was acknowledged.
Have you looked at the txack event sent by the integrations (MQTT, HTTP, …)? This is the confirmation that the gateway accepted the downlink for transmission. See https://www.chirpstack.io/application-server/integrate/sending-receiving/.
Thank you @brocaar for your response and your great work.
I know that there are different options for sending downlinks. I would like to use one integration to delete/create devices and send downlinks. The only solution for this is the gRPC integration.
I saw the comments in the code to use the gRPC method “StreamEventLogs” and “StreamFrameLogs” only for debugging, but why? Is there any reason for this?
It is to print log information in the web-interface and the output might change over time so it must not be seen as a stable API interface 