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

feature(OCPP1.6): forward VendorWarning appropriately #949

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

a-w50
Copy link
Contributor

@a-w50 a-w50 commented Nov 7, 2024

  • this change will treat the VendorWarning the same way as VendorError, so that also the error.message becomes visible in the OCPP StatusNotification message

Describe your changes

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • I read the contribution documentation and made sure that my changes meet its requirements

- this change will treat the `VendorWarning` the same way as
  `VendorError`, so that also the `error.message` becomes visible in the
  OCPP StatusNotification message

Signed-off-by: aw <aw@pionix.de>
- the forwarding of everest errors to ocpp status notifications has been
  generalized
- the generic mapping from an everest error to an ocpp status
  notification is done now as follows:
  - status notification charge point error code will always be `OtherError`
  - status notification info -> origin of everest error
  - status notification vendor error code -> everest error type and
    subtype (the error type is simplified, meaning, that its leading
    part, the interface name, is stripped)
  - status notification vendor id -> everest error message
- the main choice for using the status notification vendor id for the
  error message is that it can carry the largest string (255
  characters), whereas the other fields only allow up to 50 characters

Signed-off-by: aw <aw@pionix.de>
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

Successfully merging this pull request may close these issues.

2 participants