That’s interesting! Do you see any pattern, e.g. time wise? I have the go-e Home+ V3 ; what’s your type?
Thank you @CaptainVoni for your kind donation.
1 Like
I have a Go-e Home V3. Firstly, I don’t know whether the ‘problematic’ behaviour comes from the Homey app or from the charging station itself. If an electric vehicle is plugged in and I stop the charge with a Homey flow, the charge will remain stopped indefinitely. If I stop charging with a Homey flow and then unplug the vehicle, but if I stop charging again with a flow and the vehicle is unplugged, the next day when I plug in a vehicle, the charging starts even though I didn’t ask for it. I consider this behaviour to be abnormal. It doesn’t bother me much though, because before plugging in a vehicle, I always stop the charge first with a small Z-Wave remote control next to the charging station, precisely to prevent this behaviour.
1 Like
Is it possible to add restart go-e charger to actions? Every now and then go-e goes offline in Homey but is online in native app. Restartting go-e from native app brings it alive in Homey again.
Which version of go-e charger do you have?
Do you have a reserved fixed IP address for it?
If it offline / unreachable the restart by the app in Homey would be unable to do anything while the device is offline from the app’s point of view.
When your go-e is offline from Homey, could you send diagnostics report before you restart it.
Gemini 11kW. Yes i have fixed IP. I will send you diadnostic next time. Ah… true, wont help when offline 
I’ve seen this happen once on mine and restarting just the app recovered it.
But still, would be interesting to get more to diagnose it a bit more and see if I need to improve the recovery process.
Questions to current users
I am optimising the current app internals to better support the future models also.
Ideally there will be one driver for the complete Home series, one for Gemini series and one for Pro series.
Device type check
Could you report back to me if you have:
- go-e Charger Home serial number (CC-1…)
- go-e Charger Home serial number (CM-02…)
- go-e Charger Home serial number (CM-03…)
- go-e Charger Gemini serial number (GM-10…)
What I would like to know is:
- Which serial numbers are Home and which serials are Home+
- What is the serial number prefix for Gemini 2.0?
- And no-one probably has a Pro yet?
API versions on Home series
The Home series primarily supports APIvq, but for CM-03 devices the newer APIv2 is supported. This is also what I would like to hear from you, if go-e has enabled it for the older models also.
- So for CC-1 and CM-02, could you check you have latest firmware installed and what is the version.
- Then see, if you can enable to APIv2 in the go-e mobile app device settings:
https://github.com/goecharger/go-eCharger-API-v2/blob/main/screenshots/http-api-app-enable.png?raw=true - And, if it can be enabled, can you access http://<IP_address_of_your_charger>/api/status?filter=fna,oem,typ,vwv,sse
Autodiscovery for older devices
Finally, could you verify if the device is discoverable automatically through mDNS (Bonjour). Follow instructions here: go-eCharger bonjour discovery with mDNS-DS · oh2th-homey/com.go-e.charger · Discussion #7 · GitHub
Reply Template
Paint the following and hit the reply button, update with your information:
Device model name: Home, Home+, Homefix, Gemini, Gemini 2.0
Serial number prefix: CC-1. CM-02, CM-03, GM-10
Installed firmware version: 056.1
APIv2 available: yes/no
APIv2 result:
Autodiscovery: Screen shot of discovery data for your go-e charger
So as an example my Gemini looks like this
Device model name: Gemini
Serial number prefix: GM-10
Installed firmware version: 57.1
APIv2 available: yes
APIv2 result: {“sse”:“201397”,“fna”:“go-eCharger 201397”,“fwv”:“57.1”,“oem”:“go-e”,“typ”:“go-eCharger_V4”}
Autodiscovery:
d042b0eb-fb4a-43e4-bf63-6e746818510c Now it happened again. I sended you diagnostic.
The log shows only events after you restarted your go-e charger.
I think this may be something with the IP-address auto discovery. Is your wifi stable, so that the go-e charger has a stable network. Homey is quite sensitive if there are any stability issues.
Could you sent the diag logs before your restart the device.
Another option is that you try just to restart the go-e charger app in Homey.
Hi! Wifi should be stable. I will send logs nextime before restart. I will also try the flow that restarts the app.
And you can try this from a browser when Homey has set the device unavailable.
Can verify the homey go-e charger app version for me?
5e9c198d-86ae-4972-be7b-29c570a97574
Sended log before restartting.
V.2.8.4 is the Homey app version.
Log shows errno: ‘EHOSTUNREACH’
Which says that Homey can not reach the IP addresss.
I assume that your Homey and go-e are in the same network address space?
They are in same 2g wifi 
Not sure what you mean with address space because i´m not professional with computers.
Same wifi. That is good.
Which brand of wifi?
TP Link Deco M4
There are a couple post here in this forum about those TP Link Decos in relation to the autodiscovery. One is [APP][Pro] Homewizard 🧙♂️ - #651 by Roger_Gorissen where there more or less exactly the same issue.
When you are having the issue, could you check if the go-e Charger is actually discoverable. Instructions to check that can be found at go-eCharger bonjour discovery with mDNS-DS · oh2th-homey/com.go-e.charger · Discussion #7 · GitHub
Hi,
I want to buy a Go-E Pro charger since it has the abbility in the feature to support V2X.
But the Go-E Pro isn’t listed as supported with this App.
Can anyone confirm it would work?
BR
Jan Wynen
