Releases: marq24/ha-goecharger-api2
"Ahead of its time" Release | This repository is active notice
No functional changes
With this release I just want to signal, that this repository is activity maintained and I am continue to monitor it for any reported issue in the year 2026.
Please consider supporting me
Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.
If you haven't starred this integration in Github yet - please do so - TIA
HttpClient Session recreation on 'Connection reset by peer' / 'Server disconnected'
As reported in #82 it can happen, that (not 100% sure if this is really related to the new Firmware Version or not), that the http session to your goe-Charger will be terminated by the Wallbox causing an error in the integration.
The new release will try to handle this situation by creating a new client session - we must see over time, if this solves the issue.
Please consider support me
Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting a quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.
If you haven't starred this integration in Github yet - please do so - TIA
Support for '-dirty' Firmware
Support for '-dirty' Firmware
fixing issue #81 (none PEP 440 compliant Version numbers)
Please consider supporting the development
A donation/coffee/become sponsor would be highly appreciated - TIA
If you haven't starred this integration in Github yet - please do so - TIA
Support for firmware 60.0 beta API breaking change [2x fixed]
Support for Firmware 60.0 API breaking change [v2025.11.1]
With the latest go-eCharger firmware 60.0 beta release, go-e have decided to introduce a breaking change in the API. The previously existing cards object has been replaced by 30 single API keys. This change has caused incompatibilities with this Integration.
So when you update to the go-eCharger firmware 60.0 beta, you must also update the integration.
Of course the integration update will also work with the previous go-eCharger firmware versions - the integration detects the firmware version of the charger and use the appropriate code for the one or the other (fingers crossed).
Fix for go-eController [v2025.11.2]
Fixed #75 shame
Fix for older API's of go-eCharger [v2025.11.3]
Fixed #76 shame - shame
Recommended Update procedure
If you haven't updated the firmware of your go-eChager yet, please follow these steps:
- Update the integration to 2025.11.1
- Update the firmware of the charger to 60.0 (via go-eAPP)
- After the reboot of the charger with the new installed firmware restart HA or at least reload the integration, so that the code is able to detect the new go-eCharger firmware
Compatibility Mode added [v2025.11.0]
A new select entity have been added, allowing the following options:
- default
- kiasoul
- renaultzoe
- mitsubishiimiev
- citroenczero
- peugeotion
Please note, that setting this selection to something different than 'default', will cause the su value to be set to True (simulate unplugging) - furthermore when selecting the renaultzoe the mca (minimum charging current) will be set to the value 10 (for all others the mca value will be set to 6 again).
This will allow you to implement #73. Create an automation that detect which of the vehicles report to be @home and is connected, and based on the vehicle, set the new selection to the appropriate value (from the list above).
Please consider supporting the development
A donation/coffee/become sponsor would be highly appreciated - TIA
If you haven't starred this integration in Github yet - please do so - TIA
Support for firmware 60.0 beta API breaking change [fixed]
Support for Firmware 60.0 API breaking change [v2025.11.1]
With the latest go-eCharger firmware 60.0 beta release, go-e have decided to introduce a breaking change in the API. The previously existing cards object has been replaced by 30 single API keys. This change has caused incompatibilities with this Integration.
So when you update to the go-eCharger firmware 60.0 beta, you must also update the integration.
Of course the integration update will also work with the previous go-eCharger firmware versions - the integration detects the firmware version of the charger and use the appropriate code for the one or the other (fingers crossed).
Fix for go-eController [v2025.11.2]
Fixed #75 shame
Recommended Update procedure
If you haven't updated the firmware of your go-eChager yet, please follow these steps:
- Update the integration to 2025.11.1
- Update the firmware of the charger to 60.0 (via go-eAPP)
- After the reboot of the charger with the new installed firmware restart HA or at least reload the integration, so that the code is able to detect the new go-eCharger firmware
Compatibility Mode added [v2025.11.0]
A new select entity have been added, allowing the following options:
- default
- kiasoul
- renaultzoe
- mitsubishiimiev
- citroenczero
- peugeotion
Please note, that setting this selection to something different than 'default', will cause the su value to be set to True (simulate unplugging) - furthermore when selecting the renaultzoe the mca (minimum charging current) will be set to the value 10 (for all others the mca value will be set to 6 again).
This will allow you to implement #73. Create an automation that detect which of the vehicles report to be @home and is connected, and based on the vehicle, set the new selection to the appropriate value (from the list above).
Please consider supporting the development
A donation/coffee/become sponsor would be highly appreciated - TIA
Support for firmware 60.0 beta API breaking change
Support for Firmware 60.0 API breaking change
With the latest go-eCharger firmware 60.0 beta release, go-e have decided to introduce a breaking change in the API. The previously existing cards object has been replaced by 30 single API keys. This change has caused incompatibilities with this Integration.
So when you update to the go-eCharger firmware 60.0 beta, you must also update the integration.
Of course the integration update will also work with the previous go-eCharger firmware versions - the integration detects the firmware version of the charger and use the appropriate code for the one or the other (fingers crossed).
Recommended Update procedure
If you haven't updated the firmware of your go-eChager yet, please follow these steps:
- Update the integration to 2025.11.1
- Update the firmware of the charger to 60.0 (via go-eAPP)
- After the reboot of the charger with the new installed firmware restart HA or at least reload the integration, so that the code is able to detect the new go-eCharger firmware
Compatibility Mode added [v 2025.11.0]
A new select entity have been added, allowing the following options:
- default
- kiasoul
- renaultzoe
- mitsubishiimiev
- citroenczero
- peugeotion
Please note, that setting this selection to something different than 'default', will cause the su value to be set to True (simulate unplugging) - furthermore when selecting the renaultzoe the mca (minimum charging current) will be set to the value 10 (for all others the mca value will be set to 6 again).
This will allow you to implement #73. Create an automation that detect which of the vehicles report to be @home and is connected, and based on the vehicle, set the new selection to the appropriate value (from the list above).
Please consider supporting the development
A donation/coffee/become sponsor would be highly appreciated - TIA
Compatibility Mode [Standard, KIASoul, RenaultZoe...]
Compatibility Mode added
A new select entity have been added, allowing the following options:
- default
- kiasoul
- renaultzoe
- mitsubishiimiev
- citroenczero
- peugeotion
Please note, that setting this selection to something different than 'default', will cause the su value to be set to True (simulate unplugging) - furthermore when selecting the renaultzoe the mca (minimum charging current) will be set to the value 10 (for all others the mca value will be set to 6 again).
This will allow you to implement #73. Create an automation that detect which of the vehicles report to be @home and is connected, and based on the vehicle, set the new selection to the appropriate value (from the list above).
Please consider supporting the development
A donation/coffee/become sponsor would be highly appreciated - TIA
Support for float values for AWP
Support for float values for AWP
Kudos @peteher for reporting #69 and fixing it right away #70 - the AWP key should handle floats - https://github.com/goecharger/go-eCharger-API-v2/blob/d850f5f27214291a26db6b1dabd213153b77f4aa/apikeys-en.md?plain=1#L23
Contributors
Assets 3
go-e Charger CORE/PRO support
As reported the go-e Charger CORE/PRO does not support all states (compared to other models) - this release tries to tacked this with a more fault-tolerante reading. See #66
Support for reconfiguration
Support Home Assistant integration re-configuration