Release Notes for Latest Version

Estate Manager version 3.6.5.3 Release notes

New Features

  • MUI updated to use Angular 13 (Significant update).
  • Changed to Luxon for UI time handling (the old library was deprecated and no longer supported).
  • Updated installer to use net462 which is now the lowest Microsoft supported .net.
  • Multi-unit alignment (Requires Vector firmware >= 152).
  • Added support for BACnet network number configuration.
  • DB migration, removing SQL server specific geo-spacial types.
  • New user role between SystemAdmin and Admin: SystemManager.
  • Moved all services apart from the main EM service over to .NET 6 (Significant update).
  • Ask for confirmation before clearing the pathmap.
  • Tweaks to ‘Counts’ page to make it more obvious that data is loading in the background.

Bug Fixes

  • Modify CSP to fix problems in safari.
  • Fixed issue with changing your own user details.
  • Fixed issue with pathmap buttons.
  • Fixed issue with culling deleted devices if they had a device with node recordings
  • Fixed BACnet settings being cached between devices incorrectly.
  • Fixed Activity page caching between devices.
  • Fixed rare crash when moving between online and offline mode on a device.
  • Fixed map markers sometimes not showing the correct state when multiple devices share the same location.
  • Fixed initial map marker clustering.

 

Estate Manager version 3.4.0.07 Release notes

New Features

  • Moved website to .NET 6
  • Added device watchdog suppression when viewing a device in live view to assist with debugging device issues.
  • Added support for formatting Vector SD cards.
  • Added support for Open ID Connect.
  • Improved performance of adding user rights to address book groups.

Bug Fixes

  • Fixed crash on global recordings page when there is no thumbnail for a video
  • Removed credentials from MQTT and HTTP Post settings get REST calls to prevent potential leaking of sensitive information.
  • Fixed issue where deleting a schedule could lock up the database for an extended period of time.
  • Fixed memory leak on the diagnostics bridge.
  • Fixed issue with tooltips sometimes showing data for a different device when the device had been selected from the search box.
  • Fixed UI crash on video recordings when there was something wrong with a node recording.

 

Estate Manager version 3.2.0.20 Release notes

New Features

  • Support for Vector 'Authenticated Communications'.
  • Estate Manager outbound connections support for vector authenticated communications.
  • Web backend upgraded to .NET Core 3.1 (external link)
  • Maps now center, showing all devices with a registered location.
  • Added support for on device Vector SSL certificate validation (requires relevant firmware).
  • Improved overall speed of connecting to devices (mainly Vectors).
  • Added warnings to the diagnostics page to say if the data in Estate Manager is out of sync with the Vector device (usually happens on SD card format / replacement).
  • Added support for removing all the data for a Vector device from EM while it is still connected (useful when an SD card has been formatted / replaced on Vectors).
  • Add REST API to allow task launcher tasks to be scheduled.
  • Expanded REST API to expose video scheduling capabilities.
  • Various security-based improvements.
  • Account lockout when there have been several incorrect login attempts.
  • Added capability to also validate Vector node devices.
  • Added capability to validate up to 6 registers at the same time.
  • Performance improvements for validations.
  • Estate Manager 'Outbound Connections' can now be set by Admin type user logins.

Bug Fixes

  • The health page's last activity was not correctly adjusted to the browser's time zone.
  • Rare incorrect finish time on schedules on distributed systems when a schedule finishes very quickly.
  • Some REST API calls did not return the correct HTTP code for errors.
  • Column sorting on group pages did not persist.
  • Sometimes, video downloads could be marked as complete when they weren't.
  • Fixed issues with the recording dialog on group pages.
  • Issue connecting back to a device after reboot in the task launcher service.
  • In rare circumstances, the RIFT service could trigger high CPU usage when going into live view.
  • Crash on the 'Wide Tracker' tab when there are other devices on the network with certain register configurations.
  • Relay de-bounce settings could become corrupt on Gazelle devices.
  • Relay setup tab labelling was incorrect on Vector devices.
  • Various small relay page fixes.
  • Traceroute graphs and table incorrect times.
  • Issues with Vector Register Height Filtering.
  • Vector Height Filters could be created with a height of 0.
  • Components of the Vectors 'Occupancy' register types could have names too long for the device (Analytic only function).
  • Save button could disappear if the browser window was a certain size.
  • Allow the Fine Motion Room Sensor PIR to be correctly used with the 'Occupancy' register types (Analytic only function).
  • Registers without a visual element could lock up a Validation session.
  • Count Mode labels were inconsistent with documentation.
  • Some register types weren't being identified correctly in Validations.
  • Various small UI bugs.

 

Estate Manager version 3.0.1.114 Change notes

New Features

  • Support for new products & Vector features – BACnet, Wireless Fine Motion Room Sensor PIR, MQTT Event streaming.
  • Performance Improvements – Data culling.

Bug Fixes

  • Address book fix
  • Yaw angle support fix,
  • Count graph fix,
  • Count schedule fix.
     

Estate Manager version 3.0.1.73 Change notes

Various minor performance improvements & bug fixes.


Estate Manager version 3.0.1.67 Change notes

New Features

  • Redesign of front end. Now consistent with standalone RIFT exe setup software, and Vector onboard web-based setup software.
  • Fully compatible with all new Vector Register types, MQTT options and HTTP Push options.
  • All device settings are exposed, including master/node (Wide Tracker) configuration, IP, and outbound connection settings. Note, take care when changing any of these settings.
  • Various bug fixes.
  • Backwardly compatible with Gazelle and 3000 series devices (3000 series minimum fw version 486 required).