-
-
Notifications
You must be signed in to change notification settings - Fork 461
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
Data reported from Hoymiles Micro Inverter HMT-1800-6T 3F partially bad #1851
Comments
Are you using multiple DTUs in parallel? E.g. the original Hoymiles DTU? |
Only openDTU, this one. (yyyyyyyyyyyy discussed one) Fetch inverter: yyyyyyyyyyyy |
That has a good received frame somewhere: Fetch inverter: BADREPORTINVERTER |
Packages are only used if they have to correct checksums (yes, there are multiple checksums). Will doublecheck later if your bad values are coming directly from the inverter. If so nothing can be done because in this case all the checksums are correct and the inverter sends crap with correct checksums. |
Your logs contained 8 vaild packages (successfull received + right inverter) Excel file used for analysis: GH_Issue_1851.xlsx So unfortunatly the values are coming directly from the inverter. To be honest, I have no clue whats going on. |
Hmm…and receiving error code 152 unkown a lot of times as well |
152 was added in one of the previous releases
|
What happened?
I receive data a lot of time, which is quite impossible. Microinverter is Hoymiles Micro Inverter HMT-1800-6T 3F. At the end of the day the summary yields are good, the daily and total too. See attached an example for good (blue line background) and bad data (yellow variant) received.
To Reproduce Bug
Not applicable
Expected Behavior
Receive consisted data. Or ignore broken-invalid data packets.
Install Method
Pre-Compiled binary from GitHub
What git-hash/version of OpenDTU?
v4.4.6-dirty / 2024.03.07 / config 0.1.27 / master
Relevant log/trace output
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: