Replies: 1 comment 8 replies
-
This looks like a bug on our side. The client indicates it supports both ocpp1.5 and ocpp1.6. The HA integration supports ocpp1.6 only, so it should accept the connection. |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There are several testing/simulations charging point tools floating around in the GitHub aimed to test the functionality of your OCPP server, but unfortunately it seems that neither of them working out of the box correctly. Can anyone suggest good program to test the functionality of the OCPP HA integration while Im waiting my for my OCPP EVSE controller?
Im always get this error in HA:
Logger: custom_components.ocpp
Source: custom_components/ocpp/api.py:205
Protocols mismatched | expected Subprotocols: ['ocpp1.6'], but client supports ocpp1.6, ocpp1.5 | Closing connection
I was able to correct the main.js file on the other side to try to fool OCPP HA server into thinking that it is sending only 1.6 signals, but it doesn't work unfortunately. Does anyone have any ideas? I will be glad to hear anything from you guys, thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions