ocpp | Python implementation of the Open Charge Point Protocol | Networking library

Every Charge Point work as client and the Central Station is the Server. So, every Charge Point need to know the endpoint of Server.

Which version of OCPP you want use or server use, I recommend 1.6 Json

I geuss you should connect with http://db:3306 instead of mariadb:3306.

By default Docker Compose version 3 uses the service name as hostname of inter-container networking.

I had a look at the pic you attached for modules installed in venv. I notice that in the warning, the venv directory is not the one from your workspace.

As such, I suspect the issue is right there. Open the command pallete (ctrl+shift+P), type interpreter, and click on the option Python: Select Interpreter. Now type the path to the venv ".\venv\scripts\python.exe".

One done, open a new terminal and type .venv\scripts\activate. This should now activate the right venv. Once here, You should reinstall the required libraries if they are not there.

After that, it should work.

You are trying to save the file on the remote server using a local path. Note how you use the same path with local open and remote storbinary. I'm quite sure your remote server has a different directory structure.

If you want to upload the file to your FTP home directory, use just a filename:

It's hard to tell from what you posted why you are getting an error, so I can only add some information that can hopefully allow you to troubleshoot the issue.

Your message has WS-Addressing headers, being one of them. The value of this field should be specified in the WSDL if your WSDL also includes WS-Addressing Metadata information, or should be specified in the documentation of the web service you are invoking. Your error message "XML Request is not well formed, Action does not exist" seems to indicate that there might be an issue with this field, but there is another action that SOAP services have which is a SOAP action. I asked about it in the comment above to make sure it's eliminated as a source of problems. In SOAP 1.1 it's called SOAPAction and is a separate HTTP header, while in SOAP 1.2 it's an action parameter on the HTTP Content-Type header. Based on the http://www.w3.org/2003/05/soap-envelope namespace, you have a SOAP 1.2 message.

With these explanations layed out, I suggest you take the WSDL and feed it to SoapUI who can generate sample requests that you can use to invoke the web service. If the WSDL also contains WS-Addressing Metadata, SoapUI should be able to pick it up and help you fill in the values you need. If not, look again through the WSDL for Action elements (make sure you differentiate between the SOAP Action and the WS-Addressing Action using their XML namespaces) or through the service documentation.

Once you get a succesfull call using SoapUI, then try to duplicate it with your code. At that point you can again use SoapUI to troubleshoot things and inspect your code built message to see it resembles the one you can successfully send with SoapUI.

Hope this helps get you closer to a resolution.

[PyPI]: ocpp (currently v0.8.1) only supports Python 3. However, same thing applies to v0.1.1 (very 1^st OCPP version).

So, the only way to proceed is install (and start using) Python 3, and give up Python 2(.7) (who is dead from the beginning of allmighty 2020 ([Python]: PEP 373 - Python 2.7 Release Schedule)).

Of course, there's the (painful) alternative of porting OCPP code to Python 2, but I'd totally advice against it.