Predbat and Ohme

I've changed to an Ohme Home Pro EVSE. I have enabled the integration in Home Assistant. What do I need to do to stop the GivEnergy batteries dumping into the car during an out-of -hours slot?

The documentation (https://springfall2008.github.io/batpred/devices/#ohme) is, I think, referring to the obsolete Ohme integration. For example, it says

which is now not a part of the offical HA Ohme integration.

I have the various Ohme entities visible, but Predbat doesn't seem to see the IO charging. The Predbat plan is empty under the "Car kWh" section.

Zakalwe If you are on Octopus Intelligent then Predbat follows the Octopus Intelligent control of the car charging and so when OI starts charging the car, Predbat will charge the batteries at the same time. You need to configure apps.yaml to point to the Octopus Intelligent sensors from the Octopus Integration

https://springfall2008.github.io/batpred/car-charging/

If there is a new official HA Ohme integration then the documentation is probably out of date. Happy to change it if you can advise what the new equivalent sensors are.

Hi Geoffrey,

Yes, Ohme now has an official integration built into HA. https://www.home-assistant.io/integrations/ohme/

The sensors are:
Ohme Home Pro Approve charge: button.ohme_home_pro_approve_charge
Ohme Home Pro Status: sensor.ohme_home_pro_status
Ohme Home Pro Current: sensor.ohme_home_pro_current
Ohme Home Pro Power: sensor.ohme_home_pro_power
Ohme Home Pro Energy: sensor.ohme_home_pro_energy
Ohme Home Pro CT current: sensor.ohme_home_pro_ct_current

The old integration needed: car_charging_energy: 'sensor.ohme_session_energy'
I'm not sure what the equivalent now is?

Zakalwe car_charging_energy is only used to remove historic car charging kWh from your house load so as to not pollute the predictions https://springfall2008.github.io/batpred/apps-yaml/#car-charging-filtering

I would guess it's sensor.ohme_home_pro_energy but whether you need to configure this depends on whether givtcp "sees" the car charging as house load or not. Depends on how your EV charger and givenergy CT clamp are wired up

geoffreycoan
The CT clamp is wired to see the whole house load (the charger uses it for load balancing).

My issue seems to be that Predbat is not "seeing" the car charger and is dumping the batteries into the car when their is an out-of-offpeak slot generated.

Zakalwe You said earlier you were on IO. To confirm, Intelligent Octopus Go?

In which case Predbat really doesn’t care about the car charger, it takes the charging slot information from the Octopus integration and will ensure the batteries don’t discharge when Octopus adds extra slots.

Follow the setup instructions for Octopus Intelligent Go as linked above.

Set octopus_intelligent_slot in apps.yaml to point to the Intelligent Slot sensor in the Octopus Energy integration. You should not need to change this, but its worth checking the Predbat logfile to confirm that it has found your Octopus account details

Set switch.predbat_octopus_intelligent_charging to True

The official Ohme integration is lacking features until Dan adds them in. I suggest you use the custom one until there is feature parity

You'll need to point Predbat to the binary_sensor.ohme_home_pro_charge_slot_active sensor as this mimics plannedDispatches.

@geoffreycoan the Octopus integration doesn't provide the same data as car APIs etc if you have an Ohme hence this workaround

AHH, right. I was under the assumption that the custom integration had been deprecated in favour of the official one.
I'll give that a go.

OK, here's what I've found. Bear in mind that I am using the Ohme Home Pro unit.
Firstly the Predbat documentation says:
octopus_intelligent_slot: 'binary_sensor.ohme_slot_active'
octopus_ready_time: 'time.ohme_target_time'
octopus_charge_limit: 'number.ohme_target_percent'

The naming convention is incorrect. The sensors (using the older customer integration) are:
octopus_intelligent_slot: 'binary_sensor.ohme_home_pro_charge_slot_active'
octopus_ready_time: 'time.ohme_home_pro_target_time'
octopus_charge_limit: 'number.ohme_home_pro_target_percent'

I assume that these would be different if using a different Ohme charger.

Secondly, the Predbat docs say:

I cannot find any sensor ending with _session_energy. I'm guessing that is why the Predbat plan is not picking up the Ohme charging?

Zakalwe deanjesper if between you you can advise how the documentation needs to be updated, I can update it. Ideally for the new HA core integration if it contains enough features to work with Predbat

It presumably was right at the time it was written, but maybe for different devices it behaves differently

Zakalwe I cannot find any sensor ending with _session_energy. I'm guessing that is why the Predbat plan is not picking up the Ohme charging?

According to the custom integration documentation, the entities include:

This integration exposes the following entities:

Sensors (Other)
…
Energy Usage (kWh) - Energy used in the current/last session. This is supported by the energy dashboard.

Maybe something like sensor.ohme_home_pro_energy_usage ?

It seems to be working now- charging the car without draining the batteries.

However, the Predbat plan is not displaying the charging slots.

I also hope that these slots are at off-peak rates! I do seem to get many more daytime slots than I ever saw with the Tesla integration!

Zakalwe However, the Predbat plan is not displaying the charging slots.

That’s a crazy amount of charging slots. As you say Predbat doesn’t seem to recognise the charging and is planning to export during most of the evening slots.

What do you have setup in apps.yaml for your car setup?
Particularly octopus_intelligent_slot what does it point to and what is that sensor currently reporting?

geoffreycoan
Nothing at the moment. There wasn't an easy way to link a Tesla without paying (I'm tight!) and I haven't investigated if there's anyway to link the replacement Genesis.

Zakalwe ah that will explain why Predbat doesn't know about these charging slots.

Do they not come through the octopus integration sensor
binary_sensor.octopus_intelligent_slot or binary_sensor.octopus_energy_intelligent_dispatching ?

Dunno.
It worked fine before. That was when using an Andersen charger (no integration) and the Tesla (again, not integrated into HA). I thought that it was picking the slots up from the Octopus Bottlecap Dave integration.

geoffreycoan Particularly octopus_intelligent_slot what does it point to and what is that sensor currently reporting?

I set that up as per the Predbat documentation (with a correction for the naming of the sensor).

Zakalwe

Hi Folks, I am just wondering if this got sorted?

I have followed the instructions for the "new ohme integration" in this page. Not changed any sensor names from those described on the page. But I am still not seeing the charging slots in predbat.

The log shows the following error:

31939 2025-12-21 10:35:00.821922: Warn: Unable to get data from binary_sensor.octopus_energy_00000000_0009_4000_8020_00000006d6f5_intelligent_dispatching - octopus_intelligent_slot using action config XXX, result was None
31938 2025-12-21 10:35:00.821340: Warn: Service call binary_sensor/octopus_energy_00000000_0009_4000_8020_00000006d6f5_intelligent_dispatching data {'config_entry': 'XXX'} failed with response None

For XXX, I followed the instructions to obtain my device ID.

If you got it working, would you mind explaining what I am doing wrong?

Thanks

Ben

BenS I would double check the New Ohme integration instructions in the predbat documentation https://springfall2008.github.io/batpred/devices/#new-ohme-integration

It looks like your apps.yaml is set to try to find the IOG slots from the Octopus integration, but as I understand it, for Ohme chargers the slots are in the Ohme app not the Octopus app, so you need to get the slot details from the Ohme integration.

There is a 3rd option now to use the inbuilt Ohme component in predbat https://springfall2008.github.io/batpred/components/#ohme-charger-ohme - that probably does need to be better signposted

It looks like you just have the sensor name wrong in your apps.yaml

geoffreycoan
Thanks for the pointer. That worked no problems and very straightforward.
I have removed the other integration lines.

All good!

Ben.