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

OCPP: if setting WebSocketPingInterval is NotSupported in nightly, ocpp setup will fail #15852

Closed
jeffborg opened this issue Sep 1, 2024 · 0 comments · Fixed by #15853
Closed
Labels
bug Something isn't working

Comments

@jeffborg
Copy link
Contributor

jeffborg commented Sep 1, 2024

Describe the bug

run nightly and evse rejects this line

return cp.configure(KeyWebSocketPingInterval, "30", timeout)
before this was not an issue it now is due to being in return position

Steps to reproduce

  1. run nightly
  2. if setting WebSocketPingInterval is not supported by your ocpp evse
  3. then evcc will fail setup here because this command on this line is rejected
    return cp.configure(KeyWebSocketPingInterval, "30", timeout)

Configuration details

Any occp charger which rejects the WebSocketPingInterval configuration

Log details

[ocpp  ] TRACE 2024/09/02 09:30:05 send SN10052307203612: [2,"2478905827","ChangeConfiguration",{"key":"WebSocketPingInterval","value":"30"}]
[ocpp  ] TRACE 2024/09/02 09:30:05 recv SN10052307203612: [3,"2478905827",{"status":"NotSupported"}]

What type of operating system are you running?

Linux

Version

master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants