Nice! Still needs an external instance of EVCC though. Will there be a way to use it purely on Homey in the (nearby) future? Would have post this on a forum thread for the app, but that doesn’t exist yet.
Unfortunately, that’s not something I currently see happening. Technically it may be possible, but it would basically mean porting or running EVCC itself inside Homey, which is a completely different and complex project.
The Homey app is meant to integrate with an existing EVCC instance, bringing its data and controls into Homey for automations and dashboards (checkout the latest version 
), while leaving the actual charging logic to EVCC.
@MrDutchfighter any thoughts on this? This would be a very handy enhancement.
I don’t do hosting EVCC if that is what you are asking. If anyone wants to also add an EVCC option to the Alfen app they are free to do so. But why not use the EVCC app as provided above?
@MrDutchfighter no, my question was not about evcc hosting. I was referring to the chargeid whether this could be made available in homey to see whichbchargekey was used for the charging session
This would be handy, since it seems my car is slow on returning info with regards to if its connected, so unusefull to use in a flow to check wich car (mine or my wife’s is to be charged.
Ah, sorry. Does any of you know if the information is visible in one of Alfens own apps? I haven’t found a way yet in the API, so I highly doubt that it is available somewhere. But if they show it in one of their apps it theoretically should be in the API and then the only thing that remains is finding out where 
[screen print deleted]
It’s the ID field at the bottom of the screenprint.
Is it visible during or only after the transaction is completed?
Actually, this is only visible after the transaction is completed (just checked and my current chargingsession isn’t in the list yet). So that might be an issue…
Yikes, overlooked that! My car is actual charging and insights is not filled yet.
I tried this app and wanted to start testing the modbus connction to the Alfen Duo Pro. In order to do so I removed the app from homey to avoid conflicts. During test I noticed that the alfen charger limited the current to 7.3A per phase. After a day of debugging, factory resets (but keeping the user configuration and log files) and boots I found out that the 7,3 A came from and “old” ChargingProfile (id = -19930828). This was probably the last setting given by the homey app and this charging profile stayed active. The full logfile entry:
2026-09-13T19:57:10.246Z:INFO:db_chargingprofi:26:ChargingProfile (id = -19930828):
2026-09-13T19:57:10.257Z:INFO:db_chargingprofi:26: socket 0
2026-09-13T19:57:10.269Z:INFO:db_chargingprofi:27: primary Not specified
2026-09-13T19:57:10.277Z:INFO:db_chargingprofi:27: stackLevel 0
2026-09-13T19:57:10.289Z:INFO:db_chargingprofi:27: purposeType ExternalConstraints
2026-09-13T19:57:10.300Z:INFO:db_chargingprofi:27: transactionId 18446744073709551615 (not specified)
2026-09-13T19:57:10.312Z:INFO:db_chargingprofi:27: kindType Relative
2026-09-13T19:57:10.324Z:INFO:db_chargingprofi:27: recurrencyType Not specified
2026-09-13T19:57:10.335Z:INFO:db_chargingprofi:27: hasTariffs FALSE
2026-09-13T19:57:10.343Z:INFO:db_chargingprofi:28: validFrom NULL
2026-09-13T19:57:10.355Z:INFO:db_chargingprofi:28: validTo NULL
2026-09-13T19:57:10.363Z:INFO:db_chargingprofi:28: useLocalTime TRUE
2026-09-13T19:57:10.375Z:INFO:db_chargingprofi:28: useRandomDelay FALSE
2026-09-13T19:57:10.382Z:INFO:db_chargingprofi:28: ChargingSchedule
2026-09-13T19:57:10.394Z:INFO:db_chargingprofi:28: duration 4294967295 (not specified)
2026-09-13T19:57:10.410Z:INFO:db_chargingprofi:28: startSchedule NULL
2026-09-13T19:57:10.417Z:INFO:db_chargingprofi:28: chargingRateUnit Amperes
2026-09-13T19:57:10.429Z:INFO:db_chargingprofi:28: minChargingRate -1.00 (not specified)
2026-09-13T19:57:10.441Z:INFO:db_chargingprofi:29: schedulePeriods 1
2026-09-13T19:57:10.449Z:INFO:db_chargingprofi:29: SchedulePeriod:
2026-09-13T19:57:10.460Z:INFO:db_chargingprofi:29: startPeriod 0
2026-09-13T19:57:10.468Z:INFO:db_chargingprofi:29: limit 7.30
2026-09-13T19:57:10.480Z:INFO:db_chargingprofi:29: numberPhases 3
Questions: How can I remove this profile?
I do not know if it resides in the charger or that it is sent from homey after a reboot (I did not test that yet)
I have “OWNER” acces to the charger, but no “Installer” access.
This is a default profile that Alfen also uses through their own app. I don’t think it is deletable.
The Alfen App does not work on the Duo Pro. But if this default charging profile gives a hard limit on the max current per phase then the only option is to set it to 32A (22kW) before Uninstalling the app. I will test it the coming days.
Hm, that might be why it didn’t work. If even Alfen don’t know how to support it 
Ok, I have reconfigured the charger to accept 32A and put the slider in the app to this 32A.
This changed the charging profile to accept 32A as an external constraint and does not interfere with my own development anymore.
I do think it is a problem that whenever you install your app and use it. It leaves (at least on the double pro) a “residual” active charging profile that imposes a hard limit on the charging current that survives factory resets en even firmware downgrades…
The Alfen APP must a have a way to delete or disable this charging profile and I think it is worthwhile to investigate this. A wild guess is writing -1 to the max charging current might do the job.
@Walter_vande_kerkhof , @Daderu ; I got an email from someone pointing to a Python script that reads the raw log files of the charger. It seems that the Card ID is in there when the session starts. As it is all undocumented I tried to test a bit with my own charger, it is still a bit funky and wondering if it works for you as well. A new version with the Active Charge ID can be tested here: Alfen | Homey
@MrDutchfighter that’s good news. I will test it soon and let you know. Because it’s a testversion, is there a possibility to return to the released version if something appears to be wrong (without deleting and installing the app)?
Nice, will give it a try. Because al other tricks to indentify my car haven’t ben succesfull. I suspect the car is a bit slow given responses.
