Update DB model to support OCPP 2 transaction IDs

XMLWordPrintable

    • Type: New Feature
    • Resolution: Fixed
    • Priority: Major
    • Component/s: DB, OCPP
    • None

      In OCPP 1.6 the transaction IDs are 16-bit integers, generated by the Central Service. In OCPP 2 the transaction IDs are strings (up to 36 characters), generated by the Charge Point. To support both models, update SN to treat the transaction IDs as strings. In OCPP 1.6 16-bit integer IDs should still be generated, but stored as strings and converted to integers in the OCPP 1.6 API as needed.

            Assignee:
            Matt Magoffin
            Reporter:
            Matt Magoffin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: