Feature Request: Enhanced NRGkick Support with GPS Data and OCPP1.6 Profiles (DataTransfer, GeoLocation, SmartAttachment)

Feature Request:
We would like to request an enhancement of the software to improve support for NRGkick charging processes. This includes evaluating and storing GPS data to geographically restrict the charging area, adding support for OCPP1.6 profiles, and ensuring that SmartAttachment and GeoLocation data match the virtual RFID for charging to proceed.

---

Requirements:

1. Evaluate and Store GPS Data:

• Implement functionality to capture GPS coordinates (latitude, longitude) from the DataTransfer messages.
• Store these GPS data for each transaction.

2. Support for OCPP1.6 Profiles:

• Extend the software to process the DataTransfer commands for:

  • transaction.smart.attachment:

    • Fields:
      • TransactionId
      • SmartAttachmentType (1 = CEE, 2 = Domestic Plug, 3 = Type 2, 4 = Wall Attachment)
      • SmartAttachmentSerial
    • SmartAttachmentTypes:
      • 1 - "CEE"
      • 2 - "Domestic Plug"
      • 3 - "Type 2"
      • 4 - "Wall Attachment"
    • Example for SmartAttachment:

      DataTransfer: [2,"3d32dcb3-f58f-43b6-87a8-18af62e75cd7","DataTransfer",{"vendorId":"com.nrgkick","messageId":"transaction.smart.attachment","data":"194978479, A140523, 1"}]

  • transaction.geo.location:

    • Fields:
      • TransactionId
      • Latitude, Longitude (default value "200, 200" if no GPS position is found)
    • Example for GeoLocation:

      DataTransfer: [2,"7518a21f-373c-469c-a694-2e122c49c447","DataTransfer",{"vendorId":"com.nrgkick","messageId":"transaction.geo.location","data":"194978521, 200, 200"}]

3. Geographical Charging Restriction (Virtual RFID):

• Implement logic that allows charging only within a defined geographical area based on GPS data.
• Charging attempts outside the predefined area should be automatically rejected.

4. Match SmartAttachment and GeoLocation (Virtual RFID):

• Implement a validation step where the SmartAttachment and GeoLocation data must match the virtual RFID used in the transaction.
• If the data does not match the virtual RFID, the charging process should be automatically refused.

---

OCPP1.6 Profile Support:

OCPP1.6 profiles/commands:

Core:

• Authorize
• BootNotification
• ChangeAvailability
• ChangeConfiguration
• ClearCache -> Not applicable if no local authorization cache exists (which is optional)
• DataTransfer
• GetConfiguration
• Heartbeat
• MeterValues
• RemoteStartTransaction
• RemoteStopTransaction
• Reset -> Only Soft Reset
• StartTransaction
• StatusNotification
• StopTransaction
• UnlockConnector -> No Lock exists

Smart Charging:

• Trigger Message

Hello everyone

Is there already an update on the improvements suggested in this issue?
Are there any plans for an implementation or roadmap for these features?

Thank you in advance for your feedback!