5.08.0001
Released 2025-02-17
Important: For the best reader functionality, including improved EM reading, support for MIFARE DESFire EV3 and stability improvements, updating the VAKA readers' software is recommended. Read more, and download the update in the Reader section here .
- Updating must be carried out by an installer with knowledge of the particular VAKA system.
- Updates must be made on site.
- Before updating to a new VAKA version, it is important to ensure compatibility with integrated third-party solutions * . Examples of such solutions are Renz mail boxes and Amido Alliera. To avoid operational disturbances, check with respective party that applicable versions are compatible.- Before updating, ensure that system security is set to the default level (Settings->System->Security).
- After updating, it can take up to 45 minutes before the system is fully operational.
* For VAPI integrations with third-party systems, note that VAKA 5.08 requires at least VAPI 5.0.8.
What is new?
VAKA Admin
- Added support for access profiles with door groups and profile schedules for offline doors*. This provides simple and intuitive management of varying access rights. Read more here.
- Added support for access events, as well as battery status for offline doors*.
- Improved tooltip support.
*Requires update readers to be updated with reader package 2025-02-14.
Alarm
- Fixed an issue where motor locks, configured to be unlocked, were not automatically unlocked after alarm arming and disarming. The problem occurred when the arming and disarming were made close together in time.
Java/PC client
- Fixed issue with installer logged in mode not being restored after update.
- Added support for empty fields when importing. Default values are used for empty fields.
- Updated code signing certificate.
Other
- Security- and stability fixes
Compatibility
VAKA Admin
VAKA Admin is verified to work with at least these browser versions:
- Apple Safari: 15.6.1
- Google Chrome: 118.0.5993.71
- Microsoft Edge: 117.0.2045.60
- Mozilla Firefox: 118.0.2
Java/PC-client
The Java/PC client has been verified to work with at least these versions:
- JRE 8: Eclipse Adoptium openjdk 1.8.0.272.
- JRE 11: openjdk 11.0.20.1
- Webstart alternative (JNLP File): OpenWebStart 1.8.0.
Update information
Before updating to VAKA 5.08, the system must be at least version 3.86, 3.87 or 3.88. In case the system is in older version, follow previous update instructions to upgrade to any of the 3.8 versions.
For questions and for help with updating, please contact technical support, +46 (0)8-722 34 40, button selection 2 or [email protected].
After upgrade, the following versions apply
| Product | Version | Showed in |
|---|---|---|
| B60/VAKA Admin | 5.08.0001 | The System Diagnostics/About dialog box |
| B05, B06, B15, B16, B17, B17-R, B25, B26, B27, B27-R | 5.08.0001 | System diagnostics |
| B28, B18 | 5.08.0001 | System diagnostics |
| PC-client | 5.08.01 | VAKA window |
| Info- and booking panel | 5.08.0001 | Configuration menu in panel |
Update from VAKA version 4 and newer
To do before updating
Configure system security
Ensure that the system security is set to the default level (Settings->System->Security).
Create a backup of system data
Back up system data by following the instructions, in the JAVA/PC client, at Settings -> Backup .
Back up relevant events
In the JAVA client, filter out relevant events and export them to a CSV file.
Open port 443
After the update, some communication will take place via HTTPS. Therefore port 443 must be open where system parts communicate between network segments and where connection for remote administration is needed.
If there is at least one B60 in the system
Restart all B60s by:
- From Main Menu in B60, navigate to Tools and press return.
- Navigate to Restart Device and press return.
update
Follow the instructions for Manual update with the package vaka-mini-5.08.0001.vfp .
To do after update
Firmware update reader
Update offline lock/SimonsVoss update reader with reader package 2025-02-14 .
Firmware A56
A56 readers in the system should have at least firmware-t1.06.06r.vfp. Update if needed.
Uppdate from 3.86, 3.87 or 3.88
To do before updating
Configure system security
Ensure that the system security is set to the default level (Settings->System->Security).
Create a backup of system data
Back up system data by following the instructions, in the JAVA/PC client, at Settings -> Backup .
Back up relevant events
In the JAVA client, filter out relevant events and export them to a CSV file.
Open port 443
After the update, some communication will take place via HTTPS. Therefore port 443 must be open where system parts communicate between network segments and where connection for remote administration is needed.
If there is at least one B60 in the system
Restart all B60s by:
- From Main Menu in B60, navigate to Tools and press return.
- Navigate to Restart Device and press return.
Update
System without B60
Follow the instructions for Manual update with the package vaka-mini-5.08.0001.vfp
System with B60
Follow the instructions for Manual update with the package vaka-maxi-5.08.0001.vfp .
To do after update
Set country- and area code
To prepare for future features, the Country Code and Area Code for the intercom need to be entered upon first login after update. This is done in the dialog that is presented.
Associate email address with migrated administrators and installers
When updating to VAKA 4, or later, previous administrators and installers are migrated to users/persons with roles (and rights) to interact with VAKA. Theese users should be given valid e-mail addresses. Please note that, when an e-mail address is specified, this is used as the username when logging into VAKA.
Change playlists from HTTP to HTTPS
If there are playlists where HTTP is used, these must be changed to HTTPS.
Firmware A56
A56 readers in the system should have at least firmware-t1.06.06r.vfp. Update if needed.
Firmware update reader
Update offline lock/SimonsVoss update reader with reader package 2025-02-14 .