dbw1966
commented
2 months ago Somewhat counter intuitively, charge 58% when the soc is higher means allow to discharge to that level and then float at that point and take any futher energy needs from the grid. The only time you will see discharge is when the battery is force discharging, that is, its told to output more than the house load and feed in to the grid.
raldred
Describe the bug I am trying to get predbat working with my LuxPower inverter, I realise it's not supported, maybe, this is why. However...
The calculated plan suggests that, currently the battery should be charging, it's set the limit to 58%, and enabled charge, howver, the battery's current SOC is 64%.
Having AC charging enabled on my inverter, even if the battery is above the target SOC of 58%, it will continue to fulfil load from the grid.
I'd like to understand why the plan is enabling charge when if you look at the plan, it's expecting battery SOC to fall during the "Charge" period, which would suggest it's expecting the battery SOC to be dropping because it's servicing the load?
So why is it still trying to charge it when it's well above target SOC?
Especially as the upcoming low import period it's just planning to be sat there at 100 from 03:00%
The plan also suggests there is no cost between 23:30 and 02:00 however, because charge is enabled, load will be delivered from the grid, so there will be import cost @ 22.59p
Expected behavior I would expect the plan to only go into charge status if the SOC is below target SOC? I would also expect it not to charge at a higher import rate when the upcoming low rate comes around, the battery will already be mostly charged and it will not benifit the most from the low import, instead it's been charging at a higher rate unnecessarily.
Predbat version
v8.4.6 Installed with predbat add-on
Environment details
apps.yaml
```yaml # ------------------------------------------------------------------ # This is an example configuration, please modify it # ------------------------------------------------------------------ --- pred_bat: module: predbat class: PredBat # Sets the prefix for all created entities in HA - only change if you want to run more than once instance prefix: predbat # Timezone to work in timezone: Europe/London # Currency, symbol for main currency second symbol for 1/100s e.g. $ c or £ p or e c currency_symbols: - '£' - 'p' # Number of threads to use in plan calculation # Can be auto for automatic, 0 for off or values 1-N for a fixed number threads: auto # If you are using Predbat outside of HA then set the HA URL and Key (long lived access token here) #ha_url: 'http://homeassistant.local:8123' #ha_key: 'xxx' # Set to auto-match with a GivEnergy serial number, but you can override the serial or the sensor names # if it doesn't work or if you have more than one inverter you will need to list both # geserial: 're:sensor.givtcp_(.+)_soc_kwh' # geserial2: 're:sensor.givtcp2_(.+)_soc_kwh' # Sets the maximum period of zero load before the gap is filled, default 30 minutes # To disable set it to 1440 load_filter_threshold: 30 # # Sensors, more than one can be specified and they will be summed up automatically # # For two inverters the load today would normally be the master load sensor only (to cover the entire house) # If you have three phase and one inverter per phase then you would need three load sensors # # For pv_today if you have multiple solar inverter inputs then you should include one entry for each inverter # load_today: - sensor.lux_home_consumption_daily import_today: - sensor.lux_power_from_grid_daily export_today: - sensor.lux_power_to_grid_daily pv_today: - sensor.lux_solar_output_daily # Load forecast can be used to add to the historical load data (heat-pump) # To link to Predheat # Data must be in the format of 'last_updated' timestamp and 'energy' for incrementing kWh #load_forecast: # - predheat.heat_energy$external # # If you enable ge_cloud_data then the load/import and export data will be fetches from the GE cloud instead of from GivTCP sensors # this is usually less efficient and of course prone to internet downtime, but could be useful if you lost your GivTCP data # Set the serial to the inverter serial to pull the data from and the key to your API key # When this is set load_today, import_today and export_today are not used # # ge_cloud_data: False # ge_cloud_serial: '{geserial}' # ge_cloud_key: 'xxxx' # # Controls/status - must by 1 per inverter # num_inverters: 1 inverter_type: LuxPower inverter: name: "LuxPower" has_rest_api: False has_mqtt_api: False has_service_api: True output_charge_control: "current" current_dp: 0 has_charge_enable_time: True has_discharge_enable_time: True has_target_soc: True has_reserve_soc: False has_timed_pause: False charge_time_format: "HH:MM:SS" charge_time_entity_is_option: False soc_units: "%" num_load_entities: 1 has_ge_inverter_mode: False time_button_press: False clock_time_format: "%Y-%m-%d %H:%M:%S" write_and_poll_sleep: 10 has_time_window: False support_charge_freeze: False support_discharge_freeze: False charge_start_service: service: switch.turn_on entity_id: "switch.lux_ac_charge_enable" charge_stop_service: service: switch.turn_off entity_id: "switch.lux_ac_charge_enable" discharge_start_service: service: switch.turn_on entity_id: "switch.lux_force_discharge_enable" discharge_stop_service: service: switch.turn_off entity_id: "switch.lux_force_discharge_enable" # # Run balance inverters every N seconds (0=disabled) - only for multi-inverter balance_inverters_seconds: 60 # # When set use the REST API rather than HA entity for control, should be more reliable/faster to control # Set one per inverter # If using Docker then change homeassistant.local to the Docker IP address # givtcp_rest: # - 'http://homeassistant.local:6345' # - 'http://homeassistant.local:6346' # When enabled automatic restart will restart the add-on if communication fails # Example below is auto-restart for GivTCP add-on itself #auto_restart: # - shell: 'rm -rf /homeassistant/GivTCP/*.pkl' # - service: hassio/addon_restart # addon: a6a2857d_givtcp # Example on how to restart the inverter via GivTCP # - service: switch.turn_on # entity_id: switch.givtcp_{geserial}_reboot_invertor # If not using REST then instead set the Control here (one for each inverter) # You should keep this section even when using REST as a fallback if it fails and for charge curve calculations timed_charge_current: - number.lux_charge_current_limit timed_discharge_current: - number.lux_discharge_current_limit # charge_rate: # - input_number.lux_target_charge_current_w # discharge_rate: # - input_number.lux_target_discharge_current_w battery_power: - sensor.lux_battery_discharge_live pv_power: - sensor.lux_solar_output_live load_power: - sensor.lux_home_consumption_live # Use helper which corrects SOC when full as sticks at 99% with BMS at 0A soc_percent: - sensor.lux_battery_soc_corrected # soc_kw: # - sensor.givtcp_{geserial}_soc_kwh # - sensor.givtcp2_{geserial2}_soc_kwh soc_max: - sensor.lux_battery_capacity_kwh battery_rate_max: - 5120 battery_min_soc: - 5 battery_voltage: - sensor.lux_battery_voltage_live # - sensor.givtcp_{geserial}_battery_capacity_kwh # - sensor.givtcp2_{geserial2}_battery_capacity_kwh # reserve: # - number.givtcp_{geserial}_battery_power_reserve # - number.givtcp2_{geserial2}_battery_power_reserve # inverter_mode: # - select.givtcp_{geserial}_mode # - select.givtcp2_{geserial2}_mode # inverter_time: # - sensor.givtcp_{geserial}_invertor_time # - sensor.givtcp2_{geserial2}_invertor_time # Use input text helpers here to predbat uses HH:MM:SS, inverter expects HH:MM times charge_start_time: - input_text.lux_batpred_charge_start charge_end_time: - input_text.lux_batpred_charge_end charge_limit: - number.lux_ac_battery_charge_level scheduled_charge_enable: - switch.lux_ac_charge_enable scheduled_discharge_enable: - switch.lux_force_discharge_enable discharge_start_time: - input_text.lux_batpred_discharge_start discharge_end_time: - input_text.lux_batpred_discharge_end # Pause mode is not supported by all firmware's and will be ignored if not present # pause_mode: # - select.givtcp_{geserial}_battery_pause_mode # - select.givtcp_{geserial2}_battery_pause_mode # Not all firmwares support pause start/end time, delete these if not supported # to avoid spurious writes/warnings # pause_start_time: # - select.givtcp_{geserial}_battery_pause_start_time_slot # - select.givtcp2_{geserial2}_battery_pause_start_time_slot # pause_end_time: # - select.givtcp_{geserial}_battery_pause_end_time_slot # - select.givtcp2_{geserial2}_battery_pause_end_time_slot # Inverter max AC limit (one per inverter). E.g for a 3.6kw inverter set to 3600 # If you have a second inverter for PV only please add the two values together inverter_limit: - 7500 # Export limit is a software limit set on your inverter that prevents exporting above a given level # When enabled Predbat will model this limit #export_limit: # - 3600 # - 3600 # Some inverters don't turn off when the rate is set to 0, still charge or discharge at around 200w # The value can be set here in watts to model this (doesn't change operation) #inverter_battery_rate_min: # - 200 # Workaround to limit the maximum reserve setting, some inverters won't allow 100% to be set # Comment out if your inverter allows 100% # inverter_reserve_max : 98 # Some batteries tail off their charge rate at high soc% # enter the charging curve here as a % of the max charge rate for each soc percentage. # the default is 1.0 (full power) # The example below is from GE 9.5kwh battery with latest firmware and gen1 inverter # # Predbat can compute this curve automatically if you have enough data, restart the add-on and look in the logfile for the data # once set here Predbat will no longer re-compute the curve. # Can also be set to 'auto' to just use the calculation curve, not recommended if you are using low power charging mode. #battery_charge_power_curve: # 91 : 0.91 # 92 : 0.81 # 93 : 0.71 # 94 : 0.62 # 95 : 0.52 # 96 : 0.43 # 97 : 0.33 # 98 : 0.24 # 99 : 0.24 # 100 : 0.24 #battery_discharge_power_curve: # 4 : 1.0 # Inverter clock skew in minutes, e.g. 1 means it's 1 minute fast and -1 is 1 minute slow # Separate start and end options are applied to the start and end time windows, mostly as you want to start late (not early) and finish early (not late) # Separate discharge skew for discharge windows only inverter_clock_skew_start: 0 inverter_clock_skew_end: 0 inverter_clock_skew_discharge_start: 0 inverter_clock_skew_discharge_end: 0 # Clock skew adjusts the Appdaemon time # This is the time that Predbat takes actions like starting discharge/charging # Only use this for workarounds if your inverter time is correct but Predbat is somehow wrong (AppDaemon issue) # 1 means add 1 minute to AppDaemon time, -1 takes it away clock_skew: 0 # Solcast cloud interface, set this or the local interface below #solcast_host: 'https://api.solcast.com.au/' #solcast_api_key: 'xxxx' #solcast_poll_hours: 8 # Set these to match solcast sensor names if not using the cloud interface # The regular expression (re:) makes the solcast bit optional # If these don't match find your own names in Home Assistant pv_forecast_today: re:(sensor.(solcast_|)(pv_forecast_|)forecast_today) pv_forecast_tomorrow: re:(sensor.(solcast_|)(pv_forecast_|)forecast_tomorrow) pv_forecast_d3: re:(sensor.(solcast_|)(pv_forecast_|)forecast_(day_3|d3)) pv_forecast_d4: re:(sensor.(solcast_|)(pv_forecast_|)forecast_(day_4|d4)) # car_charging_energy defines an incrementing sensor which measures the charge added to your car # is used for car_charging_hold feature to filter out car charging from the previous load data # Automatically set to detect Wallbox and Zappi, if it doesn't match manually enter your sensor name # Also adjust car_charging_energy_scale if it's not in kwH to fix the units # car_charging_energy: 're:(sensor.myenergi_zappi_[0-9a-z]+_charge_added_session|sensor.wallbox_portal_added_energy)' # Defines the number of cars modelled by the system, set to 0 for no car num_cars: 0 # car_charging_planned is set to a sensor which when positive indicates the car will charged in the upcoming low rate slots # This should not be needed if you use Intelligent Octopus slots which will take priority if enabled # The list of possible values is in car_charging_planned_response # Auto matches Zappi and Wallbox, or change it for your own # One entry per car # car_charging_planned: # - 're:(sensor.wallbox_portal_status_description|sensor.myenergi_zappi_[0-9a-z]+_plug_status)' # car_charging_planned_response: # - 'yes' # - 'on' # - 'true' # - 'connected' # - 'ev connected' # - 'charging' # - 'paused' # - 'waiting for car demand' # - 'waiting for ev' # - 'scheduled' # - 'enabled' # - 'latched' # - 'locked' # - 'plugged in' # In some cases car planning is difficult (e.g. Ohme with Intelligent doesn't report slots) # The car charging now can be set to a sensor to indicate the car is charging and to plan # for it to charge during this 30 minute slot #car_charging_now: # - off # Positive responses for car_charging_now # car_charging_now_response: # - 'yes' # - 'on' # - 'true' # To make planned car charging more accurate, either using car_charging_planned or the Octopus Energy plugin, # specify your battery size in kwh, charge limit % and current car battery soc % sensors/values. # If you have Intelligent Octopus the battery size and limit will be extracted from the Octopus Energy plugin directly. # Set the car SOC% if you have it to give an accurate forecast of the cars battery levels. # One entry per car if you have multiple cars. #car_charging_battery_size: # - 75 #car_charging_limit: # - 're:number.tsunami_charge_limit' #car_charging_soc: # - 're:sensor.tsunami_battery' # One per car, when true only one car can charge at once, when False multiple cars can charge at once #car_charging_exclusive: # - True # If you have Octopus intelligent, enable the intelligent slot information to add to pricing # Will automatically disable if not found, or comment out to disable fully # When enabled it overrides the 'car_charging_planned' feature and predict the car charging based on the intelligent plan (unless octopus intelligent charging is False) # This matches either the intelligent slot from the Octopus Plugin or from the Intelligent plugin # octopus_intelligent_slot: 're:(binary_sensor.octopus_energy([0-9a-z_]+|)_intelligent_dispatching)' # octopus_ready_time: 're:(time.octopus_energy([0-9a-z_]+|)_intelligent_ready_time)' # octopus_charge_limit: 're:(number.octopus_energy([0-9a-z_]+|)_intelligent_charge_limit)' # Example alternative configuration for Ohme integration release >=v0.6.1 #octopus_intelligent_slot: 'binary_sensor.ohme_slot_active' #octopus_ready_time: 'time.ohme_target_time' #octopus_charge_limit: 'number.ohme_target_percent' # Carbon Intensity data from National grid carbon_intensity: 're:(sensor.carbon_intensity_uk)' # Octopus saving session points to the saving session Sensor in the Octopus plugin, when enabled saving sessions will be at the assumed # Rate is read automatically from the add-in and converted to pence using the conversion rate below (default is 8) octopus_saving_session: 're:(binary_sensor.octopus_energy([0-9a-z_]+|)_saving_session(s|))' octopus_saving_session_octopoints_per_penny: 8 # Energy rates # Please set one of these three, if multiple are set then Octopus is used first, second rates_import/rates_export and latest basic metric # Set import and export entity to point to the Octopus Energy plugin import and export sensors # automatically matches your meter number assuming you have only one (no need to edit the below) # Will be ignored if you don't have the sensor but will error if you do have one and it's incorrect # NOTE: To get detailed energy rates you need to go in and manually enable the following events in HA # event.octopus_energy_electricity_xxxxxxxx_previous_day_rates # event.octopus_energy_electricity_xxxxxxxx_current_day_rates # event.octopus_energy_electricity_xxxxxxxx_next_day_rates # and if you have export enable: # event.octopus_energy_electricity_xxxxxxxx_export_previous_day_rates # event.octopus_energy_electricity_xxxxxxxx_export_current_day_rates # event.octopus_energy_electricity_xxxxxxxx_export_next_day_rates # Predbat will automatically find the event. entities from the link below to the sensors # metric_octopus_import: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_current_rate)' # metric_octopus_export: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_export_current_rate)' # Standing charge in pounds, can be set to a sensor or manually entered (e.g. 0.50 is 50p) # The default below will pick up the standing charge from the Octopus Plugin # The standing charge only impacts the cost graphs and doesn't change the way Predbat plans # If you don't want to show the standing charge then just delete this line or set to zero # metric_standing_charge: 're:(sensor.(octopus_energy_|)electricity_[0-9a-z]+_[0-9a-z]+_current_standing_charge)' # Or set your actual rates across time for import and export # If start/end is missing it's assumed to be a fixed rate # Gaps are filled with zero rate #rates_import: # - start: "00:30:00" # end: "04:30:00" # rate: 7.5 # - start: "04:30:00" # end: "00:30:00" # rate: 40.0 # #rates_export: # - rate: 4.2 # Can be used instead of the plugin to get import rates directly online # Overrides metric_octopus_import and rates_import rates_import_octopus_url : "https://api.octopus.energy/v1/products/FLUX-IMPORT-23-02-14/electricity-tariffs/E-1R-FLUX-IMPORT-23-02-14-G/standard-unit-rates" # rates_import_octopus_url : "https://api.octopus.energy/v1/products/AGILE-FLEX-BB-23-02-08/electricity-tariffs/E-1R-AGILE-FLEX-BB-23-02-08-A/standard-unit-rates" # Overrides metric_octopus_export and rates_export rates_export_octopus_url: "https://api.octopus.energy/v1/products/FLUX-EXPORT-23-02-14/electricity-tariffs/E-1R-FLUX-EXPORT-23-02-14-G/standard-unit-rates" # rates_export_octopus_url: "https://api.octopus.energy/v1/products/AGILE-OUTGOING-BB-23-02-28/electricity-tariffs/E-1R-AGILE-OUTGOING-BB-23-02-28-A/standard-unit-rates/" # rates_export_octopus_url: "https://api.octopus.energy/v1/products/OUTGOING-FIX-12M-BB-23-02-09/electricity-tariffs/E-1R-OUTGOING-FIX-12M-BB-23-02-09-A/standard-unit-rates/" # Import rates can be overridden with rate_import_override # Export rates can be overridden with rate_export_override # Use the same format as above, but a date can be included if it just applies for a set day (e.g. Octopus power ups) # This will override even the Octopus plugin rates if enabled # #rates_import_override: # - date: '2023-09-10' # start: '14:00:00' # end: '14:30:00' # rate: 112 # load_scaling: 0.8 # For pv estimate, leave blank for central estimate, or add 10 for 10% curve (worst case) or 90 or 90% curve (best case) # If you use 10 then disable pv_metric10_weight below # pv_estimate: 10 # Days previous is the number of days back to find historical load data # Recommended is 7 to capture day of the week but 1 can also be used # if you have more history you could use 7 and 14 (in a list) but the standard data in HA only lasts 10 days days_previous: - 7 # Days previous weight can be used to control the weighting of the previous load points, the values are multiplied by their # weights and then divided through by the total weight. E.g. if you used 1 and 0.5 then the first value would have 2/3rd of the weight and the second 1/3rd # Include one value for each days_previous value, each weighting on a separate line. # If any days_previous's that are not given a weighting they will assume a default weighting of 1. days_previous_weight: - 1 # Number of hours forward to forecast, best left as-is unless you have specific reason forecast_hours: 48 # Specify the devices that notifies are sent to, the default is 'notify' which goes to all #notify_devices: # - mobile_app_treforsiphone12_2 # Battery scaling makes the battery smaller (e.g. 0.9) or bigger than its reported # If you have an 80% DoD battery that falsely reports it's kwh then set it to 0.8 to report the real figures # One per inverter battery_scaling: - 1.0 # Can be used to scale import and export data, used for workarounds import_export_scaling: 1.0 # Export triggers: # For each trigger give a name, the minutes of export needed and the energy required in that time # Multiple triggers can be set at once so in total you could use too much energy if all run # Creates an entity called 'binary_sensor.predbat_export_trigger_predbat_config.json
```json { "version":false, "expert_mode":true, "active":false, "pv_metric10_weight":0.15, "pv_scaling":0.9, "load_scaling":1.0, "load_scaling10":1.1, "load_scaling_saving":1.0, "battery_rate_max_scaling":1.0, "battery_rate_max_scaling_discharge":1.0, "battery_loss":0.03, "battery_loss_discharge":0.03, "inverter_loss":0.04, "inverter_hybrid":true, "inverter_soc_reset":true, "inverter_set_charge_before":true, "battery_capacity_nominal":false, "car_charging_energy_scale":1.0, "car_charging_threshold":6.0, "car_charging_rate":7.4, "car_charging_loss":0.08, "best_soc_min":0.0, "best_soc_max":0.0, "best_soc_keep":1.0, "metric_min_improvement":1.0, "metric_min_improvement_discharge":1.0, "metric_battery_cycle":0.0, "metric_battery_value_scaling":1.0, "metric_future_rate_offset_import":0.0, "metric_future_rate_offset_export":0.0, "metric_inday_adjust_damping":0.95, "metric_cloud_enable":true, "metric_load_divergence_enable":true, "metric_self_sufficiency":0.0, "set_reserve_min":5.0, "rate_low_threshold":0.0, "rate_high_threshold":0.0, "combine_rate_threshold":0.0, "car_charging_hold":true, "car_charging_manual_soc":false, "octopus_intelligent_charging":false, "octopus_intelligent_ignore_unplugged":false, "car_charging_plan_smart":false, "car_charging_plan_max_price":0.0, "car_charging_from_battery":false, "calculate_discharge_oncharge":true, "calculate_second_pass":false, "calculate_tweak_plan":false, "calculate_secondary_order":true, "calculate_inday_adjustment":true, "calculate_plan_every":10.0, "combine_charge_slots":false, "combine_discharge_slots":false, "set_status_notify":false, "set_inverter_notify":false, "set_charge_freeze":true, "set_charge_low_power":false, "set_reserve_enable":true, "set_discharge_freeze_only":false, "set_discharge_during_charge":true, "set_read_only":false, "balance_inverters_enable":false, "debug_enable":false, "car_charging_plan_time":"07:00:00", "mode":"Control charge & discharge", "manual_charge":"off", "manual_discharge":"off", "manual_idle":"off", "manual_freeze_charge":"off", "manual_freeze_discharge":"off", "auto_update":false, "load_filter_modal":true, "iboost_enable":false, "carbon_enable":false, "holiday_days_left":0.0, "forecast_plan_hours":24.0, "plan_debug":false } ```Screenshots If applicable, add screenshots to help explain your problem. The most useful ones can be your battery chart, the Predbat HTML plan and your current settings in HA.
Log file
predbat.log