-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Charge and Discharge curves are not generated AC3 #1621
Comments
Hmm what about predbat.status? |
predbat.status is ok. I'm using that for controlling the charge and discharge switches. sensor.givtcp_{geserial}_battery_power does not exist. Side note - something went very wrong about 4am this morning. Restarted VM at about 8am and ALL my history (yes all of it) prior to 4am today has disappeared...... |
It sounds like you suffered from a HA database corruption. If you look in the HA logs you will probably see something about a corrupt database error. If HA thinks your database is corrupted then it moves the corrupt database to something like /config/ha_databasev2_corrupt_date_time.db and starts with a blank new database - you basically loose all your sensor history. It is possible to move the corrupt database back to replace the blank HA database but without fixing the underlying issue, it can happen again. If you are fairly new with HA and can accept losing the history then I'm afraid you'll just have to live with it. |
Is this something for @britkat1980 ? Maybe
is not available on AC3 inverter so was removed when GivTCP recognises AC3 inverter? Maybe it can be reinstated with a calculation from somewhere? Or can predbat introduce a calculation depending on if it finds
or not? Edited to remove italics |
Since we are find a few ways that the 3 phase inverter doesn't have the same controls as the rest of the GivEnergy range #1607 the suggestion from @springfall2008 to introduce a new inverter type into Predbat could get around these issues. Would give the opportunity for the battery charge and discharge curve logic to take account of two different sensors rather than expect a single battery power sensor Alternatively you could create a battery power template sensor from the two givtcp sensors you have, but it'd be a bit wasteful of HA database storage to duplicate all the data like that. FYI the battery charge/discharge curve missing is not fatal to predbat, it just assumes your battery will smoothly charge and discharge at full rate to full/empty. Having the battery curves just makes the predbat plan a bit more accurate, that's all |
Describe the bug
Charge and Discharge curves are not generated
Expected behaviour
Charge and Discharge curves should be generated in the log file after restart of Add-on
apps.yaml is looking for sensor.givtcp_{geserial}_battery_power
but I do not have battery_power.
I do have battery_charge_power and battery_discharge_power
Predbat version
1.2.1
Environment details
Inverter - GIV-3HY-11. 3 phase
Batteries - 19.94kWh
Stanadard HAOS in VMWare
Screenshots
Log file
The text was updated successfully, but these errors were encountered: