When I click start transaction, it prints this error "The aggregate was not found". about motown HOT 4 CLOSED

I'm not able to reproduce the exact error you're seeing, but looking at the stacktrace and the identifier of the aggregate "DEMO_001" it looks like you're trying to start a transaction on the MOBI.Europe tab page.

That one has a hardcoded charge point identifier for demo purposes.

If you want to start a transaction on a real charge point you have to:

1. Connect the charge point to one of the endpoints (in the simple config check: http://localhost:8089/services for SOAP or connect a JSON charge point to ws://localhost:8089/websockets/chargepoint_id_here) and boot it. If you boot with a chargePointVendor (MOTOWN) and chargePointModel (MODEL1) that exists in the configuration add-on it should be configured right away.
2. Register (accept) the charge point in your Motown instance via the user interface
3. Start a transaction via the user interface

from motown.

Hi Mark,

I tried to send a boot notification request
to: http://localhost:8089/services/centralSystemServiceOcpp12
with Body
<x:Envelope xmlns:x="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="urn://Ocpp/Cs/2010/08/"> <x:Header> <ns:chargeBoxIdentity>DEMO_001</ns:chargeBoxIdentity> </x:Header> <x:Body> <ns:bootNotificationRequest> <ns:chargePointVendor>MOTOWN</ns:chargePointVendor> <ns:chargePointModel>MODEL1</ns:chargePointModel> <ns:chargePointSerialNumber>001</ns:chargePointSerialNumber> <ns:chargeBoxSerialNumber>0001</ns:chargeBoxSerialNumber> <ns:firmwareVersion>0.1</ns:firmwareVersion> <ns:iccid>00001</ns:iccid> <ns:imsi>01</ns:imsi> <ns:meterType>1</ns:meterType> <ns:meterSerialNumber>00000001</ns:meterSerialNumber> </ns:bootNotificationRequest> </x:Body> </x:Envelope>

It sent back a content:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault> <faultcode xmlns:ns1="http://www.w3.org/2005/08/addressing">ns1:MessageAddressingHeaderRequired</faultcode> <faultstring>A required header representing a Message Addressing Property is not present</faultstring> </soap:Fault> </soap:Body> </soap:Envelope>

I don't know what I'm missing here. Is there a document introducing these SOAP API calls? I read most documents there. I couldn't find a document about headers. BTW, I have already added X-Auth-Token and Cookie in the headers.

Thanks

from motown.

Are you using SoapUI? If so, please enable WS addressing: https://www.soapui.org/soap-and-wsdl/supported-standards/using-ws-addressing.html

Make sure you check "wsa:Action", "wsa:To" and "Generate MessageID".

from motown.

Still has error. But it can be tested by using OCPP Chargebox.

Issued resolved. Thanks.

from motown.