Autel MaxiCharger works well with the OCPP integration

[jds11111]

The documentation does not list this charger as working, but I just got it working with your integration. EDIT: with version 0.7.0. Updates to 0.8.0 through 0.8.4 have migration errors. I have uninstalled and reinstalled to avoid the migration errors, but the charger still works only 0.7.0.

Version of the custom_component

Latest version 0.7.0

Configuration

Running it unsecure on port 8887.
Followed these instructions on how to use the app to set up the charger. It worked as described.

Describe the bug

There is no bug with the software, just wanted to add to the documentation as another charger that works!
After setting up, there was control for availability, charger on/off and current. There were also 10 sensors available:

I blocked the charger from the internet, and still have fully local control.

Debug log

Great work, folks!

[alejandrom2]

👍🏼 Same here, Autel appears to have now properly report.
I am seeing an issue with the max current report as 32amps, but the charger is currently set to 50 amps. Will investigate if its being reported improperly or an integration issue.

[jds11111]

Mine correctly reports a maximum 48amps. I haven't ever changed it from that, though. Even with original app.

[rj45jack]

👍🏼 Same here, Autel appears to have now properly report.
I am seeing an issue with the max current report as 32amps, but the charger is currently set to 50 amps. Will investigate if its being reported improperly or an integration issue.

I am having the same issue. In the app my charger is set to 48A. The dips on the board are set to 48A. But this integration reports 32A as max.

[jds11111]

👍🏼 Same here, Autel appears to have now properly report.
I am seeing an issue with the max current report as 32amps, but the charger is currently set to 50 amps. Will investigate if its being reported improperly or an integration issue.

I am having the same issue. In the app my charger is set to 48A. The dips on the board are set to 48A. But this integration reports 32A as max.

My charger is set for 50amps, but my car limits to 48amps, which is what this integration reports. Is it maybe your car setting the limitation? What firmware is your charger running?

[rj45jack]

👍🏼 Same here, Autel appears to have now properly report.
I am seeing an issue with the max current report as 32amps, but the charger is currently set to 50 amps. Will investigate if its being reported improperly or an integration issue.

I am having the same issue. In the app my charger is set to 48A. The dips on the board are set to 48A. But this integration reports 32A as max.

My charger is set for 50amps, but my car limits to 48amps, which is what this integration reports. Is it maybe your car setting the limitation? What firmware is your charger running?

Thanks. My car isn't connected yet, but supports 48 as well. Perhaps when I get home I can plug in to check.

[alejandrom2]

What appears to be happening based on some testing is that Autel is not 100% supporting OCPP 2.0.1, in fact it returns that its using 1.6, when SupportedFeatureProfiles which is a 2.0.1 key responds with the charger results.
The following configuration key appears to properly return the set current MaxChargeCurrentLimit (in my case 50)
Follow: #1019 (comment)

[rj45jack]

What appears to be happening based on some testing is that Autel is not 100% supporting OCPP 2.0.1, in fact it returns that its using 1.6, when SupportedFeatureProfiles which is a 2.0.1 key responds with the charger results. The following configuration key appears to properly return the set current MaxChargeCurrentLimit (in my case 50) Follow: #1019 (comment)

Thanks. This is my issue as well.

[jds11111]

I have edited my original post to indicate that, for me, it works only for 0.7.0, but not more recent versions.

[rj45jack]

I have edited my original post to indicate that, for me, it works only for 0.7.0, but not more recent versions.

Hey thanks. I rolled back and it's working great.

Edit: It's still locked to 32A.

[gomsykakkar]

While I am trying to configure using configuration wizard I am getting connection failed after reboot on charger.

I am using custom port as port 9000 was being used for other docker container.

[jds11111]

Try it without the trailing forward slash. Also, maybe try using the IP of your OCPP integration, instead of 0.0.0.0

[gomsykakkar]

Hi @jds11111 , thanks for your feedback.
I finally managed to run ocpp.
The issue was since I am running Home Assistant in docker container the ocpp port(9000) from container to host was not opened. I managed to resetup the home assistant container with ha port as 8123 and ocpp port as 9000.

Once bith port are opened then start configuring ocpp plugin with 9000 port.

Now I am able to start charger but not able to set maximum current and I am stuck with @ocpp#1019

[jds11111]

I don't understand why I don't have that problem.

[gomsykakkar]

Are you using home assistant on docker?

[jds11111]

Yes, I am. This is the firmware version reported to OCPP: PFA0102|V0.00.00|V1.36.00|V1.21.00|2.4.3.0, Autel MaxichargerAC, and charger features: Profiles.CORE|FW|SMART|RES|REM|AUTH. The charger is blocked from reaching the internet at my router/firewall.

I am still running OCPP version 0.7.0, since none of the 0.8.x version work for me.

[gomsykakkar]

I switched to 0.7.0 after coming on this thread.
And my device info is.
MaxiChargerAC by Autel
Firmware: PFA0101|V0.00.00|V1.55.00|V1.19.00|2.4.0.0

[jds11111]

So, different firmware, but it is hard to decipher the different numbers. The app says that it is verion 3.2.1. If we are running the same OCPP backend, then mustn't it be the charger firmware version that is different?