documentation Alfen Eve charger ? Topic is solved

[willemd]

I upgraded to Domoticz version 2023.2 succesfully. Thanks for that new version.

I saw that the Alfen Eve charger is now available as hardware and I tried to add it.
I configured the hardware with a name, IP address, username and password.
I left the port 443 unchanged, I assume that is the one to use.

For username I used the ID of the charging station and for password I used the default password of the owner of the charging station (which I know is correct since I can login with that using the MyEve app)

After pressing "Add" the correct firmware version of the charger shows up after a few seconds, so it seems the login was succesfull.

However, no devices were created and the log shows

Code: Select all

2023-07-24 10:55:54.425 Error: WebServer:8080 thread seems to have ended unexpectedly (last update 579.000000 seconds ago)
2023-07-24 10:55:56.725 Error: Alfen Eve laadpaal: Login problem! (Check password!)
2023-07-24 10:56:01.727 Error: Alfen Eve laadpaal: Login problem! (Check password!)
2023-07-24 10:56:06.744 Error: Alfen Eve laadpaal: Login problem! (Check password!)

update to the above: I managed to get rid of the error messages. It seems you can connect with only one device at the time, so I logged out of the MyEve app and re-did the hardware setup in Domoticz. Now it shows the firmware version again, no error messages in the log, but also still no devices.

What am I doing wrong? Is there any documentation available on this new hardware?

[willemd]

Domoticz version 2023.2 released

As creator of the software, can you shed some light on this?
What should I expect from this hardware , how to use and how to set up? What am I doing wrong here?

[gizmocuz]

Domoticz version 2023.2 released

As creator of the software, can you shed some light on this?
What should I expect from this hardware , how to use and how to set up? What am I doing wrong here?

First make sure you have nothing connected to your charger.
(So no Ace installer running)

Next, make sure that you know your chargers password (the one you use with the Ace installer to login to your charger)

Also make sure under settings you enabled ''Accept new hardware Devices'' otherwise no new sensors are added

[willemd]

Domoticz version 2023.2 released

As creator of the software, can you shed some light on this?
What should I expect from this hardware , how to use and how to set up? What am I doing wrong here?

First make sure you have nothing connected to your charger.
(So no Ace installer running)

Next, make sure that you know your chargers password (the one you use with the Ace installer to login to your charger)

Also make sure under settings you enabled ''Accept new hardware Devices'' otherwise no new sensors are added

Thanks, I tried again.
Accept new hardware Devices was already on, but I also tried again with "allow for 5 minutes".

So:
* nothing else connected
* create hardware with chosen name, type alfen eve charger, ip address, port unchanged, username (=ACExxxxxxx), password (=owner password)

I see:
* hardware line is added
* logfile shows "worker started"
* hardware line shows the firmware version (so connection was succesfull)
* no error messages in the logfile (no errors about password)

but still no devices created.

[willemd]

Maybe the ID used in ACE service installer is different from the MyEve app. I will try it out.

I noted in the code the API format and tried those formats in a browser. I can open the info page but not the props page.

[willemd]

I now installed ACE service installer and received a username and id. I entered that username and id in the Domoticz hardware config.

Same result as before: it shows firmware version, worker started, no error messages.

But also no devices

Instead of updating the hardware I also tried removing it, restart domoticz, add it again. Makes no difference.

[willemd]

I also tried other ways to access the charging station, like the Alfen-Eve python software and a small python test program.

They all fail on login, with a HTTP response error 403, so I think there is some kind of security setting that prevents login with just username and password (backoffice setting?). I also tried a HTTP POST request with verify=False but that does not solve it.

HTTPError: 403 Client Error: Forbidden for url: https://xxx.xxx.xxx.xxx/api/login

Maybe the software was created for older firmware versions? With firmware version 5.3 a new setup of security was introduced.

So far I can only access the charger with the software provided by Alfen, either the ACE service installer software or the MyEve app.

I noted that the firmware version and some other info can be read without login first, so that explains why Domoticz still can show that info, but not succeed any further. Strange though that Domoticz does not show any error message about the failed login.

[willemd]

Another update:

I managed to successfully login to my charger using the alfen-eve software found here on gitlab https://gitlab.com/LordGaav/alfen-eve/-/tree/develop

With firmware version 5.3 and above (introducing the new password setup for the charging stations) you have to use "admin" as username and then the password of the owner. So don't use the ID of the station as username, just use "admin"
With that software I can then read all properties etc.

I tried the same with Domoticz.......worker started, no errors, no devices.
When I look in the logfile of the charger I see
Invalid password for user: 'admin'
Invalid username/password provided. Login not allowed

I am 100% sure I am providing the correct password.

Could it be because of this line 65 in the code? Why encode the password and not pass it on as-is?
m_szPassword(CURLEncode::URLEncode(szPassword))

[willemd]

Another update!!! It works !!!

If I change the owner password to a password that does not change as result of URLencoding, then it works.
Login succeeds and devices are created.

So it is the URLencoding of the password on line 65 of the code that causes the login problems.

Issue reported on github.

[gizmocuz]

Thanks for reporting. Fixed in beta 15477

[willemd]

And for anyone wondering what this hardware does:

It will create 9 devices as show below, of which I think the EV current and EV energie delivered are the most useful, especially if the car only shows km or % and not kWh. So you can track how much energy actually goes in.

Once my car is delivered ..... I plan to use the Alfen Even software in combination with the Hyundai or Kia car interface software on below link to track energie delivered/stored/used and mileage of the car.

https://github.com/CreasolTech/domoticz-hyundai-kia

alfeneve.jpg (126.3 KiB) Viewed 3442 times

[stelling]

Thanks gizmocuz for this extra hardware, I use it all the time. But I have one issue.

When my car is charging at full speed I get the following error in the log.
Power usage to high/low! Usage: 11290 Watt. Max Usage configured: 6000. (NodeID: 0x0000, ChildID: 0x0007, SID: Actual Usage (L1 + L2 + L3))

Can you have a look at this?

[waltervl]

Thanks gizmocuz for this extra hardware, I use it all the time. But I have one issue.

When my car is charging at full speed I get the following error in the log.
Power usage to high/low! Usage: 11290 Watt. Max Usage configured: 6000. (NodeID: 0x0000, ChildID: 0x0007, SID: Actual Usage (L1 + L2 + L3))

Can you have a look at this?

That is a general setting of Domoticz. Max Power (default 6000 Watt). You have to increase that to the max power on your system.
https://www.domoticz.com/wiki/Applicati ... ters_Setup

[stelling]

Thanks gizmocuz for this extra hardware, I use it all the time. But I have one issue.

When my car is charging at full speed I get the following error in the log.
Power usage to high/low! Usage: 11290 Watt. Max Usage configured: 6000. (NodeID: 0x0000, ChildID: 0x0007, SID: Actual Usage (L1 + L2 + L3))

Can you have a look at this?

That is a general setting of Domoticz. Max Power (default 6000 Watt). You have to increase that to the max power on your system.
https://www.domoticz.com/wiki/Applicati ... ters_Setup

Thanks for the suggestion. I was looking in the settings of the hardware. I have changed it, but I can't test it at the moment.