If you extend a reservation in Birrdi but your Uneekor system still shuts down at the original end time, this is a known limitation on Uneekor’s side.
What’s happening
When a reservation is extended in Birrdi:
Birrdi does not send an “end session” command at the original end time
However, Uneekor stores the original start and end time locally
Uneekor is not aware that the reservation was extended
Because of this, Uneekor will still shut down the session based on the original booking time.
Status
We’ve confirmed with Uneekor that this is a bug in their implementation.
Uneekor is aware of the issue
A fix is included in version 3.1 (currently in alpha)
There is no confirmed timeline for when this will be available
What you should do
We recommend reaching out to Uneekor support directly and asking:
When version 3.1 will be released
If there is a version you can upgrade to now that includes this fix
Summary
This is not a Birrdi issue. Uneekor is currently not syncing updated reservation lengths after a booking is extended, which causes sessions to end early.