-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hubject OICP connection #4234
Comments
Hello, I came back since I think I need a little more help about this! I found a small issue about the create Roaming Connections and posted here: But still facing the issue about the Service URL, which is required by Hubject to send remote start/stop. I found some code in the server, and added the config to start the OICP server but cant seem to find the proper way on how to do this. |
It is really strange that none of the contributors are ever replying to any of the issues! "at leaast mine :(" How can we have the solution setup if not from their help? |
I'm going to write here my journey for this and hopefully I will also help somebody else! I managed to get the Service URL, from the CPOService file, this: And the communication now is ok. Another problem is that when I try to do remote start I get And also the local users cant start the charging process for the Public chargers! getting the |
i am sorry i cannot contribute...i am also searching my a** of for information on this csms....but appertently you have to do everyhting yourself...hahahaha I am now starting my journey with Hubject. I will follow this and you are helping me for sure. |
Good luck, please share your experience. |
@UBT-FJ Hello. Can you please provide me with any way of communicating with you? I have some questions regarding this repository. I really appreciate any help you can provide. |
Hello,
anybody did this?
There are the endpoints in the code but don't know how to connect to them!
Is it possible to connect only through the CPO Identification? which it requires only the:
The text was updated successfully, but these errors were encountered: