Stop Charging
+++++++++++++

.. jsonschema:: ../../../schemas/StopChargingRequest.json
   :hide_key: /**/additionalProperties

Example::

    {
        "id": "dd7de5f8-64b0-4796-9fd6-a428de018e21",
        "name": "stop_charging",
        "type": "request",
        "data": {
            "evse_id": "DE*SEV*E123456789"
        }
    }

.. jsonschema:: ../../../schemas/StopChargingResponse.json
   :hide_key: /**/additionalProperties

Example::

    {
        "id": "dd7de5f8-64b0-4796-9fd6-a428de018e21",
        "name": "stop_charging",
        "type": "response",
        "data": {
            "evse_id": "DE*SEV*E123456789",
            "status": "accepted"#or"rejected"
        }
    }


.. admonition:: NOTE
   :class: tip

   The stop_charging message is used to serve at least two different use cases:

   1. **RemoteStop Request**

   After the CSMS has sent a RemoteStopRequest to the CS OCPP module and this one is accepted, we need to request either the CS directly or to 15118 to stop charging.

   2. **Stop Transaction by Authorization Token**

   On the reception of an AuthorizationRequest by the CS OCPP module on a running transaction, we shall send a stop_charging message either to the CS directly or to 15118.
   On both scenarios above, the message used for that purpose is the same for both, but the topics are different. The decision to send the message to the CS or to the 15118 service is based on the EVSE type (which we know through the response to device_model) and with the reception of v2g_setup status = finished. If v2g_setup is NOT finished and the EVSE type is AC, then we send this message to the topic: josev/cs, otherwise, in any other case we send it to ocpp/iso15118 (this also means that, if we are under a DC session, we send it to ocpp/iso15118 topic).

-------------