Skip to content
Innomesh
Room Manager

Q-Sys Interoperability

Overview

Innomesh provides comprehensive Q-Sys ecosystem monitoring capabilities through its platform. This integration addresses previously unmet needs in AV environments by providing centralised visibility into Q-Sys devices and their operations, including logs, events, vitals, peripherals, and automated configuration management.

Key Features

Q-Sys Global Logs

Aggregates logs from all Q-Sys cores in your environment with advanced filtering and querying. Supports 3 to 365 days of historical logging for troubleshooting and audit trails.

Q-Sys Global Logs

Q-Sys Global Events

Displays detected events across all Q-Sys cores, including:

  • DSP Design Status changes
  • Grandmaster Clock modifications
  • PTPv2 Offset updates
  • USB Connection Status changes
  • Certificate installations and removals

Q-Sys Global Events

Q-Sys Notifications

Live messaging alerts via Slack or Microsoft Teams for:

  • BMCA Master Clock Changes
  • PTPv1 and PTPv2 changes
  • Server configuration modifications
  • Authentication attempts (successful and failed)
  • Vital metrics anomalies

Q-Sys Global Vitals

Real-time monitoring dashboard displaying:

  • Total Q-Sys devices count
  • Faults and warnings per device
  • CPU, memory, and disk usage percentages
  • Core temperature readings
  • Device uptime metrics
  • Grandmaster Clock and PTPv2 Offset information

Q-Sys Global Vitals

Q-Sys Centric Alerts in Hotlist

Innomesh raises alerts in the Hotlist for Q-Sys specific conditions, including:

  • Peripheral health issues
  • Grandmaster clock faults
  • Core overheating
  • High CPU, memory, or storage usage

Hotlist showing Peripheral Health alerts grouped by room Innomesh release v3.4.1 — Q-Sys Interoperability — Q-Sys Centric Alerts in Hotlist

Q-Sys Core Ops

Operational actions can be triggered from the Assets Registry, including:

  • Device reboots
  • Certificate upload and deletion

Assets Registry row with Trigger Operation menu showing Add Certificate, Delete Certificate, and Reboot Q-Sys Interoperability — Assets Page > Trigger Operations

Q-Sys Peripherals

Devices connected to DSP cores that were previously unmonitored now appear in the Asset Registry. This provides visibility into the full chain of Q-Sys hardware across your environment.

QSC Q-Sys DSP Details modal on the Devices tab listing connected peripherals and status Innomesh release v3.4.1 — Q-Sys Interoperability — Q-Sys Peripherals > Assets Window

Q-Sys Asset Information

Comprehensive device details are available per Q-Sys asset, including:

  • Properties and Vitals for the individual DSP
  • Events that have occurred at the device level
  • Devices — a list of devices connected to this Q-Sys Core (these also appear in the assets list)
  • Licensing — license type and expiry date
  • Services and Multicast — network services, ports, and multicast ranges
  • Certificates loaded on the device
  • Log — detailed logs from the Q-Sys Core
  • Design Files and Support Files archives

Q-Sys Asset Information

Automated Configuration Management

Innomesh performs regular automated archiving and versioning of Q-Sys configurations. Users can:

  • View a history of design file versions.
  • Download previous design file versions.
  • Upload a previous version to restore an earlier configuration.

This capability provides a safety net for design file changes and simplifies rollback when issues arise.

Q-Sys asset detail with Design Files tab listing archived .qsys files and Download and Delete actions The Design Files list in the Q-Sys Integrations Page

Getting Started

To enable Q-Sys interoperability for your tenancy:

  1. Ensure your Q-Sys cores are network-accessible from the Innomesh monitoring infrastructure.
  2. Contact Innomate to enable the Q-Sys integration feature for your environment.
  3. Q-Sys devices will begin appearing in the Asset Registry once discovery is complete.
On this page