Error not with GO-E Charger #16717 #16722
Replies: 4 comments 6 replies
-
Config file (without passwords, Sponsortoken, etc.)? Exact model and firmware version of your go-e charger? Http API enabled in the charger settings? |
Beta Was this translation helpful? Give feedback.
-
I thought so to. It is a mesh repeater, from from FritzBox. The strength is pretty well (about 80% at the wallbox). I saw those issues to. Currently I believe it will all work out. Just want to avoid a damage at the GO-e charges which causes a breakage. Thanks again for looking in to this matter mfuchs1984! |
Beta Was this translation helpful? Give feedback.
-
No issues using 56.8 on Gemini at my end. When setting up my EVCC environment i also used a fritz mesh repeater resulting in bad connectivity with the go-e. |
Beta Was this translation helpful? Give feedback.
-
After setting the IP setting back to automatically I was able to return to 56.8. System works stable now. The Fritz Mesh Repeater is not the issue. It mus be the current firmware and even the BETA versions are affected to. The big trouble is really to the the charge back online (not only via the go-e hotspot accessible). I hope that they will get this fixed. An upgrade however will not be for now. Thanks for the feedback shared. |
Beta Was this translation helpful? Give feedback.
-
Following error pops up in EVCC. The function itself seems to work. Is anyone able to assist? Do NOT Close this case unless you have some proper advise for someone who is not a pro, thanks!
Garage: charger status: Get "http://192.XXX.XXX.XX/api/status?filter=alw,car,eto,nrg,wh,trx,cards\": dial tcp 192.XXX.XXX.XX:80: connect: no route to host
Beta Was this translation helpful? Give feedback.
All reactions