-
Notifications
You must be signed in to change notification settings - Fork 4
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
Error while connecting multiple charge points #6
Comments
I am also getting this error randomly
Before this error I saw a warning
Is this something common, and how will I be able to avoid this? |
@villekr Any suggestions? |
First one looks like there might be some messaging going on during disconnect or over already disconnected connection. Try to be careful how you initiate messaging from on_connect. Also ensure that you update charging station's connection state on on_disconnect so that your backed doesn't try to message to disconnected instance. Second one might be a bug in ocpp-asgi. Earlier in your logs before traceback error you should have 'scope' variable logged. What's the value in that case? |
@villekr Please ignore the previous comment. I have created a reproducible example. If you have any doubt about this please let me know. I am just suggesting that the WebSockets library upgrades the HTTP request by itself, then why isn't this happening over here? Is this an ocpp-asgi library error or uvicorn error? Packages Used Normal WS Code
Logs after I send an empty HTTP request through Postman
Packages Used Code through OCPP-ASGI
Logs after I send an empty HTTP request through Postman
Values of SCOPE, EVENT and SEND
|
This is fixed in #10. Now if http request has no body then return http 400 and handle that gracefully. |
@villekr Giving a version number would be easy for everyone to track. |
@villekr Sometimes when my ChargePoint reconnects to my CentralSystem, I get this error, is this a handshake error, and is it necessary that I get an Exception?
How to avoid this or else bypass this?
The text was updated successfully, but these errors were encountered: