Known Issues | Q-SYS Connect v.10.5
Learn about the Known Issues associated with Q-SYS Connect v.10.5.
Compromised or errant system / device status shown in Q-SYS Reflect.
Issue: When using Q-SYS Connect 10.3 with RMS 1.0.2, users may see incorrect system or device status in Q-SYS Reflect.
Workaround: None. This will be fixed in a future release.
Earliest Reported Version: Q-SYS Connect 10.3
Version Fixed: This issue will be resolved with a dedicated release for RMS.
Q-SYS Connect Certificate Configuration Incorrectly Displays Reboot Required Message
Issue: When modifying certificates on a Q-SYS Connect device, the UI incorrectly indicates that a full device reboot is required. A full reboot is not actually necessary for Q-SYS Connect certificate configuration, and only a refresh of the Peripheral Manager (QPM) application is needed.
Workaround: Ignore the reboot prompt displayed in the UI. Instead of performing a full device reboot, refresh the Peripheral Manager (QPM) application to apply the certificate changes.
Earliest Reported Version: Q-SYS Connect 10.3
Version Fixed: This issue will be fixed in a future release.
Q-SYS Connect cannot connect to a Core through LAN B
Issue: In a dual-network configuration, Q-SYS Connect cannot establish a stable connection to a Core through LAN B. When the Core’s LAN A port is connected to one network and LAN B is connected to a separate network, selecting a computer network interface on the same network as LAN B causes Q-SYS Connect to briefly display “Initializing” without successfully connecting.
Workaround: Connect Q-SYS Connect to the Core through LAN A instead of LAN B.
Earliest Reported Version: Q-SYS Connect v10.3
Version Fixed: This issue is under investigation.