#-------------------------- # Batcontrol Configuration # See more Details in: https://github.com/muexxl/batcontrol/wiki/Batcontrol-Configuration #-------------------------- timezone: Europe/Berlin #your time zone. not optional. time_resolution_minutes: 60 # Time resolution for forecasts: 15 (quarter-hourly) or 60 (hourly). Default: 60 loglevel: debug logfile_enabled: true log_everything: false # if false debug messages from fronius.auth and urllib3.connectionpool will be suppressed max_logfile_size: 200 #kB logfile_path: logs/batcontrol.log battery_control: # min_price_difference is the absolute minimum price difference in Euro to justify charging your battery # if min_price_difference_rel results in a higher price difference, that will be used min_price_difference: 0.05 # minimum price difference in Euro to justify charging your battery min_price_difference_rel: 0.10 # Percentage (in decimal) of the current price to justify charging your battery # _rel helps to avoid charging at high prices with less efficiency always_allow_discharge_limit: 0.90 # 0.00 to 1.00 above this SOC limit using energy from the battery is always allowed max_charging_from_grid_limit: 0.89 # 0.00 to 1.00 charging from the grid is only allowed until this SOC limit min_recharge_amount: 100 # in Wh, start & minimum amount of energy to recharge the battery #-------------------------- # Battery Control Expert Tuning Parameters # See more Details in: https://github.com/muexxl/batcontrol/wiki/battery_control_expert #-------------------------- battery_control_expert: charge_rate_multiplier: 1.1 # Increase (>1) calculated charge rate to compensate charge inefficencies. soften_price_difference_on_charging: False # enable earlier charging based on a more relaxed calculation # future_price <= current_price-min_price_difference/soften_price_difference_on_charging_factor soften_price_difference_on_charging_factor: 5 round_price_digits: 4 # round price to n digits after the comma #-------------------------- # Inverter # See more Details in: https://github.com/muexxl/batcontrol/wiki/Inverter-Configuration # # IMPORTANT: This configuration uses a "dummy" inverter for demonstration purposes. # The dummy inverter returns static values to make batcontrol work out of the box. # # For real operation, you MUST: # 1. Comment out the "dummy" type below # 2. Uncomment and configure a real inverter type (e.g., fronius_gen24) # 3. Update the address, user, and password for your actual inverter #-------------------------- inverter: type: dummy # DEMO ONLY - Change to "fronius_gen24" for real operation # For real operation, uncomment and configure the following: # type: fronius_gen24 #currently only fronius_gen24 supported # address: 192.168.0.XX # the local IP of your inverter. needs to be reachable from the machine that runs batcontrol # user: customer #customer or technician lowercase only!! # password: YOUR-PASSWORD # max_grid_charge_rate: 5000 # Watt, Upper limit for Grid to Battery charge rate. max_pv_charge_rate: 0 # Watt, This allows to limit the PV to Battery charge rate. Set to 0 for unlimited charging. # fronius_inverter_id: '1' # Optional: ID of the inverter in Fronius API (default: '1') # fronius_controller_id: '0' # Optional: ID of the controller in Fronius API (default: '0') #-------------------------- # Dynamic Tariff Provider # See more Details in: https://github.com/muexxl/batcontrol/wiki/Dynamic-tariff-provider #-------------------------- utility: type: awattar_de # [tibber, awattar_at, awattar_de, evcc, energyforecast] vat: 0.19 # only required for awattar and energyforecast fees: 0.015 # only required for awattar and energyforecast markup: 0.03 # only required for awattar and energyforecast # apikey: YOUR_API_KEY # MANDATORY for energyforecast and tibber. Uncomment and set if using those providers. #-------------------------- # MQTT API # See more Details in: https://github.com/muexxl/batcontrol/wiki/MQTT-API #-------------------------- mqtt: enabled: false logger: false broker: localhost port: 1883 topic: house/batcontrol username: user password: password retry_attempts: 5 # optional, default: 5 retry_delay: 10 # seconds, optional, default: 10 tls: false cafile: /etc/ssl/certs/ca-certificates.crt certfile: /etc/ssl/certs/client.crt keyfile: /etc/ssl/certs/client.key tls_version: tlsv1.2 auto_discover_enable: true # enables mqtt auto discover => https://www.home-assistant.io/integrations/mqtt/#mqtt-discovery auto_discover_topic: homeassistant # base topic path for auto discover config messages - default 'homeassistant' -> https://www.home-assistant.io/integrations/mqtt/#discovery-options #-------------------------- # Forecast Solar # See more Details in: https://github.com/muexxl/batcontrol/wiki/Solar-Forecast # # DEMO: This configuration uses a simple PV installation for demonstration. # For real operation, update the values below with your actual PV system details. #-------------------------- solar_forecast_provider: fcsolarapi pvinstallations: - name: Demo PV System #name - update this for your system lat: 48.4334480 # Update with your actual latitude lon: 8.7654968 # Update with your actual longitude declination: 30 # inclination toward horizon 0..90 0=flat 90=vertical (e.g. wallmounted) azimuth: 0 # -90:East, 0:South, 90:West -180..180 kWp: 10.0 # power in kWp - update with your actual system size #horizon: # leave empty for default PVGIS horizon, only modify if solar array is shaded by trees or houses #api: #fcsolarapi #-------------------------- # Forecast Consumption # See more Details in: https://github.com/muexxl/batcontrol/wiki/Consumption-forecast # # Option 1: CSV-based forecast (default) # Option 2: HomeAssistant API-based forecast #-------------------------- consumption_forecast: type: csv # Options: 'csv' or 'homeassistant-api' csv: annual_consumption: 4500 # total consumption in kWh p.a. the load profile load_profile: load_profile.csv #name of the load profile file within the config folder # Uncomment to use HomeAssistant API for consumption forecasting # homeassistant_api: # base_url: ws://homeassistant:8123 # Your HomeAssistant URL # apitoken: YOUR_LONG_LIVED_ACCESS_TOKEN # Get from HomeAssistant Profile # entity_id: sensor.energy_consumption # Entity ID with consumption data (in Wh or kWh) # sensor_unit: auto # Options: 'auto' (default, auto-detect), 'Wh', or 'kWh' # # Set to 'Wh' or 'kWh' to skip auto-detection (faster startup) # # Use 'auto' for first-time setup or if you're unsure # history_days: [-7, -14, -21] # Days to look back for historical data # history_weights: [1, 1, 1] # Weight for each history period (1-10), higher = more influence # cache_ttl_hours: 48.0 # How long to cache computed statistics (hours) # multiplier: 1.0 # Multiplier for forecast adjustment (1.0=unchanged, >1.0=increase, <1.0=decrease) #-------------------------- # evcc connection # listen to evcc mqtt messages to lock the battery if the car is charging # See more Details in: https://github.com/muexxl/batcontrol/wiki/evcc-connection #-------------------------- evcc: enabled: false broker: localhost port: 1883 status_topic: evcc/status # one loadpoints that should be monitored loadpoint_topic: - evcc/loadpoints/1/charging - evcc/loadpoints/2/charging # if true (default) the battery will be locked while the car is charging. # always_allow_discharge_limit is always relevant, together with the # battery_halt_topic (if configured), evcc controls the battery lock state. # # overshot. block_battery_while_charging: true username: user password: password tls: false cafile: /etc/ssl/certs/ca-certificates.crt certfile: /etc/ssl/certs/client.crt keyfile: /etc/ssl/certs/client.key tls_version: tlsv1.2 # Optional: # Choose which topic should deliver the limit for the battery # below this limit the battery will be locked # https://docs.evcc.io/docs/integrations/mqtt-api#site # Active if following message appears: # 'Enabling battery threshold management. battery_halt_topic: evcc/site/bufferSoc