Weird error sequence followed by repeated commands causing possible excessive register writes.

[SwiftRR]

I am running givTCP3.0.4 on Givenergy AC3.0 inverter. HAOS 14.0 with Core 2024.11.3 on a Raspberry Pi.
Inverter works with Pause mode but not with Pause end and start times.

A strange task exception which autorecovers quickly, finishing with a restart of givTCP3.0.4.
Cause may be: [ERROR ] - Self Run loop process stuck.

After an autostart of the inverter read loop, the same instruction repeated 5 times:

2024-12-23 15:03:02,317 - GivTCP - write       -  [INFO    ] - Setting Charge Slot 1 to: 15:00 - 15:30 was a success
2024-12-23 15:03:03,094 - GivTCP - write       -  [INFO    ] - Setting Charge Slot 1 to: 15:00 - 15:30 was a success
2024-12-23 15:03:03,869 - GivTCP - write       -  [INFO    ] - Setting Charge Slot 1 to: 15:00 - 15:30 was a success
2024-12-23 15:03:04,649 - GivTCP - write       -  [INFO    ] - Setting Charge Slot 1 to: 15:00 - 15:30 was a success
2024-12-23 15:03:06,519 - GivTCP - write       -  [INFO    ] - Setting Charge Slot 1 to: 15:00 - 15:30 was a success
2024-12-23 15:03:07,013 - GivTCP - write       -  [INFO    ] - Setting Charge Schedule to enable was a success
2024-12-23 15:03:07,495 - GivTCP - write       -  [INFO    ] - Setting Charge Schedule to enable was a success
2024-12-23 15:03:07,989 - GivTCP - write       -  [INFO    ] - Setting Charge Schedule to enable was a success
2024-12-23 15:03:08,485 - GivTCP - write       -  [INFO    ] - Setting Charge Schedule to enable was a success
2024-12-23 15:03:08,978 - GivTCP - write       -  [INFO    ] - Setting Charge Schedule to enable was a success

See givTCP log
givtcp3.0.4 2024-12-23.log

We are worried about excessive register writes, so it is a real problem if the same identical command is issued multiple times.

I have now restarted givTCP. It has restarted using the usual sequence and I now have each command issued once only.

I am running predbat and I received the following warning during this time. The predict command prior to the problem was a 'freeze' command which corresponds to givTCP Pause.
This is from the predbat.log at this time.

2024-12-23 14:55:32.358730: Info: record_status Freeze charging target 60%
2024-12-23 15:01:48.128751: Warn: Inverter 0 set charge slot 1 {'start': '15:00', 'finish': '15:30'} via REST failed
2024-12-23 15:01:48.180396: Warn: record_status Warn: Inverter 0 REST failed to setChargeSlot1
2024-12-23 15:03:04.340330: Warn: Set inverter 0 charge schedule True via REST failed got disable
2024-12-23 15:03:04.383274: Warn: record_status Warn: Inverter 0 REST failed to enableChargeSchedule
2024-12-23 15:06:59.937305: Info: record_status Charging target 61%-100%

Rob