Widening the window increases the delay, you need to do the opposite. I went through the same thing once while working with drones.The source of the lag is the average itself: a 20-sample moving average comes in about 1 second late, and the error grows as the turn rate increases. The calibration deficiency Büşra Hanım mentioned also explains the difference between right and left.The solution is to combine it with the gyroscope. The gyroscope sees the rotation instantly but drifts slowly, the magnetometer is slow but does not drift. A complementary filter combines the two:

// dt = 0.1 s, gz = derece/s (z ekseni jiroskop)
float a = 0.98;
heading = a * (heading + gz * dt) + (1 - a) * magHeading;
// 0/360 geçişini düzelt
float fark = magHeading - heading;
if (fark > 180) heading += 360 * (1 - a);
if (fark < -180) heading -= 360 * (1 - a);
heading = fmod(heading + 360, 360);

If the board has no gyroscope, adding an MPU6050 is the cheapest way. First, turn the boat two full circles in the water and perform the hard/soft iron calibration.The 180 issue is separate: an angle cannot be averaged. The average of 359 and 1 comes out as 180. The weekly chart reads hourly aggregated values and the default function is average. On the heading chart, set the function to last, and for analysis send heading_sin and heading_cos alongside the heading; their average comes out correctly.

It’s not the baud rate, it’s the voltage. If you measured -9 V, the answer is already there.An RS-232 signal swings roughly ±3 to ±15 V and its logic is inverted: idle is negative, “1” is negative, “0” is positive. The Pi’s UART, on the other hand, is 3.3 V TTL, 0 to 3.3 V, with normal logic. Connecting them directly gets both the level and the polarity wrong, and that garbage in the output is exactly what you’d expect. On top of that, applying a negative voltage and around 9 V to GPIO15 can kill the pin. Disconnect it right away; it’s luck if the Pi is still intact.I’ve done the same job in two places and used two approaches:1. MAX3232 module (MAX3232, not MAX232; it runs at 3.3 V). Feed VCC from the Pi’s 3.3 V, TTL side to GPIO14/15, RS-232 side to the DB9. 2. The cleaner option: a USB-RS232 adapter (PL2303 or FTDI chip). It shows up as /dev/ttyUSB0 and you don’t have to deal with GPIO at all.About the login screen issue: the Pi’s serial console is open on /dev/serial0. In raspi-config > Interface > Serial Port, answer No to “login shell over serial” and Yes to “serial port hardware”.And about TX/RX crossing: we don’t know whether the scale is DCE or DTE. If no data arrives, swap pins 2 and 3.Sending the data to Hermetry after that part is simple: using paho with an access token, you publish to v1/telemetry:

import re, json, serial
import paho.mqtt.client as mqtt

c = mqtt.Client(client_id="kantar-1")
c.username_pw_set(TOKEN, "")
c.tls_set()
c.connect(BROKER_HOST, 8883, keepalive=60)
c.loop_start()

s = serial.Serial('/dev/ttyUSB0', 9600, timeout=2)
while True:
    line = s.readline().decode('ascii', 'ignore')
    m = re.search(r'(-?d+.d+)s*kg', line)
    if m:
        c.publish("v1/telemetry", json.dumps({"weight_kg": float(m.group(1))}), qos=1)

Hakan, check the documentation, there is nothing like that. Hermetry has no scheduled or e-mailed ready-made report, it is stated clearly. But the approach that works today is this, we did exactly that at a textile factory:Measurement: for 38A, get an SCT-013-050 (1V output), connect it to the ESP32’s ADC with a 1.65V bias, and do the EmonLib-like RMS calculation on the device. Have the device send current_a every 30 seconds. If you want real kWh, you will need an energy analyzer with Modbus on a DIN rail. Accept a 10% error margin with clamp-on meter + estimated cosφ.Power and energy: in the root flow, put a Calculate block before Save telemetry and derive power_kw. Details are on the derived values page.

expr:   round(1.732 * 400 * msg.payload.current_a * 0.85 / 1000, 2)
target: msg.payload.power_kw

Report: put a chart card on the dashboard, set grouping to day, and in the card settings tick Download data (CSV). At month end, set the window to This month and download the Excel file. If you want it automated, a small script can pull the daily values from the history API with agg=sum, or with increase if you are sending a counter, and you send the e-mail yourself.