Open Sycamore967 opened 3 weeks ago
Ok I've had another look and can understand the apps.yaml file better now I'm not rushing. I've updated the following:
octopus_intelligent_slot: 're:(binary_sensor.octopus_intelligent_planned_dispatch_slot)' octopus_ready_time: 're:(select.octopus_target_ready_by_time)' octopus_charge_limit: 're:(select.octopus_target_state_of_charge)'
I'd be grateful is you could let me know if this should work. The history of the sensors certainly shows the intelligent dispatch slots I expected to trigger a charge cycle in Predbat and the correct charge level and ready times. The proof will be my next car charge cycle that falls outside of the normal 23:30 start time.
Looks correct to me, let me know if it works
@Sycamore967 please see the issue I had as well with Hypervolt HP3 here Make sure your car charging planned sensor and response are correct as the entity provides a different response than expected. Expected response = plugged in Actual Response = on Without that it won’t detect your car is plugged in.
Make sure your car charging planned sensor and response are correct as the entity provides a different response than expected.
I have BTW added details about checking the car charging planned sensor response to the documentation steps. It'll be in my next PR
Describe the bug Predbat isn't detecting that I have my car plugged in or that the charging slot is before 23:30
Expected behavior It used to work and I'm sure I've missed some sort of update or reconfig info I just don't know.
Predbat version
8.4.11
Environment details
Screenshots Octopus Integration sensors not available, Bottle Cap Dave senso showing next off peak start
Log file I've attached my config and a log file, plus the screenshots of my sensors predbat.zip