Commits on Nov 7, 2024

1. feature(OCPP1.6): forward VendorWarning appropriately …

   - 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>

   

   a-w50 committed Nov 7, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 969d5c3
   • Browse repository at this point

   Copy the full SHA

   969d5c3 View commit details

   Browse the repository at this point in the history

2. update …

   - 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>

   

   a-w50 committed Nov 7, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for e0b4219
   • Browse repository at this point

   Copy the full SHA

   e0b4219 View commit details

   Browse the repository at this point in the history