Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Charge Amp change to OCPP #59

Open
gassentb opened this issue Sep 20, 2024 · 1 comment
Open

Charge Amp change to OCPP #59

gassentb opened this issue Sep 20, 2024 · 1 comment
Assignees

Comments

@gassentb
Copy link

Hello
Will this affect the API in the Home assistantans integration?

Copied from ChageAmp's support

What is OCPP?
CAPI and OCPP EV chargers share similar functionalities that enable Charge Point Operators to remotely manage and monitor their charging infrastructure. However, they differ in communication protocols, cloud maintenance, updates and technical support. OCPP is the industry-standard international protocol for Electric Vehicle charging. It enables seamless and bidirectional communication between chargers and CMS (Central Management Systems). Charge Amps adopted the most widely used OCPP version 1.6J to offer the best features and highest security for efficient EV fleet management.

@fredriklj
Copy link
Member

Yes, it does have an impact. The state machine in the chargepoint is different. For example, you can not disable a port while there is an ongoing charging session. You must first stop the session, and then disable the port. But it was also very unreliable. I was unable to get the API working in a meaningful way after the upgrade to OCPP, for which reason I have now swapped out my charge amps wallboxes for another brand.

This is also why we are looking for new maintainers of this integration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants