Replies: 2 comments 2 replies
-
Currently only one charger per central server is supported by this integration. You can create another central server that will listen to a different port (e.g. 9001) ad connect the second charger to that. How many charger do you want to connect? |
Beta Was this translation helpful? Give feedback.
2 replies
-
It is only available if your charger supports the "Smart Charging" profile. You can check this in the value of the 'Features' sensor. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have successfully integrated an ABB charger. After I integrated the second into the network with the same configuration, it is not recognized. How are the steps to integrate more than one charger?
Error:
Logger: custom_components.ocpp
Source: custom_components/ocpp/api.py:745
Integration: Open Charge Point Protocol (OCPP) (documentation, issues)
First occurred: 12:25:34 (7 occurrences)
Last logged: 12:28:48
Exception occurred: cannot call recv while another coroutine is already waiting for the next message
Traceback (most recent call last):
File "/config/custom_components/ocpp/api.py", line 184, in on_connect
await charge_point.reconnect(websocket)
File "/config/custom_components/ocpp/api.py", line 745, in reconnect
await super().start()
File "/usr/local/lib/python3.9/site-packages/ocpp/charge_point.py", line 125, in start
message = await self._connection.recv()
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 385, in recv
raise RuntimeError(
RuntimeError: cannot call recv while another coroutine is already waiting for the next messag
e
Beta Was this translation helpful? Give feedback.
All reactions