Excessive GE EMS writes?

[markbw999]

I have just been having a conversation with @andrewmusty about the number writes we are seeing to our EMSs. My setup is an EMS and two AC coupled inverters. If I look at the GivTCP writes stats the EMS is running at 76k total and about 30k per month whereas the inverters are only about 900 each in total.

I posted about this on the GivTCP FB group and got the following from Paul Landregan - "Without spilling the hardware make up. the Settings are stored in a I2C 8K EEPROM with 1M writes. As well as RAM buffering."

If that's the limit, my EMS only has three years before it is fried at this rate. Andrew has noticed this - "With local EMS control it seems to spam the GivTCP log with: GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success every 10 seconds or so."

Is predbat doing this? I have attached my debug and log files...

predbat.log
predbat_debug.yaml.txt

[andrewmusty]

I've been using the GE cloud plugin since I noticed the spamming and todays writes so far is only 70 ish.

When using Givtcp this is an example of the Givtcp log file. It seem to be about every 10 sec

2026-06-28 14:13:13,792 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:13:24,998 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:13:33,964 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:13:44,075 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:13:54,186 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:14:04,297 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success

2026-06-28 14:15:58,451 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:16:08,572 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:16:18,775 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:16:32,397 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:16:39,006 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:16:48,980 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:16:59,099 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:17:09,210 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success
2026-06-28 14:17:18,822 - GivTCP2 - write - [INFO] - Setting Charge Target 1 was a success

[springfall2008]

If you look at the predbat log the 'count register writes' seems fine.

It seems like you have an issue with GivTCP?

[springfall2008]

Please share your apps.yaml?

[andrewmusty]

@springfall2008 This is my apps.yaml I used with GivTCP

# ------------------------------------------------------------------
# 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
  
  
  #load_ml_enable: true
  #load_ml_source: true
  #load_ml_max_days_history: 28
  #load_ml_database_days: 90


  # XXX: This is a configuration template, delete this line once you edit your configuration
  #template: true

  # Timezone to work in
  timezone: Europe/London

  # Currency, symbol for main currency and second symbol for 1/100s e.g. $ c, £ p or € 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 
  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: !secret ha_key

  # 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'

  ems: 'ems*****'
  emsgiv: 'givtcp2'

  inv1: 'ce****g****'
  inv1giv: 'givtcp'

  inv2: 'ce****g***'
  inv2giv: 'givtcp3'

  load_filter_threshold: 30

  num_inverters: 2

  inverter_type:
    - 'GEE'
    - 'GEE'

  load_today:
    - sensor.house_load_today

  import_today:
    - sensor.{emsgiv}_{ems}_import_energy_today_kwh

  export_today:
    - sensor.{emsgiv}_{ems}_export_energy_today_kwh

  pv_today:
    - sensor.total_solar_today

  balance_inverters_seconds: 0

  charge_rate:
    - number.{inv1giv}_{inv1}_battery_charge_rate
    - number.{inv2giv}_{inv2}_battery_charge_rate

  discharge_rate:
    - number.{inv1giv}_{inv1}_battery_discharge_rate
    - number.{inv2giv}_{inv2}_battery_discharge_rate

  battery_power:
    - sensor.{emsgiv}_{ems}_battery_power
    - 0

  pv_power:
    - sensor.{emsgiv}_{ems}_generation_load_power
    - 0

  load_power:
    - sensor.{emsgiv}_{ems}_calculated_load_power
    - 0

  grid_power:
    - sensor.{emsgiv}_{ems}_grid_power
    - 0

  soc_kw:
    - sensor.{inv1giv}_{inv1}_soc_kwh
    - sensor.{inv2giv}_{inv2}_soc_kwh

  soc_percent:
    - sensor.{inv1giv}_{inv1}_soc
    - sensor.{inv2giv}_{inv2}_soc

  soc_max:
    - sensor.{inv1giv}_{inv1}_battery_capacity_kwh
    - sensor.{inv2giv}_{inv2}_battery_capacity_kwh

  reserve:
    - number.{inv1giv}_{inv1}_battery_power_reserve
    - number.{inv2giv}_{inv2}_battery_power_reserve

  charge_start_time:
    - select.{emsgiv}_{ems}_ems_charge_start_time_slot_1
    - select.{emsgiv}_{ems}_ems_charge_start_time_slot_1

  charge_end_time:
    - select.{emsgiv}_{ems}_ems_charge_end_time_slot_1
    - select.{emsgiv}_{ems}_ems_charge_end_time_slot_1

  idle_start_time:
    - select.{emsgiv}_{ems}_ems_discharge_start_time_slot_1
    - select.{emsgiv}_{ems}_ems_discharge_start_time_slot_1

  idle_end_time:
    - select.{emsgiv}_{ems}_ems_discharge_end_time_slot_1
    - select.{emsgiv}_{ems}_ems_discharge_end_time_slot_1

  charge_limit:
    - number.{emsgiv}_{ems}_ems_charge_target_soc_1
    - number.{emsgiv}_{ems}_ems_charge_target_soc_1

  discharge_start_time:
    - select.{emsgiv}_{ems}_export_start_time_slot_1
    - select.{emsgiv}_{ems}_export_start_time_slot_1

  discharge_end_time:
    - select.{emsgiv}_{ems}_export_end_time_slot_1
    - select.{emsgiv}_{ems}_export_end_time_slot_1

  # Battery temperature sensor per inverter, used outside REST mode to get current temperature
  #
  #battery_temperature:
  # - sensor.givtcp_battery_stack_1_bms_temperature
  # - sensor.givtcp2_battery_stack_1_bms_temperature

  # Battery temperature history, only one for modelling, used to predict future temperature
  #
  #battery_temperature_history: sensor.givtcp_battery_stack_1_bms_temperature

  # Battery temperature charge adjustment curve
  # Specific in C which is a multiple of the battery capacity
  # e.g. 0.33 C is 33% of the battery capacity
  # values unspecified will be assumed to be 1.0 hence rate is capped by max charge rate
  #battery_temperature_charge_curve:
  #  19: 0.33
  #  18: 0.33
  #  17: 0.33
  #  16: 0.33
  #  15: 0.33
  #  14: 0.33
  #  13: 0.33
  #  12: 0.33
  #  11: 0.33
  #  10: 0.25
  #  9: 0.25
  #  8: 0.25
  #  7: 0.25
  #  6: 0.25
  #  5: 0.25
  #  4: 0.25
  #  3: 0.25
  #  2: 0.25
  #  1: 0.15
  #  0: 0.00
  #####
  # 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:
    - 3000
    - 3000

  # 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:
   - 3000
   - 3000

  # 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 app 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: '80FwgmvU6pAKxfeBZRuLdsNbAhzRmRBF'
  #solcast_poll_hours: 8

  # Forecast Solar interface, set this or the local interface below
  #forecast_solar:
  #- postcode: 'SW1A 1AA'
  #  kwp: 4.0
  #  azimuth: 180
  #  declination: 10
  #  api_key: !secret forecast_solar_api_key

  # 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))

  # Ohme EV charger cloud direct integration
  #ohme_login: !secret ohme_login
  #ohme_password: !secret ohme_password
  #ohme_automatic_octopus_intelligent: True

  # 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: 1

  # 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'
   # - 'waiting'

  # 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

  # Octopus Energy direct integration
  #octopus_api_key: !secret octopus_api_key
  #octopus_api_account: !secret octopus_api_account
  #octopus_automatic: True

  # Or if using bottle cap dave Home Assistant Octopus Energy plugin set the entities here
  # 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:((select|time).octopus_energy_([0-9a-z_]+|)_intelligent_target_time)'
  #####octopus_charge_limit: 're:(number.octopus_energy([0-9a-z_]+|)_intelligent_charge_target)'

  # 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'

  # Set this to False if you use Octopus Intelligent slot for car planning but when on another tariff e.g. Agile
  #octopus_slot_low_rate: False

  # Carbon Intensity data direct from National grid
  #carbon_postcode: 'SW1A 1AA'
  #carbon_automatic: true

  # Or using Home Assistant sensor
  #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:(event.octopus_energy([0-9a-z_]+|)_saving_session_event(s|)'
  octopus_saving_session: 're:(event.octopus_energy([0-9a-z_]+|)_saving_session_event(s|))'
  octopus_saving_session_octopoints_per_penny: 8

  # Octopus free session points to the free session Sensor in the Octopus plugin
  # Note: You must enable this event sensor in the Octopus Integration in Home Assistant for it to work
  octopus_free_session: 're:(event.octopus_energy_([0-9a-z_]+|)_octoplus_free_electricity_session_events)'

  # Alternative scraper from Octopus web site if the above is not working
  # octopus_free_url: 'http://octopus.energy/free-electricity'

  # Enter your Axle VPP API key if you have signed up to the Axle service in the UK
  # axle_api_key: !secret axle_api_key

  # 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)'

  # Energy data service (https://github.com/MTrab/energidataservice)
  #metric_energidataservice_import: 'sensor.energi_data_service_import'
  #metric_energidataservice_export: 'sensor.energi_data_service_export'

  # 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-A/standard-unit-rates"
  # rates_import_octopus_url : "https://api.octopus.energy/v1/products/AGILE-BB-24-10-01/electricity-tariffs/E-1R-AGILE-BB-24-10-01-A/standard-unit-rates/"
  #rates_import_octopus_url : https://api.octopus.energy/v1/products/COSY-22-12-08/electricity-tariffs/E-1R-COSY-22-12-08-H/standard-unit-rates/

  # Overrides metric_octopus_export and rates_export
  # rates_export_octopus_url: "https://api.octopus.energy/v1/products/FLUX-EXPORT-BB-23-02-14/electricity-tariffs/E-1R-FLUX-EXPORT-BB-23-02-14-A/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/"
  #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/
  #export_rate: 12.0

  # 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: '2026-05-20'
      start: '00:00:00'
      end: '02:00:00'
      rate: 25.55
   -  date: '2026-05-20'
      start: '02:00:00'
      end: '05:00:00'
      rate: 15.34
   -  date: '2026-05-20'
      start: '05:00:00'
      end: '16:00:00'
      rate: 25.55
   -  date: '2026-05-20'
      start: '16:00:00'
      end: '19:00:00'
      rate: 35.78
   -  date: '2026-05-20'
      start: '19:00:00'
      end: '00:00:00'
      rate: 25.55        
  rates_export_override:
   -  date: '2026-05-20'
      start: '00:00:00'
      end: '02:00:00'
      rate: 10.08
   -  date: '2026-05-20'
      start: '02:00:00'
      end: '05:00:00'
      rate:  4.74
   -  date: '2026-05-20'
      start: '05:00:00'
      end: '16:00:00'
      rate:  10.08
   -  date: '2026-05-20'
      start: '16:00:00'
      end: '19:00:00'
      rate:  29
   -  date: '2026-05-20'
      start: '19:00:00'
      end: '00:00:00'
      rate:  10.29         

     
  #    load_scaling: 0.8

  # 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: 72

  # 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_<name>' which will be turned On when the condition is valid
  # connect this to your automation to start whatever you want to trigger
  #
  # export_triggers:
  #   - name: 'large'
  #     minutes: 60
  #     energy: 1.0
  #   - name: 'small'
  #     minutes: 15
  #     energy: 0.25

  # If you have a sensor that gives the energy consumed by your solar diverter then add it here
  # this will make the predictions more accurate. It should be an incrementing sensor, it can reset at midnight or not
  # It's assumed to be in Kwh but scaling can be applied if need be
  #iboost_energy_today: 'sensor.xxxxx'
  #iboost_energy_scaling: 1.0
  # Gas rates for comparison
  #metric_octopus_gas: 're:(sensor.(octopus_energy_|)gas_[0-9a-z]+_[0-9a-z]+_current_rate)'

  # Nordpool market energy rates
  #futurerate_url: 'https://dataportal-api.nordpoolgroup.com/api/DayAheadPrices?date=DATE&market=N2EX_DayAhead&deliveryArea=UK&currency=GBP'
  #futurerate_adjust_import: True
  #futurerate_adjust_export: False
  #futurerate_peak_start: "16:00:00"
  #futurerate_peak_end: "19:00:00"
  #futurerate_peak_premium_import: 14
  #futurerate_peak_premium_export: 6.5

  # Tariff comparison feature
  # Adjust this list to the tariffs you want to compare, include your current tariff also
  # Octopus region code (https://energy-stats.uk/dno-region-codes-explained/)
  #dno_region: "A"
  #compare_list:
  #  - id: 'current'
  #    name: 'Current Tariff'
  #  - id: 'cap_seg'
  #    name: 'Price cap import/SEG export'
  #    rates_import:
  #      - rate: 24.86
  #    rates_export:
  #      - rate: 4.1
  #  - id: 'eon_next_drive'
  #    name: 'Eon Next Drive import/Fixed export'
  #    rates_import:
  #      - rate: 6.7
  #        start: "00:00:00"
  #        end: "07:00:00"
  #      - rate: 24.86
  #        start: "07:00:00"
  #        end: "00:00:00"
  #    rates_export:
  #      - rate: 16.5
  #  - id: 'igo_fixed'
  #    name: 'Intelligent GO import/Fixed export'
  #    rates_import_octopus_url: 'https://api.octopus.energy/v1/products/INTELLI-VAR-24-10-29/electricity-tariffs/E-1R-INTELLI-VAR-24-10-29-{dno_region}/standard-unit-rates/'
  #    rates_export_octopus_url: 'https://api.octopus.energy/v1/products/OUTGOING-VAR-24-10-26/electricity-tariffs/E-1R-OUTGOING-VAR-24-10-26-{dno_region}/standard-unit-rates/'
  #  - id: 'igo_agile'
  #    name: 'Intelligent GO import/Agile export'
  #    rates_import_octopus_url: 'https://api.octopus.energy/v1/products/INTELLI-VAR-24-10-29/electricity-tariffs/E-1R-INTELLI-VAR-24-10-29-{dno_region}/standard-unit-rates/'
  #    rates_export_octopus_url: 'https://api.octopus.energy/v1/products/AGILE-OUTGOING-19-05-13/electricity-tariffs/E-1R-AGILE-OUTGOING-19-05-13-{dno_region}/standard-unit-rates/'
  #  - id: 'go_fixed'
  #    name: 'GO import/Fixed export'
  #    rates_import_octopus_url: 'https://api.octopus.energy/v1/products/GO-VAR-22-10-14/electricity-tariffs/E-1R-GO-VAR-22-10-14-{dno_region}/standard-unit-rates/'
  #    rates_export_octopus_url: 'https://api.octopus.energy/v1/products/OUTGOING-VAR-24-10-26/electricity-tariffs/E-1R-OUTGOING-VAR-24-10-26-{dno_region}/standard-unit-rates/'
  #  - id: 'go_agile'
  #    name: 'GO import/Agile export'
  #    rates_import_octopus_url: 'https://api.octopus.energy/v1/products/GO-VAR-22-10-14/electricity-tariffs/E-1R-GO-VAR-22-10-14-{dno_region}/standard-unit-rates/'
  #    rates_export_octopus_url: 'https://api.octopus.energy/v1/products/AGILE-OUTGOING-19-05-13/electricity-tariffs/E-1R-AGILE-OUTGOING-19-05-13-{dno_region}/standard-unit-rates/'
  #  - id: 'agile_fixed'
  #    name: 'Agile import/Fixed export'
  #    rates_import_octopus_url: 'https://api.octopus.energy/v1/products/AGILE-24-10-01/electricity-tariffs/E-1R-AGILE-24-10-01-{dno_region}/standard-unit-rates/'
  #    rates_export_octopus_url: 'https://api.octopus.energy/v1/products/OUTGOING-VAR-24-10-26/electricity-tariffs/E-1R-OUTGOING-VAR-24-10-26-{dno_region}/standard-unit-rates/'
  #  - id: 'agile_agile'
  #    name: 'Agile import/Agile export'
  #    rates_import_octopus_url: 'https://api.octopus.energy/v1/products/AGILE-24-10-01/electricity-tariffs/E-1R-AGILE-24-10-01-{dno_region}/standard-unit-rates/'
  #    rates_export_octopus_url: 'https://api.octopus.energy/v1/products/AGILE-OUTGOING-19-05-13/electricity-tariffs/E-1R-AGILE-OUTGOING-19-05-13-{dno_region}/standard-unit-rates/'
  #  - id: 'flux'
  #    name: 'Flux import/Export'
  #    rates_import_octopus_url: 'https://api.octopus.energy/v1/products/FLUX-IMPORT-23-02-14/electricity-tariffs/E-1R-FLUX-IMPORT-23-02-14-{dno_region}/standard-unit-rates'
  #    rates_export_octopus_url: 'https://api.octopus.energy/v1/products/FLUX-EXPORT-23-02-14/electricity-tariffs/E-1R-FLUX-EXPORT-23-02-14-{dno_region}/standard-unit-rates'
  #  - id: 'cosy_fixed'
  #    name: 'Cosy import/Fixed export'
  #    rates_import_octopus_url: 'https://api.octopus.energy/v1/products/COSY-22-12-08/electricity-tariffs/E-1R-COSY-22-12-08-{dno_region}/standard-unit-rates'
  #    rates_export_octopus_url: 'https://api.octopus.energy/v1/products/OUTGOING-VAR-24-10-26/electricity-tariffs/E-1R-OUTGOING-VAR-24-10-26-{dno_region}/standard-unit-rates/'
  #  - id: 'cosy_agile'
  #    name: 'Cosy import/Agile export'
  #    rates_import_octopus_url: 'https://api.octopus.energy/v1/products/COSY-22-12-08/electricity-tariffs/E-1R-COSY-22-12-08-{dno_region}/standard-unit-rates'
  #    rates_export_octopus_url: 'https://api.octopus.energy/v1/products/AGILE-OUTGOING-19-05-13/electricity-tariffs/E-1R-AGILE-OUTGOING-19-05-13-{dno_region}/standard-unit-rates/'
  #  - id: 'snug_fixed'
  #    name: 'Snug import/Fixed export'
  #    rates_import_octopus_url: 'https://api.octopus.energy/v1/products/SNUG-24-11-07/electricity-tariffs/E-1R-SNUG-24-11-07-{dno_region}/standard-unit-rates/'
  #    rates_export_octopus_url: 'https://api.octopus.energy/v1/products/OUTGOING-VAR-24-10-26/electricity-tariffs/E-1R-OUTGOING-VAR-24-10-26-{dno_region}/standard-unit-rates/'
  #  - id: 'iflux'
  #    name: 'Intelligent Flux import/export'
  #    rates_import_octopus_url: 'https://api.octopus.energy/v1/products/INTELLI-FLUX-IMPORT-23-07-14/electricity-tariffs/E-1R-INTELLI-FLUX-IMPORT-23-07-14-{dno_region}/standard-unit-rates/'
  #    rates_export_octopus_url: 'https://api.octopus.energy/v1/products/INTELLI-FLUX-EXPORT-23-07-14/electricity-tariffs/E-1R-INTELLI-FLUX-EXPORT-23-07-14-{dno_region}/standard-unit-rates/'

  # Alert feeds - customise to your country and the alert types, severity and keep value
  #alerts:
  #  url: "https://feeds.meteoalarm.org/feeds/meteoalarm-legacy-atom-united-kingdom"
  #  event: "(Amber|Yellow|Orange|Red).*(Wind|Snow|Fog|Rain|Thunderstorm|Avalanche|Frost|Heat|Coastal event|Flood|Forestfire|Ice|Low temperature|Storm|Tornado|Tsunami|Volcano|Wildfire)"
  #  severity: "Moderate|Severe|Extreme"
  #  certainty: "Possible|Likely|Expected"
  #  keep: 40

  # Watch list, a list of sensors to watch for changes and then update the plan if they change
  # This is useful for things like the Octopus Intelligent Slot sensor so that the plan update as soon as you plugin in
  # Only uncomment the items you actually have set up above in apps.yaml, of course you can add your own as well
  # Note those using +[] are lists that are appended to this list, whereas {} items are single items only
  #watch_list:
  #  - '{octopus_intelligent_slot}'
  #  - '{octopus_ready_time}'
  #  - '{octopus_charge_limit}'
  #  - '{octopus_saving_session}'
  #  - '+[car_charging_planned]'
  #  - '+[car_charging_soc]'
  #  - '{car_charging_now}'


# 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 app 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

[markbw999]

Here is my apps.yaml

apps.yaml

[markbw999]

If you look at the predbat log the 'count register writes' seems fine.

It seems like you have an issue with GivTCP?

@springfall2008 if the problem is with GivTCP can you give any guidance on what to put in an issue report? I had assumed that GivTCP was just the conduit to the hardware and predbat issued the write requests.

[markbw999]

I just checked again this morning. The GivTCP log looks perfectly normal to me.

I based the 30k a month number of writes on data going back a couple of months. However looking at the data closer it appears the rate changed significantly around 2 July. It is now running at about 200 a day which is much more reasonable. Any insights into what might have changed?

[markbw999]

@springfall2008 I just had a thought... I can't remember the exact date but I'm pretty sure it was similar to when the writes slowed down. I was looking through predbat's config tab and realised I had quite a few settings at something other than the defaults. I couldn't remember why I had changed them so I thought you have put a lot of work into tuning these so I reset them back to the defaults. While there I also noticed I had expert mode on (again, no idea why) and turned it off. Is there anything in expert mode that I might have messed with which would account for the excessive writes - e.g. some kind of debug mode?