...
Fixed an issue where locks were not selected when editing access restrictions in Link
Extended the refresh token lifetime to 6 months
1.2.
...
Fixed an issue where the UKEY2 section was displayed despite the license being disabled on the server
1.2.328
Added session_id processing in device status messages via mqtt
328
Enhanced device connectivity detection to ensure the server displays only the current online status, ignoring outdated offline notifications.
1.2.327
Fixed an issue where monitors removed from a group continued to be displayed in the mobile API
Added support for AV-04SDI and AV-04FDI panels
...
1.2.324
Added the ability to switch seamlessly navigate between user settings profiles and identifiersFixed an issue where the UKEY2 association with the user was not removed correctlytheir linked identifiers for easier management in Link.
1.2.322
Updated rules for user roles
...
Fixed an issue with incorrectly counting the number of used licenses in linked users
Added user association in SCUD ACS logs and device logs in Link when opening a lock from the Link app
...
Fixed an issue where identifiers were not added to the BI-08FB2M panel
Fixed an issue where json: could not unmarshal array into Go struct field DeviceSettings.mqtt of type models.DeviceMqttSettingsthe Save Settings button did not function when attempting to change the device model.
Fixed an issue where device and SIP client data disappeared from the device broker and SIP proxy containers after launching the containers from a different directory
...
Added a section for booking rooms and controlling access to them
Added support for ukey2 in the Link serverAdded authorization for the mobile SDK on the server
Fixed an issue with requestor handling, changing it from "API" to "api" key
1.2.299
...
Fixed an issue where accounts without users occupied emails and were not migrated
Fixed an issue where the forwarding rule did not work if the monitor's virtual number or a number not linked to an entity was specified in the forwarding settings
Fixed an issue where endpoints /mobile-client/ did not match the specification
...