-
Notifications
You must be signed in to change notification settings - Fork 15
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
AllowOfflineTxForUnknownId with OCMF #21
Comments
From my point of view this is a setting which is not compatible to Eichrecht. So there is no reason to represent it in OCMF. |
Thanks for your reply. I think this give me a hint how to proceed. |
Can you explain why the key is not compatible with Eichrecht? |
From my understanding a transaction according to Eichrecht needs a valid user profile, which is accountable. If AllowOfflineTxForUnknownId is set to true and the charging station is offline, there is a chance that the unknown ID token will get rejected after online connection has been re-established and the consumed power has to be payed by the CPO. Strictly speaking this setting is compatible with Eichrecht as long as the ID token will be accepted afterwards from the backend (OCPP_AUTH). So this is a speculation at CPO expense. Disclaimer: I don't speak for the safe e.V. |
In OCPP 1.6 there is a configuration AllowOfflineTxForUnknownId, which indicating when the charger is offline, and the incoming RFID is not in neither localList or Cache, with this configuration set to true, the charger is allowed to authorize the session.
But there is no suitable Zuorderungsanteil OCPP for this.
This session is authorized by the OCPP standard, so the Zuorderungsanteil OCPP shall not be NONE, and this is also not part of CACHE nor WHITELIST.
Hence the question came up, what to put in this case? Any field case suggestion?
Thanks
The text was updated successfully, but these errors were encountered: