Ohme car charger login

[corautem]

Can anyone help me, please? If I have the Ohme account credentials filled in, do I still need the old Ohme car charging setup in Apps.yaml?
Do I keep the... :
ohme_name: "ohme_x"
car_charging_energy: "sensor.ohme_{ohme_name}energy"
car_charging_planned:
- "sensor.ohme{ohme_name}status"
car_charging_planned_response:
octopus_intelligent_slot: "ohme.list_charge_slots"
octopus_intelligent_slot_action_config: "xxxxxxxxxxxxxxxxxxxxxx"
octopus_ready_time: "time.ohme{ohme_name}target_time"
octopus_charge_limit: "number.ohme{ohme_name}_target_percentage" ...etc?
It's unclear to me now what to keep and what to comment out.
It used to work fine, but I noticed, now it will charge the car from the house battery during Octopus Intelligent slots.

[gcoan]

Details of setting up Ohme with the new HA integration is covered in the devices section of the documentation https://springfall2008.github.io/batpred/devices/#new-ohme-integration

If you want to stop the battery draining into the car when the car is charging you need to turn switch.predbat_car_charging_from_battery to Off
See https://springfall2008.github.io/batpred/car-charging/#additional-car-charging-configurations

[corautem]

Thank you for your reply. Sorry if I misspoke, English is not my first language. With the Ohme account credentials, I meant the part where I fill in the Ohme account name and password, because with that filled in, Predbat reports 15 entities on the Components tab

I used to use the one you point me to, but that gives me a warning in the logs now:

• Warn: Unable to get data from binary_sensor.predbat_ohme_slot_active - octopus_intelligent_slot using action config xxxxxxxxxxx result was None
• Warn: Service call binary_sensor/predbat_ohme_slot_active data {'config_entry': 'xxxxxxxxxxxxx'} failed with response None