About the use of 1 or three phase, the charger stops when is er the amps below 6. And it resume with 3x6a ( or more) when I set it to 6A or more. When is er it to 100% green, it will start charging at three times the amount of surplus my PV is giving me. So obviously some settings are wrong. Everything is on the same subnet and communication is with UTP. I can see the charger as a wired charger with the MyEve app, and it makes contact. But after trying to fetch info, it fails. Perhaps I should make a wifi connection as well, but Iām hold back by some stupid AI agent (Gemini). It was pretty convincing that it will cause communication problems. But perhaps I should make a wifi connection as well?
what I found out is that under 6 amp, it goes to one phase, above it goes to 3 phase. meaning if you steer it through the amp setting we have a large gap between appr 1800W and 4000Wā¦ there is no way I know through which you can force it to use one or 3 phases. maybe @MrDutchfighter knows? and maybe my conclusion is incorrect, so please push back hereā¦
If on 100% greenmode mine does charge on 1 phase over 6a. Charged with 2200-2400 watts the last couple of days.
I use EVCC to control the Alfen charger. EVCC can automatically switch from 1 to 3 phases.
And maybe nice to know:
The minimum charging current defined by the IEC 61851 standard (which is integrated into the NEN norms for electrical installations) is 6 Amps. [1, 2]
In terms of power, this corresponds to roughly 1.4 kW for a standard 1-phase connection or 4.1 kW for a 3-phase connection. [1]
How do you connect evcc? Via Homeassistent on Homey?
Good to know these backgrounds!
This morning I noticed that Alfen is playing up. It gives me that it is not charging a all (0w), however physically it is delivering power , 1500w, through comfort mode. I have restarted the app, but no success.
Diagnostics: 96feef63-0922-4a09-89a0-6f1471eb12b9
Filed a GitHub issue but maybe shouldāve tried here first. Ah well, just going to copy / paste the details here, maybe someone knows where to start looking?
Iām trying to get this app working, but struggling to make it so.
Situation:
- Alfen NG910 Single eve pro-line charger
- Previously only connected via SIM to back-office (Eneco)
- Now also connected via ethernet to local unifi network
- Homey is on the same subnet
- Latest version of the app (2.1.0)
- Firmware 7.4.0. of the charge point
- Iāve assigned a static IP to the charger via unifi.
At first I didnāt have the owner password. Took some convincing from both Eneco and the lease company, but eventually they gave me the password.
At first that didnāt work. I tried the app, which failed. I tried the ACE installer software which also failed. I then plugged the charge point into my laptop directly, which enabled me to use ACE. I found that Eve Connect was disabled which I guess blocks the API from being used (?) so I enabled that. I found that setting the option to āEnabled (without PIN)ā will reset itself to āEnabled (with PIN)ā, assuming that the back-office link might be overwriting that setting? Not sure whether this is at all related, but I thought Iād share just in case.
So after some fiddling things started to work and I was able to add the chargepoint to homey. On my first attempt I saw some data coming in, the power was displayed and when I started charging that reflected in the app. Great!
After not too long though (charging was stopped in the meantime), things froze and the power output stuck to 0 even when charging. So I decided to start over again, and after some rebooting / power cycling I re-added the chargepoint in homey. The adding still works, but now no data is coming in at all. Everything shows as ā-ā.
Iām a bit lost at what could be causing this and how to proceed with debugging. My use case is that Iād like to be able to see when my car is charging in order to be able to pause my home battery from discharging. My previous car (Tesla) had a proper API, new one hasnāt. So where I previously didnāt use the Alfen API at all, I now have a need for it.
Any help would be appreciated and thanks for creating this app!
Another noteworthy fact: I also tried using the Eve Connect app from my phone, that seems to be working without any issues whatsoever.
Somehow the latest version crashes for a lot of people. I will see if I can either make a fix or roll-back to previous version.
I donāt have my car atm so canāt test myself. I relied on the test group and there I didnāt see any anomalities for the past month, but it seems that it did break quite a lot for connections and stability. Will see if and how I can fix that.
Thanks! Iām new here so no history for me, but do let me know if I can do some test or validation work for you, not a problem.
I installed the new version and loaded my car. After that, my charger went into āinoperativeā-state and lost connection with the backoffice. Is that what you mean by crashes?
I have the same problem.
After the update of the Alfen App 2.1.0 in Homey, I donāt get any information from my Alfen Eve Single Pro-line charger. I charged my car, but no information of the power usage etc. is available.
I reconnected the charger in the Alfen App in Homey, but still there is no information available in Homey. I also update the charger to the newest firmware, but still no information available in Homey.
When I disable the Alfen App and connect the charger with myEve App on my phone, everything is working fine. When I enable the Alfen App in Homey again, still no information available. My charger is not connected to a back-office.
I donāt know what changed in the last update, but maybe you can help.
The diagnostic report is: edf99439-f4bf-4497-8ff7-841102cf6c5a
I have the same issue
What do you mean by lost connection with the ābackofficeā?
So there are a couple of things happening atm: In Operative in Homey just means turned off, this can happen when you used the āon/offā capability (card) or button in Homey. You can turn it on again by setting the charger limit back to 11kw (then it will take some time - but it will start-up again). Or toggle it āonā again. But when you turn your charger off with the capabilities it will probably disconnect with backoffice as well.
What Iām going to try to do:
- Disable the on/off button again, it was a much requested feature, but seems to give more confusion because I get the feeling the impact is not totally clear.
- Fix the start/stop messages every 30 seconds in Homey. This is a bug and I donāt know exactly where it comes from, but seems that every poll one of the two properties win and thus switching the toggle all the time. Which is plain annoying.
- Fix the data polling. It seems that quite some users donāt have the default charging profile with which you can configure real-time how much energy your charger can sent to your car. I thought it was a default profile that everyone had, but I think it is only there for some users. Still donāt know why this wouldnāt be available to all, because the Eve Connect app uses this exact profile to do the same thing. But maybe the profile only exists when users install and connect the Eve Connect app to their charger.
Here is a hotfix: Alfen | Homey
looks to work for me ! thanks !
That must have been it. I used the off card to test it and my charger went into inoperative state and lost vonnection with the backoffice of e-flux for reimbursements. Happy to have found the root cause of this. Thanks for the hotfix, I will test it when Iām home again
Hotfix fixes my issue as well, thanks!
My Alfen has some challenges (just submitted a diagnostic report)
it is showing that it is powering my car, but I cannot change any of the settings through flows or directly (i.e. setting default, of green powering mode. System times out.
I have restarted the app, and the alfen itself, no success.
Any steps I can further try?
The diagnostic report didnāt show anything useful (it is always cut off after some lines by Athomā¦). Maybe you can try to reboot the app, then directly toggle a setting change, and then submit the diagnostic report. Then I might be able to see something useful.
Done.
Restarted, pressed default charging. Received timeout, made diagnostic report:
6d5212c3-b4ac-4a98-ad6a-3cc00a1c623f
