Skip to content
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

Request timeout issue when ping_interval=None and ping_timeout=None are set. #626

Open
Mynk96 opened this issue Apr 15, 2024 · 2 comments
Open
Labels
bug Something isn't working need information Need more information regarding the raised issue stale

Comments

@Mynk96
Copy link

Mynk96 commented Apr 15, 2024

I dont get 'CALL' response in time its gets timeout error, but soon as I disconnect the charger from the server and when it reconnects on its own the 'CALL' are working fine .
Its happening with some of the charger they send heartbeat at regular interval but don't respond to Call like(remoteStart,clearCache,reset etc.)
It mostly happens after charger is idle for long time , it doesn't respond to any CALL but regularly send heartbeat ,until it reconnects

FYI
This particular vendor don't support ping/pong message so have diasabled them in in web socket. hope that is not causing any issue

websockets.serve(handler, "0.0.0.0", 9000 subprotocols=["ocpp1.6"], ping_interval=None, ping_timeout=None)

@Mynk96 Mynk96 added the bug Something isn't working label Apr 15, 2024
@jainmohit2001 jainmohit2001 added the need information Need more information regarding the raised issue label Oct 15, 2024
@jainmohit2001
Copy link
Collaborator

Hi @Mynk96, is this issue still relevant? Otherwise we can close this.

Copy link

github-actions bot commented Dec 9, 2024

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working need information Need more information regarding the raised issue stale
Development

No branches or pull requests

2 participants