Open lucode opened 1 month ago
I'm not sure I understand the question, but SOC only mode is when you have configured a fixed charge window and you just want Predbat to decide the charge %. I'd recommend control Charge/Discharge initially.
In your apps.yaml you can't control your system as you hard-wired the controls, these are meant to point to HA switches/numbers that Predbat can modify.
There are various control methods that can be selected in the inverter configuration section, either using these controls directly but also be using a service API to HA.
How can you control your inverter in HA currently, what do the controls look like?
charge_limit:
- 100
reserve:
- 20
scheduled_charge_enable:
- off
scheduled_discharge_enable:
- off
charge_start_time:
- off
charge_end_time:
- off
discharge_start_time:
- off
discharge_end_time:
- off
How can you control your inverter in HA currently, what do the controls look like?
Thank you for the hints. I start to understand now. So it means that "charge_limit" is a sensor, controlled by Predbat to set my SOC Target? And, charge_start/stop_time are setting the schedule to reach the SOC Target? And what about the service API (charge_start_service - Should be set to a service that is called when charging starts)? Are those if I don't want to use the charge_start/stop_time entities to control my charge?
Frankly, the list of the inverter controls should be more precise about the entities. At least they should be divided in two categories, which makes it clear which ones are input sensors or hard-coded and which are entities (variables) that are controlled by Predbat. https://springfall2008.github.io/batpred/apps-yaml/#home-assistant-entity-inverter-control
# Entity name for used to set the SOC target for the battery in percentage (AC charge target)
charge_limit:
- sensor.victron_predbat_soc_target
reserve:
- 20
scheduled_charge_enable:
- off
scheduled_discharge_enable:
- off
charge_start_time:
- sensor.victron_predbat_charge_start_time
charge_end_time:
- sensor.victron_predbat_charge_stop_time
Basically yes, although sensor. are read only entities so you can't use those for controls, they have to be a select. for times I believe.
If you don't have some of these then the inverter options can disable them. The service API is called if you have has_service_api enabled.
Basically yes, although sensor. are read only entities so you can't use those for controls, they have to be a select. for times I believe.
If you don't have some of these then the inverter options can disable them. The service API is called if you have has_service_api enabled.
Yes, I started to think that my conclusion was wrong. But how can I control my inverter, I do need the service API ? And which input parameter are essential?
In the meantime I changed the mode to Charge control, but nothing changes, it stays in idle and when I turn it active it goes back to off.
Describe the bug I have read much of the documentation and spent some time understanding the app. It works now and outputs reasonable prediction data, but I can't find any entities I could use to control my inverter or EV charger. In the logs I found the following entries, but I can't discharge my battery as it is a non-feed-in installation.
The entities for the Car charger are as follows: The value "EV charging slot" is getting synchronized with my actual charging time, but does not predict anything.
The Inverter is from Victron and I used the SF inverter type for my setup. Link to my apps.yaml: https://github.com/HA-projects/predbat/blob/main/Inverters/Victron/victron_multiplus_v2.yaml
Expected behaviour I tried the mode SOC-only and Control charge, but I can't see any difference. In the docs a value is mentioned "target charge percentage" and a charge window, which are both not present in my setup.
It is very unclear to me how to use this app in this regard, Or it is meant to use Prediction Best values to control the SOC of my battery? What is puzzling too, is that the app stays always in the "idle status".
Predbat version 8.3.1
Environment details
Screenshots
Log file