> For the complete documentation index, see [llms.txt](https://releases.holoplot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://releases.holoplot.com/august-2026/holoplot-os-2.5.2.md).

# HOLOPLOT OS 2.6.2

We're excited to announce **HOLOPLOT OS 2.6.2**. This major release introduces Macros and several performance and stability improvements to HOLOPLOT OS.

{% hint style="info" %}
The Public System API has been updated to **v1.6.0**.
{% endhint %}

***

### What's New

#### New Macros functionality in HOLOPLOT Control

[Macros](https://docs.holoplot.com/holoplot-control/operating-the-system/managing-and-operating-macros) let operators safely adjust venue areas, such as front fills or under-balconies, using section-level gain and EQ controls rather than beam-level tuning. Changes are range-limited, non-destructive, snapshot-ready, and reversible.

***

### Improvements and bug fixes

#### HOLOPLOT Control

* Performance improvements for batch operations in tuning and pairing.
* Fixed an issue that caused the active preset not to be displayed correctly after canceling a preset change.
* Fixed the Module count in the Pairing view. Only online modules are considered available for pairing.
* Modules in the UNSET state (due to a severe hardware issue) are no longer displayed in the Pairing view.
* Fix for metering stall caused by a slow or non-responsive (browser) client blocking all other metering consumers.
* Fix for HOLOPLOT Control displaying an invalid value in the System Gain Input field.
* Various improvements to increase connection robustness and speed up recovery of HOLOPLOT Control (UI).

#### System Backend

* Improved the reliability of module status reporting, including the Module Configuration Health Check.
* Improved the mechanism for reporting Analog Mode’s status (for X2 modules).
* Added additional Cloud telemetry to increase observability of the communication interface for the Powersoft amplifiers.
* Updated NATS server for improved stability and memory management of the HOLOPLOT-internal communication layer.
* Changed k3s systemd configuration to mitigate Kubernetes runtime crash (by preventing all service containers from being killed when the main process exits).
* Fix for Kubernetes software defect (so-called “nil-pointer panic”) in the Kubernetes embedded distributed registry (Spegel).
* Improved Controller hardware health monitoring to prevent false fan and PSU health alerts caused by transient iDRAC reporting issues.
* Minor timing improvement for the download step of the device software update procedure.

#### HOLOPLOT Processor

* Improved audio stream recovery to maintain consistent latency after CPU overload events.
* Fixed an issue that prevented automatic failover events from being recorded correctly in the Event Log.
* Improved Processor hardware health monitoring to prevent false fan and PSU health alerts caused by transient iDRAC reporting issues.
* Fixed an issue that led to CPU overruns following network disconnects
* Processor Failover toasts are no longer duplicated.
* Fixed a processor watchdog service bug that caused erroneous Processor failovers.
* Save Audio-Bridge configuration atomically to prevent data loss on unexpected shutdown.
* Fix for concurrency defect caused by RTSP/mDNS announcements in the Audio Bridge software.

***

### Known Issues

The following issues are known and will be addressed in an upcoming release.

1. **Control link temporarily reported as "Unknown" after a network disconnect**

   When the active control network connection (primary or secondary) to an audio module is disconnected, the module may temporarily (up to 60 seconds) report its control link state as "Unknown" until it re-establishes communication over the secondary control network link. During this transition, the connection between HOLOPLOT Control and the module may be interrupted.

   *Audio playback continues uninterrupted.*
2. **Inconsistent pairing and power status display**

   In rare cases, the Devices and Module Pairing pages in HOLOPLOT Control may display inconsistent module pairing and power status — showing modules as unpaired and sleeping while they are actually offline or removed.
3. **HOLOPLOT Control temporarily unresponsive**\
   Rebooting or power cycling a Controller can cause HOLOPLOT Control (UI) to become temporarily unresponsive (ca. 2 - 4 minutes). The Controller cluster will automatically recover and continue to work with two out of three nodes.