-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Support for multiple connectors #1366
Comments
I've reopened the pull request... but there are some issues that need to be resolved before this can be merged to main. |
Great, thank you. |
I would also be very happy to control both Wallbpxes with this great integration. ;-) |
Dual socket model support would be really great. I have 2 dual socket chargers and I can only command connector 1 (left socket) with HA. Some entities have 1 and 2 attributes like connector state and connector error but real commands would be great. Any workaeounds for this? |
I would also like to use the integration for both of my Mennekes wall charging stations. Kindly let me know, if there is any beta to test multi device support. |
Multi charger device support is already working. You just need to use different port and server/client names for these chargers when adding to ocpp server. Like: Charger 1: port 9001 server1/charger1 If you would have 2 sockets in one charger only the left socket would be working trough ocpp and this thread is about that need. |
Thanks for the hint! I was able to connect both of my chargers by adding two integrations on separate ports, and it works as expected. So the support is there, at least for this configuration 👌 |
I would like to request (once again?) the development of the feature for multiple connector support.
I believe this has been worked on before, but unfortunately, it does not seem to have been included in the integration for some reason. Below is a link to the closed feature:
https://github.com/lbbrhzn/ocpp/pull/803
I really appreciate the integration—great work! I hope the multiple connector feature can finally be included and make th integration complete.
The text was updated successfully, but these errors were encountered: