Sorry, my previous post should have been in English.
Currently:
Ik stuur mijn Alfen palen aan met de modbus app, geef dan dus modbus commando`s. Der is ook aardig wat uit te lezen via modbus
So I recently went through the required hoops to get the root password for my Alfen Eve charging station and took it “offline” (disconnected the remote backoffice for which I had to pay 6 Euro’s per month, and converted the P1 cable into a network cable, and added back load balancing capabilities via the HomeWizard P1 WiFi dongle). I now have several options to integrate into Homey:
I think I’m gonna give the 3rd option a try. This would not only add support for the Alven Eve, but a whole lot of other chargers that support OCPP (which is pretty much the industry standard nowadays, at least in the EU).
Chris
That sounds great Chris. look forward to the Homey app for Alfen Eve
Small update on my progress.
Implementing OCPP is going quite well. I can send and receive messages to a (simulated) charging station. I have also made a start on auto-discovery for known charging station manufacturers, starting with Alfen (based on mDNS). I’m implementing OCPP in such a way that any charging station that was added during a Homey pairing flow is automatically whitelisted on the OCPP server. Then you can configure the charging station to point to Homey as remote back office (I’ll add some instructions in the pairing flow). I’m also adding RFID tag whitelisting to the app settings. Please let me know what other features you would like to see.
Chris
Sounds good, what comes to mind is that it would be great to set charging to max, comfort or green for the Alfen stations from homey.
Hi Chris,
This approche would mean that a OCPP backoffice for split-billing cannot be configered on the Alfen anymore?
Depending on the charging station it could still be possible. OCPP supports a charging station having multiple back office providers (on different network interfaces, e.g. LAN for Homey and SIM for a remote provider that you use for automated billing). OCPP also supports proxying, so I could add that to the Homey app so you can still forward the charging session information to the billing provider.
Makes sense! I’m not sure if that’s standard OCPP functionality, or an Alfen custom message. Could still be implemented by creating some device sub-types for specific manufacturers with additional controls.
Use Alfen on ModBus and than connect it with Homey?
Hi Chris, just wondering if there is any progress on the app?
Also an option, but ModBus isn’t universal for all charging station brands, whereas OCCP is a standard (higher-level) protocol specifically for charging stations. This means the Homey user would need to configure a lot more things to access the correct ModBus registers, and there is more room for writing faulty data to the charging station and breaking it in the process.
Not much progress, switched jobs, went on vacation and worked on feature requests and bug fixes for my other Homey apps. I have a basic connection working (charging station can connect and authenticate, and send keep-alive messages). Next step would be deciding which basic functionality to start with so I can publish a first (test) version. Some preliminary code can be found here: homey-ocpp/drivers/ocpp/device.ts at main · ChrisTerBeke/homey-ocpp · GitHub.
Have been working on an Alfen integration. So far it is only to see how much energy has been used for the new energy dashboard. It connects to the API of the charger (partially same data as can be seen in the MyEve app). However it is quite hard to set-up. You need a username, password and fixed IP, and the fixed IP must be in the same subnet as your Homey. So if you have a network set-up with multiple subnets for WiFi, Domotica, and other devices both the Charger and Homey needs to be in the same network (and if you want to access it through the MyEve app, then also your phone).
But there is something 
You can find the source here: GitHub - robertraaijmakers/com.alfen: Project to support the Alfen charger on the local Homey platform.
You need to enter the username (admin), IP and password in code and compile your own version. Then you can add the charger as device. After that you get some nice details and power usage will show up in the new Homey Energy feature
I want to make it more dynamic with discovery and a set-up wizard, but haven’t found the best documentation from Athom yet on how to do that properly per device.
Nice! Great steps!
Hey,
Great to hear, will try it out during the next days.
If you want help, feel Free to reach out, I have Developed the Viessmann app, so I might be able to help you out to Publish it.
Groetjes
Kenny
Super, just installed it and works nice. Now I can limit the SOC of the I-pace that does not have this option in the car. It is still a calculation but better than limiting timewise
Hey,
The app works nicely.
I’ve just created a merge request that allows to configure the credentials using a custom pairing view & the device settings:
Hope this helps you out.
Merry Christmas,
Kenny
Thanks! Looks great 
Once I get back I will see if I can publish it.
If you could have a look at the turning on and off command please. When I use that, I get an error " Missing Capability Listener:onoff
