-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Comments
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. |
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 |
Yes the predbat.1.log is the one I found which went back further, but only to about 24 hours ago. |
Will try to work out how to get that data before I next do a calibration. |
Hi. Here are REST reads -
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? |
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
Log file
Sorry, log files only seem to go back about 24 hours. Are they stored somewhere else for longer?
The text was updated successfully, but these errors were encountered: