Space release notes version 6.10
Option for resyncing face enrollments with Orion Server New feature
In disaster-recovery scenarios, when data is lost in the Orion Server, this tool allows face enrollment data from the Space database to be retransmitted to the Orion Server.
See the section on face recognition for more information as well as the Salto Orion user guide.
Disable Salto original SAM keys Changed
When custom SAM data is defined, both types of cards can be used, cards issued with Salto original SAM keys, and cards issued with custom client SAM keys.
This functionality, enables the capacity to disable the original Salto SAM keys for Mifare Classic and DESFire cards.
See more on SAM and issuing options.
Increased size of the authentication token for webhook notifications Changed
Space accepts a larger (300 characters) authentication token for webhook notifications. See also the section on ports and connections from and to the Space service.
Keypad locks/CU include a new audit trail event indicating a blocked keypad New feature
Whenever the keypad is blocked in a keypad-equipped device (DBolt Touch, BLUEnet controller, CU 4000,…), the audit trail will include a new event indicating the blockage.
See more on blocked keypads in the General options > Access points section.
SVN-Flex: the two-lock-per-node constraint relaxed New feature
Before Space 6.10, only 2 locks per node and a maximum of 10 per gateway could be configured as SVN-Flex.
Now the Space software allows the SVN-Flex feature to be enabled on multiple BLUEnet locks.
Enabling this option means that, in a concurrency scenario, some keys may not update correctly at SVN-Flex update points.
See the section on access point settings for more information.
Support for binary images of Ultralight AES cards Changed
In use cases involving the encoding of cards in third-party encoders, Space supports requests for binary images of Ultralight AES cards through the SHIP and PMS (Industry Standard) interfaces.
It is highly important to write the pages of the card memory in the returned order.
Hitachi 2: Lift controller through RS485 protocol New feature
Hitachi Communication Protocol with third party device.
This new configuration will be applied to the CU4000 node. It does not apply to the UBOX4000.
When assigning floors, only floors (destinations) of the front door will be considered for Hitachi. Those that give access to the rear doors of the elevator will not be supported.
It should be noted that, although up to 128 destinations can be configured through Space, only the information corresponding to destination 1 to 63 will be transferred to the host due to protocol limitations.
New firmware is required.
Salto Network renaming Changed
Refined the naming of the Salto Network section to be more consistent with Salto device naming conventions.
Devices are grouped by family.
Space 6.9