Recommended configuration for Ohme charger and Octopus Intelligent Go

[mudge]

I've just had an Ohme Home Pro charger installed and integrated directly with Octopus Intelligent Go for use with a Skoda Enyaq (where the charger is the device in my Octopus account, not the EV itself).

Reading the following:

• https://springfall2008.github.io/batpred/devices/#octopus-energy
• https://springfall2008.github.io/batpred/devices/#ohme-ha-in-built-integration
• https://springfall2008.github.io/batpred/car-charging/#octopus-led-charging

What is the current recommended configuration out of Octopus, Ohme, or others?

I'm currently using the following with the Octopus HA integration and built-in Ohme integration as per https://springfall2008.github.io/batpred/devices/#ohme-ha-in-built-integration:

  num_cars: 1

  ohme_name: 're:time.ohme_(.+)_target_time'
  car_charging_energy: 'sensor.ohme_{ohme_name}_energy'

  car_charging_planned:
    - "sensor.ohme_{ohme_name}_status"
    - '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'
    - "plugged_in"
    - "Plugged in"
    - "pending_approval"

  octopus_intelligent_slot: 'ohme.list_charge_slots'
  octopus_intelligent_slot_action_config: 'XXXXXX'
  octopus_ready_time: 'time.ohme_{ohme_name}_target_time'
  octopus_charge_limit: 'number.ohme_{ohme_name}_target_percentage'

(Where XXXXXX is the value shown under the ohme.list_charge_slots state in the HA Developer Tools.)

However, the "Apps" view of Predbat shows the following:

The docs also mention switch.predbat_octopus_intelligent_ignore_unplugged but that no longer appears to be an option?

[mudge]

Or is a better option to stick with "Octopus-led" charging, preferring entities from the Octopus integration as much as possible, e.g.

  octopus_intelligent_slot: 're:(binary_sensor.octopus_energy([0-9a-z_]+|)_intelligent_dispatching)'

  # As the Octopus energy integration doesn't make target-time or charge-targets available for Ohme
  octopus_ready_time: 'time.ohme_{ohme_name}_target_time'
  octopus_charge_limit: 'number.ohme_{ohme_name}_target_percentage'

[mudge]

To answer my own question:

• Integrating Octopus Intelligent Go directly with Ohme means that the Octopus integration entities (i.e. those matched by re:(binary_sensor.octopus_energy([0-9a-z_]+|)_intelligent_dispatching) will not contain the charging schedule created by Ohme
• Instead, you must use the ohme.list_charge_slots and octopus_intelligent_slot_action_config documented in https://springfall2008.github.io/batpred/devices/#ohme-ha-in-built-integration (despite the misleading ohme.list_charge_slots = ? shown in the web UI)
• You will then be able to see the schedule in Predbat's predbat.car_charging_start entity
• switch.predbat_octopus_intelligent_ignore_unplugged is an option but only if you enable Expert Mode