Since doing the firmware update all my HA settings from GivTCP have failed.
My SolarEdge is fine, so I know my HA is all OK.
They all say "entity is non numeric"
Any ideas?
Thanks
Steve
Home Assistant since battery firmware update.
I don’t know if this is related, but after the update, which went well over night with confirmation issued at 07:20. All was well but at 13:30 my SOC fell to 0% from 100% though battery is full. BMS Over voltage notifications with no clearances, and high battery voltage with clearances persist and are ongoing. Also noticed that settings for power rating for charge and discharge are now set at 3200W not 3600W.
The battery is effectively off, only providing 25 or so Watts to the home, the rest from the grid.
SteveCook You need GivTCP 2.3, did you already do that upgrade ? It only came out last night to support the latest firmware._
justpassing ...and doesn't support the latest publically available firmware on Gen1 Hybrids unless you tell it you have an AC unit on old firmware. Presumably the new "Local connection security verification enhancements" for G2/3 inverters.
Needs a bit of work from the author.....
SteveCook Steve, for interest, when you said "after the firmware upgrade" what version of inverter firmware are you now on ?
Title of post says battery firmware update so I assume 3013?
If he's on a Gen1 Hybrid then the last publically available update is in 2021.
I think he just updated the battery around the time GivTCP broke Gen1 Hybrid comms where the inverter is not on a private beta build.
Vestas there is a setting in GivTCP which will allow it to work with “older” firmware. I can’t remember the exact name but should be reasonably obvious.
anglefire I know but it refers to a totally different piece of hardware so I have no idea what difference there is in registers between the AC and Gen1 Hybrid.

Think it was called this behind the scenes
Inverter_AC_X
Yeah the author changed the code after I'd posted that. Its now 2.3.1

Seems 2.3.1 is broken:
2023-07-31 07:35:35,694 - startup - [CRITICAL] - Recreating settings.py for invertor 1
Traceback (most recent call last):
File "/app/startup.py", line 256, in <module>
{1: '192.168.76.138', 2: '192.168.76.150'}
if SuperTimezone: outp.write(" timezone=\""+str(SuperTimezone)+"\"\n")
NameError: name 'SuperTimezone' is not defined
This is weird. .138 is my QNAP NAS.....150 is my inverter!
EDIT: Rolled back the docker to 2.3.0 and its working again.
Hi all
Thanks for all replies, I will try and wrap up all questions and comments in a single post.
System is Gen1 5.0Hy and 9.5kWhr battery
Update to battery fimware 3013 started night of 28th July (Friday) with calibration continuing into the morning of 29th July (Saturday)
I think the close timing of the 2 events led me to (incorrectly) assume that something was now wrong with my inverter as all other HA integrations were still working. (NeoHub, SolarEdge etc)
I did look in GivTCP config in HA (am I imagining the wording?) and it referred to a setting of old AC devices, which mine is not - so I did not toggle it on. I see now it just now refers (2.3.1) to old modbus connections. I have now toggled it on and all works.
Thank
Steve
Looking for some help to understand please. I have Gen2 5kw Hyb inv and 9.5kwh Batt running 909 and 4074 inv & batt FW. I also have a Home Assistant instance with GivTCP v2.2.4 and all working well.
Despite it all working well I feel compelled to keep on top of FW updates and so looking to get up to date but nervous about the various issues I have seen other having. The latest GivTCP at time of writing is 2.3.2 but not sure if I should upgrade this first or wait till after the FW updates. Is it the Inv FW or the Bat FW that GivTCP needs to be updated for, or both? is there a best order or do i just put them all on latest and then see what happens?

Jon-boy Use the update button on the portal which will update your inverter to 911.
Immediately after this, update GivTCP to 2.3.2
Then contact support to manually update your battery to 3013.
Do it all in that order, you'll be fine.
ProximusAl Thanks for the recommendation