A lot of time calibration requests in log

[capiman]

What happened?

05:52:40 | 05:52:40 | 1 | Wechselrichter gestartet
15:16:49 | 15:16:49 | 2 | Zeitabgleich
15:16:54 | 15:16:54 | 2 | Zeitabgleich
15:18:09 | 15:18:09 | 2 | Zeitabgleich
15:18:14 | 15:18:14 | 2 | Zeitabgleich
15:18:54 | 15:18:54 | 2 | Zeitabgleich
15:18:59 | 15:18:59 | 2 | Zeitabgleich
15:19:39 | 15:19:39 | 2 | Zeitabgleich
15:19:44 | 15:19:44 | 2 | Zeitabgleich
15:25:15 | 15:25:15 | 2 | Zeitabgleich
15:25:25 | 15:25:25 | 2 | Zeitabgleich
15:25:35 | 15:25:35 | 2 | Zeitabgleich
15:25:40 | 15:25:40 | 2 | Zeitabgleich
15:25:50 | 15:25:50 | 2 | Zeitabgleich
15:25:55 | 15:25:55 | 2 | Zeitabgleich

Who is generating this error? Inverter? Or OpenDTU device?
Is it not working? Is it loosing the time, and therefore a new time request is needed?
Temperature problem in inverter or OpenDTU device?

I saw it with month old firmware. Just updated to current firmware,
but problem occured again.

Inverter is a HM-1500-4T, decreased to 800W.

DC-Leistung | 346,7 | W
Daily 3.998 | Wh
Total 1.351,768 | kWh
Temperatur 66,3 | °C
Wirkungsgrad 95,010 | %

To Reproduce Bug

I dont know, I just had a look into logs and it appears

Expected Behavior

Time sync only once?

Install Method

Pre-Compiled binary from GitHub releases

What git-hash/version of OpenDTU?

v26.3.30

What firmware variant (PIO Environment)?

master

Relevant log/trace output

See above

Anything else?

No response

Please confirm the following

• I believe this issue is a bug that affects all users of OpenDTU, not something specific to my installation.
• I have already searched for relevant existing issues and discussions before opening this report.
• I have updated the title field above with a concise description.
• I have double checked that my inverter does not contain a W in the model name (like HMS-xxxW) as they are not supported.

[LouBen3010]

I was able to reduce the amount of those by restarting both, the inverter and the OpenDTU system via the web interface. For 2-3 days, the high amount of time syncs was resolved then.
Today, the issue came back and led to a lot of missing data frames.

Furthermore, those were being reduced by setting the transmission power to low but this seems just to be a side effect.

[ms49434]

It cannot be a general bug because I am not affected, I don't have this issue with my HM inverter.

I am querying the status every 30 seconds and I am running a local time server.

[elmr91]

I have the same thing everyday on my 2 HMS-2000-4T inverters :

A dozen of message per inverter every day (not at the same time for both inverters).

It is also happening (but with fewer messages) on my 6 HM-400-1T connected to another OpenDTU device.

Both OpenDTU are configured with NTP sync opendtu.pool.ntp.org

I checked the opendtu.pool.ntp.org pool seems OK:

ntpdate -q opendtu.pool.ntp.org
server 79.143.250.33, stratum 1, offset +0.000088, delay 0.04707
server 185.123.84.51, stratum 3, offset -0.001595, delay 0.04562
server 82.64.55.167, stratum 2, offset -0.001618, delay 0.04449
server 162.159.200.123, stratum 3, offset -0.000548, delay 0.03503
 6 May 21:59:51 ntpdate[25956]: adjust time server 79.143.250.33 offset +0.000088 sec

[ClausMueller]

11:44:44 | 11:44:44 | 2 | Time calibration
11:45:05 | 11:45:05 | 2 | Time calibration
11:55:28 | 11:55:28 | 2 | Time calibration
11:56:13 | 11:56:13 | 2 | Time calibration
11:56:28 | 11:56:28 | 2 | Time calibration
12:07:11 | 12:07:11 | 2 | Time calibration
12:09:05 | 12:09:05 | 2 | Time calibration
12:09:29 | 12:09:29 | 2 | Time calibration

+1

[Omega13x]

Ist nur ein kosmetisches Problem und geht auch nur bis 15. Kann man ignorieren. ;)

[capiman]

@Omega13x Was bedeutet "geht nur bis 15"? Wie kommt es zustande?

[Omega13x]

Hat sich irgendwann mal eingeschlichen und wurde noch nicht gefixt. Ich tippe mal so zwei Jahre ist das schon so. Wurde anfänglich auch schwer diskutiert. Aber da es keinerlei Auswirkungen hat und halt nur kosmetischer Natur ist, wurde das auch nicht weiter verfolgt. Vielleicht kümmert sich mal irgendwann einer darum. Aber mich stört es nicht.

[LouBen3010]

Since I’ve been discovering those, I’m having an unreliable transmission of MQTT data.
Every 2 seconds Home Assistant is showing the entity to be unavailable. As soon as I power cycle OpenDTU and with the UI the inverter, everything behaves normal for another 2 days. Then, the time Synchronisation messages are coming in again and the data transmission is affected.

[LouBen3010]

A tiny update on that:
I noticed that my log level has been set to 'verbose' and thus my logs were flooded. After changing back to 'info', the connection was stable again - besides the time sync messages.
Could it be the case that the latest update introduced the verbose log level per default?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.