Ah, ok makes sense. On my hypervolt the ALM setting was via a rotary selector behind the cover, so not accessable to end user.
I’ll probably just disable on mine, as no need to adjust from 80A
Version 2.4.1 of GivTCP is out now with GivEVC capability included
Thanks for your work MarkC. Just trying to add EVC to GivTCP in HA. But it refuses to connect. Just get lots of these in the log
2024-03-28 15:28:10,485 - Inv1 - sync - [ERROR ] - Connection to (192.168.1.xxx, 502) failed: [Errno 111] Connection refused
Confirmed the IP address (by the pull the cable out of switch method!). Any ideas?
Have you switched local mode on on the portal and restarted the charger?
If so, then it does take around 10 mins to open the local Comms, so connection will be refused until the time passes. Hang on there and see if it connects, mine does fine
Sorry… where’s local mode in portal? Not seen that before.in fact I don’t see anything related to the evc in the portal?
Is that right?
If you ‘edit your dashboard’ there should be an EV charger card you can add.
If you then expand the card, select Settings, Other
Then there is a toggle for Enable Local control. Sorry for poor photo (easier than screenshoting)
I’ve not been able to save the setting for local control (the logs always show a failure), but I noticed there’s a new configuration (E) “coming soon” that should add local control.
Hi @MarkC ,
Firstly many thanks for your hard work on have a solution for the EV charger via GivTCP.
I’m facing a similar problem by ColinS above, I’m seeing failures connecting to the EV charger
2024-04-10 23:29:19,257 - Inv1 - sync - [ERROR ] - Connection to (192.168.30.143, 502) failed: [Errno 111] Connection refused
I’ve tried setting the Enable Local Control On in the Online Portal and restarting the EV charger but it doesn’t hold the setting in the logs on the portal it shows as the setting failing to set.
Would you have any ideas on how I can progress to a working solution?
thanks
@MarkC [Errno 111] Connection refused - is there a fix/workaround to this? I have Giv EV connected to the AIO Gateway - config option is C.
Did anyone get anywhere with this? I’m just getting Errno 111 connection refused. LocalControl is on. And config option is C (CT Meter).
just read it another post - it works on Wifi and not on Ethernet
Well this is frustrating - why on earth would it not work on wired? I ran cables to my AIO and EVC for better reliability so a bit gutting to find out this limitation. Do you think it will be fixed?
I’ve asked GE to include it in the next firmware release, which I hope will happen soon, but I don’t have an ETA
Hi, I’ve been playing around with my EVC through GivTPC (WiFi) lately and I’ve noticed a couple of things:
- If I try to change my charge limit too many times, my modbus locks up:
2025-05-26 09:58:44,941 - EVC - evc - [DEBUG ] - Publishing: GivEnergy/xxx/Charger
2025-05-26 09:58:48,925 - EVC - evc - [DEBUG ] - MQTT Message Recieved: GivEnergy/control/xxx/setCurrentLimit= 13
2025-05-26 09:58:48,927 - EVC - evc - [INFO ] - Setting Charge current limit to: 13
2025-05-26 09:58:51,946 - EVC - evc - [DEBUG ] - MQTT Message Recieved: GivEnergy/control/xxx/setCurrentLimit= 6
2025-05-26 09:58:51,948 - EVC - evc - [INFO ] - Setting Charge current limit to: 6
2025-05-26 09:58:51,959 - EVC - evc - [ERROR ] - Error controlling EVC: (<class 'pymodbus.exceptions.ConnectionException'>, ConnectionException('Failed to connect[ModbusTcpClient(192.168.1.22:502)]'), <traceback object at 0xffff90f3c800>)
2025-05-26 09:58:51,960 - EVC - evc - [DEBUG ] - MQTT Message Recieved: GivEnergy/control/xxx/setCurrentLimit= 7
2025-05-26 09:58:51,961 - EVC - evc - [INFO ] - Setting Charge current limit to: 7
2025-05-26 09:58:51,972 - EVC - evc - [ERROR ] - Error controlling EVC: (<class 'pymodbus.exceptions.ConnectionException'>, ConnectionException('Failed to connect[ModbusTcpClient(192.168.1.22:502)]'), <traceback object at 0xffff907d44c0>)
2025-05-26 09:58:51,974 - EVC - evc - [DEBUG ] - MQTT Message Recieved: GivEnergy/control/xxx/setCurrentLimit= 12
2025-05-26 09:58:51,975 - EVC - evc - [INFO ] - Setting Charge current limit to: 12
2025-05-26 09:58:51,986 - EVC - evc - [ERROR ] - Error controlling EVC: (<class 'pymodbus.exceptions.ConnectionException'>, ConnectionException('Failed to connect[ModbusTcpClient(192.168.1.22:502)]'), <traceback object at 0xffff907d68c0>)
2025-05-26 09:58:51,988 - EVC - evc - [DEBUG ] - MQTT Message Recieved: GivEnergy/control/xxx/setCurrentLimit= 11
2025-05-26 09:58:51,989 - EVC - evc - [INFO ] - Setting Charge current limit to: 11
2025-05-26 09:58:52,001 - EVC - evc - [ERROR ] - Error controlling EVC: (<class 'pymodbus.exceptions.ConnectionException'>, ConnectionException('Failed to connect[ModbusTcpClient(192.168.1.22:502)]'), <traceback object at 0xffff90f2aa80>)
2025-05-26 09:58:54,954 - EVC - evc - [DEBUG ] - Socket is already open
2025-05-26 09:58:54,960 - EVC - evc - [DEBUG ] - Error: ('ConnectionException', 'evc.py', 194)
2025-05-26 09:59:04,961 - EVC - evc - [DEBUG ] - Socket isn't yet open
2025-05-26 09:59:04,974 - EVC - evc - [DEBUG ] - Error: ('ConnectionException', 'evc.py', 194)
I then have to power restart the EVC to recover from this error (restarting the addon also doesn’t clear the error). I’m not sure if this has something to do with the command queue size perhaps? I have a slider that would update the current limit real-time, and the 3rd command seem to fail.
- GivTPC only deals with integer currents, while through the GivEnergy app I can set the charge current with 0.5 accuracy.
- Setting “plug and go” through GivTPC get overwritten by the cloud app’s current settings
Is this something you can help me with, @MarkC? Let me know if you need more info