dan-r / HomeAssistant-Ohme

Unofficial Home Assistant integration for interacting with Ohme EV chargers (EVSE) 🚗⚡️
MIT License
37 stars 10 forks source link

Slot Active sensor incorrect state #80

Closed HnabrU closed 4 days ago

HnabrU commented 2 months ago

What happened? 'binary_sensor.ohme_slot_active' keeps 'ON' despite car charging stopped.

I have 2 x EVs (none of them using APIs), Octopus IOG integrated via Ohme Home Pro EVSE, GivEnergy inverter and battery. I use Predbat HA integration to manage all these. Whenever I use either of EVs I seem to have false info re active slots (despite slot times being visible in Ohme integration correctly). Below is an example from yesterday. Car plugged in around 19:00, given slots by IOG, finished active charging at 21:49, but 'ohme_slot_active' still active until 22:45 when I physically disconnected the car from EVSE (see screenshots). This causes the Predbat integration to work incorrectly as 'ohme_slot_active' sensor is a source of various automations like charging/discharging home battery.

Screenshots: Ohme app IOG slots notification: image

Relevant Ohme integration indications after IOG slots received: image

Ohme integration idications more than 30 minutes after car finished charging (NB. Charge Slot Active still ON): image

'binary_sensor.ohme_slot_active' history for 08/05/24 (NB. active state changed to OFF almost 1 hr after car stopped charging only becasue I unplugged the car): image

'binary_sensor.ohme_car_charging' shows correctly when car finished active charging: image

Expected behavior Slot Active sensor sets to 'OFF' when car charging stops and 30-minutes slots (i.e. XX:00 or XX:30) finishes.

Log Output Any relevant logs from Home Assistant.

Home Assistant Version Core 2024.5.2, OS 12.3

Integration Version Ohme integration v0.8.2 HACS 1.34.0

Additional context Ohme Home Pro FW 2.62 (it was th same with 1.22 I had before)

dan-r commented 1 month ago

Thanks for reporting this issue. I'll see if I can recreate in my next couple of charges...

dan-r commented 4 days ago

Should be fixed under v0.9.0. If you still have issues please reopen this.

Dan