Reservation: set all connectors to 'reserved' when there are as many 'global' reservations as there are free evse's #958
Comments
This was referenced Nov 27, 2024
maaikez
added a commit
that referenced
this issue
Dec 16, 2024
Reservation: When a global / non evse specific / evse connector 0 reservation is made and there are as many reservations as available evse's, the evse's should go to 'reserved'. Also some python tests for reservation are created. Signed-off-by: Maaike Zijderveld, iolar <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If there are three free evse's and a third reservation for a non-specific evse is made, all free evse's should go to reserved. This currently does not happen.
If there are as many free evse's as reservations for non-specific evse's and all connectors are set to reserved, as soon as one evse comes available, all connectors should go back to 'available'.
EVerest Domain
Authorization, Other
Affected EVerest Module
Auth
EVSE Manager
To Reproduce
No response
Anything else?
The ReservationHandler can keep track of this and send 'reserved' to the EVSEManager. However, currently that interface requires a reservation id, so there must be made some changes in that interface as well. Because we can not provide the reservation id, because one reservation is not tight to a specific evse or connector.
The text was updated successfully, but these errors were encountered: