using GivTcp version 2.2.4 (with two Giv AC3.0 inverters each with a battery). The latest version of HA 2023.7.2 using MQTT 6.2.1
I have my system turn off discharge at 23:30 when the off-peak rate starts via an Intelligent Octopus Trigger which calls a script to Change GivTCP Force Charge Option to 180 (which should in theory be 02:30hrs). The reverse happens at 05:30 when the cheap rate ends and a script Calls Change Giv Force Charge Option to 'cancel'. Logs show both of these scripts being called at the correct time.
For the last two days, the following has been called at 01:07
GivTCP Enable Discharge - turned on
GivTCP Power Reserve changed to 4
GivTCP Power Mode changed to Eco
GivTCP Charge End time Slot 1 changed to 04:30:00
GivTCP Charge Start Time Slot 1 changed to 00:30:00
I have no reference to this in my automation/scripts or service calls, is this a GivTCP function calling this or could it be GivEnergy Servers doing something on their end?
I have had persistent issues with the GivEnergy App not allowing me to keep my settings of 23:30 - 05:30 charge period and it consistently reverts me back to 00:30 - 04:30 which was the Octopus Go Off-peak.
If anyone is using HA and GivTcp could they see if their logbook shows anything similar?
I'm still waiting over two weeks for anyone from Giv support to come back to my feedback request around this setting of charge start/finish times.

Graham