You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked other issues already, but found no answer/solution
I checked the documentation and wiki, but found no answer/solution
I am running the latest version and the issue still occurs
I am sure that this issue is about SteVe (and not about the charging station software or something unrelated to SteVe)
Specifications
SteVe Version : 3.5.0
Operating system : Debian 11
JDK : OpenJDK 17.0.4
Database : Maria DB 10.5
I checked to changelog of 3.6.0 and couldn't find a relevant fix.
Expected Behavior
According to OCPP 1.6
A reservation SHALL be terminated on the Charge Point when either (1) a transaction is started for the reserved
idTag or parent idTag and on the reserved connector or any connector when the reserved connectorId is 0, or (2)
when the time specified in expiryDate is reached, or (3) when the Charge Point or connector are set to Faulted or Unavailable.
In case we set a connector with an active reservation to Inoperative, our expectation is that on the reservation page this reservation is marked as inactive or canceled.
Actual Behavior
After setting the connector with an active reservation to Inoperative, the reservation is still displayed as active.
Steps to Reproduce the Problem
Reserve connector 1 with an id tag in the near future of a dual charging station (uses EVerest 2024.01)
Checklist
Specifications
I checked to changelog of 3.6.0 and couldn't find a relevant fix.
Expected Behavior
According to OCPP 1.6
In case we set a connector with an active reservation to Inoperative, our expectation is that on the reservation page this reservation is marked as inactive or canceled.
Actual Behavior
After setting the connector with an active reservation to Inoperative, the reservation is still displayed as active.
Steps to Reproduce the Problem
Additional context
The text was updated successfully, but these errors were encountered: