Couple things to know -
First of all, the feedback from the QSC crestron modules is very unreliable outside of the first second or so of the poll join going high.? I basically do one stepper at program start, triggered by the DSP initialized feedback, to poll each module for 1 second just to pull all the volume and mute status modules one time.? After that, I pretty much take for granted that QSC will never give crestron reliable feedback for any change that didn't originate from within the crestron side of the module.? If you are going to be using snapshots to make changes to controls affected by crestron, you're going to have to similarly use a stepper to re-poll feedback for every affected module.? You MIGHT be able to get away with using a button presser, but I've run into errors if I try to poll more than 5 or 6 modules with the same rising edge. Generally, I just do all my "presets" in crestron using ARAM instead of using snapshots in QSC, other than for things like camera position, which Crestron doesn't need feedback on.
?
Second of all, the 5.0 button module's toggle is bugged because it works off a one shot instead of a logic wave pulse.? This can lead to the "toggle" being held high through several logic waves on faster processors, leading to it toggling itself on and off and on again several times in a single press.? I recommend using the 5.2 modules, as they address this issue.
?
Third of all, I've experienced random disconnects from QSC cores running firmware 9.6 or higher when using the 5.0 modules.? Upgrading to the 5.2 modules alleviated this issue.? I know you didn't report this issue, but it took me so long to get that figured out I figured I might throw it in for free.
