Since updating to GiVTCP 2.3 version, getting continual log message including "Garbage or failed investor Response" and after 10 attempts a "removing regCache to force update...". Scrolling back it looks like it maybe something to do with getting a serial number via MQQT
Anybody else getting similar ?
Anybody else getting similar ?
Yes I saw that today. Same times as you.
Looks like something changed in the code 12 hours ago and its broken Gen1 (at least) comms.
"If you have an AC inverter with a firmware number start with "5" then you can't access new registers so you must set the Inverter_AC_X to True."
Probably can't access the "new registers" either on a Gen1 hybrid as the firmware hasn't changed.....
Edit - yes that seems to be the issue. You have to tell GivTCP that the Gen1 Hybrid is an AC on old firmware to get the Gen1 Hybrid to communicate. Not sure if that breaks anything else....
Edit2 - incidentally this began happening here at 06:52 30/7/23 so I assume the author of GivTCP pushed out some form of update/patch to GivTCP around then which has broken Gen1 Hybrid comms on D0.450-A0.451 firmware.
Edit3 - looks like telling GivTCP that the Hybrid is an AC on old firmware breaks the Solar forecasting functions which isn't entirely surprising. Ignore that - finger trouble on my end 🙂
i think latest version it also not populating GivTCP Import Energy Today kWh either on at least Gen 1 hybrid ?
Will try setting Inverter_AC_X to True trick
If you look at the "GivTCP Update" entity you'll probably see that it was turned on around 01:00 on 30/7/23 so some change was pushed out overnight - not 2.3 in its entirety, this is something else.
I suspect this change will have broken all GivTCP installs where the inverter firmware hasn't been updated in the last few days - of course there is no firmware update for Gen1 Hybrids so it'll break all those installs for sure.
Edit - nothing at all gets populated on Gen1 Hybrids, they are simply unable to communicate with givTCP following this change unless you tell givTCP you have an old AC unit.
On my instance, it was just the import figure that wasn’t be populated with the GivTCP, the other figures that I use (which aren’t many as I use it for basic reporting only) were being populated. Now leaving it a couple of hours after “kidding” it with being an old inverter the import figures have now come through. The problem with the Gen1’s there are all the variations which is one of the reasons I am think it talking so long for GE to get inverter firmware updated and some of us may need hardware changes to get the long awaited inverter firmware update to allow it to work. I see in the GivTCP release notes that the Gen2 new firmware is allowing 10 charge and discharge time slots in the new firmware/givtcp implementation, the Gen1 aren’t I suspect big enough to support that. Even though my install is only 9 months old, I believe from reading the posts from Dragon, it is currently too old to have the latest firmware with the improved response times, which is highly frustrating.
There seems to be some changes occurring on the givTCP github page this afternoon so we'll see what we see. The GE app got updated a couple of days ago and still works so I suspect the givTCP author might need to assume two build standards (firmware revs really) for Gen1 Hybrids.
Re new inverter firmware - not really bothered TBH, this works as I'd expect and response times are perfectly acceptable. My HY3.6 is a 2022 week 44 build so I have no idea whether it can have the latest firmware or not, its not being offered anything via the portal anyway.
Re extra charging slots - I'd sort of assumed I was going to have to do some automation anyway so I don't mind.
I wish I'd seen this before updating GivTCP this morning. It's now totally broken with no data since I did the update. I have an AC3 inverter with software DO.535-AO.535.
A previous post says you need to set Inverter_AC_X to True. I have no idea how to do this.
andydsmith If you use 2.3.1 and don't use it as an HA addon....e.g. run it in its own docker, it's broken too.
I raised a bug:
andydsmith
With thanks and help from another thread - I have Gen1 5.0
This fixed it for me
HA-settings-add ons-GivTcp-configuration
set the slider "is it on old firmware" to on
SteveCook Thanks for that.
Toggling 'Is it old Firmware' to ON worked - Thanks Steve
Wolfie1959 same for me, no problems after changing this slider
ProximusAl Now fixed in 2.3.2.
I don't know about that. My G1 inverter was flashing green this morning & had to be restarted. Load of errors in the GivTCP log regarding solar forecast errors and no PV current flowing at a time when there should be around 1A. Complete power down and restart and PV is working again.
I notice these were changes from 2.3.1 -> 2.3.2 - Fixed PALM ge.batcap error, Fix CHargeslot start register offset error
I think I'll be disabling GivTCP for a few days to rule it in/out as I've not seen issues like this before.
Vestas Sorry, that batcap error was my fault. I pushed some code in that was incomplete and caused the error with solar forecasting. It was careless and I'll try to be more attentive next time. I think the developer has now fixed my mistake so I'm hoping all is well tomorrow morning.
SpeakToTheGeek Its not the batcap error which I find concerning, its the register offset error which (to me at least) suggests that data has been written to the wrong register.
Given I'm on a G1 Hybrid which doesn't support the new local comms, the only way to get 2.3.0 working was to tell GivTCP I had an old AC. I think its unlikely that the "old AC" has the same registers as a G1 Hybrid on old firmware given that G2 Hybrids have different registers. As such I think I'll either leave GivTCP disabled or go back to 2.2.4.
NB - I'm aware that the slider now says "old firmware" but that's simply cosmetic.
im on version 2.3.2 and ive noticed the plugin stops after a few minutes and i need to restart it. is there a newer version coming?
Working after inverter firmware update
SteveCook Thanks for that. I also had to make the change to the GivTcp config to 'inverter on old firmware' to make it work.