Why in the Postgresql integration is not created the event_down table where to store any downlink messages generated by the application server (as well as the event_tx_ack and event_ack) ?
I’m not sure if this would be needed?
If you enqueue a downlink, you get back a queue-item ID. On downlink transmission, the PostgreSQL integration (and other integrations) will log a TX ACK event, indicating that the downlink was transmitted by the gateway (containing the queue-item ID).
If you want to maintain a list of downlink payloads sent, then on enqueue you store the payload in your database and mark it as TXed based on the information in
event_tx_ack, or the TX ACK event sent by the MQTT, HTTP, … integrations.
In fact i want to store sent playload.
I realized that I have to do it myself
Tank you for the answer.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.