Automatic summer/winter time change with respect to the current date

I have several sockets and meters with BK7231N. Everything is connected after mqtt monitors energy consumption in my project with them.
In this case, time is important to me, to be more specific, I mean keeping the current time.
I collect all this data with an accuracy of one minute in which I collect information about the minimum and maximum value.

Does anyone know how to get OpenBK to set my winter/summer time correctly in relation to the current date? I have the time setting after ntp of course.
I forgot that we changed the time almost a week ago and I didn't manually correct the zone, all the stats/graphs got gently into the "head" because I reset some stats at midnight after mqtt well and it gently diverged in time.

As far as I'm concerned, some things should be in constant (aka astronomical) time - how do you count the 24-hour process statistic for 2:00-3:00 a.m., will you break down by /A and by /B ?

Presenting in local 'civil' time should be a matter of presentation only

>>21285209 I would answer someone similarly in the event that I did not know my needs and the problems involved.
It's the device with MQTT reporting, it's the one with the synchronised time (only in this case why?) because for example BL0937 has statistics from day 1, 2 and 3 days back. This is calculated based on internal time.
What is the point of such a solution if I have to keep an eye on the time twice a year to change the time zone from +2 to +1 or vice versa at the right moment on everything I have connected. What is the point of such a solution if I have to keep track of the time on my own side and count the data myself for statistics. If I wanted such a solution I would bet on LibreTiny , although I am not 100% convinced what it has and what it doesn't. Tasmota has it made .