Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple Time Calibrations on microinverters #1891

Open
Berondal opened this issue Apr 7, 2024 · 12 comments
Open

Multiple Time Calibrations on microinverters #1891

Berondal opened this issue Apr 7, 2024 · 12 comments
Labels
bug Something isn't working

Comments

@Berondal
Copy link

Berondal commented Apr 7, 2024

What happened?

Hello
since Firmware update from (23.3.xx) i get on two(of 6) microinverters a lot of time calibration.
Microinverter is not reachable for long time, up to 2h.
All 6 inverters:
Modell | HMS-1600-4T
Bootloader-Version | 0.1.0
Firmware-Version | 1.0.18
Firmware-Erstellungsdatum | 2022-08-26 20:51:00
Hardware-Teilenummer | 270680323
Hardware-Version | 01.00

To Reproduce Bug

no

Expected Behavior

Look if you can find the reason.

Install Method

Pre-Compiled binary from GitHub

What git-hash/version of OpenDTU?

v24.3.31

Relevant log/trace output

Begin	Ende	ID	Meldung
06:35:36	06:35:36	1	Wechselrichter gestartet
12:51:06	12:51:06	2	Time calibration
12:51:11	12:51:11	2	Time calibration
12:51:40	12:51:40	2	Time calibration
12:51:46	12:51:46	2	Time calibration
12:52:14	12:52:14	2	Time calibration
12:52:19	12:52:19	2	Time calibration
12:52:48	12:52:48	2	Time calibration
12:52:53	12:52:53	2	Time calibration
12:53:22	12:53:22	2	Time calibration
12:53:27	12:53:27	2	Time calibration
12:54:27	12:54:27	2	Time calibration
12:55:05	12:55:05	2	Time calibration
12:55:36	12:55:36	2	Time calibration
12:55:41	12:55:41	2	Time calibration

Anything else?

Other 4/6 inverters don't give any message "time calibration"

@Berondal Berondal added the bug Something isn't working label Apr 7, 2024
@stefledufinfra
Copy link

Same here with HM400
Firmware : 24.3.31

@tbnobody
Copy link
Owner

tbnobody commented Apr 9, 2024

No one (except Hoymiles) knows when this event occours. Sometimes it occours when when sending commands in a too short time period, sometimes when the RF connection is bad, or when sending invalid packages. It's also not 100% clear if the error text is correct (previously it was defined as "DTU command failed").

@stefledufinfra
Copy link

stefledufinfra commented Apr 9, 2024

No one (except Hoymiles) knows when this event occours. Sometimes it occours when when sending commands in a too short time period, sometimes when the RF connection is bad, or when sending invalid packages. It's also not 100% clear if the error text is correct (previously it was defined as "DTU command failed").

i never update HOymiles firmware , and i never had this message before i upgrade from 22 to 24 firmware.
For RF , my opendtu is at 1 meter from pannel and max 6 meter

@Peertje-62
Copy link

Hi, for what it's worth, I get the same 'output' (on both) if I connect an Open-DTU parallel to the Ahoy-DTU .
greeting

@tbnobody
Copy link
Owner

get the same 'output' (on both) if I connect an Open-DTU parallel to the Ahoy-DTU .

Thats normal.... Two DTUs on one inverter lead to crappy data, unknown side effects and other isssues....
And yes, you see the same in both projects as the event log is only held in the inverter and both projects read the eventlog directly from the inverter.
But you already knew that... it's mentioned very big in the documentation: https://www.opendtu.solar

image

@Peertje-62
Copy link

Peertje-62 commented Apr 11, 2024

Good evening,
I didn't want to offend or upset anyone.
You are right I knew this all ready for a long time, but I thought it would or could help to solve the problem of Berodal. since He has the same output with only one DTU
So apparently not.
Bye

@tbnobody
Copy link
Owner

Sorry, unfortunately not 😔
It's a strange error code.

@puni2k
Copy link

puni2k commented Apr 13, 2024

No one (except Hoymiles) knows when this event occours. Sometimes it occours when when sending commands in a too short time period, sometimes when the RF connection is bad, or when sending invalid packages. It's also not 100% clear if the error text is correct (previously it was defined as "DTU command failed").

Sometimes my openDTU device acts up and successively dis- and then reconnects to the MQTT server. I noticed this when looking at the logs of my openHAB server. Simultaneously I also see a similar number of "Time calibration" messages showing up on all my inverters (4).
According to "Uptime" the ESP itself isn't rebooting.
It doesn't happen often, at average maybe once a month so i just shrug at it.

@Berondal
Copy link
Author

I try to roll back with firmware. But I get some errors. It could be FW 23.3.28

@Berondal
Copy link
Author

Berondal commented Apr 14, 2024

I don't know, but I remember, that I have change another thing.
I installed https://github.com/henne49/dbus-opendtu on my Victron Cerbo GX. Could this influence the error?

@Berondal
Copy link
Author

Berondal commented Apr 22, 2024

Some days later... Saturday, one inverter don't do anything. wtf,

I tried a lot, ... Today, no missing data, all inverters send data.
no time calibration

I change CMT2300A Frequenz from 865 MHz to 866 MHz.

Question: If CMT2300A is for connection to HMS/HMT and Hoymiles uses 868 MHz. Why is it at 865 MHz?
Can I switch to 868 MHz?

@markusrudolf
Copy link

I had the same with any OpenDTU version newer then v24.4.12 with an Hoymiles HM800-2T. Lot's of data loss as well (no response from Inverter for extended period. Inverter is like 2m away from OpenDTU. Power Supply of OpenDTU stabilized with capacitors on RF Module and ESP32 Board.

I Downgraded to 24.4.12, no Issues any longer. I also have no idea what the problem may be. From the changelog it seems like only minor changes to WebGUI and other cosmetics but no changes to communication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants