What Changed in Integriti V25.1
Inner Range has released Integriti V25.1, and for facilities managers, IT managers, and integrators running High Availability access control architectures across commercial buildings, strata complexes, or multi-venue club sites, two changes in particular are worth understanding before your next maintenance window. The update introduces automatic controller load balancing for HA deployments and a redesigned Firmware Update dialog that makes version hygiene across distributed controller networks significantly more manageable. Neither change is cosmetic — both address real operational friction points that anyone maintaining a mid-to-large Integriti site will recognise immediately.
The Detail: Two Focused Improvements
According to Inner Range’s release announcement, V25.1 delivers two headline changes:
Automatic Controller Load Balancing for High Availability Architectures. HA configurations in Integriti pair redundant servers so that if the primary fails, the secondary takes over without dropping access control or alarm monitoring. The challenge with HA has always been that in practice, one server tends to carry a disproportionate processing load during normal operation — controllers connect to whatever they connected to first, and they stay there. V25.1 introduces automatic load balancing that distributes controllers more evenly across the HA pair. This feature requires firmware version 25.1.0 or later on the controllers themselves, which ties directly into the second change.
Redesigned Firmware Update Dialog. The updated interface now surfaces recommended firmware versions for connected hardware and actively flags controllers and LAN Modules that are running out-of-date firmware across the site. Rather than requiring a technician to manually cross-reference each device against a version matrix, the system presents that information in a consolidated view and identifies what needs attention.
Operational Implications for Your Site
If you operate an Integriti HA deployment, the load balancing improvement has a direct prerequisite: controller firmware must be at 25.1.0 or above before the feature activates. That means a firmware update campaign across your controllers is not optional if you want the benefit. For large sites with many controllers and LAN Modules distributed across floors, plant rooms, and car park levels, that has historically been a time-consuming and error-prone process — which is exactly why the redesigned Firmware Update dialog matters. The two features are operationally linked.
For facilities and IT managers, the practical implications worth discussing with your integrator include:
- Scheduling a firmware audit before upgrading to V25.1. The new dialog will surface version gaps, but knowing the scale of the task beforehand helps with maintenance window planning and minimises surprises.
- Understanding your HA failover behaviour during the update process. Updating controller firmware across a live HA site requires a sequenced approach to avoid simultaneous reboots that could disrupt door access or alarm transmission.
- Confirming LAN Module firmware is also in scope. The release notes specifically call out LAN Modules alongside controllers as devices the new dialog tracks. LAN Modules are often overlooked in firmware maintenance cycles because they sit quietly in the background — until they don’t.
- Reviewing controller load distribution after cutover. Once load balancing is active, monitor event processing and connection counts across both HA nodes to confirm the distribution is behaving as expected in your specific network topology.
Sites not running HA configurations will see less immediate operational impact from the load balancing feature, but the improved Firmware Update dialog is relevant to any Integriti deployment of meaningful scale. Version consistency across controllers is a security hygiene requirement, not just a performance consideration — outdated firmware can carry unpatched vulnerabilities, and in an access control system, that has direct physical security consequences.
The Mallen Perspective
From where we sit — planning, installing, and maintaining Integriti systems across NSW commercial, strata, and club sites day to day — the firmware update tooling improvement is the change we’re most immediately glad to see. Keeping controller and LAN Module firmware consistent across a site with dozens of devices has always required disciplined record-keeping on our end and careful sequencing on-site. Anything that reduces the risk of a technician missing a device, or a client site drifting into a mixed-firmware state that creates unexpected behaviour, is a genuine operational improvement. The new dialog consolidating that visibility into the software itself is the right place for it.
On the load balancing side, HA deployments are increasingly common as building owners and strata managers come to treat access control uptime with the same seriousness they apply to fire and CCTV. An HA system that quietly concentrates load on one node isn’t fully delivering on its resilience promise. Automatic balancing closes that gap — provided the firmware prerequisite is met, which reinforces the point that firmware maintenance isn’t a background task to defer indefinitely. If your Integriti site is running HA and you haven’t had a firmware review in the past twelve months, this release is a reasonable prompt to schedule one.
Original source: https://www.innerrange.com/post/integriti-v25-1-smarter-load-balancing-and-streamlined-firmware-updates