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

Not recognising that Inverter is calibrating AC3 #1625

Open
LeeFarm11 opened this issue Nov 15, 2024 · 6 comments
Open

Not recognising that Inverter is calibrating AC3 #1625

LeeFarm11 opened this issue Nov 15, 2024 · 6 comments
Assignees

Comments

@LeeFarm11
Copy link

Describe the bug
According to documentation if the Battery is calibrating, predbat will go into predbat.status = Calibrating but it did not

Expected behaviour
I scheduled a battery calibration via GivEnergy Portal for 00:05 on 14th November. I expected predbat.status to change to Calibrating while the calibration was taking place. But it did not.

Predbat version
1.2.1

Environment details
Inverter - GIV-3HY-11. 3 phase
Batteries - 19.94kWh
Stanadard HAOS in VMWare

Screenshots
image
image

image

Log file
Sorry, log files only seem to go back about 24 hours. Are they stored somewhere else for longer?

@gcoan
Copy link
Collaborator

gcoan commented Nov 16, 2024

This is probably a problem with GivTCP reporting that the 3 phase inverter is in calibration mode in a different way to how the other inverter types report a calibration. Predbat looks for a specific status in GivTCP (can't remember what it is) and I suspect GivTCP is reporting something differently.

r/e logfile, there should be a /addon_configs/6adb4f0d_predbat/predbat.1.log which is the previous logfile.
I had previously put through a change to increase the number of log files to 9 but for some reason this isn't happening, but the prior file is available

@springfall2008
Copy link
Owner

You would probably need to trigger another calibration and then read out the REST data to see what its set to, note that this information only comes via REST right right

@LeeFarm11
Copy link
Author

r/e logfile, there should be a /addon_configs/6adb4f0d_predbat/predbat.1.log which is the previous logfile. I had previously put through a change to increase the number of log files to 9 but for some reason this isn't happening, but the prior file is available

Yes the predbat.1.log is the one I found which went back further, but only to about 24 hours ago.

@LeeFarm11
Copy link
Author

You would probably need to trigger another calibration and then read out the REST data to see what its set to, note that this information only comes via REST right right

Will try to work out how to get that data before I next do a calibration.

@LeeFarm11
Copy link
Author

Hi.
At 13:14 I scheduled a calibaration to start at 13:17.

Here are REST reads -

  1. before scheduling calibaration. " "Battery_Calibration": "Off","
  2. after scheduling calibaration but before calibration started. " "Battery_Calibration": "Off","
  3. after calibration started. ""Battery_Calibration": "Start","
  4. later in calibaration process. While charging. " "Battery_Calibration": "Charge Only","

I don't know if I spotted all the different possibilities. Is there enough information here or how can I record REST responses over a period of time?

1.txt
2.txt
3.txt
4.txt

@LeeFarm11
Copy link
Author

And the log from Portal Remote Control -

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants