Rates not updating after Intelligent Dispatch slot starts

[mdeakin99]

As discussed on Facebook Group. The slot rates in the plan dont update even though I have confirmed an Intelligent Slot has been dispatched.

Car column also doesnt show predicted/requested energy amount.

Uploading log and debug as requested by Trefor

Log

predbat.log

Two debugs as I clicked it twice as was expecting it to download

predbat_debug_19_15_00.yaml

predbat_debug_19_10_00.yaml

[springfall2008]

Thanks for the logs and debug files - found the cause.

Root cause: in your apps.yaml, car_charging_planned_response is set to a list of Title Case values (e.g. 'Connected', 'EV Connected', 'Charging'), matching the exact state strings the myenergi Zappi integration reports for sensor.myenergi_zappi_20855673_plug_status. Predbat's matching code lowercases the sensor's value before comparing, but never lowercased the response list itself - so "EV Connected".lower() was compared against "EV Connected" (still capitalised) and never matched.

Because switch.predbat_octopus_intelligent_ignore_unplugged is enabled, that failed match meant Predbat treated the car as unplugged on every single run (Car 0 using Octopus Intelligent is unplugged in your log, all day). That's why the Intelligent dispatch slots never made it into the plan (rates not updating) and the Car column showed no requested energy - both read from the same car_charging_slots list that this bug kept empty.

Workaround (no code change needed): lowercase the entries in car_charging_planned_response in your apps.yaml, e.g.:

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'

(Also worth double-checking 'EV Disconnected' - that's currently in your response list, which means Predbat would treat "disconnected" as "plugged in and planned". You probably want that removed, or replaced with the actual "unplugged" state kept out of the list entirely.)

Fix: I've pushed a code fix so this matching is case-insensitive on both sides going forward, regardless of how a given integration capitalises its state strings - no apps.yaml change will be required once it's released.