Skip to content

❔ Question: How to handle customData #365

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

Open
2 of 5 tasks
Gozikyu opened this issue May 23, 2025 · 0 comments
Open
2 of 5 tasks

❔ Question: How to handle customData #365

Gozikyu opened this issue May 23, 2025 · 0 comments

Comments

@Gozikyu
Copy link

Gozikyu commented May 23, 2025

❔ What is your question?

Question about customData in OCPP 2.0.1 messages

I'm currently using your ocpp-go library for an OCPP 2.0.1 implementation. I'm trying to send custom, vendor-specific data to the charge point within OCPP messages like AuthorizeResponse.

However, after reviewing the Go struct definitions for requests and responses (e.g., AuthorizeResponse), it appears that a CustomData field isn't explicitly included in the structures.

As customData is a standard feature in OCPP 2.0.1 for conveying vendor-specific information, I'd like to understand how your library intends for users to achieve this.

Could you please clarify how I can pass customData within OCPP 2.0.1 requests and responses using ocpp-go? Any guidance or examples would be greatly appreciated.

Thank you for your time and assistance.

Which OCPP version referring to?

  • OCPP 1.6
  • OCPP 2.0.1

Are you using any OCPP extensions?

  • OCPP 1.6 Security
  • OCPP 1.6 Plug and Charge

👀 Have you spent some time to check if this question has been asked before?

  • I checked and didn't find a similar issue
@Gozikyu Gozikyu changed the title ❔ Question: ❔ Question: how to handle customData May 25, 2025
@Gozikyu Gozikyu changed the title ❔ Question: how to handle customData ❔ Question: How to handle customData May 25, 2025
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

1 participant