Local API via GivTCP not working on the EVSE, despite the problem being closed

Hi all,

I want to preface this by stating that I’m aware that the EVSE has had a bug in it’s firmware that prevented GivTCP to work with it over Ethernet. This was well known and was tracked as a known issue on the GivEnergy online portal/dashboard. I remember around a month ago that an update was posted, saying that this issue will be resolved on the next update, and the issue as now been removed from the Known Issues section, which i believe means that the issue is supposed to be resolved.

On my end, this clearly has not been resolved. The GivTCP container is still not able to access the EVSE via TCP Modbus on ethernet. My networking SDN controller clearly shows the EVSE connected to the IP that i’ve put down in the Add-on configuration. The Add-on logs are showing that the connection is being reset by the peer, indicating that I can’t connect to you. I am able to ping the device however, and I can use the EVSE through the app so it is connected to the interent and my network. My AIO/Gateway are accessible through GivTCP too.

I wanted to check if others are still facing this issue. Thanks

Just to add - The app reports that I’m on firmware revision AC_GL1_1.13.

The website only shows revisions up till AC_GL1_1.12 (https://givenergy.co.uk/firmware-revisions/ev-charger/)

Honestly, the amount of issues I’ve had with this charger is honestly making me contemplate selling it and moving to another brand. GivEnergy should NOT be selling commercial products with half-baked software like this.