Timezone issue

The current timezones sent by the simulated devices are not properly stored into the database. The problem we have is that they're not in the right time zone. We want EET but the DB stores them in UTC format.

The interesting thing here is that my local Timescale doesn't appear to have this problem. By setting the time zone to EET (SET TIME ZONE 'EET'), it stays like this for good. On the other hand, if I connect to the k8s Timescale and set the timezone to EET it will keep this configuration as long as I stay connected. When I disconnect the timezone configuration is forgotten and it will revert back to UTC. The reason why this happens is most likely because the Timescale deployment creates a new pod each time we connect to it.

This doesn't create a problem with any of the queries we have, but well, it is kind of wrong to have the UTC timezone. I have tried finding a solution to keep the timestamp in EET format but I haven't been successful. I'm keeping this issue to remind myself of the problem but since this hasn't created any issue, I will leave it for later.