Awareness | Sennheiser TCC 2 Stops Sending Commands
Understanding a current known issue where Sennheiser TCC 2 may stop sending commands.
Information
Sennheiser and Q-SYS have identified rare cases where Third Party communication via TCP and UDP stops working after random durations (days/weeks) in some TCC 2 installations. Commands like beam angle position data and mic level stop updating until the TCC 2 is rebooted.
The root cause is under investigation, and updates will be provided as a resolution is found.
Current Workaround
If you encounter this issue, we recommend a daily reboot of the TCC 2. The API command for rebooting is available in the TCC 2 API documentation.