Describe the bug I have a new install of predbat and everytime the appdeamon processes the givenergy / agile times I get this error...

ERROR: Exception raised 'NoneType' object has no attribute 'get'

Expected behavior No error Predbat version

7.14.23

Environment details

Inverter and battery setup - Gen 2 H5 GivEnergy - 8.2Kw Battery
Standard HAOS installer or Docker - Standrad HAOS Pi
Anything else?

Screenshots

Log file appdaemon.log

Can you capture a log file from the time of the issue, debug mode is not normally required. If you are not keeping the full logs then please enable this in appdaemon.yaml (see the installation instruction in the Predbat docs area for details on how to do this)

I probably need the more detailed error message that you will find in 'system, settings, logs, appdeamon' to find out exactly the problem, but it seems like you might not have set your import or export rates correctly. If you don't have export you should set it to 0.

Hey, this might be relevant... Does it help?

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 4816, in basic_rates start_str = this_rate.get("start", "00:00:00") ^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get'

2023-12-25 15:50:04.468790 WARNING pred_bat:

On Mon, 25 Dec 2023, 15:23 Trefor Southwell, @.***> wrote:

I probably need the more detailed error message that you will find in 'system, settings, logs, appdeamon' to find out exactly the problem, but it seems like you might not have set your import or export rates correctly. If you don't have export you should set it to 0.

— Reply to this email directly, view it on GitHub https://github.com/springfall2008/batpred/issues/527#issuecomment-1869025574, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS34JH32ZCH4M6JLW2SRLC3YLGK6NAVCNFSM6AAAAABBCNQLKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZGAZDKNJXGQ . You are receiving this because you authored the thread.Message ID: @.***>

On Mon, 25 Dec 2023, 15:53 Daniel Whelan, @.***> wrote:

Hey, this might be relevant... Does it help?

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 4816, in basic_rates start_str = this_rate.get("start", "00:00:00") ^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get'

2023-12-25 15:50:04.468790 WARNING pred_bat:

On Mon, 25 Dec 2023, 15:23 Trefor Southwell, @.***> wrote:

I probably need the more detailed error message that you will find in 'system, settings, logs, appdeamon' to find out exactly the problem, but it seems like you might not have set your import or export rates correctly. If you don't have export you should set it to 0.

— Reply to this email directly, view it on GitHub https://github.com/springfall2008/batpred/issues/527#issuecomment-1869025574, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS34JH32ZCH4M6JLW2SRLC3YLGK6NAVCNFSM6AAAAABBCNQLKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZGAZDKNJXGQ . You are receiving this because you authored the thread.Message ID: @.***>

File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10523, in run_time_loop self.update_pred(scheduled=True) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(*args, kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9766, in update_pred self.fetch_sensor_data() File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9357, in fetch_sensor_data self.rate_export = self.basic_rates(self.get_arg("rates_export_override", [], indirect=False), "export", self.rate_export) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 4816, in basic_rates start_str = this_rate.get("start", "00:00:00") ^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get' 2023-12-25 16:35:03.783425 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 16:40:04.044928 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 16:40:04.047180 WARNING pred_bat: Unexpected error in worker for App pred_bat: 2023-12-25 16:40:04.048795 WARNING pred_bat: Worker Ags: {'id': 'b21a4515aea74f6fb476a3817a8c3233', 'name': 'pred_bat', 'objectid': 'ae65d3fcd06144d488a222d829065e05', 'type': 'scheduler', 'function': <bound method PredBat.run_time_loop of <predbat.PredBat object at 0x7fb8b97150>>, 'pin_app': True, 'pin_thread': 0, 'kwargs': {'interval': 300, 'random_start': 0, 'random_end': 0, '__thread_id': 'thread-0'}} 2023-12-25 16:40:04.050078 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 16:40:04.057479 WARNING pred_bat: Traceback (most recent call last): File "/usr/lib/python3.11/site-packages/appdaemon/threading.py", line 1022, in worker funcref(self.AD.sched.sanitize_timer_kwargs(app, args["kwargs"])) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(*args, *kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10527, in run_time_loop raise e File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10523, in run_time_loop self.update_pred(scheduled=True) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(args, kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9766, in update_pred self.fetch_sensor_data() File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9357, in fetch_sensor_data self.rate_export = self.basic_rates(self.get_arg("rates_export_override", [], indirect=False), "export", self.rate_export) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 4816, in basic_rates start_str = this_rate.get("start", "00:00:00") ^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get' 2023-12-25 16:40:04.057966 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 16:45:03.613576 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 16:45:03.614684 WARNING pred_bat: Unexpected error in worker for App pred_bat: 2023-12-25 16:45:03.615374 WARNING pred_bat: Worker Ags: {'id': 'b21a4515aea74f6fb476a3817a8c3233', 'name': 'pred_bat', 'objectid': 'ae65d3fcd06144d488a222d829065e05', 'type': 'scheduler', 'function': <bound method PredBat.run_time_loop of <predbat.PredBat object at 0x7fb8b97150>>, 'pin_app': True, 'pin_thread': 0, 'kwargs': {'interval': 300, 'random_start': 0, 'random_end': 0, 'thread_id': 'thread-0'}} 2023-12-25 16:45:03.616283 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 16:45:03.621972 WARNING pred_bat: Traceback (most recent call last): File "/usr/lib/python3.11/site-packages/appdaemon/threading.py", line 1022, in worker funcref(self.AD.sched.sanitize_timer_kwargs(app, args["kwargs"])) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(*args, *kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10527, in run_time_loop raise e File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10523, in run_time_loop self.update_pred(scheduled=True) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(args, **kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9766, in update_pred self.fetch_sensor_data() File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9357, in fetch_sensor_data self.rate_export = self.basic_rates(self.get_arg("rates_export_override", [], indirect=False), "export", self.rate_export) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 4816, in basic_rates start_str = this_rate.get("start", "00:00:00") ^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get' 2023-12-25 16:45:03.623503 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 16:50:04.063567 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 16:50:04.064236 WARNING pred_bat: Unexpected error in worker for App pred_bat: 2023-12-25 16:50:04.064787 WARNING pred_bat: Worker Ags: {'id': 'b21a4515aea74f6fb476a3817a8c3233', 'name': 'pred_bat', 'objectid': 'ae65d3fcd06144d488a222d829065e05', 'type': 'scheduler', 'function': <bound method PredBat.run_time_loop of <predbat.PredBat object at 0x7fb8b97150>>, 'pin_app': True, 'pin_thread': 0, 'kwargs': {'interval': 300, 'random_start': 0, 'random_end': 0, 'thread_id': 'thread-0'}} 2023-12-25 16:50:04.065682 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 16:50:04.073193 WARNING pred_bat: Traceback (most recent call last): File "/usr/lib/python3.11/site-packages/appdaemon/threading.py", line 1022, in worker funcref(self.AD.sched.sanitize_timer_kwargs(app, args["kwargs"])) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(*args, *kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10527, in run_time_loop raise e File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10523, in run_time_loop self.update_pred(scheduled=True) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(args, **kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9766, in update_pred self.fetch_sensor_data() File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9357, in fetch_sensor_data self.rate_export = self.basic_rates(self.get_arg("rates_export_override", [], indirect=False), "export", self.rate_export) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 4816, in basic_rates start_str = this_rate.get("start", "00:00:00") ^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get' 2023-12-25 16:50:04.074073 WARNING pred_bat: ------------------------------------------------------------

What is in your apps.yaml related to rates as it’s an errror in this file?

I'd be embarrassed if its something I've done. I wouldn't be suprised.

I even got a fresh copy of the yaml file from github earlier on the day just in case I'd ruined the previous.

On Mon, 25 Dec 2023, 17:26 Trefor Southwell, @.***> wrote:

What is in your apps.yaml related to rates as it’s an errror in this file?

— Reply to this email directly, view it on GitHub https://github.com/springfall2008/batpred/issues/527#issuecomment-1869062327, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS34JH6RREUTZ6Y5T35J4CDYLGZNHAVCNFSM6AAAAABBCNQLKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZGA3DEMZSG4 . You are receiving this because you authored the thread.Message ID: @.***>

------------------------------------------------------------------

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

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

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 'resensor.giv_(.+)_sockwh' geserial2 'resensor.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.giv_{geserial}_load_energy_today_kwh import_today
sensor.giv_{geserial}_import_energy_today_kwh export_today
sensor.giv_{geserial}_export_energy_today_kwh pv_today
sensor.giv_{geserial}_pv_energy_today_kwh

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

Controlsstatus - must by 1 per inverter

# num_inverters 1 #

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 reliablefaster to control

Set one per inverter

If using Docker then change homeassistant.local to the Docker IP address

giv_rest
- 'httphomeassistant.local6345'
- 'httphomeassistant.local6346'
If not using REST then instead set the Control here (one for each inverter)

- you can delete this section if using REST

charge_rate
number.giv_{geserial}_battery_charge_rate
number.givtcp2_{geserial2}_battery_charge_rate discharge_rate
number.giv_{geserial}_battery_discharge_rate
number.givtcp2_{geserial2}_battery_discharge_rate battery_power
number.giv_{geserial}_battery_power
number.givtcp2_{geserial2}_battery_power pv_power
number.giv_{geserial}_pv_power
number.givtcp2_{geserial2}_pv_power load_power
number.giv_{geserial}_load_power
number.givtcp2_{geserial2}_load_power soc_kw
sensor.giv_{geserial}_soc_kwh
sensor.givtcp2_{geserial2}_soc_kwh soc_max
sensor.giv_{geserial}_battery_capacity_kwh
sensor.givtcp2_{geserial2}_battery_capacity_kwh reserve
number.giv_{geserial}_battery_power_reserve
number.givtcp2_{geserial2}_battery_power_reserve inverter_mode
- select.giv_{geserial}_mode
- select.givtcp2_{geserial2}_mode inverter_time
- sensor.giv_{geserial}_invertor_time
- sensor.givtcp2_{geserial2}_invertor_time charge_start_time
- select.giv_{geserial}_charge_start_time_slot_1
- select.givtcp2_{geserial2}_charge_start_time_slot_1 charge_end_time
- select.giv_{geserial}_charge_end_time_slot_1
- select.givtcp2_{geserial2}_charge_end_time_slot_1 charge_limit
- number.giv_{geserial}_target_soc
- number.givtcp2_{geserial2}_target_soc scheduled_charge_enable
- switch.giv_{geserial}_enable_charge_schedule
- switch.givtcp2_{geserial2}_enable_charge_schedule scheduled_discharge_enable
- switch.giv_{geserial}_enable_discharge_schedule
- switch.givtcp2_{geserial2}_enable_discharge_schedule discharge_start_time
- select.giv_{geserial}_discharge_start_time_slot_1
- select.givtcp2_{geserial2}_discharge_start_time_slot_1 discharge_end_time
- select.giv_{geserial}_discharge_end_time_slot_1
- select.givtcp2_{geserial2}_discharge_end_time_slot_1
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
- 3600
- 3600
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

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

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 dischargecharging

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

Set these to match solcast sensor names

The regular expression (re) makes the solcast bit optional

If these don't match find your own names in Home Assistant

pv_forecasttoday re(sensor.(solcast)(pvforecast)forecast_today) pv_forecasttomorrow re(sensor.(solcast)(pvforecast)forecast_tomorrow) pv_forecastd3 re(sensor.(solcast)(pvforecast)forecast_(day_3d3)) pv_forecastd4 re(sensor.(solcast)(pvforecast)forecast_(day_4d4))

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.myenergizappi[0-9a-z]+_charge_added_sessionsensor.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_descriptionsensor.myenergizappi[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 % sensorsvalues.

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

- 'renumber.tsunami_charge_limit'

car_charging_soc

- 'resensor.tsunami_battery'

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.octopusenergy([0-9a-z]+)_intelligent_dispatching)' octopus_ready_time 're(time.octopusenergy([0-9a-z]+)_intelligent_ready_time)' octopus_charge_limit 're(number.octopusenergy([0-9a-z]+)_intelligent_charge_limit)'

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.octopusenergy([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_importrates_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.(octopusenergy)electricity[0-9a-z]+[0-9a-z]+_current_rate)'

metric_octopus_export 're(sensor.(octopusenergy)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.(octopusenergy)electricity[0-9a-z]+[0-9a-z]+_current_standing_charge)'

Or set your actual rates across time for import and export

If startend is missing it's assumed to be a fixed rate

Gaps are filled with zero rate

rates_import

- start 003000

end 043000

rate 7.5

- start 043000

end 003000

rate 40.0

# rates_export
- rate 15.0
Can be used instead of the plugin to get import rates directly online

Overrides metric_octopus_import and rates_import

rates_import_octopus_url httpsapi.octopus.energyv1productsFLUX-IMPORT-23-02-14electricity-tariffsE-1R-FLUX-IMPORT-23-02-14-Astandard-unit-rates

rates_import_octopus_url httpsapi.octopus.energyv1productsAGILE-FLEX-BB-23-02-08electricity-tariffsE-1R-AGILE-FLEX-BB-23-02-08-Astandard-unit-rates

Overrides metric_octopus_export and rates_export

rates_export_octopus_url httpsapi.octopus.energyv1productsFLUX-EXPORT-BB-23-02-14electricity-tariffsE-1R-FLUX-EXPORT-BB-23-02-14-Astandard-unit-rates

rates_export_octopus_url httpsapi.octopus.energyv1productsAGILE-OUTGOING-BB-23-02-28electricity-tariffsE-1R-AGILE-OUTGOING-BB-23-02-28-Astandard-unit-rates

rates_export_octopus_url httpsapi.octopus.energyv1productsOUTGOING-FIX-12M-BB-23-02-09electricity-tariffsE-1R-OUTGOING-FIX-12M-BB-23-02-09-Astandard-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 '140000'

end '143000'

rate 5

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 23rd of the weight and the second 13rd

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

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.(octopusenergy)gas[0-9a-z]+[0-9a-z]+_current_rate)'

Nordpool market energy rates

futurerate_url 'httpswww.nordpoolgroup.comapimarketdatapage325currency=GBP'

futurerate_adjust_import False

futurerate_adjust_export True

futurerate_peak_start 160000

futurerate_peak_end 190000

futurerate_peak_premium_import 14

futurerate_peak_premium_export 6.5

You probably need one space before the dash eg

rate_export:

rate: 15

Sorry still no joy.

Maybe I should delete everything batpred related and start from scratch.

On Mon, 25 Dec 2023, 17:47 Trefor Southwell, @.***> wrote:

You probably need one space before the dash eg

rate_export:

rate: 15

— Reply to this email directly, view it on GitHub https://github.com/springfall2008/batpred/issues/527#issuecomment-1869067684, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS34JH5YYVEYXS4QM5PUHG3YLG345AVCNFSM6AAAAABBCNQLKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZGA3DONRYGQ . You are receiving this because you authored the thread.Message ID: @.***>

------------------------------------------------------------------

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

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

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 'resensor.giv_(.+)_sockwh' geserial2 'resensor.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.giv_{geserial}_load_energy_today_kwh import_today
sensor.giv_{geserial}_import_energy_today_kwh export_today
sensor.giv_{geserial}_export_energy_today_kwh pv_today
sensor.giv_{geserial}_pv_energy_today_kwh

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

Controlsstatus - must by 1 per inverter

# num_inverters 1 #

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 reliablefaster to control

Set one per inverter

If using Docker then change homeassistant.local to the Docker IP address

giv_rest
- 'httphomeassistant.local6345'
- 'httphomeassistant.local6346'
If not using REST then instead set the Control here (one for each inverter)

- you can delete this section if using REST

charge_rate
number.giv_{geserial}_battery_charge_rate
number.givtcp2_{geserial2}_battery_charge_rate discharge_rate
number.giv_{geserial}_battery_discharge_rate
number.givtcp2_{geserial2}_battery_discharge_rate battery_power
number.giv_{geserial}_battery_power
number.givtcp2_{geserial2}_battery_power pv_power
number.giv_{geserial}_pv_power
number.givtcp2_{geserial2}_pv_power load_power
number.giv_{geserial}_load_power
number.givtcp2_{geserial2}_load_power soc_kw
sensor.giv_{geserial}_soc_kwh
sensor.givtcp2_{geserial2}_soc_kwh soc_max
sensor.giv_{geserial}_battery_capacity_kwh
sensor.givtcp2_{geserial2}_battery_capacity_kwh reserve
number.giv_{geserial}_battery_power_reserve
number.givtcp2_{geserial2}_battery_power_reserve inverter_mode
- select.giv_{geserial}_mode
- select.givtcp2_{geserial2}_mode inverter_time
- sensor.giv_{geserial}_invertor_time
- sensor.givtcp2_{geserial2}_invertor_time charge_start_time
- select.giv_{geserial}_charge_start_time_slot_1
- select.givtcp2_{geserial2}_charge_start_time_slot_1 charge_end_time
- select.giv_{geserial}_charge_end_time_slot_1
- select.givtcp2_{geserial2}_charge_end_time_slot_1 charge_limit
- number.giv_{geserial}_target_soc
- number.givtcp2_{geserial2}_target_soc scheduled_charge_enable
- switch.giv_{geserial}_enable_charge_schedule
- switch.givtcp2_{geserial2}_enable_charge_schedule scheduled_discharge_enable
- switch.giv_{geserial}_enable_discharge_schedule
- switch.givtcp2_{geserial2}_enable_discharge_schedule discharge_start_time
- select.giv_{geserial}_discharge_start_time_slot_1
- select.givtcp2_{geserial2}_discharge_start_time_slot_1 discharge_end_time
- select.giv_{geserial}_discharge_end_time_slot_1
- select.givtcp2_{geserial2}_discharge_end_time_slot_1
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
- 3600
- 3600
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

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

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 dischargecharging

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

Set these to match solcast sensor names

The regular expression (re) makes the solcast bit optional

If these don't match find your own names in Home Assistant

pv_forecasttoday re(sensor.(solcast)(pvforecast)forecast_today) pv_forecasttomorrow re(sensor.(solcast)(pvforecast)forecast_tomorrow) pv_forecastd3 re(sensor.(solcast)(pvforecast)forecast_(day_3d3)) pv_forecastd4 re(sensor.(solcast)(pvforecast)forecast_(day_4d4))

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.myenergizappi[0-9a-z]+_charge_added_sessionsensor.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_descriptionsensor.myenergizappi[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 % sensorsvalues.

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

- 'renumber.tsunami_charge_limit'

car_charging_soc

- 'resensor.tsunami_battery'

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.octopusenergy([0-9a-z]+)_intelligent_dispatching)' octopus_ready_time 're(time.octopusenergy([0-9a-z]+)_intelligent_ready_time)' octopus_charge_limit 're(number.octopusenergy([0-9a-z]+)_intelligent_charge_limit)'

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.octopusenergy([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_importrates_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.(octopusenergy)electricity[0-9a-z]+[0-9a-z]+_current_rate)'

metric_octopus_export 're(sensor.(octopusenergy)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.(octopusenergy)electricity[0-9a-z]+[0-9a-z]+_current_standing_charge)'

Or set your actual rates across time for import and export

If startend is missing it's assumed to be a fixed rate

Gaps are filled with zero rate

rates_import

- start 003000

end 043000

rate 7.5

- start 043000

end 003000

rate 40.0

# rates_export
rate 15

Can be used instead of the plugin to get import rates directly online

Overrides metric_octopus_import and rates_import

rates_import_octopus_url httpsapi.octopus.energyv1productsFLUX-IMPORT-23-02-14electricity-tariffsE-1R-FLUX-IMPORT-23-02-14-Astandard-unit-rates

rates_import_octopus_url httpsapi.octopus.energyv1productsAGILE-FLEX-BB-23-02-08electricity-tariffsE-1R-AGILE-FLEX-BB-23-02-08-Astandard-unit-rates

Overrides metric_octopus_export and rates_export

rates_export_octopus_url httpsapi.octopus.energyv1productsFLUX-EXPORT-BB-23-02-14electricity-tariffsE-1R-FLUX-EXPORT-BB-23-02-14-Astandard-unit-rates

rates_export_octopus_url httpsapi.octopus.energyv1productsAGILE-OUTGOING-BB-23-02-28electricity-tariffsE-1R-AGILE-OUTGOING-BB-23-02-28-Astandard-unit-rates

rates_export_octopus_url httpsapi.octopus.energyv1productsOUTGOING-FIX-12M-BB-23-02-09electricity-tariffsE-1R-OUTGOING-FIX-12M-BB-23-02-09-Astandard-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 '140000'

end '143000'

rate 5

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 23rd of the weight and the second 13rd

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

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.(octopusenergy)gas[0-9a-z]+[0-9a-z]+_current_rate)'

Nordpool market energy rates

futurerate_url 'httpswww.nordpoolgroup.comapimarketdatapage325currency=GBP'

futurerate_adjust_import False

futurerate_adjust_export True

futurerate_peak_start 160000

futurerate_peak_end 190000

futurerate_peak_premium_import 14

futurerate_peak_premium_export 6.5

File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10523, in run_time_loop self.update_pred(scheduled=True) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(*args, kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9766, in update_pred self.fetch_sensor_data() File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9357, in fetch_sensor_data self.rate_export = self.basic_rates(self.get_arg("rates_export_override", [], indirect=False), "export", self.rate_export) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 4816, in basic_rates start_str = this_rate.get("start", "00:00:00") ^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get' 2023-12-25 18:15:03.489257 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 18:20:03.570429 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 18:20:03.571784 WARNING pred_bat: Unexpected error in worker for App pred_bat: 2023-12-25 18:20:03.572234 WARNING pred_bat: Worker Ags: {'id': 'b21a4515aea74f6fb476a3817a8c3233', 'name': 'pred_bat', 'objectid': 'ae65d3fcd06144d488a222d829065e05', 'type': 'scheduler', 'function': <bound method PredBat.run_time_loop of <predbat.PredBat object at 0x7fb8b97150>>, 'pin_app': True, 'pin_thread': 0, 'kwargs': {'interval': 300, 'random_start': 0, 'random_end': 0, '__thread_id': 'thread-0'}} 2023-12-25 18:20:03.572736 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 18:20:03.579934 WARNING pred_bat: Traceback (most recent call last): File "/usr/lib/python3.11/site-packages/appdaemon/threading.py", line 1022, in worker funcref(self.AD.sched.sanitize_timer_kwargs(app, args["kwargs"])) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(*args, *kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10527, in run_time_loop raise e File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10523, in run_time_loop self.update_pred(scheduled=True) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(args, kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9766, in update_pred self.fetch_sensor_data() File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9357, in fetch_sensor_data self.rate_export = self.basic_rates(self.get_arg("rates_export_override", [], indirect=False), "export", self.rate_export) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 4816, in basic_rates start_str = this_rate.get("start", "00:00:00") ^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get' 2023-12-25 18:20:03.580683 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 18:25:03.579399 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 18:25:03.581169 WARNING pred_bat: Unexpected error in worker for App pred_bat: 2023-12-25 18:25:03.582254 WARNING pred_bat: Worker Ags: {'id': 'b21a4515aea74f6fb476a3817a8c3233', 'name': 'pred_bat', 'objectid': 'ae65d3fcd06144d488a222d829065e05', 'type': 'scheduler', 'function': <bound method PredBat.run_time_loop of <predbat.PredBat object at 0x7fb8b97150>>, 'pin_app': True, 'pin_thread': 0, 'kwargs': {'interval': 300, 'random_start': 0, 'random_end': 0, 'thread_id': 'thread-0'}} 2023-12-25 18:25:03.582976 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 18:25:03.588416 WARNING pred_bat: Traceback (most recent call last): File "/usr/lib/python3.11/site-packages/appdaemon/threading.py", line 1022, in worker funcref(self.AD.sched.sanitize_timer_kwargs(app, args["kwargs"])) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(*args, *kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10527, in run_time_loop raise e File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10523, in run_time_loop self.update_pred(scheduled=True) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(args, **kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9766, in update_pred self.fetch_sensor_data() File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9357, in fetch_sensor_data self.rate_export = self.basic_rates(self.get_arg("rates_export_override", [], indirect=False), "export", self.rate_export) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 4816, in basic_rates start_str = this_rate.get("start", "00:00:00") ^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get' 2023-12-25 18:25:03.588943 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 18:30:03.503049 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 18:30:03.503913 WARNING pred_bat: Unexpected error in worker for App pred_bat: 2023-12-25 18:30:03.505319 WARNING pred_bat: Worker Ags: {'id': 'b21a4515aea74f6fb476a3817a8c3233', 'name': 'pred_bat', 'objectid': 'ae65d3fcd06144d488a222d829065e05', 'type': 'scheduler', 'function': <bound method PredBat.run_time_loop of <predbat.PredBat object at 0x7fb8b97150>>, 'pin_app': True, 'pin_thread': 0, 'kwargs': {'interval': 300, 'random_start': 0, 'random_end': 0, 'thread_id': 'thread-0'}} 2023-12-25 18:30:03.507156 WARNING pred_bat: ------------------------------------------------------------ 2023-12-25 18:30:03.512498 WARNING pred_bat: Traceback (most recent call last): File "/usr/lib/python3.11/site-packages/appdaemon/threading.py", line 1022, in worker funcref(self.AD.sched.sanitize_timer_kwargs(app, args["kwargs"])) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(*args, *kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10527, in run_time_loop raise e File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 10523, in run_time_loop self.update_pred(scheduled=True) File "/usr/lib/python3.11/site-packages/appdaemon/adbase.py", line 35, in f_app_lock return f(args, **kw) ^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9766, in update_pred self.fetch_sensor_data() File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 9357, in fetch_sensor_data self.rate_export = self.basic_rates(self.get_arg("rates_export_override", [], indirect=False), "export", self.rate_export) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/homeassistant/appdaemon/apps/batpred/predbat.py", line 4816, in basic_rates start_str = this_rate.get("start", "00:00:00") ^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get' 2023-12-25 18:30:03.514567 WARNING pred_bat: ------------------------------------------------------------

Can you attach your apps.yaml as file rather than cut pasting it so I can check the format?

Here you go ☺️

On Mon, 25 Dec 2023, 18:56 Trefor Southwell, @.***> wrote:

Can you attach your apps.yaml as file rather than cut pasting it so I can check the format?

— Reply to this email directly, view it on GitHub https://github.com/springfall2008/batpred/issues/527#issuecomment-1869085774, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS34JH6ZCBUVZRU7NHYPVJDYLHD57AVCNFSM6AAAAABBCNQLKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRZGA4DKNZXGQ . You are receiving this because you authored the thread.Message ID: @.***>

Ok, I completely removed and reinstalled and everything looks fine. Thanks for your time!

For reference the attached apps.yaml was corrupted, e.g. colons were missing

springfall2008 / batpred

pred_bat: ERROR: Exception raised 'NoneType' object has no attribute 'get' #527

2023-12-25 15:50:04.468790 WARNING pred_bat:

2023-12-25 15:50:04.468790 WARNING pred_bat:

------------------------------------------------------------------

This is an example configuration, please modify it

------------------------------------------------------------------

Sets the prefix for all created entities in HA - only change if you want to run more than once instance

Timezone to work in

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

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

Sets the maximum period of zero load before the gap is filled, default 30 minutes

To disable set it to 1440

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 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 loadimport 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

Controlsstatus - must by 1 per inverter

Run balance inverters every N seconds (0=disabled) - only for multi-inverter

When set use the REST API rather than HA entity for control, should be more reliablefaster to control

Set one per inverter

If using Docker then change homeassistant.local to the Docker IP address

If not using REST then instead set the Control here (one for each inverter)

- you can delete this section if using REST

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

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%

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

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

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

Clock skew adjusts the Appdaemon time

This is the time that Predbat takes actions like starting dischargecharging

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

Set these to match solcast sensor names

The regular expression (re) makes the solcast bit optional

If these don't match find your own names in Home Assistant

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

Defines the number of cars modelled by the system, set to 0 for no car

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