GivTCP - strange data over night

3 comments started 2025-01-09 last 2025-01-10
Home AutomationHome Assistant
M
#1 Morrisinc

Hi all

Not sure if this issues a follow on from the issues with the new year time/data bug. But since then I have been getting strange data on the start of each day.
Eg today data

In the GivTCP v3 logs for a few hours up to midnight - I see

2024-12-31 23:59:05,219 - GivTCP - read - [ERROR ] - runAll2 Error processing registers: ('KeyError', 'read.py', 1825)
2024-12-31 23:59:36,540 - GivTCP - read - [ERROR ] - inverter Update failed so using last known good data from cache: ((<class 'ValueError'>, ValueError("time data '2024-12-31T23:59:36.528954+00:00' does not match format '%Y-%m-%dT%H:%M:%S%z'"), <traceback object at 0x7fba1c6ed8c0>), 1687)
2024-12-31 23:59:36,541 - GivTCP - read - [ERROR ] - runAll2 Error processing registers: ('KeyError', 'read.py', 1825)
2025-01-01 00:00:07,853 - GivTCP - read - [ERROR ] - inverter Update failed so using last known good data from cache: ((<class 'ValueError'>, ValueError("time data '2025-01-01T00:00:07.841599+00:00' does not match format '%Y-%m-%dT%H:%M:%S%z'"), <traceback object at 0x7fba1c6ec080>), 1687)

Thanks for any help
Phil

G
#2 geoffreycoan

Morrisinc No such midnight errors in my GivTCP v3 logs at all, in fact last error was a read error at 8:30 on 3/1

my midnight last night:

2025-01-08 23:00:06,322 - G - write       -  [INFO    ] - Setting Battery Pause Mode to Disabled was a success
2025-01-08 23:00:07,576 - H - write       -  [INFO    ] - Setting Charge Schedule to disable was a success
2025-01-08 23:00:08,083 - H - write       -  [INFO    ] - Setting Battery Pause Mode to Disabled was a success
2025-01-08 23:30:04,312 - H - read        -  [INFO    ] - Saving current energy stats at start of night rate tariff (Dynamic)
2025-01-08 23:30:05,827 - G - read        -  [INFO    ] - Saving current energy stats at start of night rate tariff (Dynamic)
2025-01-08 23:30:06,105 - G - write       -  [INFO    ] - Setting Battery Pause Mode to PauseDischarge was a success
2025-01-08 23:30:06,571 - H - write       -  [INFO    ] - Setting Battery Pause Mode to PauseDischarge was a success
2025-01-09 00:00:23,166 - G - read        -  [INFO    ] - Midnight, so resetting Day/Night stats...
2025-01-09 00:00:33,560 - G - write       -  [INFO    ] - Setting battery charge rate 2300 was a success
2025-01-09 00:00:37,586 - H - read        -  [INFO    ] - Midnight, so resetting Day/Night stats...
2025-01-09 00:00:44,429 - G - write       -  [INFO    ] - Setting Charge Slot 1 to: 00:00 - 00:30 was a success
2025-01-09 00:00:44,942 - G - write       -  [INFO    ] - Setting Charge Schedule to enable was a success
2025-01-09 00:00:45,435 - G - write       -  [INFO    ] - Setting Charge Target 6 was a success
2025-01-09 00:00:55,117 - G - read        -  [INFO    ] - Midnight, so resetting Day/Night stats...
2025-01-09 00:00:56,301 - H - write       -  [INFO    ] - Setting Charge Slot 1 to: 00:00 - 00:30 was a success
2025-01-09 00:00:56,801 - H - write       -  [INFO    ] - Setting Charge Schedule to enable was a success
2025-01-09 00:00:57,343 - H - write       -  [INFO    ] - Setting Charge Target 26 was a success
2025-01-09 00:05:06,131 - H - write       -  [INFO    ] - Setting Charge Target 25 was a success
2025-01-09 00:10:06,784 - G - write       -  [INFO    ] - Setting battery charge rate 1900 was a success
2025-01-09 00:10:07,290 - G - write       -  [INFO    ] - Setting Charge Target 7 was a success
2025-01-09 00:10:08,085 - H - write       -  [INFO    ] - Setting Charge Target 23 was a success

Did you reset the date/time on your inverter per the 31/12/24 bug?

The energy dashboard screwup I’ve seen with other people, it seems that GivTCP 3 is a bit slower to update the ‘today’ sensors and this gives big spikes after midnight. If you swap to using the total sensors in the energy dashboard it should go away

M
#3 Morrisinc

Many thanks that did the trick and fixed the previous days too well except the new years day lots but that ok

Phil