Changes include
- ADD: Support for RFID card based power metering. These are hidden capabilities meter_power.card_N and name_meter_power.card_N. Only available in APIv2 devices.
Like the app? Support the work on Ko-fi or PayPal â thanks!
The firmware has issues allowing a stable connection to the API from Homey. Currently I do not have a solution to fix the issue and it is recommended to stay on lower versions.
I am waiting for a demo unit for testing and with that I can start looking at the support for firmwares 60.0 and further.
Sorry for the long delay. I just noticed that you have firmware version â59.5-dirtyâ. Have you tried with 59.4, the current stable version? Does that even show up for you as a firmware option.
If you could check this: http://IP-ADDR/api/status?filter=sse,fna,fwv,ocu from your go-e.
Hi!
Thank you for making this app, it really enabled me to use the charger to charge my car with the surplus PV.
I have been using your Go-e Charger app with great succes the last years. However this year the script I made to start the loading proces simply wonât work.
To be more precise the âSet allow charging to Yesâ command does not result in the charger starting the loading proces.
When I manually activate the charging (via the go-e app) it works normally and reading the charger in Homey is also working as well as the stopping proces and also changing the Amps up and down.
Could this have anything to do with the new Card 1-10 outputs I see in the graphs section. My line of thinking was perhaps I need to select a card first (how?) and then the allow charging works?
I have never used the RFID tag before, was not required it seems and the charger hangs indoors anyway.
Hope you can shed some light on this.
Best,
Ruud
Charger firmware: 59.4
App: 2.10.1
If you do not have authentication enabled on your charger, you do not need to select a card.
Could you:
Hi,
I created a new flow and tested both my old flow and this new one.
I created a diagnostics report with this identifier: 687d37ea-fde3-49f1-b2a9-ce865c11b69f
Let me know if you require more information from me or something else.
Thanks!
Ruud
Ok, I got from the log: is_allowed: acs=âtrueâ trx=âcard_noneâ
You have your go-e charger set to require authentication (acs=true). Thah in turn needs that you have shown a registered RFID tag to your charger.
If you turn Access â Authentication to Open. Then it should work fine.
However, this did point me to a bug that I fixed for v2.10.2
Hi!
Thanks for the fast turn-around on this issue.
I was not aware of this setting and I did not think of this since the âUnlockâ button in the Go-e app worked as before (no need for any rfid tag in that way).
Anyway, I will try tomorrow, the charger is already charging at the moment.
Thanks!
Ruud
Hi!
OK, I tested the new setup and it worked as before. Thanks again for checking and helping out, much appreciated.
Best,
Ruud
Hi! I´m thinking building load managment flow for go-e. At the daytimes I´m loading with solar panels with changing ampers and only one phase so there is no need for load managment there. At the night i use 3 phases and full amps (11kw). I´m thinking changing amps Step-by-step when load exceed 18kwh to optimize that load is near to max 18kwh. Any ideas how to do this?
Hi!
I have been using the new setting for a few days now and noticed a big difference.
Since the setting for Authentication is now âoffâ the moment I plug the car in, the loading starts. This sometimes fails, due to the car not being ready, but it is tried nonetheless. This never happened before.
Last year, I think I had the authentication setting also to âis requiredâ but I could control it via the âSet allow chargingâ card to âYesâ, but this no longer worked this year.
So I get that this setting changes that, but not in the way I intended it, it should not auto-start on connecting the car.
I checked if I had any enabled flow which works on connecting the car, but that was not the case.
Hope you can shed more light on this.
Thanks again for all the work you are doing.
Let me know if there is any more testing I can do to help find the issue. I am a web developer myself so if you want me to use tools on this, let me know how and I can probably do that too.
Best,
Ruud
Hi Matti,
I also use the daytime solar charging with changing amps. I do that by monitoring my P1 meter to see how much is flowing back to the grid, and if that exceeds (or drops) a limit I raise/lower the amps on the charger.
I think you can do something similar at night by monitoring the total uptake from the grid and adjust the charger if it exceeds a threshold etc.
Best,
Ruud
Did you turn it back on again to wait for authentication / command from Homey.?
The Access - Authentication setting is now: Open.
When I had the setting on âAuthentication is requiredâ the charger did not respond to the usual âSet allow chargingâ to YES card.
Changes include
- ADD: Support for CORE and PRO chargers.
- FIX: Chargers that have fixed charging cable would fail the status requests in 400 Bad Request error. There is now a check if the API call for checking cable type is supported on the device.
Like the app? Support the work on Ko-fi or PayPal â thanks!
Completely rewritten Official Go-e app is been developed with the kind support from Athom b.V. and go-e GmbH.
The new app will at first only support the devices that have V2 API available and for test version is built for the Gemini, CORE and PRO models.
The drivers are built with the Homey SDK3 provided evCharger capabilities and the goal is to use only those. One big advantage with the new capabilies is that you can tell your evCharger now how much power (W) is available for charging. For example only use Solar PV surplus and the driver will take care of mapping target power to device specific amperes and phases.
The given Target Power (W) maps to go-e API like this:
| Target Power (W) | Ampers | Phases | Maximum power | Note |
|---|---|---|---|---|
| 1380 | 6 | 1 | 1380W | Anything below turns charging off |
| 1610 | 7 | 1 | 1610W | |
| 2300 | 10 | 1 | 2300W | |
| 2530 | 11 | 1 | 2530W | |
| 3680 | 16 | 1 | 3680W | |
| 4140 | 6 | 3 | 4140W | first 3-phase step |
| 4830 | 7 | 3 | 4830W | |
| 5520 | 8 | 3 | 5520W | |
| 11040 | 16 | 3 | 11040W | Maximum for 11kW devices |
| 13800 | 20 | 3 | 13800W | |
| 22080 | 32 | 3 | 22080W |
Above is a sample of the values. Actual ampers is calculated automatically from the given target power.
To test the new app, please install from test version as it is not yet published.
Here is a sample flow how to use dynamic power control:
When the main energy source power consumption change:
The SDK3 provided Set the target power functions like that.
Donât worry, I will still be supporting this and the new app. Though slowly this older app will be phased out.
