Yes, he finds a device.
When acknowledged. Pop up.
1 router, 1 dhcp, 1 pool ip
SSID inside
SSID outside with cable to router.
Martin
Ahaa, that is strange. Can you try adding via my.homey.app? I wonder, if this is an Android issue of a sort.
I enchance the logging a little bit show on the diagnostics report what device.data actually contains.
If you could install the test version from Go-e | Homey and do the above process again.
The diagnostics says that no device was found. Please check that your charger is actually discoverable.
New Update (TEST 1.7.4)
Changes include
- FIX: Homeplus local discovery.
Thanks @Martin_Koning that helped.
There is a new version in the test branch. Please install that one and try adding your device.
Done. Got it now. Thanks very much. I wil start changing advanced flows next weekend. I’ve been witjh the go-eCharge Homey-app for 5 years now on my Homey Pro 2019. Integrated it in almost everything. 
This one is quite different from the original app. But has some really easy features to fit Homey’s default logic and capabilities.
Totally different. It works now, but i’m not totally convinced yet. But thats also for what i want it to do. 
I wanted the app “SlimLaden” to be the EMS. Because I’m thinking of buying a plug-in-battery.
For now.
I have SMA solar power inverters which i am dimming with modbus (% inverter-max at Grid) when the netto-price is negative. (EPEX-price €0,02/kwh. I have to pay €0,02/kWh for selling electricity )
Therefore potential solar power dissapears. You can’t now what isn’t produced. It appears in figures when used.
Gridmeter: -200W → Result: The go-eCharger won’t start and also stops very often.
Now I’m tweaking with modbus at SMA inverter. Gridmeter at -4200W when plugged in. Started charging then Gridmeter: -890 (-200-690) then the go-eCharger wil give more power. But the result is not stable yet. Maybe it’s the 10 second delay. Maybe the old Homey2019 is not quick enough.
The target power will not go to 17.250 W (3x25A)
I think the app limit’s it at 11 kW.
I have Version 3 from 2020. It can do 22 kW (3x32A)
It should retrieve the 11/22 kW info from the charger. I’ll check that.
Found the issue, please try this test release: Go-e | Homey
Meanwhile, there is one thing to know about go-e charger’s behavior:
When the go-e charger has switched between 1-phase and 3-phase charging, it will lock to that setting for 10 minutes, that can not be adjusted. Meaning that if it was in 3-phase and your surplus on grid drops below ~4000 W, it won’t switch back to single phase until the 10 minutes safety period is up.
22 kW works now
@Complus Thank you for the FAQ and helpful hints.
Do you know by chance if the trigger „on every change“ as proposed or a repeating timer will be better for Homey memory?
The flow only updates the values to the go-e app. Go-e app only keeps the last value and sends the value over the API to the charger.
So no, I do not believe it will consume more memory because of the updates.
After testing the PV Surplus I realize that power consumption at home will trigger too many start and stop events.
Maybe connected to this, I had to hard reset go-e by plug-off from source.
My idea: I‘d like to slowly decrease the surplus value.
Anyone experiencing the same? Better solutions?
@tlink Firmware 60.6 Beta installed.
I tried now (09.00) to see if it is workable now. But I was a bit dissappointed in using PV-surplus (ECO).
Every 8 seconds it stopped (Paused) and then the go-e app: no PV-surplus
The homey-app shows: Fallback dynamische prijzen (10 seconds ago). So I think the charger expects data every 10 seconds. If the connection is lost (happened) or 1-minuteflow it stops charging!
PV Surplus
Vermogensvoorkeur: Gridpower
Streefdoel: 690 W
Today (10.00) I try: advanced flow: 10 seconds → calculate average with 2 variables.
Net average = (Net average * 6 + Net now)/7
PV average = (PV average * 6 + PVnow)/7
to smooth changes in case of cloudy days.
Change of power ev-charger is once a minute. Perfect.
Only, my EV (Renault) goes to sleep if power charger stops.
Now (12.00) trying: 23A & Automatic Fase Change & PV = 0 (Found that in a previous post: nr 34, @Complus ?)
Average Net < 690 (export): NET = Net average = (Net average * 6 + Net now)/7
Average Net > 690 & < 5520 (export): → NET = 690
Average Net > 5520 (export): → NET = 5520
Hopefully now my EV doesn’t go to sleep !!!
13.00 Heatpump started →
13.02 charger 15 kW + Net 690 (2 minutes) → 13.04 ECO stops → EV goes to sleep
13.05 ECO starts but EV still sleeping
15.00 23A & Automatic Fase Change & PV = 0
Average Net < 690 (export): NET = Net average = (Net average * 6 + Net now)/7
Average Net > 690 & < 5520 (export): → NET = NET (export, P1-meter)
Average Net > 5520 (export): → NET = NET (export, P1-meter)
It works smoothly for 30 minutes with a lot of sunpower, no clouds.
1 cloud → Net (export) = 1.500 (minute 1) and 8.000 (minute 2) W → ECO stopped → EV sleeps
16.00 23A & Automatic Fase Change & PV = PV average (1 minute)
Average Net < 690 (export): NET = Net average = (Net average * 6 + Net now)/7
Average Net > 690 & < 5520 (export): → NET = NET (export, P1-meter)
Average Net > 5520 (export): → NET = NET (export, P1-meter)
EV falls in sleep after 2 unexplained restarts charging.
The go-e Charger does not store the transmitted pGrid values permanently. If no new value is received within 10 seconds, the data expires for safety reasons (data timeout). Consequently, the automatic PV surplus regulation (Eco mode) is stopped or deactivated, as the wallbox assumes that the connection to the electricity meter has been interrupted.
To avoid any charging interruption, I solved it by simulating an offset of +/-1 for each value which I send each 5s to the go-e app card.
Let me know if it helped in your case.
Could you explain what kind of a widget you would like to have. Huawei seems to have many widgets, and many of those woudn’t be relevant for an EV charger app.
