I’m observing the same pattern when using the custom charging period (in my case 11:00-18:00 for testing)
When the custom charging is turned off, it keeps the charging at 100% by looping between charging and not charging.
The integration isn’t doing regular active polling, instead relies on updates from the server, with that it should be neutral to the battery consumption.
