ok problem identified, there was a payload codec function my friend put in for this device-profile that created some illegal characters so inserting into postgresql was failing. for now I removed the decoder code and it is working now.
the issue was found in the postgresql logs /var/log/postgresql/postgresql-9.6-main.log
No, the PostgreSQL integration stores uplink related events only. However, it is going to store txack events in the next release (acknowledgement that a downlink was accepted by the gateway for downlink transmission).
Initially, I have not created tables and index
Later I have created the tables as per the description of this ticket. Then also I was getting the same error
Hi brocaar! I have a simple but vital question to continue with the integration. We have been able to get the integration with postgreSQL up and running. In the event_up table we can see each message that the devices send but we see the DATA field with the Base64 encoded information. Our intention is to share the data with an external system connected to Postgre but that the information is not encoded. What do you recommend?
have you changed the schema though in v4? I saw in postgres logs some insert statements on event_up table but i created the device_up as you had in your example
Hello,
I created the chirpstack_integration database and can successfully view all uplink data from my device. Is there a way to clear all data to start fresh without causing any errors? Alternatively, is it possible to reset the data from a specific date?
Thank you in advance.
In this end, it is just a PostgreSQL database. E.g. you can drop it and re-create it if you want to start with a new database. Or you can delete records based on a where clause (SQL query).